Re: User size caps
* Joshua Baker-LePain ([EMAIL PROTECTED]) [040308 11:48]: On Mon, 8 Mar 2004 at 11:29am, Daniel Bentley wrote Is there any way to put a 'size cap' on the amount of data being backed up from one particular source (or -all- sources, at that)? There's a big difference between 'Could you keep the size of the share you want backed up to X?' and 'There is a limit to back up sizes of X. Anything you have above this WILL NOT be backed up...' Sounds like a job for quotas to me. I can't really think of a way of enforcing this with amanda. The only thing I could suggest would be dynamically generating an excludes file on the target based on disk space utilization. Not exactly built-in to amanda, but a little less harsh than quotas (although I wouldn't want to be the system administrator (or his boss) when one of the managerial types loses a file and can't get it back...). Best, -- Patrick Michael Kane [EMAIL PROTECTED]
Re: ADIC / Dell Powervault 120T changer problems under Linux (Pt 2)
* Derrick Miller ([EMAIL PROTECTED]) [020329 12:49]: Jim, I have this changer working with RedHat 7.2 using the 2.4.2p2 chg-zd-mtx script. The trick to getting it working is getting the configuration file for chg-zd-mtx right. Make sure all the variables mentioned in the script are defined. In my case I have (in /etc/amanda/CONFIG/chg-zd-mtx.conf, replace CONFIG with your configuration name): Are you using the Amanda RPMs supplied with Red Hat 7.2, or did you compile 2.4.2p2 from source? Since I posted my previous message asking for help, I have managed to get Amanda working well with the changer, by compiling from source. I would like to switch back to the RPM version if it will work, though, since I find it's much easier to manage the system using RPM and up2date than it is with source tarballs. As a datapoint, I am happily using the RedHat 7.2 RPMs with an HP DLT changer. Best, -- Patrick Michael Kane [EMAIL PROTECTED]
Re: XFS, Linux, and Amanda
* Joshua Baker-LePain ([EMAIL PROTECTED]) [020114 15:37]: On Mon, 14 Jan 2002 at 2:57pm, Dan Rich wrote I found part of the problem, it appears that the original RPM I installed installs things in a very different location from make install. Amdump was running the wrong copy of sendsize. Now that that is fixed, I can start figuring out the next error :) Hmmm, you did 'rpm -e' the RPM version, right? Pre-build amanda=bad. Although that has been my general experience as well, the RedHat 7.1/7.2 RPMs work well enough in my setup, which is fairly complex. Earlier ones barfed all over the place. Best, -- Patrick Michael Kane [EMAIL PROTECTED]
Re: Linus Torvald's opinion on Dump.
* Jesper Holm Olsen ([EMAIL PROTECTED]) [010428 08:47]: At 08:50 28-04-01 -0500, you wrote: I've seen ads for the commercial and pricey backup packages from Syncsoft, Veritas and so on which claim no problems with live backups on *nix or NT. I suppose they have some way of write-locking files, copy to memory, then releasing the lock, but how could these utils work at the block rather than file level? Veritas file-system (VxFS) can make what they call a 'snapshot' of a file system. The idea is to take a snapshot of a filesystem and mount it as readonly on another device. Whenever a block on the original filesystem is altered the old one is copied to the snapshot and thus keeping this in the state it was in when mounted. This is for example used to backup using vxdump. Unfortunatly this is not yet available on Linux as far as I know - only Solaris and HPUX :( A quick search on google revails that someone is working on this feature for Linux as well: http://lwn.net/2001/0308/a/snapfs.php3 Linux LVM supports snapshots. It's in 2.4 kernels, although it needs some patching to make it usable. Best, -- Patrick Michael Kane [EMAIL PROTECTED]
