Correct. Utilizing multiple data streams makes it easier to manage a server
with a single schedule, but makes it more difficult to backup a "single
stream" in case of a critical failure. Without seperate schedules for each
stream, the Admin would have to perform a user-initiated backup of the data
affected by the failed stream.
Depends on what the Administrator wants to deal with. A bunch of schedules
or having to perform manual backups when/if there is a stream failure that
could not be resolved before the retry criteria is met.
Matthew Moody
Midrange Computer Solutions (MCSI)
-----Original Message-----
From: Quarantine [mailto:Quarantine AT GSCCCA DOT ORG]
Sent: Thursday, December 12, 2002 11:22 AM
To: 'Matt Moody'; Quarantine; 'Gardner, Jesse';
veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Breaking up images for optimization of many
small files
Guess I should have been more clear. I meant that if you have a problem
that is not solved by requeues, then you can restart a subset. You can't do
this if they're all in one policy.
Matt
-----Original Message-----
From: Matt Moody [mailto:mattm AT m-c-s DOT com]
Sent: Thursday, December 12, 2002 1:17 PM
To: Quarantine; 'Gardner, Jesse'; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Breaking up images for optimization of many small
files
Using multiple data streams is the same as a checkpoint backup in that only
the failed stream will restart since each stream is handled as a seperate
job when the class initiates backup.
Matt is correct, definately disable OTM on the client if you are using it.
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 Quarantine
Sent: Thursday, December 12, 2002 11:01 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
A couple of other suggestions from someone who has to back up 55 million
files with an average size of 50K:
1. Disable OTM if possible.
2. Make sure the job tracker is disabled on the client machine.
I use a policy for each subset of files that I back up so I can have more
control over what runs. Also, if you use a single policy and the backup
fails, you have to restart the whole thing. If you break it up, you can
just rerun the failed portion.
Matt
-----Original Message-----
From: Gardner, Jesse [mailto:Jesse.Gardner AT storaenso DOT com]
Sent: Thursday, December 12, 2002 11: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
|
