to take this tread a different direction...

If your backups take too long, how long would our restore take?
Do a test of this, tell management that a complete restore of
X system will require 32 hours, and see if you get the upgrade you
need.

This List always discusses backup issues, It's when you have
Down-time that is un-acceptable that the Backup Team
comes under fire.


And another direction...

How about this schedule, as food for thought.
1 monthly FULL backup.
1 Weekly Cumulative Backup.
Daily Differential Backups.

If most of your Backup is of stale data, this works great
for LONG Full Backups.


Patrick Boyle
ESRI Systems Administration
Voice:          [909] 793-2853  Ext. 1-1461
Numeric Pager:  [909] 777-2791
E-mail:         PBoyle AT esri DOT com


-----Original Message-----
From:   veritas-bu-admin AT eng.auburn DOT edu
[mailto:veritas-bu-admin AT eng.auburn DOT edu] On Behalf Of John_Wang AT enron 
DOT net
Sent:   Friday, October 13, 2000 3:19 PM
To:     veritas-bu AT mailman.eng.auburn DOT edu
Subject:        [Veritas-bu] Preemptive scheduling



Hello

Well, seeing how unsuccessful trying to see if anyone managed to do
conditional
expirations was, here's another of my backup favourites.

Can Netbackup do preemptive scheduling?

i.e.: if a full backup is running long (which full backups tend to do) and
therefore into the window for a scheduled incremental for the same drive,
there
is no real need for the incremental to run since the full is really in the
same
time frame anyway so the incremental should be preempted by the full backup
of
the same drive.

Can Netbackup scheduling be configured to do this and if so how?

Regards,
John I Wang
Sr. Systems Engineer
Steverson Information Professionals

---
Enron Broadband Services
3 Allen Center, Room 337C
PH (713) 345-6238


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu