On Thu, Apr 11, 2002 at 09:48:06AM +0200, klavs klavsen wrote: > Does amanda use the holding disk, when backing up from localhost?
Yes. > If it were smart, it would skip the holding disk, as this would just > waste space.. Hmm, I think I disagree. Using holdingdisk (assuming there's enough, and that you can run >1 backup in parallel) is a win from the point of view that holdingdisk is both faster than tape and can be accessed by multiple datastreams (backups) simultaneously. So the actual backups (tar or dump) can finish much more quickly than if they were waiting to serially access a single tape drive, and keeping your backup window as small as possible is usually considered a Good Thing. You don't (usually) really care if the tape drive is still churning for another hour or two or three afterwards; the important thing is that the file systems can safely return to full service before your users show up in the morning. > The reason I'm asking is that I was considering use System Imager to > backup all clients to my backup-server, and then use Amanda to backup > localhost (and a few systems that System Imager doesn't work with). > > I wouldn't really want it to duplicate 50gb of backup.. :-( I don't quite grok this, but if you don't want amanda to use holdingdisk, then tell just tell it; either set holdingdisk size too small to hold your 50GB of System Imager output, or use a dumptype with "holdingdisk no". -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA (fax)1.503.466.9472
