I came across this just the other day. The results were interesting.

NetBackup seems to have decided to follow the schuedule and perform
cumulative incremental backups, with a twist. This incremental had no full
backup to look back to, so it seems to have assumed the full was 'empty' and
proceeded to back up the entire system every night for the rest of the week
until the schedule full came along.

Normally here, when I add a system to the backups it's before the machine
goes into production so I do a manual full backup immediatly to ensure I
have a good baseline until the retention expires. This came up, in my case,
because I renamed some clients in the NetBackup interface, and NetBackup
seemed to do the equivalent of a delete/add.

Jason

> Does anyone know if Netbackup treats the first backup for a 
> client as a
> full backup no matter what the class schedule says?  As an 
> example, if I
> add a new NT client to a class during the day and his schedule says to
> do a cumulative-diff for that night, will Netbackup know that this
> client has not been backed up before and actually do a full backup
> instead of the cumulative-diff backup?  Thanks!