09-30-2010 06:42 AM
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
Solved! Go to Solution.
10-05-2010 10:26 PM
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.
09-30-2010 07:17 AM
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?
09-30-2010 07:27 AM
How do you configured about the client properties below?
Which type of incrementals did you run?
Do the target files have future modification time?
09-30-2010 08:14 AM
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?
09-30-2010 12:09 PM
We relly need more information to help you on this. Can you provide some details?
09-30-2010 03:33 PM
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
09-30-2010 09:57 PM
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
09-30-2010 11:51 PM
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
09-30-2010 11:59 PM
"...
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.
10-01-2010 12:58 AM
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.
10-01-2010 01:11 AM
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.
10-05-2010 10:26 PM
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.
10-10-2010 05:23 AM
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.
10-12-2010 08:09 AM
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.