Re: Amanda-Autoeject after dump
Stefan G. Weichinger wrote: amdump daily mt -f /dev/nst0 offl in my crontab. (if it is Linux, syntax varies with OS) I use chg-multi, with multiple drives, and I have this script to do my backups: ## #!/bin/sh CONFIG=$1 /opt/local/sbin/amdump $CONFIG LOGF=`ls -t /var/opt/amanda/$CONFIG/log.2* | head -1` /opt/local/sbin/amtoc -a -t $LOGF grep '^START taper .* label ' $LOGF | while read line do /opt/local/sbin/amtape $CONFIG eject /opt/local/sbin/amtape $CONFIG slot prev done ### It generates an Table-of-contents for each tape and ejects those drives which have been used. The executables may be installed in different places on your server. -- 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: Amanda-Autoeject after dump
Hi, Paul, on Montag, 01. März 2004 at 15:13 you wrote to amanda-users: PB I use chg-multi, with multiple drives, and I have PB this script to do my backups: PB ## PB #!/bin/sh ... PB It generates an Table-of-contents for each tape and PB ejects those drives which have been used. PB The executables may be installed in different places on your PB server. Yes, they do, but I just modified paths and run a test-dump. Thanks ! -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
level 0 backups nightly
I'm trying to get amanda to backup nightly monday through friday with full backups (level 0) every night. I've played around a bit with dumpcycle, runspercycle and tapecycle but with some quick testing it looks like amanda isn't doing what I'm looking for. Rather than doing a lot more trial and error, I was hoping someone here could quickly tell me what values I need or what documentation to look at so amanda does a full backup every night. Thanks, Chris -- Chris Cameron UpNIX Internet Administrator ardvark.upnix.net gak.upnix.net -- http://www.upnix.com
Dumps too big ??
I'm using amanda 2.4.4 on Solaris 9.
Until now I'd thought I'd properly configured to use up to
two tapes in the jukebox for this amanda run, which is run
only 1/week (vs the other amanda config that runs 5x/week).
I'd thought the notice of next 2 tapes was confirmation that
I'd configured things ok, but now I have to question that.
I can include as much of the config as necessary but didn't
want to make the initial email too long.
Previous weeks (we've been doing this for about 6 months)
have always completed level 0 successfully for all partitions
and put the data on a single LTO tape in the jukebox.
Should a second tape have been written by amanda ?
If not, why the level 1 dumps.
If yes, why didn't it.
thanks in advance,
Brian
---
Brian R Cuttler [EMAIL PROTECTED]
Computer Systems Support(v) 518 486-1697
Wadsworth Center(f) 518 473-6384
NYS Department of HealthHelp Desk 518 473-0773
- Forwarded message from Amanda at NNewton -
These dumps were to tape NTNWKLY26.
The next 2 tapes Amanda expects to used are: NTNWKLY27, NTNWKLY01.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:06
Run Time (hrs:min)11:55
Dump Time (hrs:min) 12:38 12:31 0:06
Output Size (meg) 199870.1 199824.9 45.1
Original Size (meg)199870.1 199824.9 45.1
Avg Compressed Size (%) -- -- --(level:#disks ...)
Filesystems Dumped 29 23 6 (1:6)
Avg Dump Rate (k/s) 4501.5 4538.3 121.9
Tape Time (hrs:min)2:56 2:56 0:00
Tape Size (meg)199870.1 199824.9 45.2
Tape Used (%) 199.9 199.90.1 (level:#disks ...)
Filesystems Taped29 23 6 (1:6)
Avg Tp Write Rate (k/s) 19384.419405.3 3360.5
USAGE BY TAPE:
Label Time Size %Nb
NTNWKLY26 2:56 199870.1 199.929
NOTES:
driver: WARNING: /amanda/work: 73400320 KB requested, but only 69849607 KB available.
planner: lyra /space 20040228 0 [dumps too big, 256212 KB, full dump delayed]
planner: nnewton /home12 20040228 0 [dumps too big, 296020 KB, full dump delayed]
planner: denali / 20040228 0 [dumps too big, 479901 KB, full dump delayed]
planner: denali /home9 20040228 0 [dumps too big, 893786 KB, full dump delayed]
planner: mira /home1 20040228 0 [dumps too big, 2976158 KB, full dump delayed]
planner: panther / 20040228 0 [dumps too big, 3494817 KB, full dump delayed]
taper: tape NTNWKLY26 kb 204667904 fm 29 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISK L ORIG-KBOUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
--- -
csserv / 0 2587360 2587360 --7:00 6161.3 4:42 9166.2
csserv /opt 0 1610528 1610528 --4:24 6096.2 1:18 20706.7
csserv /source0 17011680 17011680 -- 117:09 2420.2 13:38 20786.9
csserv /var/spool 0 19567776 19567776 -- 47:44 6832.9 15:36 20904.9
denali / 1 256 256 --0:347.5 0:02 150.9
denali /home9 1 40192 40192 --0:53 763.5 0:07 5989.7
denali /images0378112378112 --5:06 1233.8 0:24 15927.2
lyra/ 0 2017600 2017600 --7:21 4579.7 1:17 26041.5
lyra/db8 0 33198432 33198432 -- 102:13 5413.4 24:26 22639.3
lyra/db9 0 22964704 22964704 -- 61:37 6212.3 14:21 26680.5
lyra/ndevelop 0 3497152 3497152 -- 25:30 2285.6 2:39 22013.4
lyra/ndevelop2 0 4308224 4308224 -- 12:41 5657.6 8:42 8255.1
lyra/space 1 2944 2944 --0:12 240.3 0:02 1708.3
mira/ 0 1248704 1248704 -- 10:17 2022.9 0:44 28095.7
mira/bkup-db 0 4487008 4487008 -- 19:34 3821.4 4:05 18318.9
mira/db4 0 3683456 3683456 -- 26:44 2295.9 3:17 18714.0
mira/home1 19696 --1:261.1 0:01 95.2
nnewton / 0 4566624 4566624 -- 12:17 6194.9 4:42 16171.8
nnewton /home100 5307584 5307584 -- 20:01 4419.5 6:32 13530.1
nnewton /home110 4981728 4981728 -- 19:12 4323.2 5:42 14571.6
nnewton /home121 1280 1280 --0:06 224.9 0:02 849.1
nnewton /home4 0 11666176 11666176 -- 43:17 4492.0 8:50 22002.8
nnewton /nfsamba1 0 4250592 4250592 -- 15:26 4588.3 5:02 14080.5
nnewton /nfsamba2 0 9654720 9654720 -- 36:53 4363.3 10:02 16044.2
nnewton /nlocal0 8296768 8296768
Re: level 0 backups nightly
Rather than doing a lot more trial and error, I was hoping someone here
could quickly tell me what values I need or what documentation to look
at so amanda does a full backup every night.
use comp-lev0 as your dump type.
define dumptype comp-lev0 {
global
comment very important partitions on fast machines
compress client best
priority high
dumpcycle 0
}
thanks
Re: level 0 backups nightly
Chris Cameron wrote: I'm trying to get amanda to backup nightly monday through friday with full backups (level 0) every night. I've played around a bit with dumpcycle, runspercycle and tapecycle but with some quick testing it looks like amanda isn't doing what I'm looking for. in amanda.conf general parameters and/or define dumptype : dumpcycle 0 (and a big tape) Rather than doing a lot more trial and error, I was hoping someone here could quickly tell me what values I need or what documentation to look at so amanda does a full backup every night. -- 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: Dumps too big ??
Brian Cuttler wrote: USAGE BY TAPE: Label Time Size %Nb NTNWKLY26 2:56 199870.1 199.929 You seem to have a tapecapacity of 100 Gbyte, so amanda scheduled up to 200 Gbyte (for 2 runtapes). To do this it needed to do some level 1 instead of full dumps. But actually your tapes *are* bigger, and amanda put all the 200 GByte on one tape only in reality. But that was after the schedule was decided. Are these 200 Gbyte native tapes? Change your tape definition to 200 Gbyte. If you use hardware compression, you may put a (safe) guess what will fit on a tape, e.g. 200 Gbyte. -- 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: Dumps too big ??
You seem to have a tapecapacity of 100 Gbyte, so amanda scheduled up to 200 Gbyte (for 2 runtapes). To do this it needed to do some level 1 instead of full dumps. But actually your tapes *are* bigger, and amanda put all the 200 GByte on one tape only in reality. But that was after the schedule was decided. Are these 200 Gbyte native tapes? Change your tape definition to 200 Gbyte. If you use hardware compression, you may put a (safe) guess what will fit on a tape, e.g. 200 Gbyte. -- 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: Dumps too big ??
SYSLOG - Amanda on INFO I had the tape drive incorrectly configured in amanda.conf to have a capacity of 100,000 Gbytes. This is the proper capacity with no compression but incorrect for hardware compression where we will estimate 200 000 GBytes (If amanda uses SW compression the 10 Gbytes is the correct setting for physical tape capacity). I've updated the tape capacity and also set the switch to no record so that the weekend level 0 does not throw off the 5x/week tape cycle we perform from newtonr and newtonl configurations. This will have the effect of increasing the amount of data to the daily tape pools. Based on the latest amanda report we may have finally reached the point where the 2nd tape will come into play on the weekly level 0 dumps. This will give us a tape cycle of 13 rather than 27 weeks which is still 3x the life of the other amanda configs where we consume (avg) 20 tapes in 4 weeks. If tape capacity estimation becomes an issue we can change to SW compression but HW compression has worked out really really well for us so far. Paul - thank you. You seem to have a tapecapacity of 100 Gbyte, so amanda scheduled up to 200 Gbyte (for 2 runtapes). To do this it needed to do some level 1 instead of full dumps. But actually your tapes *are* bigger, and amanda put all the 200 GByte on one tape only in reality. But that was after the schedule was decided. Are these 200 Gbyte native tapes? Change your tape definition to 200 Gbyte. If you use hardware compression, you may put a (safe) guess what will fit on a tape, e.g. 200 Gbyte. 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]
Re: Dumps too big ??
Sorry all, messed my units up. The manual that arrived with our LTO drive gives the capacity as 200 Gbytes with a 2:1 compression ratio. So we would expect to put 100 Gbytes of data to the tape with HW compression disabled and the 200 GBtytes is an 'optimistic' estimate with HW compression enabled. SYSLOG - Amanda on INFO I had the tape drive incorrectly configured in amanda.conf to have a capacity of 100,000 Gbytes. This is the proper capacity with no compression but incorrect for hardware compression where we will estimate 200 000 GBytes (If amanda uses SW compression the 10 Gbytes is the correct setting for physical tape capacity). I've updated the tape capacity and also set the switch to no record so that the weekend level 0 does not throw off the 5x/week tape cycle we perform from newtonr and newtonl configurations. This will have the effect of increasing the amount of data to the daily tape pools. Based on the latest amanda report we may have finally reached the point where the 2nd tape will come into play on the weekly level 0 dumps. This will give us a tape cycle of 13 rather than 27 weeks which is still 3x the life of the other amanda configs where we consume (avg) 20 tapes in 4 weeks. If tape capacity estimation becomes an issue we can change to SW compression but HW compression has worked out really really well for us so far. Paul - thank you. You seem to have a tapecapacity of 100 Gbyte, so amanda scheduled up to 200 Gbyte (for 2 runtapes). To do this it needed to do some level 1 instead of full dumps. But actually your tapes *are* bigger, and amanda put all the 200 GByte on one tape only in reality. But that was after the schedule was decided. Are these 200 Gbyte native tapes? Change your tape definition to 200 Gbyte. If you use hardware compression, you may put a (safe) guess what will fit on a tape, e.g. 200 Gbyte. 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]
fake install path
I vaguely recall that there is variable that you can pass to 'make' to install to a different root, similar to what happens during building a binary RPM, for example: make install VARIABLE=/tmp/amanda-2.4.4p2 The result is that you end up with all of the amanda files in /tmp/amanda-2.4.4p2/usr/local and so on. Then you can do something like this: cd /tmp/amanda-2.4.4p2 tar cvzf amanda-tarball.tgz . Then you can ftp the tarball to a different machine, cd / and extract the tarball. Does anybody remember what VARIABLE is supposed to be or how to do this? My goal is to set up a Snap Appliance 4500 as an amanda server--Yeah, I have already seen Preston Smith's page about setting up amanda client on a Snap 4400, and I also know that Snap Appliance won't take responsibility if I somehow manage to screw up my Snap. Thanks, --jonathan
? amrecover doesn't see index contents
I'm running amrecover trying to restore files. After I started amrecover and set target dis and date, it said no records found like below: amrecover ls Must select a disk before listing files amrecover setdisk /test-ama1 Scanning /dumps/amanda... 200 Disk set to /test-ama1. No index records for disk for specified date If date correct, notify system administrator amrecover setdate ---01 200 Working date set to 2004-03-01. No index records for cwd on new date Setting cwd to mount point amrecover ls I can see there is index files in the index dir and the .gz file was extracted when amrecover setdisk to this disk. The extracted text file has file list inside: -- spike:root:#ls -l total 4 -rw--- 1 amanda sys 142 Mar 1 16:00 20040301_0 -rw--- 1 amanda sys 83 Mar 1 15:58 20040301_0.gz spike:root:#more 20040301_0 10020721223/./cfgadm 10020721223/./chroot 10020721223/./clri 10020721223/./coreadm.conf 10020721223/./crash 10020721223/./cron 10020721732/./ spike:root:# spike:root:#pwd /myapp/am/etc/amanda/fst/index/pete/_test-ama1 - The funny thing is that I have another SAMBA disk with same dumpetype which works fine with amrecover. Thanks Allen Liu
Re: fake install path
Jonathan Dill wrote: I vaguely recall that there is variable that you can pass to 'make' to install to a different root, similar to what happens during building a binary RPM, for example: make install VARIABLE=/tmp/amanda-2.4.4p2 The prefix= can be specified to override the configure prefix like: make install prefix=/tmp/amanda-2.4.4p2 -- 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: ? amrecover doesn't see index contents
--On Monday, March 01, 2004 16:11:47 -0500 Allen Liu --- work [EMAIL PROTECTED] wrote: I'm running amrecover trying to restore files. After I started amrecover and set target dis and date, it said no records found like below: amrecover ls Must select a disk before listing files amrecover setdisk /test-ama1 Scanning /dumps/amanda... 200 Disk set to /test-ama1. No index records for disk for specified date If date correct, notify system administrator amrecover setdate ---01 200 Working date set to 2004-03-01. No index records for cwd on new date Setting cwd to mount point amrecover ls I can see there is index files in the index dir and the .gz file was extracted when amrecover setdisk to this disk. The extracted text file has file list inside: -- spike:root:#ls -l total 4 -rw--- 1 amanda sys 142 Mar 1 16:00 20040301_0 -rw--- 1 amanda sys 83 Mar 1 15:58 20040301_0.gz spike:root:#more 20040301_0 10020721223/./cfgadm 10020721223/./chroot 10020721223/./clri 10020721223/./coreadm.conf 10020721223/./crash 10020721223/./cron 10020721732/./ BAD version of tar, make sure you are using at least 1.13.19. However, one person on the list had success by manually editing out the leading numbers from the paths and then running amrecover. Frank spike:root:# spike:root:#pwd /myapp/am/etc/amanda/fst/index/pete/_test-ama1 - The funny thing is that I have another SAMBA disk with same dumpetype which works fine with amrecover. Thanks Allen Liu -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: fake install path
Thanks, that worked: make install prefix=/tmp/amanda-2.4.4p2/usr/local cd /tmp/amanda-2.4.4p2 tar cvzf ../amanda-tarball.tgz Paul Bijnens wrote: The prefix= can be specified to override the configure prefix like: make install prefix=/tmp/amanda-2.4.4p2
Re: fake install path
On Mon, Mar 01, 2004 at 10:10:13PM +0100, Paul Bijnens wrote: Jonathan Dill wrote: I vaguely recall that there is variable that you can pass to 'make' to install to a different root, similar to what happens during building a binary RPM, for example: make install VARIABLE=/tmp/amanda-2.4.4p2 The prefix= can be specified to override the configure prefix like: make install prefix=/tmp/amanda-2.4.4p2 This is not what you want, Jonathan. DESTDIR is the correct variable to overload for package building at the make install stage. PREFIX is defined at configure time as the install location. DESTDIR will be prepended to PREFIX at make install time. HTH, Brandon D. Valentine -- [EMAIL PROTECTED] http://www.geekpunk.net Pseudo-Random Googlism: february is national pet dental health month
Re: ? amrecover doesn't see index contents
Frank Smith wrote: --On Monday, March 01, 2004 16:11:47 -0500 Allen Liu --- work [EMAIL PROTECTED] wrote: spike:root:#more 20040301_0 10020721223/./cfgadm 10020721223/./chroot BAD version of tar, make sure you are using at least 1.13.19. However, one person on the list had success by manually editing out the leading numbers from the paths and then running amrecover. tar 1.13.19 or better yet 1.13.25 from : ftp://alpha.gnu.org/gnu/tar/tar-1.13.25.tar.gz ( but NOT 1.13.90 or later, yet). This works to fix the index-files: $ gunzip 2004* $ perl -pi.bak -e 's!^\d+/\.!!' 2004* $ gzip 2004*[0-9] (remove the .bak files afterwards if it's fixed) -- 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: fake install path
Brandon D. Valentine wrote: On Mon, Mar 01, 2004 at 10:10:13PM +0100, Paul Bijnens wrote: Jonathan Dill wrote: make install VARIABLE=/tmp/amanda-2.4.4p2 The prefix= can be specified to override the configure prefix like: make install prefix=/tmp/amanda-2.4.4p2 This is not what you want, Jonathan. DESTDIR is the correct variable to overload for package building at the make install stage. PREFIX is defined at configure time as the install location. DESTDIR will be prepended to PREFIX at make install time. Thanks for correcting me. I also found a decent explanation: http://sources.redhat.com/autobook/autobook/autobook_107.html -- 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 * ***
