07-12-2013 11:59 AM
Hi ,
On multiple servers, even though this is not the first backup, at times, the NBU considers the backup as the first backup and backs up the complete data on the server. This is irrespective of whether it is a full / incremental backup. During this backup, even accelerator also will be considering this as the first job.
Has anyone noticed this issue?
I have noticed this on two entirely backup environments.
1st ENV:
====
Master/media: Netbackup applaince 5220 2.5.2
Client: 7.5.0.6
====
2nd ENV:
===
Master: RHEL NBU 7.5.0.6
Media: Netbackup applaince 5220 2.5.2
Client: 7.5.0.6
===
07-12-2013 12:55 PM
Are you running the same policy with different schedules or different policies?
Do backups end with status 0 or status 1?
07-12-2013 01:42 PM
1 policy with 2 schedules - Incrementals on weekdays and Full on weekend.
The jobs ends with 0.
07-25-2013 12:21 AM
I'm seeing a similar issue with a couple of large remote clients
Master/media: Netbackup applaince 5220 2.5.2
Client: 7.5.0.5
A full backup completes, then the incremental backs up much more then we'd expect and equals the full in size and time.
07-25-2013 12:44 AM
For normal incremental backups NetBackup takes last full back as a reference point to determine files to backup in an incremental backup.
NetBackup is sensitive to atime, ctime and mtime if anything is changing around here on the source filesystem, incremental backups can end up backing up entire data.
This technote covers NetBackup behaviour: