Re: Cant run two Linux Servers behind my firewall at the same time - only one and vice versa.
Hi List Sorry to nag on is there any suggestions to my post. Cheers On Thu, 2007-01-18 at 08:27 +, chuck.amadi wrote: Hi List I was hoping for some direction to my issue with two servers behind a firewall running ipchains I can backup one or the other but when I uncomment both DLE I get host down. Thanks in advance. chuck.amadi wrote: Hi I have two Linux SuSE 9 SLES servers outside of my lan behind a firewall using (I know don't laugh) IPChains. The first server I setup worked without problems by compiling with the tcp and udp port range and changing a parameter in security.c file and increasing the timeout using a ipchain rule, which worked a treat but I have another new server outside and behine a firewall. Thus when I tried following the same reciepe and compile using the same tcp and udp port range and thus a separate tcp and udp port range to no joy I am unable to get both to work at the same time if I comment out one of the amanda clients within the disklist the other doesn't work and vice versa So I know it is not the setup or configure. #The timeout is in seconds. If you set the timeout of TCP, TCPFIN #and UDP to 5 seconds, 5 seconds and 5 seconds, I think they are #too short. Please try to set them to 5min, 1min #and 5min respectively such as 300 60 300. # ipchains -M -S 300 tcp 60 tcpfin 300 udp works ok. ipchains -M -S 7200 60 300 I get the Warning: selfcheck request timed out. Host down!. Note that when I comment out one of them amcheck works accordingly I am aware the it's using udp over the firewall But I haven't been able to suss this out I assume that my connection is poor. I have checked both /tmp/amanda/amanda-date.debug and they both moan about timeouts failed But are OK when only one of them is in use. 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
Server outside of my firewall is now experiencing problems
Hi List I have a server outside of my firewall and I am now experiencing problems when I receive amcheck email notifications. I have increased the etimeout in my amanda.conf File. Thus I have had a look in my /tmp/amanda debug directory. less amandad.2007045710.debug amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 003-589B0808 SEQ 1168527371 amandad: time 0.008: bsd security: remote host fwall.mycompany.co.uk user amanda local user amanda amandad: time 0.009: amandahosts security check passed amandad: time 0.009: running service noop amandad: time 0.009: sending REP packet: Amanda 2.4 REP HANDLE 003-589B0808 SEQ 1168527371 OPTIONS features=feff9ffe0f; amandad: time 10.001: dgram_recv: timeout after 10 seconds amandad: time 10.001: waiting for ack: timeout, retrying amandad: time 10.150: got packet: Amanda 2.4 REQ HANDLE 003-589B0808 SEQ 1168527371 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; amandad: time 10.150: weird, it is not a proper ack addr: peer 193.131.77.174 dup 193.***.***.174, port: peer 64206 dup 64209 amandad: time 20.141: dgram_recv: timeout after 10 seconds amandad: time 20.142: waiting for ack: timeout, retrying amandad: time 20.330: got packet: Amanda 2.4 REQ HANDLE 003-589B0808 SEQ 1168527371 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; amandad: time 20.330: weird, it is not a proper ack addr: peer 193.131.77.174 dup 193.***.***.***, port: peer 64206 dup 64209 amandad: time 30.321: dgram_recv: timeout after 10 seconds amandad: time 30.321: waiting for ack: timeout, retrying amandad: time 40.321: dgram_recv: timeout after 10 seconds amandad: time 40.321: waiting for ack: timeout, retrying amandad: time 50.321: dgram_recv: timeout after 10 seconds amandad: time 50.321: waiting for ack: timeout, giving up! amandad: time 50.321: pid 6823 finish time Thu Jan 11 14:58:00 2007 -- 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.
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
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
planner: disk server1.my.co.uk:/, estimate of level 2 failed: -1.
Hi List Please can some one explain whats happening here I did increase the etimeout as it had timed out. NOTES: planner: disk server1.my.co.uk:/, estimate of level 2 failed: -1. 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
DUMP SUMMARY Failed - on one of my clients on my side of the firewall
Hi List I recieved an unexpected error in my dump summary. server1.my.co.uk 0 Failed. I run # less sendsize.20061128194512.debug sendsize: debug 1 pid 12174 ruid 37 euid 37: start at Tue Nov 28 19:45:12 2006 sendsize: version 2.4.4p2 sendsize[12174]: time 0.020: waiting for any estimate child: 1 running sendsize[12176]: time 0.020: calculating for amname '/', dirname '/', spindle -1 sendsize[12176]: time 0.020: getting size via gnutar for / level 0 sendsize[12176]: time 0.044: spawning /usr/lib/amanda/runtar in pipeline sendsize[12176]: argument list: /bin/tar --create --file /dev/null --directory / --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/k tinga.smtl.co.uk__0.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendsize._.20061128194512.exclude . sendsize[12176]: time 820.848: /bin/tar: ./dev/log: socket ignored sendsize[12176]: time 826.070: /bin/tar: ./tmp/ssh-CoTSEt9723/agent.9723: socket ignored sendsize[12176]: time 826.094: /bin/tar: ./tmp/ssh-dyXac5016/agent.5016: socket ignored sendsize[12176]: time 916.822: /bin/tar: ./var/run/rcd/rcd: socket ignored sendsize[12176]: time 1729.064: Total bytes written: 5596303360 (5.2GB, 3.1MB/s) sendsize[12176]: time 1729.083: . sendsize[12176]: estimate time for / level 0: 1729.039 sendsize[12176]: estimate size for / level 0: 5465140 KB sendsize[12176]: time 1729.083: waiting for /bin/tar / child sendsize[12176]: time 1729.083: after /bin/tar / wait sendsize[12176]: time 1729.084: getting size via gnutar for / level 1 sendsize[12176]: time 1729.279: spawning /usr/lib/amanda/runtar in pipeline sendsize[12176]: argument list: /bin/tar --create --file /dev/null --directory / --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/k tinga.smtl.co.uk__1.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendsize._.20061128201401.exclude . sendsize[12176]: time 2584.337: /bin/tar: ./dev/log: socket ignored sendsize[12176]: time 2584.646: /bin/tar: ./tmp/ssh-CoTSEt9723/agent.9723: socket ignored sendsize[12176]: time 2584.646: /bin/tar: ./tmp/ssh-dyXac5016/agent.5016: socket ignored sendsize[12176]: time 2594.983: /bin/tar: ./var/run/rcd/rcd: socket ignored sendsize[12176]: time 2596.421: Total bytes written: 220354560 (210MB, 248kB/s) sendsize[12176]: time 2596.422: . sendsize[12176]: estimate time for / level 1: 867.142 sendsize[12176]: estimate size for / level 1: 215190 KB sendsize[12176]: time 2596.422: waiting for /bin/tar / child sendsize[12176]: time 2596.442: after /bin/tar / wait sendsize[12176]: time 2596.442: done with amname '/', dirname '/', spindle -1 sendsize[12174]: time 2596.443: child 12176 terminated normally sendsize: time 2596.443: pid 12174 finish time Tue Nov 28 20:28:28 2006 and also run # less amandad.20061128194512.debug amandad: debug 1 pid 12173 ruid 37 euid 37: start at Tue Nov 28 19:45:12 2006 amandad: version 2.4.4p2 amandad: build: VERSION=Amanda-2.4.4p2 amandad:BUILT_DATE=Wed Jun 30 23:45:53 UTC 2004 amandad:BUILT_MACH=Linux eisenstein 2.6.5 #1 Thu Nov 14 12:14:04 UTC 2002 i686 i686 i386 GNU/Linux amandad:CC=gcc amandad:CONFIGURE_COMMAND='./configure' '--mandir=/usr/share/man' '--prefix=/usr' '--infodir=/usr/share/info' '--sysconfdir=/etc' '--libdir=/ usr/lib' '--libexecdir=/usr/lib/amanda' '--localstatedir=/var/lib' '--with-index-server=localhost' '--with-gnutar-listdir=/var/lib/amanda/gnutar-lists ' '--with-smbclient=/usr/bin/smbclient' '--with-amandahosts' '--with-user=amanda' '--with-group=disk' '--with-gnutar=/bin/tar' '--disable-libtool' '-- disable-shared' '--disable-static' amandad: paths: bindir=/usr/bin sbindir=/usr/sbin amandad:libexecdir=/usr/lib/amanda mandir=/usr/share/man amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda amandad:CONFIG_DIR=/etc/amanda DEV_PREFIX=/dev/ amandad:RDEV_PREFIX=/dev/r DUMP=/sbin/dump amandad:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF amandad:XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF amandad:SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/tar amandad:COMPRESS_PATH=/usr/bin/gzip amandad:UNCOMPRESS_PATH=/usr/bin/gzip LPRCMD=/usr/bin/lpr amandad:MAILER=/usr/bin/Mail amandad:listed_incr_dir=/var/lib/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1 amandad:DEFAULT_TAPE_SERVER=localhost amandad:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc amandad: time 0.000: got packet: Amanda 2.4 REQ HANDLE 001-00660808 SEQ 1164743107 SECURITY USER amanda SERVICE sendsize OPTIONS
I would like to backup bi-weekly/fornightly a full backup to the external USB 250GB hard drive.
Hi List I have a Daily Config and Monthly archive Config (Last Friday of every month script) backup running using SuSE SLES 9, Amanda version 2.4.4p2 on the DAT 4MM*150MM tape server and 4 clients but version 2.5 on a new client I added to the DLE. Anyway I for now dont want to update my main Amanda server for now due to other commitments but I would like to know is it possible TO add say a bi-weekly config that will back up to a external USB 250GB hard drive. As I am likely to purchase two external USB 250GB hard drive and I would like to backup bi-weekly/fornightly a full backup to the external USB 250GB hard drive. Which I can take off-site along with the Monthly archive DAT tapes, thus leave the other bi-weekly/fornightly on site. Thus have a Daily(incremental) Bi-weekly(full) and Monthly archive(full) setup running is this feasible. I have read up on Amanda virtual stuff but would rather for now utilise Amanda version 2.4.4p2. 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: Can I change the /tmp/amanda dir somewhere on the client host to another mount point as I have disabled executables in /tmp dir
Hi List Thanks for your help and direction. As a previous post from Paul stated my /etc/fstab entries for the mounted /tmp shouldn't prevent amanda from writing the debug logs So I am going go back to basics and trouble shoot why amcheck' report `selfcheck request timed out for my web server. Cheers On Tue, 2006-09-05 at 10:50 -0400, Gene Heskett wrote: On Tuesday 05 September 2006 10:18, Chuck Amadi Systems Administrator wrote: Hi List Is it possible to set the AMANDA_DBGDIR directory (usually /tmp/amanda) to some thing else example /usr/tmp/amanda . Yes you can Chuck, but its in the configuration as you prepare to build amanda, not in the amanda.conf. So to move it, you'll need to build the tarball. 2.4.2 is now very long in the tooth anyway. Here is an example of my ./configure drivers script: #!/bin/sh # since I'm always forgetting to su amanda... if [ `whoami` != 'amanda' ]; then echo echo Warning echo Amanda needs to be configured and built by the user amanda, echo but must be installed by user root. echo exit 1 fi make clean rm -f config.status config.cache ./configure --with-user=amanda \ --with-group=disk \ --with-owner=amanda \ --with-gnu-ld \ --prefix=/usr/local \ --with-tapedev=FILE:/amandatapes \ --with-debugging=/tmp/amanda-dbg/ \ --with-tape-server=coyote \ --with-bsdtcp-security --with-amandahosts \ --with-configdir=/usr/local/etc/amanda \ --with-config=Daily \ --with-gnutar=/usr/local/bin/tar make -- Its possible that the SuSe src rpm could be rebuilt after the appropriate edits and effect the change that way, but I've never tried that, mainly because most of the rpms are also configured to accept localhost, a huge security hole but its the only way to make an rpm that will run anyplace. I can build and install a new tarball snapshot and amcheck it, on two machines in less than 20 minutes. The above script is of course for the server, the clients script is slightly simpler. I am using Amanda 2.4.2 that came with SuSE Linux ES 9 server. Which was installed using Yast. Cheers Chuck Tue, 2006-09-05 at 13:49 +0100, Chuck Amadi Systems Administrator wrote: Hi List Got a good one here! Mi boss decode to tighten up are new web server which is due to be commissioned soon thus when I re partitioned the hard disk I created new disks and thus create a /tmp dir mounted on /dev/hda9 Thus here is my /etc/ftsab thus I stopped the possibilities of runing any executables from the /tmp directory but thus amanda cant create selfchecks in /tmp/amanda /dev/hda9/tmp reiserfs noexec,auto,nouser,rw,async,nosuid 1 2 Thus I am using amanda default program using Yast2 So is there a parameter I can change on the client to use and create another directory for example /usr/tmp/amanda which /usr directory has fstab entry as below /dev/hda8 /usr reiserfs acl,user_xattr 1 2 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: Can I change the /tmp/amanda dir somewhere on the client host to another mount point as I have disabled executables in /tmp dir
Hi List I have removed /tmp/amanda directory. Thus cd /usr/lib/amanda/ and run ./amandad This re created the amanda directory and the debug file: server#/tmp/amanda # less amandad.20060906111651.debug amandad: debug 1 pid 498 ruid 37 euid 37: start at Wed Sep 6 11:16:51 2006 amandad: version 2.4.4p2 amandad: build: VERSION=Amanda-2.4.4p2 amandad:BUILT_DATE=Wed Jun 30 23:45:53 UTC 2004 amandad:BUILT_MACH=Linux eisenstein 2.6.5 #1 Thu Nov 14 12:14:04 UTC 2002 i686 i686 i386 GNU/Linux amandad:CC=gcc amandad:CONFIGURE_COMMAND='./configure' '--mandir=/usr/share/man' '--prefix=/usr' '--infodir=/usr/share/info' '--sysconfdir=/etc' '--libdir=/usr/ lib' '--libexecdir=/usr/lib/amanda' '--localstatedir=/var/lib' '--with-index-server=localhost' '--with-gnutar-listdir=/var/lib/amanda/gnutar-lists' '--wit h-smbclient=/usr/bin/smbclient' '--with-amandahosts' '--with-user=amanda' '--with-group=disk' '--with-gnutar=/bin/tar' '--disable-libtool' '--disable-shar ed' '--disable-static' amandad: paths: bindir=/usr/bin sbindir=/usr/sbin amandad:libexecdir=/usr/lib/amanda mandir=/usr/share/man amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda amandad:CONFIG_DIR=/etc/amanda DEV_PREFIX=/dev/ amandad:RDEV_PREFIX=/dev/r DUMP=/sbin/dump amandad:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF amandad:XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF amandad:SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/tar amandad:COMPRESS_PATH=/usr/bin/gzip amandad:UNCOMPRESS_PATH=/usr/bin/gzip LPRCMD=/usr/bin/lpr amandad:MAILER=/usr/bin/Mail amandad:listed_incr_dir=/var/lib/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1 amandad:DEFAULT_TAPE_SERVER=localhost amandad:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc amandad: time 29.997: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout amandad: time 29.998: error receiving message: timeout amandad: time 29.998: pid 498 finish time Wed Sep 6 11:17:21 2006 Thus is there any tell tale signs on why Amanda Client process amanadad is not working properly and causing my tape server to selfcheck request timed out message Please note that I have added ports 10080 10082 and 10083 within SuSE SLES 9 Default Firewall and I also disbaled it and it didn't make any difference. Plus it's on my side of the firewall. Cheers List. On Tue, 2006-09-05 at 12:19 -0400, Ian Turner wrote: On Tuesday 05 September 2006 10:18, Chuck Amadi Systems Administrator wrote: Is it possible to set the AMANDA_DBGDIR directory (usually /tmp/amanda) to some thing else example /usr/tmp/amanda . Yes, but you have to compile from source. When you configure the compilation, use --with-debugging=/path/to/amanda/debug/files. Cheers, --Ian -- 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: Can I change the /tmp/amanda dir somewhere on the client host to another mount point as I have disabled executables in /tmp dir
Hi List sorry I had a typo No Amanda Admin errors Just to let you know solved my issue it was my SuSE Default Firewall I ran tcpdump -X -s 1500 udp and port 10080 0 packets captured 0 packets received by filter 0 packets dropped by kernel Thus via Yast turned the Firewall off and after running my daily/monthly script file on the tape server I got No Amanda Admin Errors. Cheers List.On Wed, 2006-09-06 at 11:57 +0100, Chuck Amadi Systems Administrator wrote: Hi List Just to let you know solved my issue it was my SuSE Default Firewall I ran tcpdump -X -s 1500 udp and port 10080 0 packets captured 0 packets received by filter 0 packets dropped by kernel Thus via Yast turned the Firewall off and after running my daily/monthly script file on the tape server I got Amanda Admin Errors. Cheers List. -- 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
Can I change the /tmp/amanda dir somewhere on the client host to another mount point as I have disabled executables in /tmp dir
Hi List Got a good one here! Mi boss decode to tighten up are new web server which is due to be commissioned soon thus when I re partitioned the hard disk I created new disks and thus create a /tmp dir mounted on /dev/hda9 Thus here is my /etc/ftsab thus I stopped the possibilities of runing any executables from the /tmp directory but thus amanda cant create selfchecks in /tmp/amanda /dev/hda9/tmp reiserfs noexec,auto,nouser,rw,async,nosuid 1 2 Thus I am using amanda default program using Yast2 So is there a parameter I can change on the client to use and create another directory for example /usr/tmp/amanda which /usr directory has fstab entry as below /dev/hda8 /usr reiserfs acl,user_xattr 1 2 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: Can I change the /tmp/amanda dir somewhere on the client host to another mount point as I have disabled executables in /tmp dir
Hi List Is it possible to set the AMANDA_DBGDIR directory (usually /tmp/amanda) to some thing else example /usr/tmp/amanda . I am using Amanda 2.4.2 that came with SuSE Linux ES 9 server. Which was installed using Yast. Cheers Chuck Tue, 2006-09-05 at 13:49 +0100, Chuck Amadi Systems Administrator wrote: Hi List Got a good one here! Mi boss decode to tighten up are new web server which is due to be commissioned soon thus when I re partitioned the hard disk I created new disks and thus create a /tmp dir mounted on /dev/hda9 Thus here is my /etc/ftsab thus I stopped the possibilities of runing any executables from the /tmp directory but thus amanda cant create selfchecks in /tmp/amanda /dev/hda9/tmp reiserfs noexec,auto,nouser,rw,async,nosuid 1 2 Thus I am using amanda default program using Yast2 So is there a parameter I can change on the client to use and create another directory for example /usr/tmp/amanda which /usr directory has fstab entry as below /dev/hda8 /usr reiserfs acl,user_xattr 1 2 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: Can I change the /tmp/amanda dir somewhere on the client host to another mount point as I have disabled executables in /tmp dir
HI Paul My tmp has the correct permissions. # ls -ld tmp drwxrwxrwt 14 root root 552 Sep 5 15:30 tmp server:/ # Yes my Amanda client has stopped working since I re partitioned and set noexec and nouser for /tmp dir but I have done a fair bit since the partition. Anyway I amended the fstab and things didn't get better So for now I am ruling fstab out. Thus going to disable SuSE default Firewall I did add the ports anyway kets see. Cheers On Tue, 2006-09-05 at 16:28 +0200, Paul Bijnens wrote: On 2006-09-05 14:49, Chuck Amadi Systems Administrator wrote: Hi List Got a good one here! Mi boss decode to tighten up are new web server which is due to be commissioned soon thus when I re partitioned the hard disk I created new disks and thus create a /tmp dir mounted on /dev/hda9 Thus here is my /etc/ftsab thus I stopped the possibilities of runing any executables from the /tmp directory but thus amanda cant create selfchecks in /tmp/amanda /dev/hda9/tmp reiserfs noexec,auto,nouser,rw,async,nosuid 1 2 Why do you think that amanda tries to execute a program from /tmp/amanda? It just writes some debugging information there. And it writes a temporary file used as value for the --exclude-from option to gnutar (if excluding anything). But nothing is being executed there, AFAIK. Some (all?) programs put the working directory there too (at least some years ago, I did find some core dumps there -- ddrwxrwxrwt idn't verify in recent versions if this is still the case). Do you mean that Amanda stops working when the noexec flag is set? Or is it just that you had wrong permissions on /tmp after mounting? (should be 1777: drwxrwxrwt ) Thus I am using amanda default program using Yast2 So is there a parameter I can change on the client to use and create another directory for example /usr/tmp/amanda which /usr directory has fstab entry as below /dev/hda8 /usr reiserfs acl,user_xattr 1 2 No parameter, you have to recompile: ./configure ... --with-tmpdir=/usr/tmp/amanda ... Actually two configure options can be used: one to put the temporary files, an another to enable debugging and specify where those debuggingfiles should be: --with-tmpdir=... --with-debugging=...(defaults to value of --with-tmpdir) btw, Debian puts them in /var/lib/amanda, good enough? -- 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: amanda cygwin question(s)
Hi Robert Is your win box between a firewall or is it within the same LAN as I assume your linux/nix boxes. As I had timeout issues relating to my zope/plone server siting behind my firewall and not in my LAN. I had to increase my ipchains timeouts Thus note I am currently preparing,install/config as new fw(dmz) server to use Iptables In case you'll shout at me ;(. Cheers On Thu, 2006-07-06 at 08:20 -0400, McGraw, Robert P. wrote: I am running Amanda 2.4.5P1 server on a Solaris 10 host. I want to back up a WindowXP client using cygwin software. The files on my cygwin system look like --/etc/inetd.conf-- amanda dgram udp wait SYSTEM /local/Amanda/amanda/libexec/amandad amandad --/etc/service-- amanda 10080/udp#AMANDA backup services amandaidx 10082/tcp#AMANDA backup services amidxtape 10083/tcp#AMANDA backup services --passwd-- SYSTEM:*:18:18:,S-1-5-18:/home/root: root:*:18:18:,S-1-5-18:/home/root When I run amcheck on the amanda server I get: zorn-[42] ./sbin/amcheck -c daily coriolis Amanda Backup Client Hosts Check WARNING: coriolis: selfcheck request timed out. Host down? Client check: 1 host checked in 30.025 seconds, 1 problem found (brought to you by Amanda 2.4.5p1) If I run nc (netcat) I get: ##R##-zorn-[87] ## ./nc -v -z -u coriolis 10080 coriolis.math.purdue.edu [128.210.3.202] 10080 (amanda) open It seems that I can make a UDP connection. Also I ran ldd.sh on amandad.exe and got the following: C:/cygwin/local/Amanda/amanda-2.4.5p1/libexec/amandad.exe C:\cygwin\bin\cygwin1.dll C:\WINDOWS\system32\ADVAPI32.DLL C:\WINDOWS\system32\ntdll.dll C:\WINDOWS\system32\KERNEL32.dll C:\WINDOWS\system32\RPCRT4.dll I assume that this shows that amanda.exe does not have any unknown libraries. Any idea why the amcheck times out? Where else should I investigate? Thanks _ Robert P. McGraw, Jr. Manager, Computer System EMAIL: [EMAIL PROTECTED] Purdue University ROOM: MATH-807 Department of MathematicsPHONE: (765) 494-6055 150 N. University Street FAX: (419) 821-0540 West Lafayette, IN 47907-2067 -- 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: amanda cygwin question(s)
Hi Again whats does it say on the client's Linux of causer /tmp/amanda amandad.date.debug amcheck.date.debug I assume you have created the similar directories for your windoze box. Also can you run tcpdump to dump traffic on a network. # tcpdump host amanda_client /tmp/log_of_your_dump_packets I used tcpdump to check my client servers status and I thus was bale to sort my firewall which isn't your issue I know. I assume you are looking for tests to do from your windoze So I guess I am stuck all my windoze clients are only accessible from their work group and I backup them individualy with the ntbackup utiltiy as they are really only running standalone apps. Cheers Cheers Chuck On Thu, 2006-07-06 at 08:52 -0400, McGraw, Robert P. wrote: Chuck, Wow, I just love the internet. Send a question from the US and someone in the UK answers in minutes. My hosts are not behind a firewall and are on the same subnet. I seem to be able to get to the 10080 UDP port on the win box from my amanda server by my netcat test so I believe this part is ok but then not being a window type guy who knows. Thanks for your input. Robert _ Robert P. McGraw, Jr. Manager, Computer System EMAIL: [EMAIL PROTECTED] Purdue University ROOM: MATH-807 Department of MathematicsPHONE: (765) 494-6055 150 N. University Street FAX: (419) 821-0540 West Lafayette, IN 47907-2067 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chuck Amadi Systems Administrator Sent: Thursday, July 06, 2006 8:30 AM To: Amanda List Subject: Re: amanda cygwin question(s) Hi Robert Is your win box between a firewall or is it within the same LAN as I assume your linux/nix boxes. As I had timeout issues relating to my zope/plone server siting behind my firewall and not in my LAN. I had to increase my ipchains timeouts Thus note I am currently preparing,install/config as new fw(dmz) server to use Iptables In case you'll shout at me ;(. Cheers On Thu, 2006-07-06 at 08:20 -0400, McGraw, Robert P. wrote: I am running Amanda 2.4.5P1 server on a Solaris 10 host. I want to back up a WindowXP client using cygwin software. The files on my cygwin system look like --/etc/inetd.conf-- amanda dgram udp wait SYSTEM /local/Amanda/amanda/libexec/amandad amandad --/etc/service-- amanda 10080/udp#AMANDA backup services amandaidx 10082/tcp#AMANDA backup services amidxtape 10083/tcp#AMANDA backup services --passwd-- SYSTEM:*:18:18:,S-1-5-18:/home/root: root:*:18:18:,S-1-5-18:/home/root When I run amcheck on the amanda server I get: zorn-[42] ./sbin/amcheck -c daily coriolis Amanda Backup Client Hosts Check WARNING: coriolis: selfcheck request timed out. Host down? Client check: 1 host checked in 30.025 seconds, 1 problem found (brought to you by Amanda 2.4.5p1) If I run nc (netcat) I get: ##R##-zorn-[87] ## ./nc -v -z -u coriolis 10080 coriolis.math.purdue.edu [128.210.3.202] 10080 (amanda) open It seems that I can make a UDP connection. Also I ran ldd.sh on amandad.exe and got the following: C:/cygwin/local/Amanda/amanda-2.4.5p1/libexec/amandad.exe C:\cygwin\bin\cygwin1.dll C:\WINDOWS\system32\ADVAPI32.DLL C:\WINDOWS\system32\ntdll.dll C:\WINDOWS\system32\KERNEL32.dll C:\WINDOWS\system32\RPCRT4.dll I assume that this shows that amanda.exe does not have any unknown libraries. Any idea why the amcheck times out? Where else should I investigate? Thanks _ Robert P. McGraw, Jr. Manager, Computer System EMAIL: [EMAIL PROTECTED] Purdue University ROOM: MATH-807 Department of MathematicsPHONE: (765) 494-6055 150 N. University Street FAX: (419) 821-0540 West Lafayette, IN 47907-2067 -- 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 -- 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: /-- server / lev 0 FAILED [data write: Connection reset by peer]
Hi List I am a bit concerned as for a few days I have had to run amflush after amdump has complained as per error below: This particular server siis on the other side of the fw fence thus not in my LAN I had increased the timeouts on the firewall but I am again getting problems. Amanda Admin Report These dumps were to tape SMTLSet105. *** A TAPE ERROR OCCURRED: [[writing file: No space left on device]]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next tape Amanda expects to use is: SMTLSet106. /-- server / lev 0 FAILED [data write: Connection reset by peer] I checked the servers /tmp/amanda directory and less the debuy file But I see nothing there to alarm me!.. # less amandad.20060704144439000.debug amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 003-18910808 SEQ 1152020450 amandad: time 0.007: bsd security: remote host firewall.mycompany.co.uk user amanda local user amanda amandad: time 0.008: amandahosts security check passed amandad: time 0.008: running service /usr/local/libexec/selfcheck amandad: time 0.017: sending REP packet: Amanda 2.4 REP HANDLE 003-18910808 SEQ 1152020450 OPTIONS features=feff9ffe0f; OK / OK / OK / OK /usr/local/libexec/runtar executable OK /bin/tar executable OK /etc/amandates read/writable OK /usr/local/var/amanda/gnutar-lists/. read/writable OK /dev/null read/writable OK /tmp/amanda has more than 64 KB available. OK /tmp/amanda has more than 64 KB available. OK /etc has more than 64 KB available. amandad: time 0.019: got packet: Amanda 2.4 ACK HANDLE 003-18910808 SEQ 1152020450 amandad: time 0.019: pid 15803 finish time Tue Jul 4 14:44:39 2006 Thus any pointer would be great before something flares up!. 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
Holding area has files that are quite old Can I remove as I am doing some house keeping.
Hi List I am just doing a bit of house keeping and in my holding disk partition I have [EMAIL PROTECTED]:/backup/amanda-daily # du /backup | sort -nr | head 6417567 /backup 5400953 /backup/amanda-daily 636267 /backup/amanda-monthly/20060331 636267 /backup/amanda-monthly 297081 /backup/amanda-daily/20050923 296328 /backup/amanda-daily/20060111 294270 /backup/amanda-daily/20051027 293762 /backup/amanda-daily/20060102 293605 /backup/amanda-daily/20051227 293169 /backup/amanda-daily/20060215 Thus when I had a look in /backup/amanda-daily The files are below The first file is dated 13/07/2005 Can these files be deleted I assume that because I haven't run amlflush at some point there still in the holding disk. drwxr-xr-x 26 amanda disk 624 2006-05-24 22:45 . drwxr-xr-x 9 amanda disk 952 2006-05-12 16:21 .. drwx-- 2 amanda disk 88 2005-07-13 19:48 20050713 drwx-- 2 amanda disk 88 2005-07-14 19:50 20050714 drwx-- 2 amanda disk 88 2005-08-29 16:32 20050829 drwx-- 2 amanda disk 88 2005-09-05 19:51 20050905 drwx-- 2 amanda disk 328 2005-09-23 20:21 20050923 drwx-- 2 amanda disk 240 2005-10-24 09:59 20051018 drwx-- 2 amanda disk 376 2005-10-24 20:10 20051024 drwx-- 2 amanda disk 288 2005-10-27 20:06 20051027 drwx-- 2 amanda disk 344 2005-12-14 20:07 20051214 drwx-- 2 amanda disk 104 2005-12-15 20:11 20051215 drwx-- 2 amanda disk 392 2005-12-27 20:10 20051227 drwx-- 2 amanda disk 248 2005-12-28 20:05 20051228 drwx-- 2 amanda disk 344 2006-01-02 20:05 20060102 drwx-- 2 amanda disk 336 2006-01-04 20:22 20060104 drwx-- 2 amanda disk 296 2006-01-10 20:19 20060110 drwx-- 2 amanda disk 336 2006-01-11 20:21 20060111 drwx-- 2 amanda disk 376 2006-02-10 20:18 20060210 drwx-- 2 amanda disk 424 2006-02-15 20:20 20060215 drwx-- 2 amanda disk 424 2006-02-28 20:19 20060228 drwx-- 2 amanda disk 336 2006-03-01 20:15 20060301 drwx-- 2 amanda disk 320 2006-03-29 20:20 20060329 drwx-- 2 amanda disk 368 2006-04-14 20:13 20060414 drwx-- 2 amanda disk 320 2006-04-17 20:16 20060417 drwx-- 2 amanda disk 320 2006-05-01 20:14 20060501 Thus please advise if it's OK to cleanup and remove these files. 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
Should I run amtapetype -f /dev/nst0 to define my Monthly DDS-5 tapes as I was using DDS-4 tapes
Hi List
I have been running a Daily and Monthly config on two SuSE SLES 9
servers using DDS-4 TAPES.
I have a problem with the Monthly archives doing full backups (uptp 98%
full) I am looking at a complete back strategy using a dedicated rack
backup server LTO or DLT drives.
But for now I am going to use DDS-5 36GB Native tapes at the moment I am
using DDS-4 20GB Native tapes for my DAT/DDS drives which as stateds are
getting rather full for MonthlySet full backups for archiving.
Thus if I run the command amtapetype -f /dev/nst0 as previous did for
DDS-4 tapes.
When this is done I receive an analysis of the tape device and the tape
types.
As the output from amtapetype may well take many hours as it writes to
the complete tape a couple of times So is it worth running the above
command.
The previous output is something like this for my current DDS-4 tapes
which I am using and works.
define tapetype tape-dds4 {
comment just produced by tapetype program(hardware compression
off)
length 19015 mbytes
filemark 399 kbytes
speed 1570 kps
}
Thus should I still run amtapetype -f /dev/nst0 command to get the
precise definitions and add the new one I have just created, or just
amend/hack the MonthlySet config file.
tapetype tape-dds5
define tapetype tape-dds5 {
comment just produced by tapetype program(hardware compression
off)
length 37537 mbytes # guess or gooogle for something practical
filemark 623 kbytes
speed 1570 kps
}
or as per this URL
http://wiki.zmanda.com/index.php/Tapetype_definitions#DDS-5_170_meter_tapes
define tapetype tape-dds5 {
comment DDS5 (hardware compression off)
length 37537 mbytes
filemark 623 kbytes
speed 1758 kps
}
I have hardware compression set to off as I was told that Amanda uses
software compression in my case tar not gzip thus cant use hardware
compression as well
turn off datacompression run mt command below that controls magnetic
tape
drive operation.
server:~ # mt -f /dev/nst0 status
server:~ # mt -f /dev/nst0 datcompression 0
Compression off.
I have digested the list and told to use one *or* the other of hardware
and software compression;
general consensus on the list is that software compression is better if
you can spare the cycles.
Thus what is the best way to get my MonthlySet to use DAT/DDS-5 tapes.
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: Should I run amtapetype -f /dev/nst0 to define my Monthly DDS-5 tapes as I was using DDS-4 tapes
Hi Francis
Cheers I now got a better understanding from the replies.
Thx
On Wed, 2006-05-10 at 11:53 +0200, Francis Galiegue wrote:
Le Mercredi 10 Mai 2006 11:13, Chuck Amadi Systems Administrator a écrit :
Hi List
I have been running a Daily and Monthly config on two SuSE SLES 9
servers using DDS-4 TAPES.
I have a problem with the Monthly archives doing full backups (uptp 98%
full) I am looking at a complete back strategy using a dedicated rack
backup server LTO or DLT drives.
But for now I am going to use DDS-5 36GB Native tapes at the moment I am
using DDS-4 20GB Native tapes for my DAT/DDS drives which as stateds are
getting rather full for MonthlySet full backups for archiving.
Thus if I run the command amtapetype -f /dev/nst0 as previous did for
DDS-4 tapes.
When this is done I receive an analysis of the tape device and the tape
types.
As the output from amtapetype may well take many hours as it writes to
the complete tape a couple of times So is it worth running the above
command.
The previous output is something like this for my current DDS-4 tapes
which I am using and works.
define tapetype tape-dds4 {
comment just produced by tapetype program(hardware compression
off)
length 19015 mbytes
filemark 399 kbytes
speed 1570 kps
}
Thus should I still run amtapetype -f /dev/nst0 command to get the
precise definitions and add the new one I have just created, or just
amend/hack the MonthlySet config file.
tapetype tape-dds5
define tapetype tape-dds5 {
comment just produced by tapetype program(hardware compression
off)
length 37537 mbytes # guess or gooogle for something practical
filemark 623 kbytes
speed 1570 kps
}
or as per this URL
http://wiki.zmanda.com/index.php/Tapetype_definitions#DDS-5_170_meter_tapes
define tapetype tape-dds5 {
comment DDS5 (hardware compression off)
length 37537 mbytes
filemark 623 kbytes
speed 1758 kps
}
I have hardware compression set to off as I was told that Amanda uses
software compression in my case tar not gzip thus cant use hardware
compression as well
turn off datacompression run mt command below that controls magnetic
tape
drive operation.
server:~ # mt -f /dev/nst0 status
server:~ # mt -f /dev/nst0 datcompression 0
Compression off.
I have digested the list and told to use one *or* the other of hardware
and software compression;
general consensus on the list is that software compression is better if
you can spare the cycles.
Thus what is the best way to get my MonthlySet to use DAT/DDS-5 tapes.
Cheers
Hello,
FWIW I use a HP-DAT72x6 tape changer which uses 36/72GB tapes. I use it with
hardware compression DISABLED (I use compress server fast instead). I ran
amtapetype and obtained this:
define tapetype HP-DAT72 {
comment Produced by tapetype prog (hardware compression off)
length 37511 mbytes
filemark 625 kbytes
speed 1758 kps
}
--
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
The server on the other side of my firewall is timming out agian.
FAILURE AND STRANGE DUMP SUMMARY: server / lev 0 FAILED [server.my.co.ukNAK : amandad busy] tapeserver.sm /var lev 0 STRANGE Thus this was working fine but for some unknown reason the timeout has exceeded 300 seconds Here is my log using less command /tmp/amanda/amandad.20060316205008000.debug file amandad: time 600.049: received other packet, NAKing it addr: peer 193.131.77.174 dup 193.131.77.174, port: peer 63313 dup 63366 amandad: time 600.182: sending nack: Amanda 2.4 NAK HANDLE 003-60610808 SEQ 1142538305 ERROR amandad busy amandad: time 617.155: sending REP packet: Amanda 2.4 REP HANDLE 003-60610808 SEQ 1142538305 OPTIONS features=feff9ffe0f; / 0 SIZE 5303320 / 1 SIZE 1568330 amandad: time 627.154: dgram_recv: timeout after 10 seconds amandad: time 627.154: waiting for ack: timeout, retrying amandad: time 637.154: dgram_recv: timeout after 10 seconds amandad: time 637.154: waiting for ack: timeout, retrying amandad: time 647.154: dgram_recv: timeout after 10 seconds amandad: time 647.154: waiting for ack: timeout, retrying amandad: time 657.154: dgram_recv: timeout after 10 seconds amandad: time 660.933: waiting for ack: timeout, retrying amandad: time 670.924: dgram_recv: timeout after 10 seconds amandad: time 670.924: waiting for ack: timeout, giving up! amandad: time 670.936: pid 13540 finish time Thu Mar 16 21:01:19 2006 Thus I assume that I need to amend my IPCHAIN rule from ipchains -M -S 7200 10 300 to ipchains -M -S 7200 10 800 Cheers 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
amrecover tar: ./tmp/enterprise-file-recovery: Cannot open: Not a directory
Hi List I am attempting to recover a md5sum file I created to run a test exercise. Created myserver-file-recovery 0n the 06/03/2006 (run md5sum on the file ready for that evenings backup). On the 07/03/2006 deleted the myserver-file-recovery file [EMAIL PROTECTED]:/home/chuck # amrecover -C DailySet1 -s backupserver.my.co.uk -t AMRECOVER Version 2.4.4p2. Contacting server on backupserver.my.co.uk ... 220 backup AMANDA index server (2.4.4p2) ready. 200 Access OK Setting restore date to today (2006-03-07) 200 Working date set to 2006-03-07. Warning: no log files found for tape SMTLSet105 written 2006-02-23 Warning: no log files found for tape SMTLSet104 written 2006-02-22 Warning: no log files found for tape SMTLSet103 written 2006-02-21 Warning: no log files found for tape SMTLSet102 written 2006-02-20 Warning: no log files found for tape SMTLSet101 written 2006-02-17 Warning: no log files found for tape SMTLSet110 written 2006-02-16 Scanning /backup/amanda-daily... amrecover sethost myserver.my.co.uk 200 Dump host set to myserver.my.co.uk. amrecover setdisk / 200 Disk set to /. amrecover setdate 2006-03-06 200 Working date set to 2006-03-06. amrecover ls amrecover cd /tmp /tmp amrecover ls amrecover add myserver-file-recovery Added /tmp/myserver-file-recovery amrecover extract Extracting files using tape drive /dev/nst0 on host backupserver.my.co.uk. The following tapes are needed: SMTLSet109 Restoring files into directory /home/chuck Continue [?/Y/n]? y Extracting files using tape drive /dev/nst0 on host backupserver.my.co.uk. Load tape SMTLSet109 now Continue [?/Y/n/s/t]? y Error Message output after I put the SMTLSet109 tape. amanda tar: ./tmp/myserver-file-recovery: Cannot open: Not a directory Any Ideas whats going on I want to extract a File and please advise or point me in the right direction I have used this procedure on my other hosts and all was well except this host hides behind a firewall. 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: amrecover tar: ./tmp/enterprise-file-recovery: Cannot open: Not a directory
Hi Alexander Thanks Yes I was hoping to extract to my /home/chuck which is NFS mounted as this is also the main file and document server. Thus I have cd on my backup server /tmp directory and will try again Cheers On Tue, 2006-03-07 at 14:28 +0100, Alexander Jolk wrote: Chuck Amadi Systems Administrator wrote: I still unable to trouble shoot I can see the file and other files and directories but unable to extract. Error Message output amanda tar: ./tmp/myserver-file-recovery: Cannot open: Not a directory tar: Error exit delayed from previous errors It would seem to me you didn't have the necessary permissions to create the directory `tmp' when you did the restore. That's either because you weren't root, or you were on an NFS-mounted file-system with root squashing, or a file named `tmp' existed in your current directory. I always restore (space permitting) into my machine's local /tmp as root, in order to avoid this kind of problem. Alex -- 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: Amdump utility still hasn't run across the firewall amcheck reports no errors.
Hi Paul Your a diamond My zope/web server is now being backed up across the firewall appreciate your help and guidance Now got to get by boss to buy a Rack able LTO-2 drive server for a backup server So got my notes. Thanks. On Thu, 2006-02-23 at 13:33 +0100, Paul Bijnens wrote: On 2006-02-23 13:30, Chuck Amadi Systems Administrator wrote: Hi Paul Would thus be ipchains -M -S 10080(tcp) tcpin 1009(udp) no simply: ipchains -M -S 7200 10 300 -- 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
Amdump utility still hasn't run across the firewall amcheck reports no errors.
Hi Paul again I received via the Amanda Report this morning that my server client Failed. I am still lost in the woods. On the ipchains firewall I added ipchains -M -S tcp tcpin udp to masqueraded and set the timeouts. My Amanda Report output below: server / lev 0 FAILED [Estimate timeout from server.my.co.uk] Here is my amanda client debug file It looks OK to me: amandad: debug 1 pid 4211 ruid 501 euid 501: start at Thu Feb 23 10:35:42 2006 amandad: version 2.4.4p2 amandad: build: VERSION=Amanda-2.4.4p2 amandad:BUILT_DATE=Mon Feb 20 13:24:23 GMT 2006 amandad:BUILT_MACH=Linux server 2.4.20-4GB #1 Mon Mar 17 17:54:44 UTC 2003 i686 unknown unknown GNU/Linux amandad:CC=gcc amandad:CONFIGURE_COMMAND='./configure' '--with-user=amanda' '--with-group=disk' '--with-configdir=/etc/amanda' '--with-udpportrange=1001,1009' '--with-tcpportrange=11000,11030' amandad: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin amandad:libexecdir=/usr/local/libexec mandir=/usr/local/man amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda amandad:CONFIG_DIR=/etc/amanda DEV_PREFIX=/dev/ amandad:RDEV_PREFIX=/dev/ DUMP=UNDEF RESTORE=UNDEF VDUMP=UNDEF amandad:VRESTORE=UNDEF XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF amandad:VXRESTORE=UNDEF SAMBA_CLIENT=UNDEF GNUTAR=/bin/tar amandad:COMPRESS_PATH=/usr/bin/gzip amandad:UNCOMPRESS_PATH=/usr/bin/gzip LPRCMD=/usr/bin/lpr amandad:MAILER=/usr/bin/Mail amandad:listed_incr_dir=/usr/local/var/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=enterprise DEFAULT_CONFIG=DailySet1 amandad:DEFAULT_TAPE_SERVER=server amandad:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc amandad: time 0.024: got packet: Amanda 2.4 REQ HANDLE 003-D0990808 SEQ 1140687005 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; amandad: time 0.024: sending ack: Amanda 2.4 ACK HANDLE 003-D0990808 SEQ 1140687005 amandad: time 0.065: bsd security: remote host firewall.my.co.uk user amanda local user amanda amandad: time 0.065: amandahosts security check passed amandad: time 0.065: running service noop amandad: time 0.066: sending REP packet: Amanda 2.4 REP HANDLE 003-D0990808 SEQ 1140687005 OPTIONS features=feff9ffe0f; amandad: time 0.067: got packet: Amanda 2.4 ACK HANDLE 003-D0990808 SEQ 1140687005 amandad: time 0.068: pid 4211 finish time Thu Feb 23 10:35:42 2006 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: Amdump utility still hasn't run across the firewall amcheck reports no errors.
Hi Here is my sendsize log. sendsize[2481]: time 220.652: Total bytes written: 5132001280 (4.8GB, 22MB/s) sendsize[2481]: time 220.726: . sendsize[2481]: estimate time for / level 0: 220.672 sendsize[2481]: estimate size for / level 0: 5011720 KB sendsize[2481]: time 220.727: waiting for /bin/tar / child sendsize[2481]: time 220.727: after /bin/tar / wait sendsize[2481]: time 220.736: done with amname '/', dirname '/', spindle -1 sendsize[2479]: time 220.822: child 2481 terminated normally sendsize: time 220.823: pid 2479 finish time Wed Feb 22 21:04:3 On the firewall run less /var/log/messages and search for udp and port 1001 and 1009 no UDP Packets log entries unless I need to search for something else. Cheers On Thu, 2006-02-23 at 11:42 +0100, Paul Bijnens wrote: On 2006-02-23 11:36, Chuck Amadi Systems Administrator wrote: Hi Paul again I received via the Amanda Report this morning that my server client Failed. I am still lost in the woods. On the ipchains firewall I added ipchains -M -S tcp tcpin udp to masqueraded and set the timeouts. My Amanda Report output below: server / lev 0 FAILED [Estimate timeout from server.my.co.uk] Here is my amanda client debug file It looks OK to me: There should be more debug files. This is the succeeded noop request (for the exchange of the features between client and host). There should also be a sendsize request in another amanda.*.debug file. That one should contain timestamps. Verify if the ACK is sent within the udp timeout from ipchains. Do you see that UDP packet logged in the firewall logs? amandad: time 0.024: got packet: Amanda 2.4 REQ HANDLE 003-D0990808 SEQ 1140687005 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; The text between the hyhens is the REQuest packet and you see the line SERVICE noop. amandad: time 0.024: sending ack: Amanda 2.4 ACK HANDLE 003-D0990808 SEQ 1140687005 ANd this is the ACK package, sent back immediatly (without the millisecond). amandad: time 0.065: bsd security: remote host firewall.my.co.uk user amanda local user amanda amandad: time 0.065: amandahosts security check passed amandad: time 0.065: running service noop amandad: time 0.066: sending REP packet: Amanda 2.4 REP HANDLE 003-D0990808 SEQ 1140687005 OPTIONS features=feff9ffe0f; And here is the reply package, 0.021 seconds later. amandad: time 0.067: got packet: Amanda 2.4 ACK HANDLE 003-D0990808 SEQ 1140687005 And an ACK from the server indicating good delivery over there. amandad: time 0.068: pid 4211 finish time Thu Feb 23 10:35:42 2006 And all this took only 0.068 seconds. Now find the amanda.*.debug file for the SERVICE sendsize, and look for the timestamps. Find out where the connection is lost. -- 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: Still get ERROR [host fw.my.co.uk: port 62679 not secure]
Hi List This morning I got my AMANDA MAIL REPORT and server had failed. Thus I have less /tmp/amanda/amandad.20060220210110.debug Here is the output from the server client debug I have since changed the Estimate timeout parameter from 300 to etimeout 380 on my ~tape server/amanda.conf Thus doubled the amandad: time 180.183: dgram_recv in debug report. amandad: RDEV_PREFIX=/dev/ DUMP=UNDEF RESTORE=UNDEF VDUMP=UNDEF amandad: VRESTORE=UNDEF XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF amandad: VXRESTORE=UNDEF SAMBA_CLIENT=UNDEF GNUTAR=/bin/tar amandad: COMPRESS_PATH=/usr/bin/gzip amandad: UNCOMPRESS_PATH=/usr/bin/gzip LPRCMD=/usr/bin/lpr amandad: MAILER=/usr/bin/Mail amandad: listed_incr_dir=/usr/local/var/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=server DEFAULT_CONFIG=DailySet1 amandad: DEFAULT_TAPE_SERVER=server amandad: DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM amandad: LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad: AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad: CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP amandad: COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad: COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc amandad: time 0.000: got packet: Amanda 2.4 REQ HANDLE 003-30610808 SEQ 1140464706 SECURITY USER amanda SERVICE sendsize OPTIONS features=feff9ffe0f;maxdumps=1;hostname=server.my.co.uk; GNUTAR / 0 1970:1:1:0:0:0 -1 OPTIONS |;bsd-auth;index;exclude-list=/usr/local/lib/amanda/exclude.gtar; amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 003-30610808 SEQ 1140464706 amandad: time 0.053: bsd security: remote host fw.my.co.uk user amanda local user amanda amandad: time 0.053: amandahosts security check passed amandad: time 0.053: running service /usr/local/libexec/sendsize amandad: time 170.173: sending REP packet: Amanda 2.4 REP HANDLE 003-30610808 SEQ 1140464706 OPTIONS features=feff9ffe0f; / 0 SIZE 5006670 amandad: time 180.183: dgram_recv: timeout after 10 seconds amandad: time 180.194: waiting for ack: timeout, retrying amandad: time 190.193: dgram_recv: timeout after 10 seconds amandad: time 190.193: waiting for ack: timeout, retrying amandad: time 200.193: dgram_recv: timeout after 10 seconds amandad: time 200.193: waiting for ack: timeout, retrying amandad: time 210.193: dgram_recv: timeout after 10 seconds amandad: time 210.193: waiting for ack: timeout, retrying amandad: time 220.193: dgram_recv: timeout after 10 seconds amandad: time 223.994: waiting for ack: timeout, giving up! amandad: time 223.994: pid 29022 finish time Mon Feb 20 21:04:54 2006 amandad.20060220210110.debug lines 12-61/61 (END) Thus is there anything else I can do as amcheck is working but amdump which I believe is the issue relating to TCP but I have ports open on my firewall 10080:10083 I have also read that via MAILING LIST - *Mailing List Blurb *** It seems that the client receives an ACK, but the ACK is not what the client thinks it ought to be. After that it times out. *** Cheers for you help. On Mon, 2006-02-20 at 15:03 +0100, Paul Bijnens wrote: On 2006-02-20 14:51, Chuck Amadi Systems Administrator wrote: Amanda Backup Client Hosts Check ERROR: server.my.co.uk: [access as amanda not allowed from [EMAIL PROTECTED] co.uk] open of /home/amanda/.amandahosts failed Client check: 4 hosts checked in 10.078 seconds, 1 problem found I created a dir and file /var/lib/amanda/.amandahosts file I have of course not got a /home/amanda/.amandahosts on my fw.my.co.uk server So should I created a user and the necessary dir and files. What is the home directory of the user Amanda? i.e. what is the sixth field in /etc/passwd of that client (not the server!)? So on that client, add the next line to the .amandahosts file: amanda fw.my.co.uk Thus added to .amandahosts file: I haven't create a user amanda or group disk Yet But am I on the right track with this new amacheck error. localhost amanda localhost root server.my.co.uk amanda server.my.co.uk root tape-server.myl.co.uk amanda tape-server.my.co.uk root See also: http://wiki.zmanda.com/index.php/Amcheck:_access_as_localuser_not_allowed_from_remoteuser%40remotehost -- 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: request failed: timeout waiting for ACK
Hi Have you had a look at your amanda tape server amanda.conf file and amending the etimeout parameter default is usually 300 seconds. I run less command on /tmp/amanda/amanda-date-.debug and my client was timing out on 180.33 seconds So I had read a good possibility is that udp which is stateless is taken to my time and hences times out. Worth a try I hope it helps I have a similar problem amcheck states no errors found but whem amdump tries to do it's thing I get a timeout error as below: amandad: time 180.183: dgram_recv in debug report. So I am googggling around and reading amanda mailing list for a solution to my issue I am nearly there. All the best. On Tue, 2006-02-21 at 09:45 +0100, Stefan Herrmann wrote: hello list, i made a fresh install of Amanda 2.5.0b2 on a debian 3.1 system. then i set up amanda for a hourly backup. i did some test backups that worked ok. then i mentioned an error in the amanda.conf and aborted the dump manually. stopped all amanda processes on the client manually and corrected the error. since then i get lots of (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) when doing backups: [EMAIL PROTECTED]:~$ amstatus hourly Using /usr/local/etc/amanda/hourly/amdump.1 from Tue Feb 21 09:22:36 CET 2006 pille.hq.imos.net:/0 driver: (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) pille.hq.imos.net:/opt 0 driver: (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) pille.hq.imos.net:/usr 0 driver: (aborted:[request failed: timeout waiting for ACK])(too many dumper retry) pille.hq.imos.net:/var 1 45m finished (9:28:16) SUMMARY part real estimated size size partition : 4 estimated : 455036m flush : 0 0m failed : 355015m ( 99.96%) wait for dumping: 00m ( 0.00%) dumping to tape : 00m ( 0.00%) dumping : 0 0m 0m ( 0.00%) ( 0.00%) dumped : 145m20m (220.31%) ( 0.08%) wait for writing: 0 0m 0m ( 0.00%) ( 0.00%) wait to flush : 0 0m 0m (100.00%) ( 0.00%) writing to tape : 0 0m 0m ( 0.00%) ( 0.00%) failed to tape : 0 0m 0m ( 0.00%) ( 0.00%) taped : 145m20m (220.31%) ( 0.08%) tape 1: 145m20m ( 0.04%) hourly009 6 dumpers idle : no-dumpers taper idle network free kps: 14000 holding space :258607m (100.00%) chunker0 busy : 0:00:00 ( 0.00%) dumper0 busy : 0:03:10 ( 36.36%) taper busy : 0:00:02 ( 0.55%) 0 dumpers busy : 0:08:37 ( 98.82%)not-idle: 0:05:31 ( 64.11%) client-constrained: 0:02:01 ( 23.49%) start-wait: 0:00:34 ( 6.57%) no-dumpers: 0:00:30 ( 5.83%) 1 dumper busy : 0:00:05 ( 1.05%) start-wait: 0:00:05 ( 99.46%) i already rebooted the amanda server and cant find any more processes running on the client. also did a restart of inetd on the client. does anyone have a clue whats the problem ? os what this abort message means ? thanks and by Stefan Herrmann -- 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: Still get ERROR [host fw.my.co.uk: port 62679 not secure] after I added my ipchain rule:
Hi Paul
I just want my server that is the other side of my Lan which of cause is
where the tape server resides which is separated by my ipchains
firewall. To allow responses from the server through the firewall to my
tape server.
I have re compiled with the UDP and TCP portrange switch and edit the
common-src/security.c file with the 1 || within line 232 if statement.
When I run tcpdump port 10080 on the server and then in another window
on the tape server amcheck DailySet1 I see on the server that insecure
port 6 is still being used and not the one I defined when I re
compiled amanda client using port range and commn-src/security.c file.
Any other suggestions other than migrating the firewall to iptable which
I will don eventually after a lot of other things on my to do list.
Cheers
On Fri, 2006-02-17 at 13:26 +0100, Paul Bijnens wrote:
On 2006-02-17 13:23, Chuck Amadi Systems Administrator wrote:
As you stated it's still forking to the firewall ipnumber and not the
tape server.
(...forking... ???I'm afraid I don't understand that word in
this context...)
Yes, as expected, the client sees the request coming from the
NAT-firewall itself, but is that a problem?
Cheers for your help
On Thu, 2006-02-16 at 17:52 +0100, Paul Bijnens wrote:
On 02/16/2006 05:02 PM, Chuck Amadi Systems Administrator wrote:
Hi List sorry for the continuous cries for help.
Regarding Amanda and ipchains rules it didn't work Amanda client on
server was still
forking to secure ports that weren't in my udp range. I run tcpdump
port 10080 on server.
ERROR [host firewall.my.co.uk: port 64524 not secure]
So the firewall does NAT (that is why, from the client's point of view,
the ipnumber is the firewall itself, and not the amanda server, and the
portnumber is 6).
So, as already said, you should patch the client amanda software only
for that host (i.e. no need to install that version on any other machine
or amanda server), to disable the check for a udp source port 1024:
For amanda 2.4.5p1, edit the file common-src/security.c:
You find this section:
229
230 /* next, make sure the remote port is a reserved one */
231
232 if(ntohs(addr-sin_port) = IPPORT_RESERVED) {
233 ap_snprintf(number, sizeof(number), %d,
ntohs(addr-sin_port));
234 *errstr = vstralloc([,
235 host , remotehost, : ,
236 port , number, not secure,
237 ], NULL);
238 amfree(remotehost);
239 return 0;
240 }
and make test test succeed always, by changing line 232:
232 if(1 || ntohs(addr-sin_port) = IPPORT_RESERVED) {
i.e. add the 1 || string to the if statement.
--
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: Still get ERROR [host fw.my.co.uk: port 62679 not secure] after I added my ipchain rule:
Hi Paul
[EMAIL PROTECTED]:/root /usr/sbin/amcheck DailySet1
Amanda Tape Server Host Check
-
Holding disk /backup/amanda-daily: 5216316 KB disk space available,
that's plent
y
NOTE: skipping tape-writable test
Tape SMTLSet102 label ok
WARNING: info
file /var/lib/amanda/DailySet1/curinfo/server.my.co.uk/_/inf
o: does not exist
Server check took 8.838 seconds
Amanda Backup Client Hosts Check
ERROR: server.my.co.uk: [access as amanda not allowed from [EMAIL PROTECTED]
co.uk] open of /home/amanda/.amandahosts failed
Client check: 4 hosts checked in 10.078 seconds, 1 problem found
I created a dir and file /var/lib/amanda/.amandahosts file I have of
course not got a /home/amanda/.amandahosts on my fw.my.co.uk server So
should I created a user and the necessary dir and files.
Thus added to .amandahosts file:
I haven't create a user amanda or group disk Yet But am I on the right
track with this new amacheck error.
localhost amanda
localhost root
server.my.co.uk amanda
server.my.co.uk root
tape-server.myl.co.uk amanda
tape-server.my.co.uk root
Cheers Paul and List.
On Mon, 2006-02-20 at 12:33 +0100, Paul Bijnens wrote:
On 2006-02-20 12:29, Paul Bijnens wrote:
On Thu, 2006-02-16 at 17:52 +0100, Paul Bijnens wrote:
You find this section:
229
230 /* next, make sure the remote port is a reserved one */
231
232 if(ntohs(addr-sin_port) = IPPORT_RESERVED) {
233 ap_snprintf(number, sizeof(number), %d,
ntohs(addr-sin_port));
234 *errstr = vstralloc([,
235 host , remotehost, : ,
236 port , number, not secure,
237 ], NULL);
238 amfree(remotehost);
239 return 0;
240 }
and make test test succeed always, by changing line 232:
232 if(1 || ntohs(addr-sin_port) = IPPORT_RESERVED) {
i.e. add the 1 || string to the if statement.
Oops, that should have been: 0 , not 1 ||.
The ideas is to make this always fail, not always succeed.
PS. btw, any mail to [EMAIL PROTECTED] bounces!
--
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: Still get ERROR [host fw.my.co.uk: port 62679 not secure] after I added my ipchain rule:
Hi Paul
I'm running 2.4.4p2 on my amanda clients and tape server.
Anyway the file exists in my version,rin make clean I edited the
common-src/security.c file and added 1 || string to the if statement
to line 232.
Thus run make make clean make install and run on my server client
that sits on the other side of Firewall.
./configure --with-user=amanda --with-group=disk
--with-configdir=/etc/amanda --with-uspportrange=11000,111030
--with-tcpportrange=11000,11030
Thus tcpdump port 10080 on the amanda client and run amcheck Config on
the tape server.
As you stated it's still forking to the firewall ipnumber and not the
tape server.
Cheers for your help
On Thu, 2006-02-16 at 17:52 +0100, Paul Bijnens wrote:
On 02/16/2006 05:02 PM, Chuck Amadi Systems Administrator wrote:
Hi List sorry for the continuous cries for help.
Regarding Amanda and ipchains rules it didn't work Amanda client on server
was still
forking to secure ports that weren't in my udp range. I run tcpdump
port 10080 on server.
ERROR [host firewall.my.co.uk: port 64524 not secure]
So the firewall does NAT (that is why, from the client's point of view,
the ipnumber is the firewall itself, and not the amanda server, and the
portnumber is 6).
So, as already said, you should patch the client amanda software only
for that host (i.e. no need to install that version on any other machine
or amanda server), to disable the check for a udp source port 1024:
For amanda 2.4.5p1, edit the file common-src/security.c:
You find this section:
229
230 /* next, make sure the remote port is a reserved one */
231
232 if(ntohs(addr-sin_port) = IPPORT_RESERVED) {
233 ap_snprintf(number, sizeof(number), %d,
ntohs(addr-sin_port));
234 *errstr = vstralloc([,
235 host , remotehost, : ,
236 port , number, not secure,
237 ], NULL);
238 amfree(remotehost);
239 return 0;
240 }
and make test test succeed always, by changing line 232:
232 if(1 || ntohs(addr-sin_port) = IPPORT_RESERVED) {
i.e. add the 1 || string to the if statement.
--
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: Still get ERROR [host fw.my.co.uk: port 62679 not secure] after I added my ipchain rule:
Hi Paul
Nah still getting ipnumber of the firewall not tape server.
# tcpdump port 10080
tcpdump: listening on eth0
13:37:12.636083 firewall.my.co.uk.62374 server.my.co.uk.amanda: udp
117 (DF)
13:37:22.740457 firewall.my.co.uk.62374 server.my.co.uk.amanda: udp
117 (DF)
13:37:32.800639 firewall.my.co.uk.62374 server.my.co.uk.amanda: udp
117 (DF)
Thus DF means packets are still fragmented and not getting through.
Any other ideas.
Cheers for your help
Thu, 2006-02-16 at 17:52 +0100, Paul Bijnens wrote:
On 02/16/2006 05:02 PM, Chuck Amadi Systems Administrator wrote:
Hi List sorry for the continuous cries for help.
Regarding Amanda and ipchains rules it didn't work Amanda client on server
was still
forking to secure ports that weren't in my udp range. I run tcpdump
port 10080 on server.
ERROR [host firewall.my.co.uk: port 64524 not secure]
So the firewall does NAT (that is why, from the client's point of view,
the ipnumber is the firewall itself, and not the amanda server, and the
portnumber is 6).
So, as already said, you should patch the client amanda software only
for that host (i.e. no need to install that version on any other machine
or amanda server), to disable the check for a udp source port 1024:
For amanda 2.4.5p1, edit the file common-src/security.c:
You find this section:
229
230 /* next, make sure the remote port is a reserved one */
231
232 if(ntohs(addr-sin_port) = IPPORT_RESERVED) {
233 ap_snprintf(number, sizeof(number), %d,
ntohs(addr-sin_port));
234 *errstr = vstralloc([,
235 host , remotehost, : ,
236 port , number, not secure,
237 ], NULL);
238 amfree(remotehost);
239 return 0;
240 }
and make test test succeed always, by changing line 232:
232 if(1 || ntohs(addr-sin_port) = IPPORT_RESERVED) {
i.e. add the 1 || string to the if statement.
--
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: Still get ERROR [host fw.my.co.uk: port 62679 not secure] after I added my ipchain rule:
Hi
Yesterday Someone posted a amadmin command to egrep
--with-udpportrange=,
So I can check my tape server.
Please could you resend the amadmin ConfigName | egrep -i
--with-udpportrange=1001,1009
something like that thx.
amadmin conf command {args} ...
I also run the tcpdump port 10080 on the amanda client and then on the
amanda tape server on amcheck ConfigName and I could see that the port
on my main tape server was 957 which is privileged port.
The port was not 1001, 1009 on the amanda tape server.
Cheers
On Tue, 2006-02-14 at 17:19 +0100, Paul Bijnens wrote:
On 02/14/2006 04:56 PM, Chuck Amadi Systems Administrator wrote:
I have just edited my firewall and added a ipchain rule but I still got
an error as below:
Amanda Backup Client Hosts Check
ERROR: server.my.co.uk: [host fw.smtl.co.uk: port 62679 not secure]
This seems to be a result of the NAT in ipchains:
it changes the source port to someting over 6.
However, why is the name fw.smtl.co.uk? I did not know that
ipchains used uses NAT for traffic to the firewall itself too?
Make really really sure that the amandaserver does bind to a port
from the udp-port range:
In one window start as root:
# tcpdump port 10080
In another window, to the amcheck.
And verify the that port on the amandaserver is one from 1001-1009.
This could also happen when amcheck lost the suid root bit
(but I believe that it would complain about that before you get
that far).
A possible workaround here is to recompile the
software on the client to not fail on a non secure port.
That notion of secure port (ports 1024 require root
priviledge to open), is in these days not a strong
security check anyway, where anyone can install a workstation
or boot from a live-CD and be root to open any port 1024.
I have setup my fw rules as below:
# Amanda Client - Enterprise random udp forks to Nemesis Server
ipchains -A input -i $EXTERNAL_INTERFACE -p udp -s 193.XX.XX.XXX
1001:1009 -j ACCEPT
ipchains -A input -i $EXTERNAL_INTERFACE -p udp -s 193.XX.XX.XXX
10080:10083 -j ACCEPT
Outgoing packets are allowed from behind our firewall and all forwaded
to our main file server that is the same server for amanda backup tape
server
I do not remember anymore, but maybe there is a possibility
to not do NAT for a certain portrange/host ?
I re compiled amanda client as below:
./configure --with-user=amanda --with-group=disk
--with-configdir=/etc/amanda --with-udpportrange=1001, 1009
--with-tcpportrange=11000, 11300
--
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
Still get ERROR [host fw.my.co.uk: port 62679 not secure] after I added my ipchain rule:
Hi List sorry for the continuous cries for help. Regarding Amanda and ipchains rules it didn't work Amanda client on server was still forking to secure ports that weren't in my udp range. I run tcpdump port 10080 on server. Then run /usr/sbin/amcheck DailySet1 on tape-server tape server. server output below: tcpdump: listening on eth0 16:41:14.529918 firewall.my.co.uk.64524 server.my.co.uk.amanda: udp 117 (DF) 16:41:14.537221 server.my.co.uk.amanda firewall.my.co.uk.64524: udp 50 (DF) 16:41:14.543520 server.my.co.uk.amanda firewall.my.co.uk.64524: udp 100 (DF) Thus on server less /tmp/amanda/amandad.20060216164114.debug Amanda 2.4 REQ HANDLE 003-D0990808 SEQ 1140104146 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 003-D0990808 SEQ 1140104146 amandad: time 0.006: sending REP packet: Amanda 2.4 REP HANDLE 003-D0990808 SEQ 1140104146 ERROR [host firewall.my.co.uk: port 64524 not secure] It should have forked to the ports in udp port range that I had compiled with the switch --with-udpportrange=1001,1009 . I am still trouble shooting and awaiting info on mailing list. I had edit my firewall and added the following ipchain rules Outgoing mail has no restrictions. 1001 and 1009 is what I used for the udp port range and I use 11000 11030 for tcp port range I am led to believe that this doesn't cause any isses with the ussally amanda ports 10080,10082 and 10083. ipchains -A input -i $EXTERNAL_INTERFACE -p udp -s 193.xx.xx.xxx 1001:1009 -j ACCEPT ipchains -A input -i $EXTERNAL_INTERFACE -p udp -s 193.xx.xx.xxx 10080:10083 -j ACCEPT Any other tips in order to get through the firewall until one day move to iptables. 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: [Fwd: Re: WARNING: server.my.co.uk: selfcheck request timed out. Host down? this is a private IP address.]
Hi Paul Bijnes Was the UDP also to be recompiled --with-udpportrange=11000,11030 thus the same port range as tcp. Cheers On Tue, 2006-02-14 at 08:19 +, chuck.amadi wrote: email message attachment (Re: WARNING: server.my.co.uk: selfcheck request timed out. Host down? thisis a private IP address.) On Tue, 2006-02-14 at 08:19 +, chuck.amadi wrote: -- 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: WARNING: server.my.co.uk: selfcheck request timed out. Host down? this is a private IP address.
Hi I have re compiled amanda client on the server that sits outside of
my LAN with the following port range. --with-udpportrange=1100,11030
Thus you stating that it must be a system udp port range i.e 1023
If So I have Unassigned range -f 1001-1009 So I would use this when I re
compile a udp system port range --with-udpportrange=1001,1009 Does the
tcp port range stay the same. --with-tcpportrange=1100,11030 .
My IPChain example.
ipchains -A input -p udp -i -s $193.XXX.XXX.XXX{AMANDA_CLIENT} 1001:1009
--dport $192.168.1.XXX{AMANDA_SERVER} -j ACCEPT
ipchains -A input -p tcp -i -s $193.XXX.XXX.XXX {AMANDA_CLIENT}
10080:10083 --dport $192.168.1.XXX{AMANDA_SERVER} -j ACCEPT
CheersOn Tue, 2006-02-14 at 10:44 +0100, Paul Bijnens wrote:
On 02/14/2006 10:25 AM, Chuck Amadi Systems Administrator wrote:
Hi Agian
I am re compiling my amanda client thus after running the switch
--with-udpportrange=11000,110030 and --with-tcpportrange=11000,110030
I edit the /etc/services on the amanda client and add the following:
# Leave this lot intact:
amanda 10080/tcp # Amanda
the 10080/tcp is not used.
amanda 10080/udp # Amanda
amandaidx 10082/tcp
amidxtape 10083/tcp
# Check that these port ranges are Unassigned.
amanda 11000-11030/tcp # Amanda
(--with-tcpportrange=11000,110030)
amanda 11000-11030/udp # Amanda
(--with-udpportrange=11000,110030)
I think these two will give a syntax error in /etc/services :-)
You cannot give a name to a range (and the name amanda must
be for the 10080/udp port!)
Moreover, it is not strictly needed that the range is unassigned.
When Amanda wants to use a port in the range that is already in
use by something else, it will simply skip that port.
But because you need 3 tcp connections for each dump in parallel,
(inparallel in amanda.conf) you must add some extra ports in
the range to take into account the ports that are already in use.
--
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: Still get ERROR [host fw.my.co.uk: port 62679 not secure] after I added my ipchain rule:
Hi List I would like to mention that the selected port range udp 1001,1009 and tcp 11000,11300 have only been re compiled on the Amanda client, thus I haven't been opened on both amanda client and amanda server ends of the firewall. I didn't want to re compile a productive amanda tape server plus I used the default software within SuSE Linux Enterprise Server 9. So if I have to open the selected port range on the amanda tape server can I just edit /etc/services and add the 1001 and 1009 systems privileged ports. or have I got to run the --with-udpportrange=1001,1009 thus having to start from scratch which is not really feasible. amanda 1001/udp # Amanda amanda 1009/udp # Amanda Cheers On Tue, 2006-02-14 at 15:56 +, Chuck Amadi Systems Administrator wrote: Hi all I have just edited my firewall and added a ipchain rule but I still got an error as below: Amanda Backup Client Hosts Check ERROR: server.my.co.uk: [host fw.smtl.co.uk: port 62679 not secure] Client check: 4 hosts checked in 10.780 seconds, 1 problem found Here is also my Amanda Debug file: less /tmp/amanda/amandad.20060214163540.debug Amanda 2.4 REQ HANDLE 003-D0990808 SEQ 1139931009 SECURITY USER amanda SERVICE noop OPTIONS features=ecfffeff9ffe0f; amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 003-D0990808 SEQ 1139931009 amandad: time 0.006: sending REP packet: Amanda 2.4 REP HANDLE 003-D0990808 SEQ 1139931009 ERROR [host fw.my.co.uk: port 62679 not secure] amandad: time 0.007: got packet: Amanda 2.4 ACK HANDLE 003-D0990808 SEQ 1139931009 I have setup my fw rules as below: # Amanda Client - Enterprise random udp forks to Nemesis Server ipchains -A input -i $EXTERNAL_INTERFACE -p udp -s 193.XX.XX.XXX 1001:1009 -j ACCEPT ipchains -A input -i $EXTERNAL_INTERFACE -p udp -s 193.XX.XX.XXX 10080:10083 -j ACCEPT Outgoing packets are allowed from behind our firewall and all forwaded to our main file server that is the same server for amanda backup tape server I re compiled amanda client as below: ./configure --with-user=amanda --with-group=disk --with-configdir=/etc/amanda --with-udpportrange=1001, 1009 --with-tcpportrange=11000, 11300 I haven't edited the /etc/services as I had read this does not effect initial UDP request made from the amanda tape server. I have read and digested learnt a few things but I am still having issues using Amanda between hosts separated by a firewall using ipchains. Cheers for your help. -- 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: Still get ERROR [host fw.my.co.uk: port 62679 not secure] after I added my ipchain rule:
Hi all I have just edited my firewall and added a ipchain rule but I still got an error as below: Amanda Backup Client Hosts Check ERROR: server.my.co.uk: [host fw.smtl.co.uk: port 62679 not secure] Client check: 4 hosts checked in 10.780 seconds, 1 problem found Here is also my Amanda Debug file: less /tmp/amanda/amandad.20060214163540.debug Amanda 2.4 REQ HANDLE 003-D0990808 SEQ 1139931009 SECURITY USER amanda SERVICE noop OPTIONS features=ecfffeff9ffe0f; amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 003-D0990808 SEQ 1139931009 amandad: time 0.006: sending REP packet: Amanda 2.4 REP HANDLE 003-D0990808 SEQ 1139931009 ERROR [host fw.my.co.uk: port 62679 not secure] amandad: time 0.007: got packet: Amanda 2.4 ACK HANDLE 003-D0990808 SEQ 1139931009 I have setup my fw rules as below: # Amanda Client - Enterprise random udp forks to Nemesis Server ipchains -A input -i $EXTERNAL_INTERFACE -p udp -s 193.XX.XX.XXX 1001:1009 -j ACCEPT ipchains -A input -i $EXTERNAL_INTERFACE -p udp -s 193.XX.XX.XXX 10080:10083 -j ACCEPT Outgoing packets are allowed from behind our firewall and all forwaded to our main file server that is the same server for amanda backup tape server I re compiled amanda client as below: ./configure --with-user=amanda --with-group=disk --with-configdir=/etc/amanda --with-udpportrange=1001, 1009 --with-tcpportrange=11000, 11300 I haven't edited the /etc/services as I had read this does not effect initial UDP request made from the amanda tape server. I have read and digested learnt a few things but I am still having issues using Amanda between hosts separated by a firewall using ipchains. Cheers for your help. -- 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
WARNING: server.my.co.uk: selfcheck request timed out. Host down? this is a private IP address.
Hi List I have added a new Amanda client that doesn't belong to my LAN it's our zope/web server that has a public address and is on another network it's entry is in my dns server and in the /etc/hosts file which I thought would be it's first port of call before asking the ns server. Both LAN and zope/web server sit behind our firewall. Could be that because it's on another network LAN's 192.168.1.xx broadcast 255.255.255.0 and 123.345.567.89 225.225.225.224 or can I possible use the public IPA instead of server.my.co.uk in the DLE on the tape server. I am assuming this is something to do with my firewall. I have amandad running on the new amanda client. but I get the following error when amcheck runs fron the cron. I have created /var/lib/amanda/DailySet1/curinfo/server.my.co.uk/_ directory and chown amanda.disk. Also when I run the following commands server:/etc/xinetd.d # netstat -a | grep -i amanda tcp0 0 *:amandaidx *:* LISTEN udp0 0 *:amanda *:* server:/etc/xinetd.d # server:/etc/xinetd.d # ps auxxx|egrep amanda amanda 14847 0.0 0.3 4160 872 pts/3S12:30 0:00 [su] amanda 14848 0.0 0.6 4620 1584 pts/3S12:30 0:00 bash root 18452 0.0 0.1 3540 500 pts/3S15:51 0:00 /bin/grep -E amanda server:/etc/xinetd.d # Error Message below: WARNING: info file /var/lib/amanda/DailySet1/curinfo/server.my.co.uk/_/info: does not exist Server check took 10.788 seconds Amanda Backup Client Hosts Check WARNING: server.my.co.uk: selfcheck request timed out. Host down? Client check: 4 hosts checked in 29.328 seconds, 1 problem found -- 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: WARNING: server.my.co.uk: selfcheck request timed out. Host down? this is a private IP address.
Hi List I had a look on the amanda client less /tmp/amanda less amandad.20060213153537.debug Here is the debug report: Amanda 2.4 REQ HANDLE 003-E0990808 SEQ 1139841004 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; amandad: time 9.815: it is not an ack amandad: time 9.815: sending REP packet: Amanda 2.4 REP HANDLE 003-E0990808 SEQ 1139841004 ERROR [host fw.my.co.uk: port * not secure] amandad: time 18.975: got packet: Amanda 2.4 REQ HANDLE 003-E0990808 SEQ 1139841004 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; amandad: time 18.975: it is not an ack amandad: time 18.975: sending REP packet: Thus I assume I need to add rules for the Firewall server: Any examples or notes Cheers On Mon, 2006-02-13 at 14:51 +, Chuck Amadi Systems Administrator wrote: Hi List I have added a new Amanda client that doesn't belong to my LAN it's our zope/web server that has a public address and is on another network it's entry is in my dns server and in the /etc/hosts file which I thought would be it's first port of call before asking the ns server. Both LAN and zope/web server sit behind our firewall. Could be that because it's on another network LAN's 192.168.1.xx broadcast 255.255.255.0 and 123.345.567.89 225.225.225.224 or can I possible use the public IPA instead of server.my.co.uk in the DLE on the tape server. I am assuming this is something to do with my firewall. I have amandad running on the new amanda client. but I get the following error when amcheck runs fron the cron. I have created /var/lib/amanda/DailySet1/curinfo/server.my.co.uk/_ directory and chown amanda.disk. Also when I run the following commands server:/etc/xinetd.d # netstat -a | grep -i amanda tcp0 0 *:amandaidx *:* LISTEN udp0 0 *:amanda *:* server:/etc/xinetd.d # server:/etc/xinetd.d # ps auxxx|egrep amanda amanda 14847 0.0 0.3 4160 872 pts/3S12:30 0:00 [su] amanda 14848 0.0 0.6 4620 1584 pts/3S12:30 0:00 bash root 18452 0.0 0.1 3540 500 pts/3S15:51 0:00 /bin/grep -E amanda server:/etc/xinetd.d # Error Message below: WARNING: info file /var/lib/amanda/DailySet1/curinfo/server.my.co.uk/_/info: does not exist Server check took 10.788 seconds Amanda Backup Client Hosts Check WARNING: server.my.co.uk: selfcheck request timed out. Host down? Client check: 4 hosts checked in 29.328 seconds, 1 problem found -- 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
Backup a public server outside of my LAN by adding it to my DLE
Hi List I have another server that I need to add to my current main Amanda backup server. This server unlike the servers which are within my LAN and thus on the same network. Sits outside the LAN and is a public server. Thus is it still possible to just add the server outside of my LAN to disklist file: as I assume providing I add the xinetd and ports I should be able to backup a server ouside of my LAN. outsideserver.mycompany.co.uk /projects root-tar # /projects outsideserver.mycompany.co.uk /backup root-tar # /backup outsideserver.mycompany.co.uk /tmp root-tar # /tmp outsideserver.mycompany.co.uk /var root-tar # /var outsideserver.mycompany.co.uk /data root-tar # /data 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: Backup a public server outside of my LAN by adding it to my DLE
Hi List Cheers On Wed, 2006-02-08 at 09:47 -0500, Jon LaBadie wrote: On Wed, Feb 08, 2006 at 09:50:45AM +, Chuck Amadi Systems Administrator wrote: Hi List I have another server that I need to add to my current main Amanda backup server. This server unlike the servers which are within my LAN and thus on the same network. Sits outside the LAN and is a public server. Thus is it still possible to just add the server outside of my LAN to disklist file: as I assume providing I add the xinetd and ports I should be able to backup a server ouside of my LAN. outsideserver.mycompany.co.uk /projects root-tar # /projects outsideserver.mycompany.co.uk /backup root-tar # /backup outsideserver.mycompany.co.uk /tmp root-tar # /tmp outsideserver.mycompany.co.uk /var root-tar # /var outsideserver.mycompany.co.uk /data root-tar # /data Perfect problem to address using amcheck. Make your client installation on out.my.co.uk, add the entries to your amanda server's disklist, and ask amcheck to see if things are ok with host out.my.co.uk. -- 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: Backup to a DLT drive but two servers to the backup hard drives.
Sorry if my last post is confusing I have confused myself lately. Howto get Amanda to back up individual servers large directories as seperate Disk List Entries (DLEs) using tar (GNUTAR) to the backup servers hard drives but another server to DLT cartridge for off site storage. I will be purchasing a 80GB DLT drive and a dedicated backup server with two 80GB scsi hard drives. 1) I want to backup our main file server onto the 80GB DLT drive. 2) I want backup The 80gb web server and 80gb mail server to the two 80gb drives on the backup server not the 80gb DLT drive. 3) Would this be possible as I want a robust final solution that is affordable and maintainable for upgrades etc etc. 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: Howto or crib for backing up two tape drives - amanda 2.5
Hi Again When tape drive 1 (slot1) fills up I assume without any user intervention the remainder of the data will backup onto tape drive 2 (slot2) be it external drive (Which I haven't concluded yet looking for a minimum of 160gb media capacity!) As version 2.5.0b1 has New tape spanning features. On Tue, 2006-01-10 at 23:14 +0100, Paul Bijnens wrote: Jon LaBadie wrote: And create a new file named chg-multi.conf in the same directory as the amanda.conf file with this content: multieject 0 gravity 0 needeject 0 ejectdelay 0 statefile /var/lib/amanda/daily/changer-status # changeme firstslot 1 lastslot 2 slot 1 /dev/nst0 # changeme slot 2 /dev/nst1 # changeme and fill in appropriate values for your environment in the lines marked with changeme Can the two devices be different format tapes? No, unfortunately, because there is only one tapetype, used for both of the devices. Of course you can use the lowest of the two capacities, or maybe the mean (Amanda will write to a tape until it hits the physical end of tape). -- 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
Tapelist issue only using 3 tape out of a tapecycle of 10.
Hi I have noticed that the backup schedule as changed somehow and is only using DailySet108 to DailySet110 (3 tapes) is there away to check and force it to use the next tape after DailySet110 which should be DailySet101. I did relabel a faulty tape recently. finaceserver:/etc/amanda/DailySet1 # less tapelist 20051005 DailySet109 reuse 20050930 DailySet108 reuse 20050929 DailySet107 reuse 20050922 DailySet106 reuse 20050916 DailySet105 reuse 20050915 DailySet104 reuse 20050909 DailySet103 reuse 20050908 DailySet102 reuse 20050907 DailySet101 reuse 20050906 DailySet110 reuse I did Replace a tape DailySet107 which Amanda reports a tape to be faulty, the label could not be read on the tape, or the data could not be saved on the tape. It is time to replace the tape. In order to keep the set of tapes consistant, the new tape should have the same label as the old tape. So I used the label DailySet107. 1. Connect on Amanda server, first as root, then change to the user amanda, with the command su. 2. Edit the file /etc/amanda/DailySet1/tapelist and remove the line containing the label,(DailySet107) Usually the line is the last one of the file. 3. Edit the file /usr/local/etc/amanda/tapelist.yesterday in the same way. Usually the line is the one before the last. 4. prepare a new tape and write the label on it with the command: amlabel normal DailySet107. 5. Edit the file /etc/amanda/DailySet1/tapelist again, note that the line with the label is back, but it is now at the top of the file, and the number at the begining is 0. Just move that line to the bottom of the file. This worked So I assumed. 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
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
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
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 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: My Monthly archive config - issue (Trying to source and use a tape changer if possible)
Hi all and Scott I am trying a Monthly archive but in order to follow a setup similar to Scott I need a tape changer. I have found a SCSI tape drive spec below it was once used for backups prior to moving over to Amanda. External Seagate DAT subsystem for NT, Windows, NetWare, DDS-3 recording format, consists of STD124000N DAT drive (data transfer rate 2.2 MB/s, 24 GB capacity with DDS-DC data compression), tabletop enclosure, tape, 1 m cable with 50pin high density plug, Thus could this possible be used a a tape changer I have checked the Amanda homepage but doesn't mention any devices. Cheers Chuck On Fri, 2005-09-30 at 07:39 -0400, Scott R. Burns wrote: Hi Chuck, Sorry I don't have any experience without a changer. You would be best to ask the list about this one. There may be a way to have it pause and prompt for the next tape ? I do know that you can pick up the changer I have on Ebay usually for about $ 100 USD - $ 200 USD with a 30day warrenty. Unfortunately I bought mine brand new in it's day for about $ 3000 USD :-( Scott... Scott R. Burns NETCON Technologies Incorporated Suite 135 - 4474 Blakie Road London, Ontario, Canada N6L 1G7 Voice: +1.519.652.0401 Fax: +1.519.652.9275 Web: www.netcontech.com -Original Message- From: Chuck Amadi Systems Administrator [mailto:[EMAIL PROTECTED] Sent: Friday, September 30, 2005 6:23 AM To: Scott R. Burns Subject: RE: My Monthly archive config - issue Hi I have received an error after running amcheck Monthly WARNING: if a tape changer is not available, runtapes must be set to 1 Thus I have not got a tape changer I just want to amflush data that cannot fit on tape 1 to 2,3 or in the future tape 4 to backup potential around 80GB. Cheers Chuck On Thu, 2005-09-29 at 12:23 -0400, Scott R. Burns wrote: I have a similar setup. I have HW compression turned off on the drive (HP DAT24X6 changer). In my monthly config: dumpcycle 0 weeks runspercycle 1 tapecycle 1000 tapes runtapes 3 Also, record is turned off so my normal daily amanda config does not think the level 0 has been completed after the monthly. We never re-use our monthly tapes we send them offsite and leave them so thats why I have it set to 1000. We use between 2-3 tapes on a monthly run so runtapes is at 3. Scott... Scott R. Burns NETCON Technologies Incorporated Suite 135 - 4474 Blakie Road London, Ontario, Canada N6L 1G7 Voice: +1.519.652.0401 Fax: +1.519.652.9275 Web: www.netcontech.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Chuck Amadi Systems Administrator Sent: Thursday, September 29, 2005 12:01 PM To: Amanda List Subject: My Monthly archive config - issue Hi again Its that time for a monthly archive backup I have currently 80GB server and using a DAT DDS-4 20GB native 40GB compression I am aware that I cannot have both hardware compression and software compression on So Amanda usually behaviour is to have hardware compression turned off using the mt command. Thus my amanda.conf is as follows I want a full dump for archiving and this tape will pulled out. dumpcycle 4 weeks # the number of days in the normal dump cycle runspercycle 2 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 12 tapes # the number of tapes in rotation to pull each monthly tape for archiving. runtapes 1 # number of tapes to be used in a normal run. Should I increase runtapes to 2 to ensure that I backup at a minimum 40GB. Also should I amend dumpcycle to dumpcycle 0 weeks for a full dump and not incremental. Please advice of the best setup to backup for a monthly archive. 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 -- 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 -- 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: Disable Tape Compression
Hi
My org uses SuSE 9 SLES servers and I used the following commands.
Turn off datacompression as Root run mt command that controls magnetic
tape
drive operation.
# Check datacompression status
myserver:~ # mt -f /dev/nst0 status
# Turns datacompression off
myserver:~ # mt -f /dev/nst0 datcompression 0
Compression off.
I hope this helps if not someone on the list will guide you as I have
made a lot of progress thru this mailinf list.
Cheers
On Fri, 2005-09-30 at 14:10 +0200, [EMAIL PROTECTED] wrote:
Hi Listers,
Just to give my 0.02EUR
mt -f /dev/nst0 defcompression off (or 0 depending on your mt)
mt -f /dev/nst0 compression off (or 0 depending on your mt)
I am running SuSE 9.3 and the only available mt operation is
datcompression
See:
athene:~ # mt --version
GNU mt version 2.5
athene:~ # man mt
[...]
datcompression
(some SCSI-2 DAT tapes) Inquire or set the compression
status
(on/off). If the count is one the compression status is
printed.
If the count is zero, compression is disabled. Otherwise,
com-
pression is enabled. The command uses the SCSI ioctl to read
and
write the Data Compression Characteristics mode page (15).
ONLY
ROOT CAN USE THIS COMMAND.
And in fact I do have the problem that I use at one site the Tandberg SLR7
without knowing how to switch off hw-compression. The mt datcompression
{off|0} operation fails. That leads to my amanda.conf:
define tapetype SLR7 {
comment just produced by tapetype prog (hardware compression on)
length 16500 mbytes # Manually decreased again
filemark 186 kbytes
speed 1300 kps
}
athene:~ # dmesg | grep SLR
Vendor: TANDBERG Model: SLR7 Rev: 0483
Type: Sequential-Access ANSI SCSI revision: 02
Attached scsi tape st0 at scsi0, channel 0, id 3, lun 0
st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA
1048575
BTW: Is it true that a tape formerly written with hw-compression will
override the 'drive compression off setting' because the compression
on/off status has been written on the header of the tape? If yes, I should
reformat a lot of tapes as described by Gene :-/
Best regards
Uwe
Virus checked by G DATA AntiVirusKit
Version: AVK 16.727 from 30.09.2005
--
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: Disable Tape Compression
Here's my output
#mt -f /dev/nst0 status
drive type = Generic SCSI-2 tape
drive status = 637534208
sense key error = 0
residue count = 0
file number = 0
block number = 1
Tape block size 0 bytes. Density code 0x26 (unknown).
Soft error count since last status=0
General status bits on (101):
The last but on line BOT ONLINE IM_REP_EN - tape drive is online and
ready.
I am afraid I don't know the message - Can't write mode page.
All the best
On Fri, 2005-09-30 at 14:31 +0200, [EMAIL PROTECTED] wrote:
Hi Chuck,
You are right but unfortunately my Tandberg SLR fails on that operation. It
worked well with all my HP drives.
Have a look:
minerva:~ # mt -f /dev/nst0 status
drive type = Generic SCSI-2 tape
drive status = 838861312
sense key error = 0
residue count = 0
file number = 0
block number = 0
Tape block size 512 bytes. Density code 0x32 (unknown).
Soft error count since last status=0
General status bits on (4101):
BOT ONLINE IM_REP_EN
minerva:~ # mt -f /dev/nst0 datcompression 0
Can't write mode page.
mt: /dev/nst0
Thanks
Uwe
-Original Message-
From: Chuck Amadi Systems Administrator [mailto:[EMAIL PROTECTED]
Sent: Friday, September 30, 2005 2:25 PM
To: [EMAIL PROTECTED]
Cc: Amanda List
Subject: RE: Disable Tape Compression
Hi
My org uses SuSE 9 SLES servers and I used the following commands.
Turn off datacompression as Root run mt command that controls magnetic
tape
drive operation.
# Check datacompression status
myserver:~ # mt -f /dev/nst0 status
# Turns datacompression off
myserver:~ # mt -f /dev/nst0 datcompression 0
Compression off.
I hope this helps if not someone on the list will guide you as I have
made a lot of progress thru this mailinf list.
Cheers
On Fri, 2005-09-30 at 14:10 +0200, [EMAIL PROTECTED] wrote:
Hi Listers,
Just to give my 0.02EUR
mt -f /dev/nst0 defcompression off (or 0 depending on your mt)
mt -f /dev/nst0 compression off (or 0 depending on your mt)
I am running SuSE 9.3 and the only available mt operation is
datcompression
See:
athene:~ # mt --version
GNU mt version 2.5
athene:~ # man mt
[...]
datcompression
(some SCSI-2 DAT tapes) Inquire or set the
compression
status
(on/off). If the count is one the compression
status is
printed.
If the count is zero, compression is
disabled. Otherwise,
com-
pression is enabled. The command uses the
SCSI ioctl to read
and
write the Data Compression Characteristics
mode page (15).
ONLY
ROOT CAN USE THIS COMMAND.
And in fact I do have the problem that I use at one site
the Tandberg SLR7
without knowing how to switch off hw-compression. The mt
datcompression
{off|0} operation fails. That leads to my amanda.conf:
define tapetype SLR7 {
comment just produced by tapetype prog (hardware
compression on)
length 16500 mbytes # Manually decreased again
filemark 186 kbytes
speed 1300 kps
}
athene:~ # dmesg | grep SLR
Vendor: TANDBERG Model: SLR7 Rev: 0483
Type: Sequential-Access ANSI SCSI revision: 02
Attached scsi tape st0 at scsi0, channel 0, id 3, lun 0
st0: try direct i/o: yes (alignment 512 B), max page
reachable by HBA
1048575
BTW: Is it true that a tape formerly written with
hw-compression will
override the 'drive compression off setting' because the
compression
on/off status has been written on the header of the tape?
If yes, I should
reformat a lot of tapes as described by Gene :-/
Best regards
Uwe
Virus checked by G DATA AntiVirusKit
Version: AVK 16.727 from 30.09.2005
--
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
Virus checked by G DATA AntiVirusKit
Version: AVK 16.727 from 30.09.2005
--
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: My Monthly archive config - issue (Trying to source and use a tape changer if possible)
Hi Gene I am using DDS-4 DAT tapes 20GM native and 40GB compression So I hope amanda using and amanda, using gzip, can probably put well over 40GB on the tape if your are correct. Cheers On Fri, 2005-09-30 at 11:33 -0400, Gene Heskett wrote: On Friday 30 September 2005 08:09, Chuck Amadi Systems Administrator wrote: Hi all and Scott I am trying a Monthly archive but in order to follow a setup similar to Scott I need a tape changer. I have found a SCSI tape drive spec below it was once used for backups prior to moving over to Amanda. External Seagate DAT subsystem for NT, Windows, NetWare, DDS-3 recording format, consists of STD124000N DAT drive (data transfer rate 2.2 MB/s, 24 GB capacity with DDS-DC data compression), tabletop enclosure, tape, 1 m cable with 50pin high density plug, Thus could this possible be used a a tape changer I have checked the Amanda homepage but doesn't mention any devices. Cheers Chuck It should work just fine, Chuck, as long as thats a large enough tape. With hardware compression off, it will hold 12GB, and amanda, using gzip, can probably put well over 24GB on the tape. The only caveat is the tape format. Its cheap, and in DDS2's at least, I had tape trouble after 20-50 passes per tape. They claim a million passes, but the drives heads are worn out long before that in my experience. Rotary heads, are like your vcr in design, and the lifetime is measured in a small number of thousands of hours, like 3 to 5 for the life of the head. I've had maybe 1% of the problems I had with DDS2 tapes since I switched to the FILE device on a 200GB drive. For rotating heads, the head wear and damage occurs as each head tip engages the edge of the tape at the start of the track, there is tape contact and bounce there, but once 'on' the tape, there is a micron thick air cushion between the tape and the head tip. Its that crash at the entrance edge of the tape that does the damage. I've looked at tips that were actually shattered in my many years of keeping broadcast recorders going. DVC-PRO heads are 1/3rd the size of a dat head, and they can read and write 100 MB/second these days. But the electronics in those is 1000x smarter in terms of error correction too. And the error correction doesn't have to be 100%, as long as the pixal coming out somewhat resembles what went in, thats good enough, the eye is a whole lot more forgiving than data storage. Todays tape drives are still in the horse and buggy era in comparison. On Fri, 2005-09-30 at 07:39 -0400, Scott R. Burns wrote: Hi Chuck, Sorry I don't have any experience without a changer. You would be best to ask the list about this one. There may be a way to have it pause and prompt for the next tape ? I do know that you can pick up the changer I have on Ebay usually for about $ 100 USD - $ 200 USD with a 30day warrenty. Unfortunately I bought mine brand new in it's day for about $ 3000 USD :-( Scott... Scott R. Burns NETCON Technologies Incorporated Suite 135 - 4474 Blakie Road London, Ontario, Canada N6L 1G7 Voice: +1.519.652.0401 Fax: +1.519.652.9275 Web: www.netcontech.com -Original Message- From: Chuck Amadi Systems Administrator [mailto:[EMAIL PROTECTED] Sent: Friday, September 30, 2005 6:23 AM To: Scott R. Burns Subject: RE: My Monthly archive config - issue Hi I have received an error after running amcheck Monthly WARNING: if a tape changer is not available, runtapes must be set to 1 Thus I have not got a tape changer I just want to amflush data that cannot fit on tape 1 to 2,3 or in the future tape 4 to backup potential around 80GB. Cheers Chuck On Thu, 2005-09-29 at 12:23 -0400, Scott R. Burns wrote: I have a similar setup. I have HW compression turned off on the drive (HP DAT24X6 changer). In my monthly config: dumpcycle 0 weeks runspercycle 1 tapecycle 1000 tapes runtapes 3 Also, record is turned off so my normal daily amanda config does not think the level 0 has been completed after the monthly. We never re-use our monthly tapes we send them offsite and leave them so thats why I have it set to 1000. We use between 2-3 tapes on a monthly run so runtapes is at 3. Scott... Scott R. Burns NETCON Technologies Incorporated Suite 135 - 4474 Blakie Road London, Ontario, Canada N6L 1G7 Voice: +1.519.652.0401 Fax: +1.519.652.9275 Web: www.netcontech.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Chuck Amadi Systems Administrator Sent: Thursday, September 29, 2005 12:01 PM To: Amanda List Subject: My Monthly archive config - issue Hi again Its that time for a monthly archive backup I have currently 80GB server and using a DAT DDS-4 20GB native 40GB compression I am aware that I cannot have both hardware
FAILURE AND STRANGE DUMP SUMMARY:
Hi all I note that a FAILURE AND STRANGE DUMP SUMMARY: occurred and I
assume that from the message at the bottom of the report that - file
changed as we read it has caused a FAILURE AND STRANGE DUMP.
Have I got anything to worry about here!.
On the myserver machine, the file _.1.tmp: has changed while it was
getting saved.
and I have read that GNU tar is able to recover from this error.
These dumps were to tape MYDailySet109.
The next tape Amanda expects to use is: MYDailySet110.
FAILURE AND STRANGE DUMP SUMMARY:
myserver.co.uk / lev 1 STRANGE
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:27
Run Time (hrs:min) 1:39
Dump Time (hrs:min)1:12 1:06 0:06
Output Size (meg) 11238.311181.1 57.2
Original Size (meg) 11238.311181.1 57.2
Avg Compressed Size (%) -- -- --
(level:#disks ...)
Filesystems Dumped8 4 4 (1:4)
Avg Dump Rate (k/s) 2660.5 2906.8 151.5
Tape Time (hrs:min)1:07 1:06 0:01
Tape Size (meg) 11238.311181.1 57.2
Tape Used (%) 57.6 57.30.3
(level:#disks ...)
Filesystems Taped 8 4 4 (1:4)
Avg Tp Write Rate (k/s) 2871.9 2885.2 1507.1
USAGE BY TAPE:
LabelTime Size %Nb
MYDailySet109 1:07 11238.3 57.6 8
FAILED AND STRANGE DUMP DETAILS:
/-- nemesis.co.co.uk / lev 1 STRANGE
sendbackup: start [myserver.co.co.uk:/ level 1]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/tar -f... -
sendbackup: info end
? gtar: ./dumps/amanda/20050928/myserver.co.co.uk._.1.tmp: file changed
as we read it
| Total bytes written: 26163200 (25MB, 218kB/s)
sendbackup: size 25550
sendbackup: end
\
NOTES:
planner: Full dump of myserver.co.co.uk:/home promoted from 27 days
ahead.
planner: Full dump of myserver.co.co.uk:/data promoted from 22 days
ahead.
planner: Full dump of myserver.co.co.uk:/tmp promoted from 26 days
ahead.
planner: Full dump of myserver.co.co.uk:/var promoted from 27 days
ahead.
taper: tape MYDailySet109 kb 11508384 fm 8 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER
STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS
KB/s
-- -
myserver.co / 1 25550 25550 --1:57 217.6 0:221185.3
myserver.co /backup 16070 6070 --0:46 131.7 0:032114.0
myserver.co /data 0 45434804543480 -- 25:302970.3 25:302969.7
myserver.co /home 0 63069406306940 -- 37:242810.9 37:242810.6
myserver.co /projects 1 12590 12590 --1:18 160.8 0:071815.0
myserver.co /share 1 14370 14370 --2:25 99.2 0:081913.8
myserver.co /tmp0 181530 181530 --0:305965.2 0:593086.0
myserver.co /var0 417500 417500 --2:153091.1 2:163080.8
(brought to you by Amanda version 2.4.4p2)
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: FAILURE AND STRANGE DUMP SUMMARY:
Hi Cheers for the reassurance. I will make note of your comments to file. Thanks On Thu, 2005-09-29 at 07:15 -0400, Jon LaBadie wrote: On Thu, Sep 29, 2005 at 11:13:01AM +0100, Chuck Amadi Systems Administrator wrote: Hi all I note that a FAILURE AND STRANGE DUMP SUMMARY: occurred and I assume that from the message at the bottom of the report that - file changed as we read it has caused a FAILURE AND STRANGE DUMP. Have I got anything to worry about here!. On the myserver machine, the file _.1.tmp: has changed while it was getting saved. and I have read that GNU tar is able to recover from this error. You may not be able to recover that one file. But it was a temporary, probably only partially complete, file anyway so why care about it. Should not impact the rest of the dump. -- 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 add a new host and disk to my Amanda backup server WARNING Host down! (emailserver).
Hi all I have just been asked to add our email server to our Amanda server backup. I have installed the Amanda version 2.4.4p2 rpm using SuSE SLES 9 Yast2 and added the email server to disklist as below: #/etc/amanda/DailySet1/disklist file: # hostname diskname or mountpoint dumptype # mounted as. myserver.co.co.uk / root-tar # backup all myservers / and sub directories (This works) emailserver.co.co.uk / root-tar # backup email servers / and sub directories. or have I for the emailserver list all the local dir after / i.e emailserver.co.co.uk /usr root-tar #/usr dir emailserver.co.co.uk /local root-tar #/local dir Thus enabled xinetd amanda, amadaidx and amidxtape. Thus checked that the emailserver can participate with the amanda backup server over the network exspecailly the amanda client utility amanda. amanda 10080/tcp # Amanda amanda 10080/udp # Amanda amandaidx 10082/tcp amidxtape 10083/tcp I have run amcheck and I get this error have I missed anything. Amanda Backup Client Hosts Check WARNING: emailserver.co.co.uk: selfcheck request timed out. Host down? Client check: 2 hosts checked in 30.167 seconds, 1 problem found I have added the emailserver to my main backup server named myserver. [EMAIL PROTECTED]:/var/lib/amanda # less .amandahosts localhost amanda localhost root myserver.co.co.uk amanda myserver.co.co.uk root emailserver.co.co.uk amanda emailserver.co.co.uk root Also added emailserver to var/lib/amanda/.amandahosts file [EMAIL PROTECTED]:/var/lib/amanda # less .amandahosts localhost root emailserver.co.co.uk amanda emailserver.co.co.uk root Chers for your help suggestions. 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: Howto add a new host and disk to my Amanda backup server WARNING Host down! (emailserver).
Hi
I rechecked the /etc/xinetd/amanda file and the other two
# default: off
# description: Amanda backup client
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = disk
server = /usr/lib/amanda/amandad
}
[EMAIL PROTECTED]:/etc/xinetd.d # ls -l /usr/lib/amanda/amandad (it's
there I did use rpm's)
and the same for the other amanda utilities and thus
run /etc/init.d/xinetd restart on both hosts added to /etc/hosts and run
chkconfig --list all amanda utilities are on.
Cheers
Chuck
On Thu, 2005-09-29 at 15:19 +0200, Stefan G. Weichinger wrote:
Chuck Amadi Systems Administrator wrote:
Thus enabled xinetd amanda, amadaidx and amidxtape.
Recheck the entries in /etc/xinetd.d (paths to binaries?) and make sure
that you also restarted xinetd.
--
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 add a new host and disk to my Amanda backup server WARNING Host down! (emailserver).
Hi got a bit further I had on the emailserver SuSE's default firewall
running thus disabled
Now get this error:
Amanda Backup Client Hosts Check
ERROR: ktinga.smtl.co.uk: [access as amanda not allowed from
[EMAIL PROTECTED] amandahostsauth failed
Client check: 2 hosts checked in 10.190 seconds, 1 problem found
Thus I have add to the my new host
emailserver's /var/lib/amanda/.amandahostss file the main Amanada server
(myserver).
myserver amanda
myserver root
And guess what No problems!.
Cheers
On Thu, 2005-09-29 at 15:44 +0200, Stefan G. Weichinger wrote:
Chuck Amadi Systems Administrator wrote:
Hi
I rechecked the /etc/xinetd/amanda file and the other two
# default: off
# description: Amanda backup client
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = disk
server = /usr/lib/amanda/amandad
}
[EMAIL PROTECTED]:/etc/xinetd.d # ls -l /usr/lib/amanda/amandad (it's
there I did use rpm's)
And you use amanda:disk as AMANDA-user?
and the same for the other amanda utilities and thus
run /etc/init.d/xinetd restart on both hosts added to /etc/hosts and run
chkconfig --list all amanda utilities are on.
Does xinetd tell you (in /var/log/messages) that it has read and enabled
the amanda-related services? ALso check the permissions of the daemons,
they should be owned by the amanda-user and executable for it.
Eg.
# ll /usr/local/libexec/amandad
-rwxr-xr-x 1 amanda disk 31K Sep 28 21:06 /usr/local/libexec/amandad
Basically the error you get points to the fact that amandad doesn't get
contacted properly, either because it is not reachable or not started ...
Any firewall enabled between these hosts?
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
My Monthly archive config - issue
Hi again Its that time for a monthly archive backup I have currently 80GB server and using a DAT DDS-4 20GB native 40GB compression I am aware that I cannot have both hardware compression and software compression on So Amanda usually behaviour is to have hardware compression turned off using the mt command. Thus my amanda.conf is as follows I want a full dump for archiving and this tape will pulled out. dumpcycle 4 weeks # the number of days in the normal dump cycle runspercycle 2 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 12 tapes # the number of tapes in rotation to pull each monthly tape for archiving. runtapes 1 # number of tapes to be used in a normal run. Should I increase runtapes to 2 to ensure that I backup at a minimum 40GB. Also should I amend dumpcycle to dumpcycle 0 weeks for a full dump and not incremental. Please advice of the best setup to backup for a monthly archive. 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: Amanda want allow me to amflush to tape Amverify give me this - Error reading label on tape -Fixed.
Hi all Sorted my problem used the notes from this gooogled website if anyone is interested as I had previlously used amrmtape and then amlabel. Ref: Replacing a tape Sometime Amanda reports a tape to be faulty, the label could not be read on the tape, or the data could not be saved on the tape. It is time to replace the tape. https://wwws.cs.ait.ac.th/amanda/operator.shtml Thus got a Report stating the next tape will be Dailyset107. Cheers CSIM On Thu, 2005-09-22 at 11:17 +0100, Chuck Amadi Systems Administrator wrote: Hi I am experiencing a problem when I try and run amflush to Dailyset106 On running amverify I get this error but the correct tape Dailyset106 is in the tape drive. I aslo run amcheck and that stated Dailyset106 or a new tape So I tried Dailyset107 but of cause it's not a new tape So how can I sort this problem with Dailyset106 not be backed too. Tapes: Errors found: amdd: read error: Input/output error 0+0 in 0+0 out amverify DailySet1 Thu Sep 22 11:16:53 BST 2005 Using device /dev/nst0 ** Error reading label on tape Cheers On Thu, 2005-09-22 at 11:17 +0100, Amanda admin wrote: Tapes: Errors found: amdd: read error: Input/output error 0+0 in 0+0 out amverify DailySet1 Thu Sep 22 11:16:53 BST 2005 Using device /dev/nst0 ** Error reading label on tape -- 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
Unable to amrestore my disk partitions
Hi all
I have tried amrecover which seemed to of worked except I had no data,
file or directories within backups, homes, data1, shares, projecta, and
var. I did get the partition name but not the sub-directiories.
My disklist is as follows
nemesis.smtl.co.uk /homes root-tar
nemesis.smtl.co.uk /shares root-tar
nemesis.smtl.co.uk /projecta root-tar
nemesis.smtl.co.uk /backups root-tar
nemesis.smtl.co.uk /var root-tar
nemesis.smtl.co.uk /data1 root-tar
Here is a email report which I assumed backed up the partitions disks.
These dumps were to tape SMTLSet105.
The next tape Amanda expects to use is: SMTLSet106.
FAILURE AND STRANGE DUMP SUMMARY:
myserver.smtl.co.uk / lev 1 STRANGE
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:29
Run Time (hrs:min) 1:43
Dump Time (hrs:min)1:13 1:09 0:04
Output Size (meg) 11398.711229.5 169.2
Original Size (meg) 11398.711229.5 169.2
Avg Compressed Size (%) -- -- --
(level:#disks ...)
Filesystems Dumped7 3 4 (1:4)
Avg Dump Rate (k/s) 2658.9 2775.9 699.9
Tape Time (hrs:min)1:10 1:09 0:01
Tape Size (meg) 11398.711229.5 169.2
Tape Used (%) 58.4 57.60.9
(level:#disks ...)
Filesystems Taped 7 3 4 (1:4)
Avg Tp Write Rate (k/s) 2769.1 2775.4 2408.1
USAGE BY TAPE:
LabelTime Size %Nb
SMTLSet105 1:10 11398.7 58.4 7
FAILED AND STRANGE DUMP DETAILS:
/-- myserver.sm / lev 1 STRANGE
sendbackup: start [myserver.smtl.co.uk:/ level 1]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/tar -f... -
sendbackup: info end
? gtar: ./dumps/amanda/20050921/myserver.smtl.co.uk._.1.tmp: file
changed as we read it
? gtar: ./dumps/amanda/20050921/myserver.smtl.co.uk._data.1: Warning:
Cannot stat: No such file or directory
| Total bytes written: 26081280 (25MB, 220kB/s)
sendbackup: size 25470
sendbackup: end
\
NOTES:
planner: Full dump of myserver.smtl.co.uk:/home promoted from 27 days
ahead.
planner: Full dump of myserver.smtl.co.uk:/share promoted from 23 days
ahead.
planner: Full dump of myserver.smtl.co.uk:/projects promoted from 26
days ahead.
taper: tape SMTLSet105 kb 11672544 fm 7 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER
STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS
KB/s
-- -
myserver.smtl / 1 25470 25470 --1:56 219.3
0:122147.5
myserver.smtl /backups 16070 6070 --0:40 151.5 0:13
455.0
myserver.smtl /data1 1 35140 35140 --1:09 509.9
0:122941.7
myserver.smtl /homes 0 61993006199300 -- 36:522802.9
36:522802.5
myserver.smtl /projecta 0 18879001887900 -- 11:302736.1
11:302735.2
myserver.smtl /shares 0 34118003411800 -- 20:412750.0
20:412749.5
myserver.smtl /var1 106550 106550 --0:224760.0
0:353062.7
(brought to you by Amanda version 2.4.4p2)
Thus have I mis-configured my disklist file as I need to backup disk
partitions as well as root (/) directory which worked.
--
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 utilise DDS-4 20/40GB tape with Amanda
Hi PB My other issue is that concerns me If I also increase the number of tapes I currently use from 10 to possibly 20 will this enable me in the future to backup a server that is 80GB using incremental dumps and what is best for my monthly 20GB tapes that I wanted to pull out to archive as I wanted to do a full backup to 1 tape if this is now not possible could I still to the same as with my daily config and increase the runspercycle to 5 or more. I am using in my Daily amanda.conf dumpcycle 4 weeks # the number of days in the normal dump cycle # Setting dumpcycle to 0 - Setting this to zero tries to do a full backup each run. runspercycle 1 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 10 tapes Would it be better to use your full suggestion as below: dumcycle 1 week runspercycle 5 # each working day tapecycle 20 tapes My Monthly is currently as below: dumpcycle 0 weeks # the number of days in the normal dump cycle runspercycle 1 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 12 tapes But would these mean that I will have to change the tape frequently during the day. I am contemplating cannibalising a workstation and installing a DLT drive as a possible solution but cost rather a lot. Cheers On Mon, 2005-09-12 at 09:58 +0200, Paul Bijnens wrote: Chuck Amadi Systems Administrator wrote: Hi relating to possible Here's my current amanda.conf dumpcycle 0 weeks runspercycle 1 tapecycle 10 tapes Thus increase runspercycle to any figure below tapecycle of 10 tapes. So for example runspercycle 1 would be sufficient. oho. You're doing a full dump each run. But your tapecapacity is not sufficient to do that. So that leaves you to do runtapes 2 or more (use more tapes for each run. Or increase the dumpcycle (to avoid a full dump each time), and then run multiple times during such a dumpcycle. Why not: dumcycle 1 week runspercycle 5# each working day tapecycle 10 tapes And if you need more history increase the number of tapes. Cheers Chuck Amadi Systems Administrator wrote: Hi I have managed to config the hard disk partitions in my disklist but I am short of tape space to include the remainder of the hard disk partitions. I had initially run the following commands is it possible to get compression functioning to enable to use 40GB as opposed to native 20GB. * - amtapetype -f /dev/nst0 # determine tape type takes along time When specifying also a realistic estimate -e 20 g it is usually much faster (2-4 hours) * - turn off datacompression run mt command that controls magnetic tape drive operation. * - mt -f /dev/nst0 status and mt -f /dev/nst0 datcompression 0 Compression off. As I don't want to buy bigger tapes if possible. If you already use software compression, than enabling hardware compression will _reduce_ your effective tapecapacity by 15-35%, because the compression algorithms in those tapedrives behave bad on already compressed data. When not too many files change, you can run less fulls and more incrementals on each run by increasing the dumpcycle (runspercycle actually). Or increase runtapes (and flush each morning the remainders if you have only one drive). -- 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 utilise DDS-4 20/40GB tape with Amanda
Hi I have managed to config the hard disk partitions in my disklist but I am short of tape space to include the remainder of the hard disk partitions. I had initially run the following commands is it possible to get compression functioning to enable to use 40GB as opposed to native 20GB. * - amtapetype -f /dev/nst0 # determine tape type takes along time * - turn off datacompression run mt command that controls magnetic tape drive operation. * - mt -f /dev/nst0 status and mt -f /dev/nst0 datcompression 0 Compression off. As I don't want to buy bigger tapes if possible. 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: Howto utilise DDS-4 20/40GB tape with Amanda
Hi Cheers for the guidance. Thanks On Fri, 2005-09-09 at 09:37 -0400, Jon LaBadie wrote: On Fri, Sep 09, 2005 at 09:39:31AM +0100, Chuck Amadi Systems Administrator wrote: Hi I have managed to config the hard disk partitions in my disklist but I am short of tape space to include the remainder of the hard disk partitions. I had initially run the following commands is it possible to get compression functioning to enable to use 40GB as opposed to native 20GB. * - amtapetype -f /dev/nst0 # determine tape type takes along time * - turn off datacompression run mt command that controls magnetic tape drive operation. * - mt -f /dev/nst0 status and mt -f /dev/nst0 datcompression 0 Compression off. As I don't want to buy bigger tapes if possible. Your tape's capacity is 20GB! Not 40GB, never will be, no way, no how. But compression (hardware or software) might be able to shrink a lot of data down to 20GB. The rub is that compression algorithms, whether applied by your computer or by the computer in your tape drive, are only effective the first time they are applied. And as PB pointed out, when fed already compressed data, the dumb algorithm used by the tape drive is likely to expand, rather than shrink, the data! An analogy, your new 250GB hard disk drive. If you use it to store a bunch of zip'ed files, does it become a 500GB hard disk drive? No, it is still a 250GB drive that happens to be storing compressed data. Similarly, your 20GB tape stores 20GB of data. Those data may be 20GB of plain old uncompressed information, or a lot more information that is compressed by your computer before taping or by the drive during taping -- but not both!. -- 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
Amanda unable to use amrecover ssince dumptype change for a New Monthly back up as well as Daily.
Hi I have just recently included a monthly backup script whereby I was
advised to amend the parameters of dumptype {
recored no
}
Thus as default was set to yes I would cause amanda confusion.
Also when I tried a amrecover exercise I am now unable to recover.
Basically where previously I would be told what tape to put into the
server after I set
setdate -mm-dd as below I was told which tape to use Not Now
I get Setting restore date to today But I want data from last Friday
which as a exercise was backed up and today we deleted the data for the
test but of cause I am unable to put the correct tape in. So if possible
has anyone any ideas as the only thing I can think of is the parameter I
changed.
[EMAIL PROTECTED]:/ # amrecover -s myserver.smtl.co.uk -t
myserver.smtl.co.uk
AMRECOVER Version 2.4.4p2. Contacting server on myserver.smtl.co.uk ...
220 myserver AMANDA index server (2.4.4p2) ready.
200 Access OK
Setting restore date to today (2005-09-06)
200 Working date set to 2005-09-06.
Warning: no log files found for tape SMTLSet109 written 2005-08-25
Warning: no log files found for tape SMTLSet108 written 2005-08-24
Warning: no log files found for tape SMTLSet107 written 2005-08-23
Warning: no log files found for tape SMTLSet106 written 2005-08-22
Warning: no log files found for tape SMTLSet105 written 2005-08-22
Warning: no log files found for tape SMTLSet104 written 2005-08-19
Scanning /dumps/amanda...
20050702: found Amanda directory.
20050707: found Amanda directory.
20050713: found Amanda directory.
20050714: found Amanda directory.
20050829: found Amanda directory.
20050905: found Amanda directory.
200 Config set to DailySet1.
501 Host myserver is not in your disklist.
Trying host myserver.smtl.co.uk ...
200 Dump host set to myserver.smtl.co.uk.
Trying disk / ...
$CWD '/' is on disk '/' mounted at '/'.
200 Disk set to /.
/
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: Amanda unable to use amrecover ssince dumptype change for a New Monthly back up as well as Daily.
Hi I had a monthly and daily script that checked if it was last friday
of the month.
Thus it reverts back to daily config after amcheck notes that a monthly
tape is still in the server thus I have since the first monthly tape was
used to backup I have been using daily tape thus data that We used on
the friday last was a daily but when I try amrecover it doesn't tell
which tape use for the date. I did change the dumptype paremeter from
default yes TO no So I may have mos configured but the fact that
amdump made a back up of that date I still believed I could still get
that date data back using amrecover.
Thus is there away say using amadmin to get data by the a way inserting
that date tape.
Cheers
On Tue, 2005-09-06 at 09:22 -0400, Jon LaBadie wrote:
On Tue, Sep 06, 2005 at 01:28:25PM +0100, Chuck Amadi Systems Administrator
wrote:
Hi I have just recently included a monthly backup script whereby I was
advised to amend the parameters of dumptype {
recored no
}
Thus as default was set to yes I would cause amanda confusion.
Also when I tried a amrecover exercise I am now unable to recover.
Basically where previously I would be told what tape to put into the
server after I set
setdate -mm-dd as below I was told which tape to use Not Now
I get Setting restore date to today But I want data from last Friday
which as a exercise was backed up and today we deleted the data for the
test but of cause I am unable to put the correct tape in. So if possible
has anyone any ideas as the only thing I can think of is the parameter I
changed.
[EMAIL PROTECTED]:/ # amrecover -s myserver.smtl.co.uk -t
myserver.smtl.co.uk
If I recall correctly your monthly backup used a new amanda config.
Did you tell amrecover to use that new config rather than your default?
--
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: Amanda unable to use amrecover ssince dumptype change for a New Monthly back up as well as Daily.
Hi I have looked at running command amrestore DailySet1 info myserver
Thus insert the tape SMTLSet103 as per the amadmin command below,thus
can I run amrestore -c /dev/nst0 myserver SMTLSet1
Thus have I go to rewind the tape first as I dont want to mess things
up.
amadmin DailySet1 info myserver
Current info for myserver.smtl.co.uk /:
Stats: dump rates (kps), Full: 2878.0, 2859.0, 2863.0
Incremental: 1083.0, 2757.0, 1375.0
compressed size, Full: -100.0%,-100.0%,-100.0%
Incremental: -100.0%,-100.0%,-100.0%
Dumps: lev datestmp tape file origK compK secs
0 20050902 SMTLSet103 1 4401130 4401130 1529
1 20050905 SMTLSet104 1 139790 139790 129
[EMAIL PROTECTED]:/tmp/myserver-backup #
Cheers
Chuck
On Tue, 2005-09-06 at 09:22 -0400, Jon LaBadie wrote:
On Tue, Sep 06, 2005 at 01:28:25PM +0100, Chuck Amadi Systems Administrator
wrote:
Hi I have just recently included a monthly backup script whereby I was
advised to amend the parameters of dumptype {
recored no
}
Thus as default was set to yes I would cause amanda confusion.
Also when I tried a amrecover exercise I am now unable to recover.
Basically where previously I would be told what tape to put into the
server after I set
setdate -mm-dd as below I was told which tape to use Not Now
I get Setting restore date to today But I want data from last Friday
which as a exercise was backed up and today we deleted the data for the
test but of cause I am unable to put the correct tape in. So if possible
has anyone any ideas as the only thing I can think of is the parameter I
changed.
[EMAIL PROTECTED]:/ # amrecover -s myserver.smtl.co.uk -t
myserver.smtl.co.uk
If I recall correctly your monthly backup used a new amanda config.
Did you tell amrecover to use that new config rather than your default?
--
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: Amanda unable to use amrecover ssince dumptype change for a New Monthly back up as well as Daily.
Hi again
I have run the following :
[EMAIL PROTECTED]:/ # amrecover DailySet1 -s myserver.smtl.co.uk -t
myserver.smtl.co.uk
AMRECOVER Version 2.4.4p2. Contacting server on nemesis.smtl.co.uk ...
220 nemesis AMANDA index server (2.4.4p2) ready.
200 Access OK
Setting restore date to today (2005-09-06)
200 Working date set to 2005-09-06.
Warning: no log files found for tape SMTLSet109 written 2005-08-25
Warning: no log files found for tape SMTLSet108 written 2005-08-24
Warning: no log files found for tape SMTLSet107 written 2005-08-23
Warning: no log files found for tape SMTLSet106 written 2005-08-22
Warning: no log files found for tape SMTLSet105 written 2005-08-22
Scanning /dumps/amanda...
20050707: found Amanda directory.
20050713: found Amanda directory.
20050714: found Amanda directory.
20050829: found Amanda directory.
20050905: found Amanda directory.
200 Config set to DailySet1.
501 Host myserver is not in your disklist.
Trying host myserver.smtl.co.uk ...
200 Dump host set to myserver.smtl.co.uk.
Trying disk / ...
$CWD '/' is on disk '/' mounted at '/'.
200 Disk set to /.
/
amrecover setdate 2005-09-02
200 Working date set to 2005-09-02.
amrecover ls
amrecover cd backup
amrecover ls
The test-recovery file doesn't now exist I have the correct tape that
was used from last friday and I expected to be able to extrat previous
test a file exist and when a run add and extract it promted me to put
the tape in have I missed something as I am aware that the test-recovery
file doesn't exist except for on the SMTLSet103 tape that's currently in
the tape server.
Cheers
On Tue, 2005-09-06 at 11:18 -0400, Jon LaBadie wrote:
On Tue, Sep 06, 2005 at 03:07:54PM +0100, Chuck Amadi Systems Administrator
wrote:
Hi I had a monthly and daily script that checked if it was last friday
of the month.
Thus it reverts back to daily config after amcheck notes that a monthly
tape is still in the server thus I have since the first monthly tape was
used to backup I have been using daily tape thus data that We used on
the friday last was a daily but when I try amrecover it doesn't tell
which tape use for the date. I did change the dumptype paremeter from
default yes TO no So I may have mos configured but the fact that
amdump made a back up of that date I still believed I could still get
that date data back using amrecover.
Thus is there away say using amadmin to get data by the a way inserting
that date tape.
Cheers
On Tue, 2005-09-06 at 09:22 -0400, Jon LaBadie wrote:
On Tue, Sep 06, 2005 at 01:28:25PM +0100, Chuck Amadi Systems
Administrator wrote:
Hi I have just recently included a monthly backup script whereby I was
advised to amend the parameters of dumptype {
recored no
}
Thus as default was set to yes I would cause amanda confusion.
Also when I tried a amrecover exercise I am now unable to recover.
Basically where previously I would be told what tape to put into the
server after I set
setdate -mm-dd as below I was told which tape to use Not Now
I get Setting restore date to today But I want data from last Friday
which as a exercise was backed up and today we deleted the data for the
test but of cause I am unable to put the correct tape in. So if possible
has anyone any ideas as the only thing I can think of is the parameter I
changed.
[EMAIL PROTECTED]:/ # amrecover -s myserver.smtl.co.uk -t
myserver.smtl.co.uk
If I recall correctly your monthly backup used a new amanda config.
Did you tell amrecover to use that new config rather than your default?
soapbox
Top posting is such a pain in continuing a conversation.
/soapbox
Chuck, your old posts showed this in your scripts:
if ...
then su -c /usr/sbin/amcheck MonthlySet
else su -c /usr/sbin/amcheck DailySet1
So you are using two amanda configs, have two sets of logs,
have two sets of indexes. One is the default, DailySet1.
Guess which of the two configs, logs, and indexes this amrecover
command that you showed us tries to use?
[EMAIL PROTECTED]:/ # amrecover -s myserver.smtl.co.uk -t
myserver.smtl.co.uk
The default of course, you did not tell it any different.
Unless I missed something as I did in earlier posts today :)
--
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: Has anyone a script for Monthly/Daily backups
Hi all
I would like comments on this solution to run fortnight daily backup
using 10 tapes.
and on the last Friday of the month to run a Monthly backup for
archiving purposes and pull out of System until the following year.
I have hacked up two scripts from the this list.
First of all here is mt cronjob::
I need to know what tape is in the current tape drive be it the usual
daily tape
and of course if it happened to be the last friday in the month or say a
monday I will to put the next daily tape or on the thursday before the
last friday of the month backup to be ready to put the next monthly tape
in.
I am aware the amdump send a report on failures or successful backups
but
if a daily schedule is run and it's going to be a last friday and I put
in daily tape
does the script ignore the daily tape and amdump monthly report So and
thus I can say on monday put in the monthly tape and run amflush.
Cheers
# Check which Amanda tape if Daily or Monthly.
0 14 * * 1-5 /usr/sbin/check_amanda_tape.sh
45 19 * * 1-5 /usr/sbin/last_friday_month.sh
Here is the Last Friday In Month script (last_friday_month.sh).
#!/bin/sh
# Script last_friday_month.sh
# chmod 755
# Amdump - Last friday of the month script to check prior to running
usual daily tape
# or the monthly tape backup.
# Ensure the in the amamda.conf file the within the dumptype
# paramter for root-tar that record is set to no
# example - record no This is to stop Monthly ruining the Daily
Schedule.
# Summarisation of the script
# cal - prints month calendar
# awk - selects friday column date
# tail - last date
# -eq - date compared last date with todays date.
if [ `cal | awk 'NF = 6 {print $6}' | tail -1` -eq `date +%d` ]
then su -c /usr/sbin/amdump MonthlySet
else su -c /usr/sbin/amdump DailySet1
fi
Here is the Check which tape (check_amanda_tape.sh) is in the drive
prior to any amdumps running at 19:45
#!/bin/sh
# Script check_amanda_tape.sh
# chmod 755
# Amcheck - Last friday of the month script to check prior to running
usual daily tape
# or the monthly tape backup.
# Ensure the in the amamda.conf file the within the dumptype
# paramter for root-tar that record is set to no
# example - record no This is to stop Monthly ruining the Daily
Schedule.
# Summarisation of the script
# cal - prints month calendar
# awk - selects friday column date
# tail - last date
# -eq - date compared last date with todays date.
if [ `cal | awk 'NF = 6 {print $6}' | tail -1` -eq `date +%d` ]
then su -c /usr/sbin/amcheck MonthlySet
else su -c /usr/sbin/amcheck DailySet1
fi
On Thu, 2005-08-18 at 19:41 +0100, chuck.amadi wrote:
Paul Bijnens wrote:
chuck.amadi wrote:
Hi again do you run amcheck prior to amdump running. or is it a
simple caseof just hacking your script as below:
#!/bin/sh
# Script lfdom.sh
# Last friday of the month script
if [ `cal | awk 'NF = 6 {print $6}' | tail -1` -eq `date +%d` ]
then su -c /usr/sbin/amcheck MonthlySet1; su -c /usr/sbin/amdump
MonthlySet1
else su -c /usr/sbin/amcheck DailySet1; su -c /usr/sbin/amdump
DailySet1
fi
amcheck is used to check for a valid tape and warn the sysadmin
if there is some problem. Therefore, I run it during the day, when
I'm still there to correct things.
I do not run any additional amcheck just before launching the amdump
program in the night.
Therefore, I have two entries in my crontab.
One for amcheck, running at 16:15 Mon-Fri (in the hope that any
problems that might pop up can be still be solved before I go home.
Then another entry that just does amdump, running at 00:05 (yes, that's
actually the next day -- beware if you run the last-friday-of-month
check, in that case, start amdump just a few minute earlier, like 23:55).
Hi I used this script and my test was`successful without the amcheck But
I will a mail command to ensure that I put in a Monthly tape .
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
Have an issue with amanda extracting - cannot connect to server.co.uk: Connection refused
Hi I have two amanda tape servers within the organisation I managed successful to do a disaster recovery exercise for main file server - worked accordingly but on the second tape server for our spin off company I get the the following I am able to run daily amdumps and amchecks with no error messages Thus please could you direct where I can find out whats causing the extract problem. O/S SuSE SLES 9 Amanda version (2.4.4p2). The makeup is identical and I checked the ~.amamdahosts file. localhost amanda localhost root server.co.uk amanda server.co.uk root Extracting files using tape drive /dev/nst0 on host server.co.uk. The following tapes are needed: DailySet110 Restoring files into directory / Continue [?/Y/n]? y Extracting files using tape drive /dev/nst0 on host server.co.uk. Load tape DailySet110 now Continue [?/Y/n/s/t]? y cannot connect to server.co.uk: Connection refused amrecover - can't talk to tape server amrecover Cheers Chuck -- 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: planner,dumper and amcheck keep reverting back to (not setuid-root)
Hi Thanks for that my boss more than likely add such a program before he went on holiday as this has only started to occur last week. I have had no previous problem and I have been running this for over two months. I will check whats going on. Thanks again. On Fri, 2005-07-29 at 13:39 -0400, Jon LaBadie wrote: On Fri, Jul 29, 2005 at 03:34:29PM +0100, Chuck Amadi Systems Administrator wrote: Hi I run by hand amcheck it is in my crontab but every now and then I run it to check. Amanda Tape Server Host Check - WARNING: program /usr/lib/amanda/planner: not setuid-root WARNING: program /usr/lib/amanda/dumper: not setuid-root WARNING: program /usr/sbin/amcheck: not setuid-root Thus I use chmod u+s as root. # chmod u+s /usr/lib/amanda/planner # chmod u+s /usr/lib/amanda/dumper # chmod u+s /usr/sbin/amcheck The above sorts this out bit I have had to do this a few times this week. I haven't got to do this on the other tape server Where is the best place to check why it keeps reverting to the following below. Chuck, I hope you realize this has nothing to do with amanda. The system probably has some security program that runs periodically and reports on all root-setuid programs. Perhaps automatically removing the setuid on those not in some list of known safe programs. I once had an ATT sysadmin who when to a security class. At the class they learned that setuid programs were a huge security problem. When she got back, that Sunday night, she came in to the training site where I consulted and ran a find command on all the systems to locate and remove all setuid permissions on all programs. Monday morning, very little worked right. -- 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: planner,dumper and amcheck keep reverting back to (not setuid-root)
Hi I have been running amanda 2.4.4 around three months now on two servers One on our main file server the other for a spin out company as part of our SLA. The spin out companies has the exact setup except for Label string and name of the report. I run by hand amcheck it is in my crontab but every now and then I run it to check. Amanda Tape Server Host Check - WARNING: program /usr/lib/amanda/planner: not setuid-root WARNING: program /usr/lib/amanda/dumper: not setuid-root WARNING: program /usr/sbin/amcheck: not setuid-root Thus I use chmod u+s as root. # chmod u+s /usr/lib/amanda/planner # chmod u+s /usr/lib/amanda/dumper # chmod u+s /usr/sbin/amcheck The above sorts this out bit I have had to do this a few times this week. I haven't got to do this on the other tape server Where is the best place to check why it keeps reverting to the following below. -rwxr-x--- 1 root disk 166883 Jul 1 2004 planner -rwxr-x--- 1 root disk 165718 Jul 1 2004 dumper and also amcheck in /usr/sbin . Cheers Chcuk -- 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
driver: WARNING: got empty schedule from planner
Hi all I received the following message below: NOTES: driver: WARNING: got empty schedule from planner Please could someone point me n the right direction to read and digest what has happend I have had a gooogle and looked at FAQ But haven't found any information. 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
The next tape Amanda expects to use is: DailySet104 and the DailSet104 is in the drive.
Hi all I have running amanda for a week but Fridays tape DailySet4 didn't get backed up because The DailySet4 tape is in the drive but my amanda doesn't think So. What is the best way to check what amanda tape it is as I assume when labelling I may of made a mistake. Is there a amanda program that will check what tape I have in the drive. *** A TAPE ERROR OCCURRED: [not an amanda tape]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next tape Amanda expects to use is: DailySet104. Here is the message when I run amverify Defects file is /tmp/amanda/amverify.20028/defects amverify DailySet1 Mon Jun 27 15:41:39 BST 2005 Using device /dev/nst0 Waiting for device to go ready... Rewinding... Processing label... ** No amanda tape in slot So whats the best step to correct this. 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: The next tape Amanda expects to use is: DailySet104 and the DailSet104 is in the drive.
Hi I don't have no tpchanger specified in my ~amanda.conf As below # Specify tape device and/or tape changer. If you don't have a tape # changer, and you don't want to use more than one tape per run of # amdump, just comment out the definition of tpchanger. I am only using one tape per run that does a full backup onto tape. Thus is there a way to check my tapes I did orderly label them but need to verify which tape is DailySet4. Cheers On Mon, 2005-06-27 at 10:51 -0500, Vicki Stanfield wrote: Chuck Amadi Systems Administrator wrote: Hi all I have running amanda for a week but Fridays tape DailySet4 didn't get backed up because The DailySet4 tape is in the drive but my amanda doesn't think So. What is the best way to check what amanda tape it is as I assume when labelling I may of made a mistake. Is there a amanda program that will check what tape I have in the drive. *** A TAPE ERROR OCCURRED: [not an amanda tape]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next tape Amanda expects to use is: DailySet104. Here is the message when I run amverify Defects file is /tmp/amanda/amverify.20028/defects amverify DailySet1 Mon Jun 27 15:41:39 BST 2005 Using device /dev/nst0 Waiting for device to go ready... Rewinding... Processing label... ** No amanda tape in slot So whats the best step to correct this. Cheers I would try amtape [config] show. Vicki -- 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
server / lev 0 FAILED [/bin/tar returned 2] - server / lev 0 FAILED [dump to tape failed]
Hi again
I was getting the following this error - server / lev 0 FAILED [dump to
tape failed] I assume tar is not working.
I am using this version of tar.
server:/etc/postfix # /bin/tar --version
tar (GNU tar) 1.13.25
cd /var/lib/amanda/DailySet1
ls -lt less amdump
(output)
driver: result time 1615.665 from dumper0: FAILED 01-2 [/bin/tar
returned 2]
Amanda Report below:
These dumps were to tape DailySet110.
The next tape Amanda expects to use is: a new tape.
The next new tape already labelled is: DailySet101.
FAILURE AND STRANGE DUMP SUMMARY:
server / lev 0 FAILED [/bin/tar returned 2]
server / lev 0 FAILED [dump to tape failed]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:27
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:27 0:27 0:00
Tape Size (meg) 4212.7 4212.70.0
Tape Used (%) 21.6 21.60.0
Filesystems Taped 1 1 0
Avg Tp Write Rate (k/s) 2696.0 2696.0--
USAGE BY TAPE:
Label Time Size %Nb
DailySet110 0:274212.7 21.6 1
FAILED AND STRANGE DUMP DETAILS:
/-- server / lev 0 FAILED [/bin/tar returned 2]
sendbackup: start [greenbottle.smtl.co.uk:/ level 0]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
? gtar: ./media/cdrom: Cannot savedir: No medium found
? gtar: ./media/floppy: Cannot savedir: No medium found
? gtar: ./media/cdrom: Warning: Cannot savedir: No medium found
? gtar: ./media/floppy: Warning: Cannot savedir: No medium found
| gtar: ./dev/log: socket ignored
| gtar: ./tmp/.s.PGSQL.5432: socket ignored
| gtar: ./tmp/.ICE-unix/19580: socket ignored
| gtar: ./tmp/.ICE-unix/dcop19563-1118847061: socket ignored
| gtar: ./tmp/.X11-unix/X0: socket ignored
| gtar: ./tmp/ksocket-root/kdeinit-\:0: socket ignored
| gtar: ./tmp/ksocket-root/kdeinit__0: socket ignored
| gtar: ./tmp/ksocket-root/klaunchermrw2tb.slave-socket: socket ignored
| gtar: ./tmp/mcop-root/linux_site-28b2-423ab4ee: socket ignored
| gtar: ./tmp/ssh-PFKtU17880/agent.17880: socket ignored
| gtar: ./tmp/ssh-TQywwj4017/agent.4017: socket ignored
| gtar: ./var/lib/mysql/mysql.sock: socket ignored
| gtar: ./var/lib/ntp/dev/log: socket ignored
| gtar: ./var/run/.nscd_socket: socket ignored
| gtar: ./var/run/.resmgr_socket: socket ignored
| gtar: ./var/run/powersave_socket: socket ignored
| gtar: ./var/spool/postfix/private/anvil: socket ignored
| gtar: ./var/spool/postfix/private/bounce: socket ignored
| gtar: ./var/spool/postfix/private/bsmtp: socket ignored
| gtar: ./var/spool/postfix/private/cyrus: socket ignored
| gtar: ./var/spool/postfix/private/defer: socket ignored
| gtar: ./var/spool/postfix/private/error: socket ignored
| gtar: ./var/spool/postfix/private/ifmail: socket ignored
| gtar: ./var/spool/postfix/private/lmtp: socket ignored
| gtar: ./var/spool/postfix/private/local: socket ignored
| gtar: ./var/spool/postfix/private/maildrop: socket ignored
| gtar: ./var/spool/postfix/private/procmail: socket ignored
| gtar: ./var/spool/postfix/private/proxymap: socket ignored
| gtar: ./var/spool/postfix/private/relay: socket ignored
| gtar: ./var/spool/postfix/private/rewrite: socket ignored
| gtar: ./var/spool/postfix/private/smtp: socket ignored
| gtar: ./var/spool/postfix/private/trace: socket ignored
| gtar: ./var/spool/postfix/private/uucp: socket ignored
| gtar: ./var/spool/postfix/private/verify: socket ignored
| gtar: ./var/spool/postfix/private/virtual: socket ignored
| gtar: ./var/spool/postfix/private/vscan: socket ignored
| gtar: ./var/spool/postfix/public/cleanup: socket ignored
| gtar: ./var/spool/postfix/public/flush: socket ignored
| gtar: ./var/spool/postfix/public/showq: socket ignored
| Total bytes written: 5874155520 (5.5GB, 3.5MB/s)
? gtar: Error exit delayed from previous errors
sendbackup: error [/bin/tar returned 2]
\
NOTES:
planner: Last full dump of server.domain.co.uk:/ on tape
overwritten in 1 run.
taper: tape DailySet110 kb 4313856 fm 1 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER
STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS
KB/s
-- -
server. / 0 FAILED
---
I have tried to figure out what is going on any suggestions would be
great.
--
Unix/ Linux Systems Administrator
Chuck Amadi
The
Re: server / lev 0 FAILED [/bin/tar returned 2] - server / lev 0 FAILED [dump to tape failed]
Thanks I am using the link to digest the rest Cheers On Thu, 2005-06-23 at 12:04 +0200, [EMAIL PROTECTED] wrote: Hello, Chuck, on 23.06.2005, 11:41 you wrote to amanda-users@amanda.org: I was getting the following this error - server / lev 0 FAILED [dump to tape failed] I assume tar is not working. I am using this version of tar. server:/etc/postfix # /bin/tar --version tar (GNU tar) 1.13.25 Ok. tar works: Total bytes written: 5874155520 (5.5GB, 3.5MB/s) USAGE BY TAPE: Label Time Size %Nb DailySet110 0:274212.7 21.6 1 Seems you use the right tapetype now ... FAILED AND STRANGE DUMP DETAILS: /-- server / lev 0 FAILED [/bin/tar returned 2] sendbackup: start [greenbottle.smtl.co.uk:/ level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/bin/tar -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? gtar: ./media/cdrom: Cannot savedir: No medium found ? gtar: ./media/floppy: Cannot savedir: No medium found ? gtar: ./media/cdrom: Warning: Cannot savedir: No medium found ? gtar: ./media/floppy: Warning: Cannot savedir: No medium found | gtar: ./dev/log: socket ignored | gtar: ./tmp/.s.PGSQL.5432: socket ignored | gtar: ./tmp/.ICE-unix/19580: socket ignored | gtar: ./tmp/.ICE-unix/dcop19563-1118847061: socket ignored | gtar: ./tmp/.X11-unix/X0: socket ignored | gtar: ./tmp/ksocket-root/kdeinit-\:0: socket ignored | gtar: ./tmp/ksocket-root/kdeinit__0: socket ignored | gtar: ./tmp/ksocket-root/klaunchermrw2tb.slave-socket: socket ignored | gtar: ./tmp/mcop-root/linux_site-28b2-423ab4ee: socket ignored | gtar: ./tmp/ssh-PFKtU17880/agent.17880: socket ignored | gtar: ./tmp/ssh-TQywwj4017/agent.4017: socket ignored | gtar: ./var/lib/mysql/mysql.sock: socket ignored | gtar: ./var/lib/ntp/dev/log: socket ignored | gtar: ./var/run/.nscd_socket: socket ignored | gtar: ./var/run/.resmgr_socket: socket ignored | gtar: ./var/run/powersave_socket: socket ignored | gtar: ./var/spool/postfix/private/anvil: socket ignored | gtar: ./var/spool/postfix/private/bounce: socket ignored | gtar: ./var/spool/postfix/private/bsmtp: socket ignored | gtar: ./var/spool/postfix/private/cyrus: socket ignored | gtar: ./var/spool/postfix/private/defer: socket ignored | gtar: ./var/spool/postfix/private/error: socket ignored | gtar: ./var/spool/postfix/private/ifmail: socket ignored | gtar: ./var/spool/postfix/private/lmtp: socket ignored | gtar: ./var/spool/postfix/private/local: socket ignored | gtar: ./var/spool/postfix/private/maildrop: socket ignored | gtar: ./var/spool/postfix/private/procmail: socket ignored | gtar: ./var/spool/postfix/private/proxymap: socket ignored | gtar: ./var/spool/postfix/private/relay: socket ignored | gtar: ./var/spool/postfix/private/rewrite: socket ignored | gtar: ./var/spool/postfix/private/smtp: socket ignored | gtar: ./var/spool/postfix/private/trace: socket ignored | gtar: ./var/spool/postfix/private/uucp: socket ignored | gtar: ./var/spool/postfix/private/verify: socket ignored | gtar: ./var/spool/postfix/private/virtual: socket ignored | gtar: ./var/spool/postfix/private/vscan: socket ignored | gtar: ./var/spool/postfix/public/cleanup: socket ignored | gtar: ./var/spool/postfix/public/flush: socket ignored | gtar: ./var/spool/postfix/public/showq: socket ignored | Total bytes written: 5874155520 (5.5GB, 3.5MB/s) I have tried to figure out what is going on any suggestions would be great. Maybe use exclusions for all those sockets? This would remove all those nasty ignore-errors above. Refer to http://www.amanda.org/docs/exclude.html for example. Best regards, Stefan G. Weichinger. mailto://[EMAIL PROTECTED] -- 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: server / lev 0 FAILED [/bin/tar returned 2] - server / lev 0 FAILED [dump to tape failed]
Hi again I have briefly read info with the link provide and I had previous entries in the exclude list as below: #Exclude a number of files from the backup, this is done using the following file: # /usr/local/lib/amanda/exclude.gtar #The contents of the file will be similar to the following: core *.o *.gz.tmp */.mozilla/cache */gnutar-lists/*.new */spool/mqueue/?f[A-Z]* */tmp/*.errout *pagefile.sys */.thumbnails/* */trader-cache/* */cache/* */.thumbcache/* # Thus use exclusions for all those sockets? This would remove all # those nasty ignore-errors and No media found in the Report. ./dev ./tmp ./var ./media/cdrom ./media/floppy I assume the last five entries are the correct syntax to Exclude those directories. Cheers On Thu, 2005-06-23 at 12:04 +0200, [EMAIL PROTECTED] wrote: Hello, Chuck, on 23.06.2005, 11:41 you wrote to amanda-users@amanda.org: I was getting the following this error - server / lev 0 FAILED [dump to tape failed] I assume tar is not working. I am using this version of tar. server:/etc/postfix # /bin/tar --version tar (GNU tar) 1.13.25 Ok. tar works: Total bytes written: 5874155520 (5.5GB, 3.5MB/s) USAGE BY TAPE: Label Time Size %Nb DailySet110 0:274212.7 21.6 1 Seems you use the right tapetype now ... FAILED AND STRANGE DUMP DETAILS: /-- server / lev 0 FAILED [/bin/tar returned 2] sendbackup: start [greenbottle.smtl.co.uk:/ level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/bin/tar -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? gtar: ./media/cdrom: Cannot savedir: No medium found ? gtar: ./media/floppy: Cannot savedir: No medium found ? gtar: ./media/cdrom: Warning: Cannot savedir: No medium found ? gtar: ./media/floppy: Warning: Cannot savedir: No medium found | gtar: ./dev/log: socket ignored | gtar: ./tmp/.s.PGSQL.5432: socket ignored | gtar: ./tmp/.ICE-unix/19580: socket ignored | gtar: ./tmp/.ICE-unix/dcop19563-1118847061: socket ignored | gtar: ./tmp/.X11-unix/X0: socket ignored | gtar: ./tmp/ksocket-root/kdeinit-\:0: socket ignored | gtar: ./tmp/ksocket-root/kdeinit__0: socket ignored | gtar: ./tmp/ksocket-root/klaunchermrw2tb.slave-socket: socket ignored | gtar: ./tmp/mcop-root/linux_site-28b2-423ab4ee: socket ignored | gtar: ./tmp/ssh-PFKtU17880/agent.17880: socket ignored | gtar: ./tmp/ssh-TQywwj4017/agent.4017: socket ignored | gtar: ./var/lib/mysql/mysql.sock: socket ignored | gtar: ./var/lib/ntp/dev/log: socket ignored | gtar: ./var/run/.nscd_socket: socket ignored | gtar: ./var/run/.resmgr_socket: socket ignored | gtar: ./var/run/powersave_socket: socket ignored | gtar: ./var/spool/postfix/private/anvil: socket ignored | gtar: ./var/spool/postfix/private/bounce: socket ignored | gtar: ./var/spool/postfix/private/bsmtp: socket ignored | gtar: ./var/spool/postfix/private/cyrus: socket ignored | gtar: ./var/spool/postfix/private/defer: socket ignored | gtar: ./var/spool/postfix/private/error: socket ignored | gtar: ./var/spool/postfix/private/ifmail: socket ignored | gtar: ./var/spool/postfix/private/lmtp: socket ignored | gtar: ./var/spool/postfix/private/local: socket ignored | gtar: ./var/spool/postfix/private/maildrop: socket ignored | gtar: ./var/spool/postfix/private/procmail: socket ignored | gtar: ./var/spool/postfix/private/proxymap: socket ignored | gtar: ./var/spool/postfix/private/relay: socket ignored | gtar: ./var/spool/postfix/private/rewrite: socket ignored | gtar: ./var/spool/postfix/private/smtp: socket ignored | gtar: ./var/spool/postfix/private/trace: socket ignored | gtar: ./var/spool/postfix/private/uucp: socket ignored | gtar: ./var/spool/postfix/private/verify: socket ignored | gtar: ./var/spool/postfix/private/virtual: socket ignored | gtar: ./var/spool/postfix/private/vscan: socket ignored | gtar: ./var/spool/postfix/public/cleanup: socket ignored | gtar: ./var/spool/postfix/public/flush: socket ignored | gtar: ./var/spool/postfix/public/showq: socket ignored | Total bytes written: 5874155520 (5.5GB, 3.5MB/s) I have tried to figure out what is going on any suggestions would be great. Maybe use exclusions for all those sockets? This would remove all those nasty ignore-errors above. Refer to http://www.amanda.org/docs/exclude.html for example. Best regards, Stefan G. Weichinger. mailto://[EMAIL PROTECTED] -- 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: server / lev 0 FAILED [/bin/tar returned 2] - server / lev 0 FAILED [dump to tape failed]
Hi Paul I run the comand here is the output. server:/etc/amanda/DailySet1 # tar -cf - --sparse --one-file-sys --tot --dir /media . | cat /dev/null tar: ./cdrom: Cannot savedir: No medium found tar: ./floppy: Cannot savedir: No medium found Total bytes written: 10240 (10kB, 74kB/s) tar: Error exit delayed from previous errors server:/etc/amanda/DailySet1 # Thus I assume that it falls over when hit comes across /media/cdrom /media/floopy and is what I need to fix. My fstab is as follows but when using Yast and floppy I have had no issues. /dev/cdrom /media/cdrom subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/fd0 /media/floppysubfs fs=floppyfss,procuid,nodev,nosuid,sync 0 0 On Thu, 2005-06-23 at 13:03 +0200, Paul Bijnens wrote: [EMAIL PROTECTED] wrote: /-- server / lev 0 FAILED [/bin/tar returned 2] sendbackup: start [greenbottle.smtl.co.uk:/ level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/bin/tar -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? gtar: ./media/cdrom: Cannot savedir: No medium found ? gtar: ./media/floppy: Cannot savedir: No medium found ? gtar: ./media/cdrom: Warning: Cannot savedir: No medium found ? gtar: ./media/floppy: Warning: Cannot savedir: No medium found | gtar: ./dev/log: socket ignored | gtar: ./tmp/.s.PGSQL.5432: socket ignored | gtar: ./tmp/.ICE-unix/19580: socket ignored | gtar: ./tmp/.ICE-unix/dcop19563-1118847061: socket ignored | gtar: ./tmp/.X11-unix/X0: socket ignored | gtar: ./tmp/ksocket-root/kdeinit-\:0: socket ignored | gtar: ./tmp/ksocket-root/kdeinit__0: socket ignored [...] | gtar: ./var/spool/postfix/public/showq: socket ignored | Total bytes written: 5874155520 (5.5GB, 3.5MB/s) Maybe use exclusions for all those sockets? This would remove all those nasty ignore-errors above. Note that the error is not in the sockets (those lines are marked with a pipe-symbol as normal), but in the no medium found lines, marked with a question mark. Thus there is no need to add the sockets in the ignore list. Now the problem is: why does the OS complain about missing media in those directories? I cannot reproduce this on any of my systems, with or without media inserted. What version of Linux are you using? How are the /media/* directories managed ? (in /etc/fstab? automouter?) What happens when you do: gtar -cf - --sparse --one-file-sys --tot --dir /media . | cat /dev/null -- 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: server / lev 0 FAILED [/bin/tar returned 2] - server / lev 0 FAILED [dump to tape failed]
Hi I am using SuSE SLES 9,version Amanda 2.4.2 and /etc/fstab. Very weired I just mounted a floppy and cdrom with no problems So it is working. Cheers On Thu, 2005-06-23 at 13:03 +0200, Paul Bijnens wrote: [EMAIL PROTECTED] wrote: /-- server / lev 0 FAILED [/bin/tar returned 2] sendbackup: start [greenbottle.smtl.co.uk:/ level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/bin/tar -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? gtar: ./media/cdrom: Cannot savedir: No medium found ? gtar: ./media/floppy: Cannot savedir: No medium found ? gtar: ./media/cdrom: Warning: Cannot savedir: No medium found ? gtar: ./media/floppy: Warning: Cannot savedir: No medium found | gtar: ./dev/log: socket ignored | gtar: ./tmp/.s.PGSQL.5432: socket ignored | gtar: ./tmp/.ICE-unix/19580: socket ignored | gtar: ./tmp/.ICE-unix/dcop19563-1118847061: socket ignored | gtar: ./tmp/.X11-unix/X0: socket ignored | gtar: ./tmp/ksocket-root/kdeinit-\:0: socket ignored | gtar: ./tmp/ksocket-root/kdeinit__0: socket ignored [...] | gtar: ./var/spool/postfix/public/showq: socket ignored | Total bytes written: 5874155520 (5.5GB, 3.5MB/s) Maybe use exclusions for all those sockets? This would remove all those nasty ignore-errors above. Note that the error is not in the sockets (those lines are marked with a pipe-symbol as normal), but in the no medium found lines, marked with a question mark. Thus there is no need to add the sockets in the ignore list. Now the problem is: why does the OS complain about missing media in those directories? I cannot reproduce this on any of my systems, with or without media inserted. What version of Linux are you using? How are the /media/* directories managed ? (in /etc/fstab? automouter?) What happens when you do: gtar -cf - --sparse --one-file-sys --tot --dir /media . | cat /dev/null -- 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: server / lev 0 FAILED [/bin/tar returned 2] - server / lev 0 FAILED [dump to tape failed]
Hi Great News I have included the ./media or be it ./media/cdrom and ./media/floppy I will use the simpler format and run the amdump. Cheers Chuck On Thu, 2005-06-23 at 14:52 +0200, Paul Bijnens wrote: Chuck Amadi Systems Administrator wrote: My fstab is as follows but when using Yast and floppy I have had no issues. /dev/cdrom /media/cdrom subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/fd0 /media/floppysubfs fs=floppyfss,procuid,nodev,nosuid,sync 0 0 Aha, it's the subfs kernel module that notices access to these dirs, and magically mounts the stuff. You need indeed to add ./media to the excludes for that DLE. see: http://gentoo-wiki.com/HOWTO_Submount I use mostly CentOS (and good old Slackware!) and they don't use subfs. That's why I could not reproduce it. -- 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: server / lev 0 FAILED [/bin/tar returned 2] - server / lev 0 FAILED [dump to tape failed]
) sendbackup: size 5740990 sendbackup: end \ NOTES: planner: Last full dump of greenbottle.smtl.co.uk:/ on tape overwritten in 1 run. taper: tape DailySet102 kb 5741024 fm 1 [OK] DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - greenbottle. / 0 57409905740990 -- 31:213052.3 31:213052.0 (brought to you by Amanda version 2.4.4p2) On Thu, 2005-06-23 at 14:52 +0200, Paul Bijnens wrote: Chuck Amadi Systems Administrator wrote: My fstab is as follows but when using Yast and floppy I have had no issues. /dev/cdrom /media/cdrom subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/fd0 /media/floppysubfs fs=floppyfss,procuid,nodev,nosuid,sync 0 0 Aha, it's the subfs kernel module that notices access to these dirs, and magically mounts the stuff. You need indeed to add ./media to the excludes for that DLE. see: http://gentoo-wiki.com/HOWTO_Submount I use mostly CentOS (and good old Slackware!) and they don't use subfs. That's why I could not reproduce it. -- 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: server / lev 0 FAILED [/bin/tar returned 2] - server / lev 0 FAILED [dump to tape failed]
Hi Thanks for the advise I will monitor as suggested but worth the voyager. Cheers All On Thu, 2005-06-23 at 12:01 -0400, Jon LaBadie wrote: ./var/tmp ./var/spool/postfix ./var/spool/cups -- 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
dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Hi I have run the amtapetype command and used the output and entered
into the amanda.conf as below.
# Produced after running amtapetype command.
define tapetype tape-DDS-4 {
comment Produced by tapetype 20gb(hardware compression off)
length 19510 mbytes
filemark 79 kbytes
speed 1740 kps
}
Note the other tapetype parameters are still there which I what I think
is still causing my dumps to fail as is still complaining about dump
larger than tape, 2862305 KB, but cannot incremental dump new disk.
Have I got to comment out the other tapetyps definitions
Here is my ~amdump.6 file output.
From this blurb - tape length 1976320 mark 111 I note that was in my
previous HP
define tapetype HP-DAT {
comment DAT tape drives
# data provided by Rob Browning [EMAIL PROTECTED]
length 1930 mbytes #I have changed this to 2
filemark 111 kbytes
speed 468 kbytes
dumper: dgram_bind: socket bound to 0.0.0.0.990
dumper: pid 28445 executable dumper1 version 2.4.4p2, using port 990
planner: time 3.216: got result for host server.domain.co.uk disk /: 0
- 5735560K, -1 - -1K, -1 - -1K
planner: time 3.216: getting estimates took 3.212 secs
FAILED QUEUE: empty
DONE QUEUE:
0: server.domain.co.uk /
ANALYZING ESTIMATES...
pondering server.domain.co.uk:/... next_level0 -12951 last_level -1 (due
for level 0) (new disk, can't switch to degraded
mode)
curr level 0 size 2867780 total size 2868209 total_lev0 2867780
balanced-lev0size 2867780
INITIAL SCHEDULE (size 2868209):
server.domain.co.uk / pri 12951 lev 0 size 2867780
DELAYING DUMPS IF NEEDED, total_size 2868209, tape length 1976320 mark
111
planner: FAILED server.domain.co.uk / 20050616 0 [dump larger than tape,
2867780 KB, but cannot incremental dump new disk] delay: Total size now
286.
planner: cannot fit anything on tape, bailing out
planner: time 3.217: cannot fit anything on tape, bailing out
planner: time 3.217: pid 28441 finish time Thu Jun 16 13:12:52 2005
driver: adding holding disk 0 dir /dumps/amanda size 20971520
Thus have I got to reset anything as Amanda is still thinking of my
previous tapetype.
--
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
dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Hi again When I tried to comment this out Got this msg - /etc/amanda/DailySet1/amanda.conf, line 79: tapetype HP-DAT not defined. How do it start amanda So is uses another tapetype parameter which I have added to amanda.conf 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: dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Hi again
The reason to reset as I only left the correct tapetype that was
produced using amtapetype and thus commented out the remainder and I got
this error below
/etc/amanda/DailySet1/amanda.conf, line 79: tapetype HP-DAT not
defined
So I assume that it's still assuming the previous tapetype and thus I am
unable to backup.
Cheers
On Fri, 2005-06-17 at 13:49 +0200, Paul Bijnens wrote:
Chuck Amadi Systems Administrator wrote:
Hi again
When I tried to comment this out
Got this msg - /etc/amanda/DailySet1/amanda.conf, line 79: tapetype
HP-DAT not defined.
How do it start amanda So is uses another tapetype parameter which I
have added to amanda.conf
How about editing that line and putting tapetype tape-DDS-4
so that amanda now looks at the tapetype you just added (at least that
what I presume you did after reading your other message).
Or do I feel that there is actually a little misunderstanding in
how the amanda.conf file finds the tapetype?
The tapetype line instructs amanda you are using tape of
a kind , from all of the kinds that are defined with
the define tapetype xyz {...} groups.
--
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: dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Hi When I do Got this message when I treid that - /etc/amanda/DailySet1/amanda.conf, line 79: tapetype HP-DAT not defined. So how do I tell amanda to let go of this tapetype and use another or let me create a new definition. Cheers On Fri, 2005-06-17 at 08:07 -0400, Matt Hyclak wrote: On Fri, Jun 17, 2005 at 12:28:51PM +0100, Chuck Amadi Systems Administrator enlightened us: When I tried to comment this out Got this msg - /etc/amanda/DailySet1/amanda.conf, line 79: tapetype HP-DAT not defined. How do it start amanda So is uses another tapetype parameter which I have added to amanda.conf You've added a define tapetype FOO section. Now you need to go back towards the top of the amanda.conf file and find the tapetype HP-DAT line and change it to tapetype YOURNEWDEFINITION. Matt -- 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
still getting - dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Hi I am still getting - dump larger than tape, 2862305 KB, but cannot incremental dump new disk but it's only less than 3gb. Here's my less /var/mail/root ANALYZING ESTIMATES... pondering server.domain.co.uk:/... next_level0 -12951 last_level -1 (due for level 0) (new disk, can't switch to degraded mode) curr level 0 size 2862305 total size 2862734 total_lev0 2862305 balanced-lev0size 2862305 INITIAL SCHEDULE (size 2862734): server.domain.co.uk / pri 12951 lev 0 size 2862305 DELAYING DUMPS IF NEEDED, total_size 2862734, tape length 1976320 mark 111 planner: FAILED server.domain.co.uk / 20050616 0 [dump larger than tape, 2862305 KB, but cannot incremental dump new disk] delay: Total size now 286. planner: cannot fit anything on tape, bailing out planner: time 3.118: cannot fit anything on tape, bailing out 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
dump larger than tape, 2867765 KB, but cannot incremental dump new disk
Hi I have tried backing up / using the disklist with a 20GB DDS-4 150MM DAT tape and I get this error below. The size is only 3GB Is there a level I need to adjust in the amanda.conf file. sever.domain.co.uk:/ 0 planner: [dump larger than tape, 2867765 KB, but cannot incremental dump new disk] 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
dump larger than tape, 2862305 KB, but cannot incremental dump new disk
Hi agian Here is my /var/lib/amanda/amdump.1 ANALYZING ESTIMATES... pondering server.domian.co.uk:/... next_level0 -12951 last_level -1 (due for level 0) (new disk, can't switch to degraded mode) curr level 0 size 2862305 total size 2862734 total_lev0 2862305 balanced-lev0size 2862305 INITIAL SCHEDULE (size 2862734): server.domain.co.uk / pri 12951 lev 0 size 2862305 DELAYING DUMPS IF NEEDED, total_size 2862734, tape length 1976320 mark 111 planner: FAILED server.smtl.co.uk / 20050616 0 [dump larger than tape, 2862305 KB, but cannot incremental dump new disk] delay: Total size now 286. Any Ideas as I am using a 20GB dat tape. -- 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: R: dump larger than tape, 2867765 KB, but cannot incremental dump newdisk
Hi just posted it When I first configured I did rub the command that took for ever and a day. But I did have a 20gb tape in the drive. Cheers Is there a way to reset it as I have edited the On Thu, 2005-06-16 at 14:20 +0200, Montagni, Giovanni wrote: Have you ever run amtapetype command? it seems amanda doesn't recognize entire tape lenght... could paste us your tape definition? another stupid thing, is the tape rewinded? Giovanni -Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] conto di Chuck Amadi Systems Administrator Inviato: gioved 16 giugno 2005 14.03 A: Amanda List Oggetto: dump larger than tape, 2867765 KB, but cannot incremental dump newdisk Hi I have tried backing up / using the disklist with a 20GB DDS-4 150MM DAT tape and I get this error below. The size is only 3GB Is there a level I need to adjust in the amanda.conf file. sever.domain.co.uk:/ 0 planner: [dump larger than tape, 2867765 KB, but cannot incremental dump new disk] 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: I am correctly concluding I need only a tapecycle of 10 tapes - Using 10 tapes for fortnightly backup scheme.
Hi Again Would it be simplier to create a Monthly config for a monthly full backup that con exists with my Daily. If So is there and examples of this setup. Cheers On Tue, 2005-06-14 at 16:43 -0400, Gene Heskett wrote: On Tuesday 14 June 2005 09:03, Chuck Amadi Systems Administrator wrote: Hi Great Yes I am going to use 10 tapes in total and reuse the first tape after 10 week days worth of backups. Thus is it fine to pull the last Friday tape at the end of the Month for archiving and then re-label the tape I pulled. Unless you are doing an 'always full' all the time, then that tape you remove on friday is not going to be a complete, usable image you can restore from and get a full restore. I think in a previous message you said you were using dat's but didn't spec which one. But here, even the largest DDS4 wouldn't begin to hold an always full of this 2 machine home system. Also, keep in mind that amanda performs index file housekeeping based on the tapelist. That means the indice files for that tape will be removed from amandas database when that tape is replaced/reused/relabled. This is one of the reasons that I wrote a wrapper that appends this data to the individual tape after amanda is done. You'll have to reduce the tapes size slightly in the tapetype entry in order to ascertain there is space on the tape for its indices. I write the config directory too just in case its a bare metal recovery, but that file is relatively small compared to the indice tree's current 805 megs here. Things to ponder... Thanks I am nearly there . Cheers On Tue, 2005-06-14 at 08:21 -0400, Jon LaBadie wrote: On Tue, Jun 14, 2005 at 12:45:07PM +0100, Chuck Amadi Systems Administrator wrote: Hi I have 10 dat tapes that I will run per my cycle 5 per 5 day week. Thus every fortnight. I am correctly concluding I need only a tapecycle of 10 tapes I hope to pull out the last Friday tape in that Month to archive and thus label another tape to replace it. Here's my config file. dumpcycle 0 weeks # the number of days in the normal dump cycle runspercycle 1 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 10 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that Think of tapecycle as how many different tapes amanda must use before it will reuse the first one. In your setup, it looks like full backups every run, tapecycle is as critical as a setup doing mixed full and incrementals. Set it to whatever you want, or are comfortable, having amanda not overwrite before being allowed to reuse. If you want the last 10 full dumps to be sure to be around, then set it to 10. If the last 5 is comfortable, you can set it to 5, but still use 10 tapes. Amanda will only check that at least 5 are still the most recent. -- 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: I am correctly concluding I need only a tapecycle of 10 tapes - Using 10 tapes for fortnightly backup scheme.
Hi again From what I gathered I will more than likely go with labelling 22 tapes for 2 week cycle not including weekends and 12 DAT DDS-4 to pull out at the end on the month. When I pull the monthly tape i.e daily14 out can I just label a replacement tape daily14 as per the pulled tape or must I use a new name. Cheers On Tue, 2005-06-14 at 10:24 -0400, Jon LaBadie wrote: Mark it as no-reuse and label up a new DS-05.1. -- 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: Using 10 tapes for fortnightly DailySet backup scheme and for a Monthly Config 12 tapes.
Hi again If I run a Monthly config #'sudo -u amanda crontab -e # Backup check running amcheck at 4.30pm on the 2nd day of each and every month. 30 16 2 1-12 * /usr/sbin/amcheck MonthlySet1 Thus use 12 DSS-4 DAT Tapes and set the Monthly amanda.conf as below dumpcycle 4 weeks # the number of days in the normal dump cycle runspercycle 1 # One run per month tapecycle 12 tapes # the number of tapes in rotation 12 per Year. Would these be better On Tue, 2005-06-14 at 17:50 +0100, Chuck Amadi Systems Administrator wrote: Hi Again Thus continue and labelling DailySet101 - 110 as So far, to Dailyset 122 Thus end of each month pull that tape and carry on as usual. Thus as I started the backup with tape DailySet102 for tuesday as I want DailySet101 for first week monday. Have I got to edit the tapelist accordingly. Do I just On Tue, 2005-06-14 at 10:24 -0400, Jon LaBadie wrote: On Tue, Jun 14, 2005 at 02:03:19PM +0100, Chuck Amadi Systems Administrator wrote: Hi Great Yes I am going to use 10 tapes in total and reuse the first tape after 10 week days worth of backups. Thus is it fine to pull the last Friday tape at the end of the Month for archiving and then re-label the tape I pulled. On Tue, 2005-06-14 at 08:21 -0400, Jon LaBadie wrote: On Tue, Jun 14, 2005 at 12:45:07PM +0100, Chuck Amadi Systems Administrator wrote: Hi I have 10 dat tapes that I will run per my cycle 5 per 5 day week. Thus every fortnight. I am correctly concluding I need only a tapecycle of 10 tapes I hope to pull out the last Friday tape in that Month to archive and thus label another tape to replace it. Here's my config file. dumpcycle 0 weeks # the number of days in the normal dump cycle runspercycle 1 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 10 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that Think of tapecycle as how many different tapes amanda must use before it will reuse the first one. In your setup, it looks like full backups every run, tapecycle is as critical as a setup doing mixed full and incrementals. Set it to whatever you want, or are comfortable, having amanda not overwrite before being allowed to reuse. If you want the last 10 full dumps to be sure to be around, then set it to 10. If the last 5 is comfortable, you can set it to 5, but still use 10 tapes. Amanda will only check that at least 5 are still the most recent. I just want to make certain I'm not confusing your intent because of terminology. You want to pull the monthly tape and relabel the tape you pulled. That second part (relabelling) is a different tape, right? If so, it is not relabelling but just an initial label for that tape. Now, if you mean to use the same label as the one pulled, think twice. Amanda keeps indexes of what is on a tape. If you use the same label as the pulled tape, then you will soon lose the index for the pulled tape (when the new tape is used). Instead, when you pull a tape, mark it a no-reuse. The index will be retained. But the new tape will need to have a different label. In fact, you could label up 22 tapes, 10 for cycling, 12 in anticipation of pulling monthly for a year. Your tapecycle could be set to 10, and you could cycle through your first 10, or all 22. Amanda will still ensure that the most recently used 10 are not overwritten. Monthly, just pull whichever of the 22 was used. You will have a hole in your tape cycle, but amanda won't care. But maybe the human (you) will :)) If so, set your label scheme up to be something like DS-xx.y where xx is your ordering sequence and y is which replac- ment. Maybe you label up DS-01.0 to DS-10.0. At the end of the month, say you have to pull DS-05.0 Mark it as no-reuse and label up a new DS-05.1. This preserves your ordering and tells you it is a tape not in the initial cycle. Might be important for some tapes (eg. DAT) which have a fairly short life. Just some ideas. jl -- 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 -- 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
Re: Using 10 tapes for fortnightly DailySet backup scheme and for a Monthly Config 12 tapes.
Hi Martin Please check over So create in /etc/amanda/MonthlySet1/amanda.conf dumpcycle 0 weeks # the number of days in the normal dump cycle runspercycle 1 # One run per month tapecycle 12 tapes # the number of tapes in rotation 12 per Year. In my crontab for amanda user # sudo -u amanda crontab -e # Backup check running amcheck at 4.30pm on the 2nd day of each and every month. 30 16 2 1-12 * /usr/sbin/amcheckMonthlySet1 # Backup dump running amdump at 18.30pm on the 2nd day of each and every month. 30 18 2 1-12 * /usr/sbin/amdump MonthlySet1 Thus label 12 Monthly tapes MonthlySet101 to MonthlySet112. Tobe pulled and archived accordingly. On Wed, 2005-06-15 at 14:55 +0100, Martin Hepworth wrote: dumpcycle 4 weeks # the number of days in the normal dump cycle runspercycle 1 # One run per month tapecycle 12 tapes # the number of tapes in rotation 12 per Year. -- 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
[dump larger than tape, 2866960 KB, but cannot incremental dump new disk]
Hi all server.domain.co.uk:/ 0 planner: [dump larger than tape, 2866960 KB, but cannot incremental dump new disk] I had changed the disklist from /etc to / and run amdump #disklist file #server.domain.co.uk / comp-root-tar #Thought I was using tar. and I get the above error. Whats the best to tackle this still using DSS-4 150mm DAT tapes. and how to cannot incremental dump new disk as above error. Thus can I change from dump to tar Chuck -- 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: [dump larger than tape, 2866960 KB, but cannot incremental dump new disk]
Hi Just read the following about amanda? Amanda can not back up filesystems that are larger than the tape will fit Amanda can not back up filesystems that are larger than the tape will fit. I. e. Amanda can not span tapes. It is unclear whether this is a bug or a feature. :-) Allowing spanning would make it difficult to perform backup recovery with standard UNIX tools, i. e. without using Amanda. One workaround is to make sure that all file systems are smaller than the tape capacity. Another is to ask Amanda to back up individual large directories as seperate Disk List Entries (DLEs). This can AFAIK only be done using tar, not using dump. One tape per day, 5 (week)days per week. We were doing all level zeros, but one of the filesystems has grown too big to do this, so now we're doing incrementals as well, with a level zero every other day for each filesystem: Thus time to look at the exclude list. Cheers On Wed, 2005-06-15 at 16:26 +0100, Chuck Amadi Systems Administrator wrote: Hi all server.domain.co.uk:/ 0 planner: [dump larger than tape, 2866960 KB, but cannot incremental dump new disk] I had changed the disklist from /etc to / and run amdump #disklist file #server.domain.co.uk / comp-root-tar #Thought I was using tar. and I get the above error. Whats the best to tackle this still using DSS-4 150mm DAT tapes. and how to cannot incremental dump new disk as above error. Thus can I change from dump to tar Chuck -- 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 commence using a previously used test tape into production cycle of tapes to backup root directory.
Hi all I have finished testing phase and I would like to use the initial tape again this tape had dumped /etc which obviously didn't dump much data. I am now going to change the disklist from /etc to / what is the best way to go about it. 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: Howto commence using a previously used test tape into production cycle of tapes to backup root directory.
Hi Great I did see that note Q: Why does `amcheck' say `cannot overwrite active tape'? A: Because, if you configure Amanda to use N tapes, by setting tapecycle to N in `amanda.conf', before Amanda overwrites a tape, it must write to at least other N-1 tapes. Of course, Amanda will always refuse to overwrite a tape marked for `noreuse' with `amadmin'. Furthermore, such tapes are not counted when Amanda computes `N-1' tapes. If, for some reason, you want to tell Amanda to overwrite a particular tape, regardless of its position in the cycle, use `amrmtape'. This command will remove this tape from the `tapelist' file, that is used to manage the tape cycle, and will delete information about backups stored in that tape from the Amanda database. Cheers On Tue, 2005-06-14 at 12:58 +0200, Filip Rembiakowski wrote: At 06/14/05 12:19, Chuck Amadi Systems Administrator wrote: Hi all I have finished testing phase and I would like to use the initial tape again this tape had dumped /etc which obviously didn't dump much data. I am now going to change the disklist from /etc to / what is the best way to go about it. Cheers just amrmtape and amlabel again :) -- 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
I am correctly concluding I need only a tapecycle of 10 tapes - Using 10 tapes for fortnightly backup scheme.
Hi I have 10 dat tapes that I will run per my cycle 5 per 5 day week. Thus every fortnight. I am correctly concluding I need only a tapecycle of 10 tapes I hope to pull out the last Friday tape in that Month to archive and thus label another tape to replace it. Here's my config file. dumpcycle 0 weeks # the number of days in the normal dump cycle runspercycle 1 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 10 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that Cheers Chuck -- 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: I am correctly concluding I need only a tapecycle of 10 tapes - Using 10 tapes for fortnightly backup scheme.
Hi Great Yes I am going to use 10 tapes in total and reuse the first tape after 10 week days worth of backups. Thus is it fine to pull the last Friday tape at the end of the Month for archiving and then re-label the tape I pulled. Thanks I am nearly there . Cheers On Tue, 2005-06-14 at 08:21 -0400, Jon LaBadie wrote: On Tue, Jun 14, 2005 at 12:45:07PM +0100, Chuck Amadi Systems Administrator wrote: Hi I have 10 dat tapes that I will run per my cycle 5 per 5 day week. Thus every fortnight. I am correctly concluding I need only a tapecycle of 10 tapes I hope to pull out the last Friday tape in that Month to archive and thus label another tape to replace it. Here's my config file. dumpcycle 0 weeks # the number of days in the normal dump cycle runspercycle 1 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 10 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that Think of tapecycle as how many different tapes amanda must use before it will reuse the first one. In your setup, it looks like full backups every run, tapecycle is as critical as a setup doing mixed full and incrementals. Set it to whatever you want, or are comfortable, having amanda not overwrite before being allowed to reuse. If you want the last 10 full dumps to be sure to be around, then set it to 10. If the last 5 is comfortable, you can set it to 5, but still use 10 tapes. Amanda will only check that at least 5 are still the most recent. -- 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
