Video Screencast Help

Cumulative Job taking a long time

Created: 16 Apr 2013 | 4 comments

Hi all,

Never had an issue like this..

My weekend full backup completed fine so last nights cumulative-incremental should only take an hour or so yet for some reason the job is estimated to be 50% the size of the full backup.

Something isn't right as not much data changes on a daily basis and the cumulative-incremental job normally takes between 1-2 hours.

Any ideas?

Thanks.

Operating Systems:

Comments 4 CommentsJump to latest comment

Marianne's picture

The job estimate is based on a previous similar backup and is in no way a true reflection of actual backup size.

For Windows clients, you may want to read up about "Archive Bit" or "Date Stamp" incrementals.
Best to run about one week with default Archive bit, and change it the next week to date stamp.

Please bear in mind that 'walking the filesystem' on a large volume with lots of folders and files and heavy fragmentation will take a long time... Nothing much that can be done from NBU point of view.

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

markdavies1978's picture

Thanks for the reply Marianne, just seems odd that this policy has been working fine for the last few years then suddenly this has happened.

Jaykullar's picture

Have you checked the backup selection and if it has increased in size, or any new data created or changed? Check the over all time and compare backup sizes, also compare backup speed.

Marianne's picture

If anything in Backup Selection has changed after a Full backup has completed, it could result in Incremental backup running as Full.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links