>1) I am having 5 server data to backup ( including my amanda backup server). >2) The Backup will run everyday . >3) I have modified disklist for the partitions for each server . >4) I require 2 DLT s [ with 20 GB compressed mode ] for each server >partition. >5) I wish that on a single tape dump image of only one server will be >there , which may span second tape [ two tapes per server as mentioned ] . >6) I am having 10 sets of DLT tapes ready per day basis . Total 70 tapes > are ready for a week long backup . >7) the tapes wil be recycled and overwritten on each passing week as > usual.
Why do you have to have requirement #5? Segregating clients (what Amanda calls the machines it backs up) to separate tapes is going to make your life harder. Although I can think of reasons to want this, most people let Amanda mix all the clients. If you have to have separate tapes, you're going to need to create five separate configurations, one per machine being backed up. And you'll need to split the 70 tapes up into five sets of 14 and dedicate a set to each configuration. Then you'll have to run one configuration (amdump) after another in your cron job. As to item #7, the tapes will be overwritten when they are the oldest in the list. For instance, if you allocate two tapes per day but Amanda only needs one, it is not going to skip over the unused second tape for that day. It will ask for it as the first tape of the next run. Also, you will want to set your dumpcycle slightly smaller than one week. If you set it to exactly match the tape cycle, it will be overwriting the last good full dump of some of the file systems at least once a week. If an error happens during that run, you will not have a valid set of backups to restore from. Tapecycle should be at least dumpcycle + 1. In your case, dumpcycle should not be larger than six days. >B.N.C John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
