When you initiate a scheduled client backup, the Client Job Tracker will
initiate a search of the system to report backup information (icon in job
tray has a yellow arrow). When utilizing a system with a large number of
files, I have seen this process take hours and 80%+ CPU utilization to
calculate the backup. While this is happening, the job is active and tape
drives are being held up waiting for the job to start sending data. Due to
this reason, it is suggested to not allow the job tracker to start
automatically on the client.
Matthew Moody
Midrange Computer Solutions (MCSI)
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Niehaus,
Michael T.
Sent: Thursday, December 12, 2002 11:21 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Breaking up images for optimization of many
small files
When you say "not enabled", does that mean "not running" or "not installed"?
How does this affect the backup performance? What does it do?
Thanks,
-Michael
-----Original Message-----
From: Matt Moody [mailto:mattm AT m-c-s DOT com]
Sent: Thursday, December 12, 2002 11:53 AM
To: Gardner, Jesse; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Breaking up images for optimization of many
small files
First off, make sure the "Client Job Tracker" is NOT enabled on the server
as this will take a huge amount of resources and a long time to compute the
backup information (if the client is Windows). Second, you need to
determine a breakdown of system speed for backup (ex: If this is a 100bt
attached client, the max throughput will be 12.5MB/s to tape). If you have
a large pipe or this server is a media server, then you should break the
client down into multiple data streams for the data (equal amounts of data
per stream) using whatever wildcards you need in the file listing. You can
then tune the class with multiplexing to get the greatest amount of speed
out of the LTO tapedrives.
Matthew Moody
Midrange Computer Solutions (MCSI)
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Gardner,
Jesse
Sent: Thursday, December 12, 2002 10:32 AM
To: (veritas-bu AT mailman.eng.auburn DOT edu)
Subject: [Veritas-bu] Breaking up images for optimization of many small
files
Netbackup 4.5 with the latest patches on Win2000 SP3, using an HP Surestore
E LTO Ultrium tape library with 2 drives and 20 slots.
We've got a situation where we're backing up almost 6 million files, about
150GB. It takes over 24 hours for a full backup. Right now we need to
restore everything from the production box to a new test server, and it is
just horrendous. I found several discussions on this mailing list that
suggest breaking up the file list into smaller chunks, so that NetBackup
doesn't have to crunch all 6 million files at one time.
My question is: To do this, do I create several entries in the file list
portion of one policy, or do I have to create multiple policies?
Jesse Gardner
510 High Street
Wisconsin Rapids, WI 54495
(715) 422-1516
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
