Re: Is there a way to force a amdump - Monthly Backup at end of day from the command line.
Hi List I just run as Amanda to create a Monthly Backup prior to the usually Last Friday of the Month. As Amanda User $ /usr/sbin/amdump Monthly Cheers On Fri, 2007-01-05 at 12:20 +, Chuck Amadi Systems Administrator wrote: > Hi List > > I have a scare yesterday with our raid 5 a raid disk died. > Hence I have ordered a hot spare and an additional raid disk But I > need to do a full amanda backup prior to tar'ing up my file system. > > Thus I currently run a daily increment backup and a last day on a friday > full amanda backup. > > Is there a way to force a amdump - Monthly Backup at end of day from the > command line. > > Cheers > > -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: Is there a way to force a amdump - Monthly Backup at end of day from the command line.
On Fri, 5 Jan 2007 at 12:20pm, Chuck Amadi Systems Administrator wrote I have a scare yesterday with our raid 5 a raid disk died. Hence I have ordered a hot spare and an additional raid disk But I need to do a full amanda backup prior to tar'ing up my file system. Thus I currently run a daily increment backup and a last day on a friday full amanda backup. Is there a way to force a amdump - Monthly Backup at end of day from the command line. I don't fully understand your setup, but there's a couple of ways to force a full backup: 1) In your normal 'daily' setup, run 'amadmin $CONFIG force' for each DLE. 2) Copy your daily config's amanda.conf and disklist into a new config (e.g. Archive) and change your dumpcycle to 0 in the new config. Then run that config. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Is there a way to force a amdump - Monthly Backup at end of day from the command line.
Hi List I have a scare yesterday with our raid 5 a raid disk died. Hence I have ordered a hot spare and an additional raid disk But I need to do a full amanda backup prior to tar'ing up my file system. Thus I currently run a daily increment backup and a last day on a friday full amanda backup. Is there a way to force a amdump - Monthly Backup at end of day from the command line. Cheers -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: Monthly backup
This is a good idea. Thanks for your reply. Jon LaBadie wrote: On Wed, Nov 01, 2006 at 11:17:09AM -0800, Steven Kurylo wrote: James Wilson wrote: Well I have a folder lets say its called "voice" and in voice I have a bunch of folders in there labeled by date. Starting with todays date all the way back to 10-01-2005. I want to backup everything till may of 2006 for the. Then I'm going to delete all those files because I have them on tape. Then every month I just want to back up the next month so in this case the next month would be June then July etc. So you don't want a full backup, just a specific folder whose name changes each month. I would create a symlink /path/to/link, pointing to /path/to/2006-04. I'm sure there might be a few other ways. Here is another ;) Have amanda totally exclude your voice directory tree. Outside of amanda create a monthly cronjob to make an archive (gnutar or zip or ???) of the voice directory you want to backup. The archive should be created somewhere amanda will backup. Perhaps an empty directory just for this purpose so it will be easy to find on recovery. Once the archive is made, and you are sure amanda has backed it up, delete the archive and the voice directory it contained. This could also be a cronjob that runs a day or several after the archive was made. It could even run daily, check the if an archive is in the directory, if so, check the amanda index files to see if it has been backed up, and only do the deletions if all conditions are met.
Re: Monthly backup
the folder name doesn't change. for example if I have folders 2006-01 2006-02 2006-03 2006-04 And I only want to back up folders 2006-01 and 2006-02. Is this possible? To back up certain folders and not others in a particular directory. Steven Kurylo wrote: James Wilson wrote: Well I have a folder lets say its called "voice" and in voice I have a bunch of folders in there labeled by date. Starting with todays date all the way back to 10-01-2005. I want to backup everything till may of 2006 for the. Then I'm going to delete all those files because I have them on tape. Then every month I just want to back up the next month so in this case the next month would be June then July etc. So you don't want a full backup, just a specific folder whose name changes each month. I would create a symlink /path/to/link, pointing to /path/to/2006-04. Tell the backup to backup /path/to/link. When the backup is done, have a script which deletes /path/to/2006-04, then changes /path/to/link to point at 2006-05. Or you could have amanda backup everything, but use an exclude to block the most recent folders. Then you'd have to rewrite the exclude file regularly. I'm sure there might be a few other ways.
Re: Monthly backup
On Wed, Nov 01, 2006 at 11:17:09AM -0800, Steven Kurylo wrote: > James Wilson wrote: > > Well I have a folder lets say its called "voice" and in voice I have a > > bunch of folders in there labeled by date. Starting with todays date > > all the way back to 10-01-2005. > > I want to backup everything till may of 2006 for the. Then I'm going > > to delete all those files because I have them on tape. Then every > > month I just want to back up the next month so in this case the next > > month would be June then July etc. > So you don't want a full backup, just a specific folder whose name > changes each month. > > I would create a symlink /path/to/link, pointing to /path/to/2006-04. > > I'm sure there might be a few other ways. Here is another ;) Have amanda totally exclude your voice directory tree. Outside of amanda create a monthly cronjob to make an archive (gnutar or zip or ???) of the voice directory you want to backup. The archive should be created somewhere amanda will backup. Perhaps an empty directory just for this purpose so it will be easy to find on recovery. Once the archive is made, and you are sure amanda has backed it up, delete the archive and the voice directory it contained. This could also be a cronjob that runs a day or several after the archive was made. It could even run daily, check the if an archive is in the directory, if so, check the amanda index files to see if it has been backed up, and only do the deletions if all conditions are met. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Monthly backup
James Wilson wrote: > Well I have a folder lets say its called "voice" and in voice I have a > bunch of folders in there labeled by date. Starting with todays date > all the way back to 10-01-2005. > I want to backup everything till may of 2006 for the. Then I'm going > to delete all those files because I have them on tape. Then every > month I just want to back up the next month so in this case the next > month would be June then July etc. So you don't want a full backup, just a specific folder whose name changes each month. I would create a symlink /path/to/link, pointing to /path/to/2006-04. Tell the backup to backup /path/to/link. When the backup is done, have a script which deletes /path/to/2006-04, then changes /path/to/link to point at 2006-05. Or you could have amanda backup everything, but use an exclude to block the most recent folders. Then you'd have to rewrite the exclude file regularly. I'm sure there might be a few other ways.
Re: Monthly backup
Well I have a folder lets say its called "voice" and in voice I have a bunch of folders in there labeled by date. Starting with todays date all the way back to 10-01-2005. I want to backup everything till may of 2006 for the. Then I'm going to delete all those files because I have them on tape. Then every month I just want to back up the next month so in this case the next month would be June then July etc. Steven Kurylo wrote: 1. Have a backup run once a month on the 1st. We have a config which only does full backups and cron schedules it to run at the start of the month. 2. Only backup data 7 months prior to todays date based on -mm format. Do you mean only keep 7 months worth of data? Then only put 7 tapes in the rotation.
Re: Monthly backup
> 1. Have a backup run once a month on the 1st. We have a config which only does full backups and cron schedules it to run at the start of the month. > 2. Only backup data 7 months prior to todays date based on -mm > format. Do you mean only keep 7 months worth of data? Then only put 7 tapes in the rotation.
Monthly backup
Hey All, I was wondering if someone could tell me if it is possible to back up data depending on the date? Here is what I want to do. 1. Have a backup run once a month on the 1st. 2. Only backup data 7 months prior to todays date based on -mm format.
Re: Monthly Backup Problem
Eric Siegerman wrote: On Mon, May 03, 2004 at 10:01:47AM +0200, Paul Bijnens wrote: Kianusch Sayah Karadji wrote: [...] the plan was to not put in a tape, and have amanda backup everything to the dumps Partition. After that use amflush to move the data from the partition to tapes in several runs. Why so complicated? Let it dump to one tape, and flush the rest in the morning to the other tape(s). I do our all-level-0 configurations this way, but for a different reason: it more fully packs the first tape. Since taping doesn't start until all of the DLEs have been dumped, the largestfit algorithm has all the data it needs to fill the tape as full as possible. If instead we let amdump write the first tape, largestfit would pick the optimum DLE from among those available at the moment the drive became free, which would be suboptimal for minimizing tape usage. There is an interaction between the number of dumpers, dumporder and taperalgo. See msg: http://marc.theaimsgroup.com/?l=amanda-users&m=106277015010167&w=2 Conclusion: it sometimes helps to lower the number of dumpers, and surely to change the default dumporder from "tttT" to something like "" or "T". The border case is indeed to have zero dumpers while taper is working: first everything to holdigdisk disk and then flushing optimally to tape. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: Monthly Backup Problem
On Mon, May 03, 2004 at 10:01:47AM +0200, Paul Bijnens wrote: > Kianusch Sayah Karadji wrote: > > > [...] the plan was to not put in a > > tape, and have amanda backup everything to the dumps Partition. After that > > use amflush to move the data from the partition to tapes in several runs. > > Why so complicated? > Let it dump to one tape, and flush the rest in the morning to the other > tape(s). I do our all-level-0 configurations this way, but for a different reason: it more fully packs the first tape. Since taping doesn't start until all of the DLEs have been dumped, the largestfit algorithm has all the data it needs to fill the tape as full as possible. If instead we let amdump write the first tape, largestfit would pick the optimum DLE from among those available at the moment the drive became free, which would be suboptimal for minimizing tape usage. I'm not sure whether this applies to 2.4.3, since I don't know what (hardwired) tape algorithm it used. > runtapes 1 > maxdumpsize 90g That's what I did, but in 2.4.3, I presume one could get the same effect by increasing runtapes instead. In this situation, runtapes doesn't seem to have any direct effect on the actual number of tapes used :-/ > reserve 0 > taperalgo largestfit That's what we have. -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / It must be said that they would have sounded better if the singer wouldn't throw his fellow band members to the ground and toss the drum kit around during songs. - Patrick Lenneau
Re: Monthly Backup Problem
> maxdumpsize 90g > taperalgo largestfit Those are 2.4.4 options ... I run 2.4.3 ,,, But I got the idea :) Kianusch
Re: Monthly Backup Problem
Hi! > Not needed, just change maxdumpsize (or runtapes). Thanks ... that's what I was looking for. > Why so complicated? Let it dump to one tape, and flush the rest in the > morning to the other tape(s). Just configure Amanda a little bit more, > to allow her to schedule all backups. Because at that time the Daily Backup-Tape is in the drive ... and as the tapes are changed by persons who do not know anything about what's going on - I want to avoid that they have to think! :) Regards Kianusch
Re: Monthly Backup Problem
Kianusch Sayah Karadji wrote: My Monthly Backup is designed to make a "level 0" from all available Data - which will not fit to one tape anyway - so the plan was to not put in a tape, and have amanda backup everything to the dumps Partition. After that use amflush to move the data from the partition to tapes in several runs. Why so complicated? Let it dump to one tape, and flush the rest in the morning to the other tape(s). Just configure Amanda a little bit more, to allow her to schedule all backups. Some parameters you'll need to set: # you may set runtapes to more if you like, amanda # will not find them all, and continue to disk runtapes 1 # Even with runtapes 1, you can let amanda plan # for a lot more gigabytes than fit on one tape maxdumpsize 90g # When dumping to holdingdisk because tapes are full # you need to lower the reserved-for-incremental space # Setting it to 0 percent lets all the space be used # for level0 backups. (Or set it to some low value.) reserve 0 # You can get amanda to optimize tape usage too. # See for an extended explanation: # http://marc.theaimsgroup.com/?l=amanda-users&m=106277015010167&w=2 taperalgo largestfit What i do now ist using a "dummy" tape definition with the following entry "length 9 mbytes", so that the backup is done in any case ... and changing the setup back to the correct value for tape operation. Not needed, just change maxdumpsize (or runtapes). -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Monthly Backup Problem
Hi! I use amanda 2.4.3 to make Daily and Monthly Backups to Tapes :) Daily works fine. My Monthly Backup is designed to make a "level 0" from all available Data - which will not fit to one tape anyway - so the plan was to not put in a tape, and have amanda backup everything to the dumps Partition. After that use amflush to move the data from the partition to tapes in several runs. But ... amanda uses the configured tape-size and excludes some backups even when not using the tape: xxx /data/xxx lev 0 FAILED [dumps too big, but cannot incremental dump new disk] What i do now ist using a "dummy" tape definition with the following entry "length 9 mbytes", so that the backup is done in any case ... and changing the setup back to the correct value for tape operation. It works ... but I was wondering if there is an easyer way to accomplish this. Regards Kianusch