"Carl D. Blake" <[EMAIL PROTECTED]> wrote: >I would prefer to let amanda handle the scheduling. I'm just having >trouble figuring out a reasonable configuration where I can get weekly >full backups as well as monthly (or every 4 weeks) full backups that I >can archive for a year. > >You mention that your archive config runs once a week and does monthly >backups for each filesystem. Is that configuration something like: > dumpcycle 0 > runspercycle 4 > tapecycle 52 >where dumpcycle 0 tells amanda to perform full backups every time, >runspercycle 4 tells amanda to put the full backups on 4 tapes, and >tapecycle 52 provides enough tapes for a year?
Actually, the archival config is more like: dumpcycle 4 weeks # 1 full backup / month runspercycle 4 # 12 dailys + 2 archives / fortnight tapecycle 1000 tapes # the number of tapes in rotation (We don't recycle the archival tapes. It may be time to bump up the 1000, come to think of it.) The dumptypes have: record no skip-incr yes The daily config is something like: dumpcycle 2 weeks # 1 full backup / fortnight runspercycle 12 # 12 dailys + 2 archives / fortnight tapecycle 20 tapes # the number of tapes in rotation >Also, how many tapes do you use for your daily config? Is it enough to >cover an entire month? 20, which isn't quite enough. Since most of the I-deleted-something-I-shouldn't-have restores are handled by the Network Appliance's snapshots, our backups are mostly for minor disaster recovery (disk failure and the like) and we only need tapecycle > runspercycle. Tommy McGuire
