incremental backup run as full

[Andreas_Holmstr]

We upgraded to 6.5 MP2 yesterday, and we experienced a quite strange thing today....

This morning’s incremental backup on one server was running a bit long. After a few hours we began to investigate and notice that some smaller file system on the servers image which was completed were as big as the file system. So it seems that the Incremental backup ran as a Full backup, even though the information on the image tell us it is a incremental... 

Have anyone else experienced something similar?

I know there has been some bug’s in the MP2 regarding the scheduler, not being able to run any jobs from the policies, but we haven’t experienced any problems with that yet.

The backup environment is running on Windows 2003 server, 64bit Intel processors.

 Andreas


Message Edited by Andreas Holmström on 06-12-2008 11:37 AM

[Darren_Dunham]

Are the clients also 2003?

Does your policy use TIR?

There used to be several technotes about incrs running as a full, but several of the ones that pop up in the search appear to be unavailable.  I'm not sure why.

e.g.
http://seer.entsupport.symantec.com/docs/290012.htm

--
Darren

[Andreas_Holmstr]

Yes, the client we experience the problem on also runs w2k3, so the ticket you Darren posted does not cover our problem, but thanks anyway.
The strange thing is that it was five days ago since we made the Full backup and the previous inc's were run as inc's.
Even more strange is that today's inc run as an inc's..... 

[Andreas_Holmstr]

My error, 3 out of 5 images were successful yesterday, two were canceled(the big once). This mornings incs were run on the changes from last days inc because the two big images were not complete yesterday these two were run as a "Full backup" today. Even though we can restore files from the previous full backup...  

[CRZ]

Are the backups multistreamed, by chance?  It sounds like you're experiencing the behaviour covered in this TechNote:

DOCUMENTATION: After applying the NetBackup 6.5.2 release update, the first incremental backup run for each multistreamed policy on each client will run as if they were full backups.

 http://support.veritas.com/docs/304269

[aktrout]

We had the same exact thing happen to us. See this:

http://support.veritas.com/docs/304269

Basically, if you have policies that are using Mutliple Streams and you upgrade to 6.5.2 then it runs a full backup after the upgrade, or at least the first time the incremental job runs it runs as a Full Backup.

Argh

[Andreas_Holmstr]

Thank you CRZ and aktrout for finding the problem.

//andreas