How I understand the database/app backups to work, the app-backup schedule
entry is what governs the retention and storage device, the automatic ones
govern the timing & frequency (sort of a schedule wrapper for the actual
application backups)
How I have mine set up (for Oracle), is that I have a full-application-backup
and incr-application-backup that have their own retention periods (1 month for
incr-app-backup, 1 year for full-app-backup), daily/weekly pools, and backup
storage device (real tape on weekends, dssu during the week). The schedules are
set for wide open (24/7). My automatic backups (daily & full) govern the time
windows that I want backups to happen, but their retention periods, afaik,
don't mean much - although you mentioning that it governs how long the catalog
is maintained inspires me to want to go read through it again.
~ Robin
>>> "Wilkinson, Alex" <alex.wilkinson AT dsto.defence.gov DOT au> 6/11/2007
>>> 1:44 AM >>>
If I interpret this correctly this means for all "Application Backup Schedules"
(MSSQL,Oracle,SYBASE etc) - backup images are only being kept for 1 month.
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|