Hello,
I am puzzled by the Netbackup comments, are you actually backing up other
servers from the file server you backup with Legato ? It may interfere or
compete for TCP ports ?
The delay you are seeing may the time Networker needs to walk the file
system before starting the backup and since the file system is large it
may take a while to get started.
Does the client have enough Memory\CPU during backup cycle ?
I would use Storage Node capability to backup any thing over 150 GB or
saveset that takes over 4 hrs, your criteria may vary.
Snapimage module may help if you chose that route, but SN may be preferred
alternative.
HTH
"Clark, Patti" <clarkp AT OSTI DOT GOV>
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
04/09/2008 04:37 PM
Please respond to
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please respond
to
"Clark, Patti" <clarkp AT OSTI DOT GOV>
To
NETWORKER AT LISTSERV.TEMPLE DOT EDU
cc
Subject
[Networker] Backup of large Windows 2003 file system hanging
We are running Networker v7.3.3 on server and clients. I have a new
client, Windows 2003 Server 64-bit, that is single purposed as a file
server and currently holding backup files for our Exchange store
produced by Netbackup. The disk space has been carved up into a
relatively small C:\ @ 12 GB (6 GB free) and a large D:\ @ 1.5 TB. The
number of files is fairly small, less than 300GB of space is being used,
and the directory structure is shallow, 2-3 levels deep. I have been
successfully backing up a similar setup on a 32-bit system that was
getting short on space.
The Networker full backups on the new server were successful on the
system state (VSS) components and the C:\. The D:\ starts the backup
process, gets about 50GB written and then simply stops. The daemon.log
says that the saveset is done saving to the pool and a write completion
notice is posted to the volume. After about a 10 minute wait, the
saveset backup for D:\ is started again with pretty much the same
results and the backup is completed with the D:\ saveset as a failure.
The event logs on the Win box has nothing, nor does any other log of
relevance. There are no network firewalls between the networker server
and client. Forward and reverse DNS on both boxes are consistent. All
necessary privileges have been granted.
I am backing up the backups. Netbackup runs on a server that is not in
the backup rotation. Is this a problem?
Also, when I start any type of Windows client backup manually using the
NMC interface, a full 10 minutes passes, consistently, before anything
visible happens - tape movements, saveset starts, etc. The only thing
that happens immediately is the announcement that group has started with
# clients. Is this normal?
Patti Clark
Sr. Unix System Administrator - RHCT, GSEC
Office of Scientific and Technical Information
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
|
