Veritas-bu

[Veritas-bu] ALL_LOCAL_DRIVES is fine but ...

2003-09-09 12:53:28
Subject: [Veritas-bu] ALL_LOCAL_DRIVES is fine but ...
From: Hector.Villalobos AT roxio DOT com (Hector Villalobos)
Date: Tue, 9 Sep 2003 09:53:28 -0700
What I have done in cases like this; is to break up the job into two different 
policies; and have the large directories and/or drives in their own policy.  
Works good.



-----Original Message-----
From: Richard Hellier [mailto:rlh AT lsil DOT com]
Sent: Tuesday, September 09, 2003 6:22 AM
To: veritas-bu
Subject: [Veritas-bu] ALL_LOCAL_DRIVES is fine but ...


        Hi -- I'm a satisfied "customer" of the ALL_LOCAL_DRIVES directive
but I've run into a snag with it and I'm hoping someone may be able to
help.

        In my site, almost all the backup traffic comes from a single
fileserver with several hundred filesystems ranging in size from 500
Mbyte
to 350 Gbyte.  The ALL_LOCAL_DRIVES directive does exactly what it
should
and everything gets backed up ... BUT the problem we see is that the
various filesystems are backed up in no particular order and what
happens
from time to time is that one or two of the larger filesystems are left
until last.  The downside here is that if one of the "big" backups
hiccups
in some way and has to be repeated, the schedule's window may have
closed
and then jiggery-pokery is needed to mop up the stragglers. If the big
backups were done first, they'd have plenty of time for re-runs if they
became necessary.


        SO ... the question is, is there a way to force backup jobs 
created using A/L/D to be queued in a particular order (e.g. size)?
I was hoping there might be a "magic" file you can just touch to
trigger this behaviour ...


Cheers,

Richard.


<Prev in Thread] Current Thread [Next in Thread>
  • [Veritas-bu] ALL_LOCAL_DRIVES is fine but ..., Hector Villalobos <=