Well -- I have paranoid management.
We have weekend full backups (including a filesystem level backup
with the database down) with nightly hot full of the database, and
incremental of the servers. The test and development systems are
backed up on the weekends.

After backups run, duplicates are made of the production systems
and sent to a different facility. They pull the backup tapes and 
the duplicate tapes every morning. (Even though the incremental +
full database hot is on the order of 25G ) This means tape usage
is very high with a 6wk retention on the tapes, roughly 3 tapes
per night pulled + weekend schedule. Also, once a month, the colds
are marked for permanent retention and sent off to a data storage
company.

-charlie

> -----Original Message-----
> From: Norm Szcyrek [mailto:nszcyrek AT iocenter DOT net]
> Sent: Tuesday, August 27, 2002 2:53 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] What types of backup schedule does everyone use?
> 
> 
> I'm considering a change to our current backup schedule, and 
> I'm curious to hear from everyone on this list what type of 
> schedule do they use and why?   For example, we perform full 
> backups weekly, with differential incremental backups the 
> other 6 days of the week. We employ a 5 week rotation of 
> tapes for the weekly & daily backups.  Also, at the start of 
> the month, a full backup is performed on each server on a 
> different set of backup tapes, to be stored offsite.  Of 
> course, the full backups are performed on weekends when the 
> server loads are relatively light.
> 
> I've employed this type of schedule for the last two 
> companies I've worked for, and it has worked pretty well. I'd 
> really like to hear from others to help me get a better 
> understanding of what may be improved upon our own scheduling. TIA.
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>