On Sun, May 17, 2015 at 02:57:09PM -0700, Alan Murrell wrote: > Hello, > > I am currently evaluating Amanda (community edition). I have been > intrigued by it for a long time now, but am just now seriously looking > at it. > > Our current practice when we setup backups for clients (using a > well-known commercial backup software) is to do backups to external > drives and each day someone (employee of the client) is responsible for > taking the "weekly" drive home each week. > > Amanda's scheduler will, by default, spread these full backups (which is > what intrigues me the most about it), but this also means that there > will not be one drive to take home each week, as they all will > (theoretically) have different full backups on them. > > I am wondering what others do or suggest for and offsite strategy? So > far, I have come up with the following options: > > 1.) Have a set enough drives to do four weeks' worth of backups, and > that weeks'-worth of backups get taken offsite each week > > 2.) Create a seperate weekly backup job (and set of external drives) > which would run over the weekend and backs up to as many drives as needed > > 3.) Subscribe to an offsite/online backup service and have that as the > offsite strategy > > Thoughts and further advice greatly appreciated. Thanks! :-) >
I've done both 1 & 2. Sometimes simultaneously :) Never tried 3. When scheme 1 was to tape I had at least 4 dumpcycles in rotation. Assuming a 1 wk dumpcycle they were "in use", "last week's", "off-site", "next weeks". I kept on-site last week's for recovery of recent data and next week's to avoid problems if retreval of the off-site set is delayed. If money, network bandwidth, time, ... allow I'd probably opt for a separate config to full dump always for the off-site/archives. That isn't always possible, especially for clients that are not connected full-time. Jon -- Jon H. LaBadie [email protected] 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
