cancel
Showing results for 
Search instead for 
Did you mean: 

Incr running as a full

NolanE
Level 4
Partner Accredited Certified

Hi All,

 

I have installed a new LTO4 library on my system replacing an old LTO2 device,

 

After the installation some of the backups keep on running full backups even thou it suppose to run incr. I ran a full backup of the client and ran the incr again and still it is running full.

 

I run NBU 6.5 on win 2003 and the client is a file server also with Win 2003

1 ACCEPTED SOLUTION

Accepted Solutions

NolanE
Level 4
Partner Accredited Certified

I got the backups to run as incremental again, i had to delete the schedule from the policy and recreate it and it is running correctly now.

View solution in original post

13 REPLIES 13

Andy_Welburn
Level 6

Just for one client?

I presume it is a policy that worked previously?

 

Searching for "incrementals run as fulls" on the KB & filtering down to NetBackup results in at least 12 different TechNotes for this or similar issues - maybe worth a look through see if any are appropriate?

Yasuhisa_Ishika
Level 6
Partner Accredited Certified

How do you configured about the client properties below?

  • Incrementals based on archive bit  or Incrementals based on timestamp
  • Time Overlap

Which type of incrementals did you run?

Do the target files have future modification time?

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Stupid question, but this has been the cause of many similar problems -

Do you have Full and Incr schedules as part of the SAME policy?

Can you verify when last a full backup for this particular policy ran?

Stumpr2
Level 6

We relly need more information to help you on this. Can you provide some details?

mph999
Level 6
Employee Accredited

Hmmm ...

 

"ran a full backup of the client and ran the incr again"

How much time did you leave between the full finishing and then running the incr ?

Leave it for 15-20 mins and then try running the incr.

 

Martin

Nicolai
Moderator
Moderator
Partner    VIP   

Have you TIR enabled and  DFSR folder in the file list path ?

http://www.mass.dk/netbackup/quick-hints/79-netbackup-dfs-r-backup-always-full-with-tir-enabled.html

NolanE
Level 4
Partner Accredited Certified

Here is how it is.

I have 2 policies for the same client one is a daily (Incr-Diff) the other policy is a weekly (Full).

I ran the first night the weekly policy and the next day a ran the daily and the daily policy and it ran as a full.

there was nothing changed on the policies only a new backup device.

Thanks

Andy_Welburn
Level 6

"...

Stupid question, but this has been the cause of many similar problems -

Do you have Full and Incr schedules as part of the SAME policy?

..."

 

They need to be in the same policy.

NolanE
Level 4
Partner Accredited Certified

No, like i said one policy is the daily and another is the weekly 2 policies with the same client.

I have checked the Archive bit settings on the server and the client and all is correct.

it was working before and nothing changed on the policies only a new library.

Andy_Welburn
Level 6

This is the point we are trying to make:

DOCUMENTATION: The cumulative incremental backups consistently run as full backups.
http://www.symantec.com/business/support/index?page=content&id=TECH66214

I also understand what you're saying in that this only happened following installation of a new library - I cannot offer any insight here as I cannot see how this could, in any way, affect how a policy behaves.

NolanE
Level 4
Partner Accredited Certified

I got the backups to run as incremental again, i had to delete the schedule from the policy and recreate it and it is running correctly now.

Andy_Welburn
Level 6

Unfortunately that sometimes is the only recourse.

Some "corruption" in the policy can mean that even copying to a new policy will transfer the "corruption" also.

Daryl_Kinnaird
Level 4

The first backup ran for a client in a policy will always be a full backup even if you scheduel is an Incr.  I would bet if you ran the Incr again the following day or a little later it would have worked, with out having to delete and re-add the scheduel.