This looks more like the date on the VS itself is wrong. Note that the date is
November 2nd Last year. Clocks should be in sync between client and server.
I'm unsure why it's not simply a case of picking up on the archive bit, but get
the clocks synched and see what the results are then.
Only time I've seen problems like this was after Y2K testing when clients had
files dated 2007 and were looking for anything newer than 2001. They'd back up
every time.
Cheers,
Stuart.
________________________________
From: EMC NetWorker discussion on behalf of Barton
Sent: Wed 30/05/2007 05:35
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Incremental Backup issue on Windows Virtual Server
Hi,
Anybody seen this one before? After a successful full backup of a saveset on a
VS, subsequent incremental backups do not use the correct full backup date
(causing huge incremental backups....) Here is an example -
May 27 05:52:51 rizzo root: [ID 702911 daemon.notice] fsmavs02: S:\
level=full, 178 GB 03:56:52 406120 files
May 28 05:30:50 rizzo root: [ID 702911 daemon.notice] fsmavs02: S:\
level=incr, 177 GB 03:34:22 400860 files
Here is what a "probe" says -
# savegrp -p -c fsmavs02
fsmavs02:Probe level=full, pool=Windows, save as of Wed May 30
11:45:43 GMT+0930 2007
fsmavs02:S:\ level=incr, pool=Windows, save as of Thu Nov 2
01:59:52 GMT+1030 2006
fsmavs02:index level=9, pool=Windows, save as of Sun May 27
05:52:29 GMT+0930 2007
(ie it appears the incremental is backing up to Nov 2!!)
I'm guessing Networker is finding the last full backup of this vs on a
different physical server (there are only 2 physical servers in this particular
cluster) Are there any known issues with Networker when virtual servers
failover to different physical servers? (my knowledge ot this product is rather
limited...)
We are using Networker 7.3.2 , server is Solaris 10. System times and dates are
correct and synced on server and all clients.
We have many other incremental backups across unix and windows using this
server and there are no problems, this issue only occurs on virtual servers.
Any suggestions and ideas appreciatively received! Thanks
+----------------------------------------------------------------------
|This was sent by dbarton AT fsma.com DOT au 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
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
|