What I've noticed is that sometimes the networker agent gets confused about the 
expected size of a file during a backup.  What I mean by this is that in my 
shop we have a lot of backups where we mount a "copy" of the file systems onto 
a backup server for the purposes of backing up a very large client database.  
So, the "copy" is mounted as read only and we perform a backup.  We will on 
occasion start seeing the shrunk/grew messages while backing up these read only 
file systems.  Obviously, since they are mounted read only and only networker 
processes accessing the file systems the files are not shrinking or growing 
during the backup.  We will sometimes see these messages for up to a week at a 
time, and then they go away.  I have confirmed that the actual amount of data 
backed up is correct.  I've also noticed that the prior to backup size was 
identical in the shrunk/grew messages, when in fact the files involved where 
very much different.  This indicates that  "prior size" i!
 s getting corrupted somehow.

Why this happens, who knows?  I have not opened an issue with EMC on this 
issue.  

hth,
Jim



> Hi,
> 
> I checked the listing and didn't see any previous posts that
> specifically addressed this question.
> 
> In the savegroup completion notifications, I sometimes see messages
> regarding a file that changed, shrunk or grew during save. Log files
> will, of course, do this, and I know I can create a directive to
> suppress those warnings, but my question is:
> 
> 1. When does NetWorker report 'shrunk or grew' versus changed?
> 
> 2. Does it look at the size of the file before backing it up and then
> check the size again after the file has been backed up to decide if to
> report 'shrunk' or 'grew'? What will cause 'changed' as opposed to
> 'shrunk or grew'?
> 
> NOTE: We are using NMO with Oracle, but I do not see any of these
> messages on those notifications. These messages occur on other
> non-oracle stuff, but not most of the time, just once in a while.
> 
> My assumption is that any such files will be captured again on
> subsequent incrementals, and there's always going to be some files that
> will change during the backups - that's obvious - but the wording:
> 'changed' versus 'shrunk or 'grew' confuses me?
> 
> Thanks.
> 
> George 


+----------------------------------------------------------------------
|This was sent by japgar AT cablevision DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER