On Thu, 21 Oct 2010 15:50:34 -0400 Jon LaBadie <[email protected]> wrote:
> > As the amount of data is very large (630GB), thus the backup time > > would be very long (especially L0's) I divided the data into data > > which changes fast and should be backed up daily (DailySet1) and > > data which is very static and should be backed up weekly. The > > weekly data I also divided into 4 parts (WeeklySet1-4) so that the > > runtime of the backup is shorter. > > I'm not sure if it is best to make up 5 distinct Amanda configs, or > just one config with customized DLEs and dumptypes. I'd probably try > the latter first. I think it would make the best use of your storage > media rather than targeting specific amounts for each config. I concur. I'm reluctant to say that a computer is smarter than I am, but there a few things I am willing to delegate to a computer. Amanda's backup scheduling is one of them. I set things up for a 15 day dump cycle, M-F, so three weeks. This implies *at least* one level 0 per DLE. You will find Amanda staggers them so as to even out the load. That's much better than one can do manually, especially as DLE sizes change over time. Also, Amanda will do more than one level 0 per cycle if it finds the assets to do so. Be generous with tapes. They are cheaper than your time, and much cheaper than replacing your data. -- Charles Curley /"\ ASCII Ribbon Campaign Looking for fine software \ / Respect for open standards and/or writing? X No HTML/RTF in email http://www.charlescurley.com / \ No M$ Word docs in email Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
