We use ALL_LOCAL_DRIVES in our backup policies, which can cause some
problems with a few clients who have some very large drives that take a
very long time to backup. Sometimes these jobs will stay in a queued
state and go active towards the end of their backup window, which
usually requires us to cancel them.

 

My thoughts on a solution to the problem is to create a separate
"priority" policy for the clients who take a long amount of time to
backup so they start right away, then have a separate policy that starts
an hour or so later for those jobs that don't take as long. This way we
ensure that our longest running jobs start at the beginning of the
backup window.

 

I'd like to setup the policy to only backup the drives that take the
longest, rather than all the drives, to ensure those jobs always start
(there are only about a dozen or so). However because the drives are
different on each client I don't want to create separate policies
(unless it would be easier to administer) for each client. I was
thinking of creating a series of exclude/include lists for the dozen or
so clients. For example:

 

client1:

priority_policy - exclude ALL_LOCAL_DRIVES, include J:\

normal_policy - exclude J:\

 

client2:

priority_policy - exclude ALL_LOCAL_DRIVES, include X:\

normal_policy - exclude X:\

 

This way the job for the J:\ or X:\ drive on the client starts
immediately under the priority_policy and later the other drives, which
don't take as long, will be backed up under the normal_policy. Would
this work? Or am I going about this the wrong way?

 

I also plan to set the job priority on the priority_policy higher to
ensure these jobs start as soon as resources are available.

 

Jason Ellis
Technical Consultant, Data Protection Team
IndyMac Bank, La Mirada Datacenter
Phone: (714) 520-3414
Mobile: (714) 889-8734

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20070405/0c863aae/attachment.html