Hello this is just a guess. 
 
If you have netbackup set to use the archive bit for the check for a new 
backup, then it might be that the archive is not reset by the full backup. 
Maybe the job does not have update auth on the CIFS network drive. 
If so, you might change netbackup to use timestamps and not the archive bit. 
 
len

________________________________

From: veritas-bu-bounces at mailman.eng.auburn.edu [mailto:veritas-bu-bounces 
at mailman.eng.auburn.edu] On Behalf Of Veritas Netbackup
Sent: Wednesday, August 16, 2006 3:00 PM
To: veritas-bu at mailman.eng.auburn.edu
Cc: biju.krishnan at 3i-infotech.com; sysadmin-oprs at icicibank.com
Subject: [Veritas-bu] What is cumulative incremental???


We backup a CIFS network drive, which stores scanned images on a windows 
machine, to which it is mapped.

Since Images are'nt modified they are just read. The application team claims 
that the drive gets updated with 4 GB of data everyday.

We have used a cumulative Incremental backup type and it is observed that

SUN -> Full backup -> 120 GB

Mon -> cumulative incremental backup -> 74 GB

Tue -> cumulative incremental 76 GB

Why is the backup so huge when we have specified only cumulative incremental?? 
The backup size shd have been approx 8 GB by TUE.

Another question is whether we can identfiy images about to expire on a 
particular day??? I need to identify images which have'nt been vaulted and 
which are nearing expiry.

Regards,
PP BIJU KRISHNAN



-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20060816/a75ecf4b/attachment.html