I'm trying to figure out why it is taking so long to back up a Windows
2008R2 64-bit VM we have. It is running the 7.6.1 client currently...I
will be updating it to the 7.6.2 client when possible. It is backing up
to a 7.6.2 server running on Linux.
The client is behind a Netscreen firewall, but ports 7937-9936 are
currently permitted in both directions (we will close this up later, but
we don't want to change it while we are just trying to get this to
work), plus portmapper from client to server (it is not running on client).
The client is a VM on an ESXi 5.0 host, but is being backed up as a
"normal" client currently, and is the only VM on that host (so no
contention). The client is also running VMware vCenter (for a different
VMware cluster, not the one it is running on).
What is happening is that it takes a very long time for it to start
sending data after initiating each save command. After it finally does
start.
For instance, I've started a new session. All the connections seem to
get created fine. The server tells it to back up the appropriate volumes
("All" is selected). The server sees the "save" session for the first
one (VSS SYSTEM FILESET:\ is first) - but not a single byte was
transferred after that for 10 minutes, and then it starts streaming.
After it is done, it took about 2 minutes before even the next "save"
command started on the client. Then it seemed to do "VSS OTHER:\" in a
matter of seconds, and now "VSS USER DATA:\" has started - but again, no
data was passing over the network at all at the moment, even though the
connection has been established. About 3 minutes later, the data got
transferred - a whopping 16MB. Then another couple of minutes before the
next save starts, then no data for a while...interestingly, the
"savegrp" command output doesn't report that the save succeeded until
after that 2 minute delay before starting the next one.
The client doesn't not appear to be busy at all during this time.
I do not have problems with other clients behind the firewall (I did
have one fail last night for no reported reason - absolutely nothing in
the log files about it, only that a retry was attempted...), and I have
one other 2008R2 server that doesn't exhibit any delays, but is not
behind a firewall and is not running vCenter, and is not a VM (we are
not currently backing up any other Windows server on a VM).
Is this "normal"? Is it just going to take forever for these volumes to
back up?
-Brian
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
