What program do Amanda use to do the backup ?
Hi List, How can you tell what program Amanda used to do the backup ? TIA Bernie Wu [EMAIL PROTECTED] The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
Re: Disable Tape Compression
On Tuesday 04 October 2005 03:20, Sven Rudolph wrote: >Gene Heskett <[EMAIL PROTECTED]> writes: >> On Thursday 29 September 2005 17:06, Christopher Davis wrote: >>>The drive doesn't have any dip switches - I even took the drive out of >>> the encosure and couldn't find anything. >>> >>>I copied the wrong mt command over - >>> >>>Where I'm at now is looking at stinit ant the /etc/stinig.def file to >>> create a /dev/nst0l device which disables compression - I'm in the >>> middle of another test right now and can't try it out just yet - but >>> if this works for me I'll send it to the list. We have a ton of >>> these Sun SDLT 220 drives floating around and want to use them. >>> >>> >>>I ran some tests using hardware compression and wasn't impressed with >>> the results so I'm trying it with it off. >> >> Be aware that for many tape formats, the compression status is saved >> in a hidden header of the tape, so that once its been written in the >> compression on mode, that will be restored to on when the >> tape is loaded regardless of your wishes unless specifically disabled. >> >> I had a script at one time that turned these flags off, and it looked >> something like this: >> >> #!/bin/sh >> mt -f /dev/nst0 rewind >> dd if=/dev/st0 of=./scratch count=1 >> mt -f /dev/nst0 defcompression off (or 0 depending on your mt) >> mt -f /dev/nst0 compression off (or 0 depending on your mt) >> dd if=./scratch of =/dev/nst0 >> dd if=/dev/zero of=/dev/st0 count=(your drives buffer size plus 1) >> dd if=/dev/st0 (should show the tape label unchanged from ./scratch) >> >> Note use of /dev/st0 for its automatic rewind in places. simplifies >> the script.. > >I use a bit less magic (it is enough to overwrite the first block on >tape (SDLT220/SDLT600)); see below. And in my do_amdump (a wrapper >around amdump) I have: > >/usr/sbin/amtape DailySet1 taper > >/usr/local/bin/erase_tape /dev/st2 > >(Some time ago we had a discussion on having a hook to run a command >when a tape is to be written, but we didn't find a good solution.) > > Sven >- >host:~# cat /usr/local/bin/erase_tape >#!/bin/sh > >tapedev=$1 >labelfile=$(tempfile) > >mt -f $tapedev rewind > >dd if=$tapedev of=$labelfile bs=32k count=1 > >sudo unset_tape_compression $tapedev > >dd if=$labelfile of=$tapedev bs=32k count=1 > > > >host:~# cat /usr/local/bin/unset_tape_compression >#!/bin/sh > >tapedev="$1" > >case "$tapedev" in >/dev/st[0-9]) ;; >*) >echo "invalid device $tapedev" >&2 >exit 1 >esac > >mt -f $tapedev datcompression off Neat, and with better housekeeping than some of my hacks have had. I tend to scratch the itchiest place first and when thats fixed, the rest just get a lick and a promise. Sometimes its a year before I get back to the promise :) -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.35% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Howto exclude a addition server in my exclude.gtar list
Chuck Amadi Systems Administrator wrote: Hi I have create the path and exclude.gtar file with the same permissions as on my main tape/index server. So I assume that when the GNU tar runs on the backup server it will not tar/backup any files within the dumptype parameter on the amanda clients with the default path thus I can know see the logic as different clients would have different exclude list to suit. Yes, the exclude list has to exist on every client dumped using the related dumptype. -- Stefan G. Weichinger AMANDA core team member mailto://[EMAIL PROTECTED] -- oops! linux consulting & implementation http://www.oops.co.at --
Re: Howto exclude a addition server in my exclude.gtar list
Hi I have create the path and exclude.gtar file with the same permissions as on my main tape/index server. So I assume that when the GNU tar runs on the backup server it will not tar/backup any files within the dumptype parameter on the amanda clients with the default path thus I can know see the logic as different clients would have different exclude list to suit. I see what happens tomorrow . Cheers On Tue, 2005-10-04 at 11:08 +0200, Stefan G. Weichinger wrote: > Chuck Amadi Systems Administrator wrote: > > Hi all > > > > I have added a new server to my DLE and I need to exclude a few > > directories from a addition server. > > > > I have in place a exclude list in /usr/local/lib/amanda.exclude.gtar > > This works for my main backup server (myserver) which acts as the index > > and tape server. > > How do I add a entry like ./local/Backups for addition server and > > exclude I have added ./local/Backups but this didn't prevent it from > > being excluded. > > Without going into too much detail: > > The exclude list for the additional server (= AMANDA-client) has to be > placed on the AMANDA-client. > > From http://www.amanda.org/docs/exclude.html: > > "An exclude list is a file that resides on the CLIENT machine and > contains paths to be excluded, one per line. This file can be in any > location on the CLIENT so long as the same path is specified in the > dumptype. Some find /usr/local/etc/amanda an appropriate location, but > it is up to you." > > Stefan > > -- 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: Howto exclude a addition server in my exclude.gtar list
Hi again Thus I assume that I can use my current path on the tape/index server. /usr/local/lib/amanda/exclude.gtar and just create the path and exclude.gtar file on client and when the main tape/index server runs the backup will also exclude that same path and exclude.gtar file on the addition server. Cheers On Tue, 2005-10-04 at 11:08 +0200, Stefan G. Weichinger wrote: > Chuck Amadi Systems Administrator wrote: > > Hi all > > > > I have added a new server to my DLE and I need to exclude a few > > directories from a addition server. > > > > I have in place a exclude list in /usr/local/lib/amanda.exclude.gtar > > This works for my main backup server (myserver) which acts as the index > > and tape server. > > How do I add a entry like ./local/Backups for addition server and > > exclude I have added ./local/Backups but this didn't prevent it from > > being excluded. > > Without going into too much detail: > > The exclude list for the additional server (= AMANDA-client) has to be > placed on the AMANDA-client. > > From http://www.amanda.org/docs/exclude.html: > > "An exclude list is a file that resides on the CLIENT machine and > contains paths to be excluded, one per line. This file can be in any > location on the CLIENT so long as the same path is specified in the > dumptype. Some find /usr/local/etc/amanda an appropriate location, but > it is up to you." > > Stefan > > -- 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: Howto exclude a addition server in my exclude.gtar list
Hi Thanks for the pointer. Cheers On Tue, 2005-10-04 at 11:08 +0200, Stefan G. Weichinger wrote: > Chuck Amadi Systems Administrator wrote: > > Hi all > > > > I have added a new server to my DLE and I need to exclude a few > > directories from a addition server. > > > > I have in place a exclude list in /usr/local/lib/amanda.exclude.gtar > > This works for my main backup server (myserver) which acts as the index > > and tape server. > > How do I add a entry like ./local/Backups for addition server and > > exclude I have added ./local/Backups but this didn't prevent it from > > being excluded. > > Without going into too much detail: > > The exclude list for the additional server (= AMANDA-client) has to be > placed on the AMANDA-client. > > From http://www.amanda.org/docs/exclude.html: > > "An exclude list is a file that resides on the CLIENT machine and > contains paths to be excluded, one per line. This file can be in any > location on the CLIENT so long as the same path is specified in the > dumptype. Some find /usr/local/etc/amanda an appropriate location, but > it is up to you." > > Stefan > > -- 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
Howto exclude a addition server in my exclude.gtar list
Hi all I have added a new server to my DLE and I need to exclude a few directories from a addition server. I have in place a exclude list in /usr/local/lib/amanda.exclude.gtar This works for my main backup server (myserver) which acts as the index and tape server. How do I add a entry like ./local/Backups for addition server and exclude I have added ./local/Backups but this didn't prevent it from being excluded. I have the new server in DLE as secondserver.co.co.uk disklist file: # Main Server myserver/ partition backup myserver.cd.co.uk / root-tar # hostname diskname or mountpoint dumptype # mounted as. myserver.co.co.uk /home root-tar # /home myserver.co.co.uk /share root-tar # /share myserver.co.co.uk /projects root-tar # /projects myserver.co.co.uk /backup root-tar # /backup myserver.co.co.uk /tmp root-tar # /tmp myserver.co.co.uk /var root-tar # /var myserver.co.co.uk /data root-tar # /data # Remote backup of secondserver email server secondserver.co.co.uk / root-tar # backup second/ dir and sub dir's exclude.gtar file *.gz.tmp */.netscape/cache */gnutar-lists/*.new */spool/mqueue/?f[A-Z]* #*/tmp/*.errout *pagefile.sys */.thumbnails/* */trader-cache/* */cache/* */.thumbcache/* ./media ./var/tmp ./var/spool/postfix ./var/spool/cups ./dumps ./local/Backups ./tmp/.X11-unix/X0 ./var/lib/imap/proc ./var/lib/imap/socket ./var/lib/ntp/dev ./var/run/.resmgr_socket ./var/run/powersave_socket ./var/run/sasl2/mux ./var/spool/amavis My report produces the following below: /-- ktinga.smt / lev 0 STRANGE sendbackup: start [secondserver.co.co.uk:/ level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/tar -f... - sendbackup: info end | gtar: ./dev/log: socket ignored | gtar: ./local/Backups/var/lib/imap/socket/idle: socket ignored | gtar: ./local/Backups/var/lib/imap/socket/lmtp: socket ignored | gtar: ./local/Backups/var/run/.resmgr_socket: socket ignored | gtar: ./local/Backups/var/run/powersave_socket: socket ignored | gtar: ./local/Backups/var/run/sasl2/mux: socket ignored | gtar: ./local/Backups/var/spool/amavis/amavisd.sock: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/anvil: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/bounce: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/bsmtp: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/cyrus: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/defer: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/error: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/ifmail: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/lmtp: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/local: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/maildrop: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/procmail: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/proxymap: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/relay: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/rewrite: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/smtp: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/smtp-amavis: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/trace: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/uucp: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/verify: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/virtual: socket ignored | gtar: ./local/Backups/var/spool/postfix/private/vscan: socket ignored | gtar: ./local/Backups/var/spool/postfix/public/cleanup: socket ignored | gtar: ./local/Backups/var/spool/postfix/public/flush: socket ignored | gtar: ./local/Backups/var/spool/postfix/public/lmtp: socket ignored | gtar: ./local/Backups/var/spool/postfix/public/showq: socket ignored | gtar: ./tmp/.X11-unix/X0: socket ignored | gtar: ./tmp/ssh-ZslLylH562/agent.562: socket ignored | gtar: ./var/lib/imap/socket/idle: socket ignored | gtar: ./var/lib/imap/socket/lmtp: socket ignored | gtar: ./var/lib/ntp/dev/log: socket ignored | gtar: ./var/run/.resmgr_socket: socket ignored | gtar: ./var/run/powersave_socket: socket ignored | gtar: ./var/run/sasl2/mux: socket ignored | gtar: ./var/spool/amavis/amavisd.sock: socket ignored ? gtar: ./var/spool/amavis/amavis-20051003T203006-29040/email.txt: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/amavis/amavis-20051003T205856-29174/email.txt: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/amavis/amavis-20051003T210218-29184/email.txt: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/amavis/amavis-20051003T210655-29259/email.txt: Warning: Cannot stat: No such file or directory | Total bytes written: 3948554240 (3.7GB, 921kB/s) sendbackup: size 3856010 sendbackup: end \ Cheers -- Unix/ Linux Systems Administrator Chuck Amadi T
Re: Disable Tape Compression
Gene Heskett <[EMAIL PROTECTED]> writes: > On Thursday 29 September 2005 17:06, Christopher Davis wrote: >>The drive doesn't have any dip switches - I even took the drive out of >> the encosure and couldn't find anything. >> >>I copied the wrong mt command over - >> >>Where I'm at now is looking at stinit ant the /etc/stinig.def file to >> create a /dev/nst0l device which disables compression - I'm in the >> middle of another test right now and can't try it out just yet - but if >> this works for me I'll send it to the list. We have a ton of these Sun >> SDLT 220 drives floating around and want to use them. >> >> >>I ran some tests using hardware compression and wasn't impressed with >> the results so I'm trying it with it off. >> > Be aware that for many tape formats, the compression status is saved > in a hidden header of the tape, so that once its been written in the > compression on mode, that will be restored to on when the > tape is loaded regardless of your wishes unless specifically disabled. > > I had a script at one time that turned these flags off, and it looked > something like this: > > #!/bin/sh > mt -f /dev/nst0 rewind > dd if=/dev/st0 of=./scratch count=1 > mt -f /dev/nst0 defcompression off (or 0 depending on your mt) > mt -f /dev/nst0 compression off (or 0 depending on your mt) > dd if=./scratch of =/dev/nst0 > dd if=/dev/zero of=/dev/st0 count=(your drives buffer size plus 1) > dd if=/dev/st0 (should show the tape label unchanged from ./scratch) > > Note use of /dev/st0 for its automatic rewind in places. simplifies > the script.. I use a bit less magic (it is enough to overwrite the first block on tape (SDLT220/SDLT600)); see below. And in my do_amdump (a wrapper around amdump) I have: /usr/sbin/amtape DailySet1 taper /usr/local/bin/erase_tape /dev/st2 (Some time ago we had a discussion on having a hook to run a command when a tape is to be written, but we didn't find a good solution.) Sven - host:~# cat /usr/local/bin/erase_tape #!/bin/sh tapedev=$1 labelfile=$(tempfile) mt -f $tapedev rewind dd if=$tapedev of=$labelfile bs=32k count=1 sudo unset_tape_compression $tapedev dd if=$labelfile of=$tapedev bs=32k count=1 host:~# cat /usr/local/bin/unset_tape_compression #!/bin/sh tapedev="$1" case "$tapedev" in /dev/st[0-9]) ;; *) echo "invalid device $tapedev" >&2 exit 1 esac mt -f $tapedev datcompression off
