Welcome to amanda-users
-- Welcome to the amanda-users mailing list! Please save this message for future reference. Thank you. If you ever want to remove yourself from this mailing list, you can send mail to [EMAIL PROTECTED] with the following command in the body of your email message: unsubscribe amanda-users or from another account, besides [EMAIL PROTECTED]: unsubscribe amanda-users [EMAIL PROTECTED] If you ever need to get in contact with the owner of the list, (if you have trouble unsubscribing, or have questions about the list itself) send email to [EMAIL PROTECTED] . This is the general rule for most mailing lists when you need to contact a human. Here's the general information for the list you've subscribed to, in case you don't already have it: The amanda-users mailing list is for questions and general discussion about the Amanda Network Backup Manager. This package and related files are available via anonymous FTP from ftp.amanda.org in the /pub/amanda directory. NOTE: the amanda-users list is itself on the amanda-announce distribution, so you only need to subscribe to one of the two lists, not both. You can find archives of this, and the other amanda lists in: ftp://ftp.amanda.org/pub/amanda/maillist-archives You can find more information on the amanda project in general at: http://www.amanda.org/ [Last updated Sun Sep 13 13:19:47 EDT 1998 ]
pre/post run commands
Hi, I am using amanda to back up to a hard disk on my system and would like to protect the backed up disk from accidental erasure. I thought one way to do this would be to mount it then run amdump, and then umount it. The disk is going to be vulnerable during the backup period, but safe when not doing a backup or recover. Is there a way to do this? Or are there some permission settings that would prevent a rm -rf /* as root from erasing all of the backup disk? Thanks, Scott
Re: pre/post run commands
On Sun, Jul 06, 2003 at 09:36:56AM -0700, Scott Petler wrote: Hi, I am using amanda to back up to a hard disk on my system and would like to protect the backed up disk from accidental erasure. I thought one way to do this would be to mount it then run amdump, and then umount it. The disk is going to be vulnerable during the backup period, but safe when not doing a backup or recover. Is there a way to do this? Or are there some permission settings that would prevent a rm -rf /* as root from erasing all of the backup disk? In general, permissions are not checked for root. So I doubt any setting of permissions would help. Even root can not modify a file on a file system mounted read-only. You could mount it rw during backup, ro other times. The advantage to mounting it ro is that you can still do recoveries from the backed up data. Putting umount/mount commands in your cron might work. I'd be worried that the umount and mount would fail if something had a file open on that file system. Some mount commands (possibly FS type specific) may have an option to do a remount. This option may let you change the properties of the mount without affecting open files. Note, I said may let you, I've never tried it. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: pre/post run commands
Depending on your platform and choice of dump/tar, you may be able to just leave it umounted.
