To hardware compress or not?
Hi, Im using amanda on a linux box with an old SONY-SDT5000 DDDS2 drive. Everything works like a charm - I have actually restored some files ;) The question: Is it recommended to use hardware compression or should I leave it off? When I first configured the thing a few month ago I left compression ON, but now im not sure if it actually were a good idea. best, Kasper Kasper Edwards Ph.D. Stipendiat, Civilingeniør Institut for Produktion og Ledelse Danmarks Tekniske Universitet Byg 423, rum 028 2800 Lyngby tlf. : +45 4525 6010 Mobil: +45 2225 6320 Fax. :+45 4593 4467 Web : http://www.its.dtu.dk/ansat/ke/index_d.htm Email: [EMAIL PROTECTED]
Re: every run a new tape?
At 10:51 28-02-2002 +0100, Juanjo wrote: >Why amanda uses a new tape on every night run? > >Tapes are 40/80GB DLT1, and I dont understand why It dumps daily >incrementals to a new tape always, most of tapes are not even at 20%. > >Any help? Is it any parameter I've missed out? Amanda does not append to tape, so it expects the next tape in the cycle or a new one. /Kasper
Re: Disaster Recovery on Windows
At 15:58 25-02-2002 -0500, Jan Boshoff wrote: >Hi all > >I just had a thought and would like to probe the great minds of this >list. Would anyone do a disaster recovery type of restore of a Winbox >that was backed up using smbclient?I'm currently backing up the >complete winbox, but it occured to me that I don't know how I would >restore if something happened to the Winbox that we needed to restore >the complete drive. I mean, you need to have Win installed for >smbclient to talk to it accross the network. I have thought about but not yet implemented anything so be advised: This is thought-stuff ;) Use a regular win98 (or perhaps toms rtbt) bootfloppy to partition and format filesystem (not NTFS - but you could convert to NTFS later). Use toms RTBT http://www.toms.net/rb/ to boot a micro linux and mount the filesystem with network support to retrive the image from the server. Toms RTBT has a small tar and gzip that could extract the image. Be sure to have the boot sector backuped up using dd (also on toms RTBT). As I said, not tested yet but I think it should work. If you test something like this please post your findings. best, Kasper
Re: dumper is dying
It seems that .amandahosts was the source of the problem. When I use the full hostname 'bifrost.edwards.dk' in .amhosts and disklist the dumper dies. However, uing only the hostname 'bifrost' in both .amhosts and disklist solved the problem. /Kasper At 12:44 21-02-2002 +0100, Kasper Edwards wrote: >I got the following error today: > bifrost/usr lev 0 FAILED [dumper1 died] >[snip] >NOTES: > planner: Adding new disk bifrost:/usr. > driver: dumper0 pid 16521 is messed up, ignoring it. > driver: dumper0 died while dumping bifrost:/usr lev 0. > driver: dumper1 pid 16522 is messed up, ignoring it. > taper: tape daily2 kb 0 fm 0 [OK] > >This happened after I changed from using localhost to hostname (bifrost) >in the disklist. The hostname is recognised on the computer and dump >starts fine, but somewhare in begining of the process I get the error. It >works fine as long as I use localhost in the disk list, however localhost >is no good to use. >Im running Amanda 2.4.2p2 on redhat 7.1. >sendbackup.debug is below. > >Thanks > >Kasper > >sendbackup: debug 1 pid 16586 ruid 33 euid 33 start time Wed Feb 20 >21:56:25 2002 >/usr/lib/amanda/sendbackup: version 2.4.2p2 >sendbackup: got input request: GNUTAR /usr 0 1970:1:1:0:0:0 OPTIONS >|;bsd-auth;srvcomp-best;index; > parsed request as: program `GNUTAR' > disk `/usr' > lev 0 > since 1970:1:1:0:0:0 > opt `|;bsd-auth;srvcomp-best;index;' >sendbackup: try_socksize: send buffer size is 65536 >sendbackup: stream_server: waiting for connection: 0.0.0.0.33863 >sendbackup: stream_server: waiting for connection: 0.0.0.0.33864 >sendbackup: stream_server: waiting for connection: 0.0.0.0.33865 > waiting for connect on 33863, then 33864, then 33865 >sendbackup: stream_accept: connection from 192.168.1.1.33866 >sendbackup: stream_accept: connection from 192.168.1.1.33867 >sendbackup: stream_accept: connection from 192.168.1.1.33868 > got all connections >sendbackup-gnutar: doing level 0 dump as listed-incremental to >/var/lib/amanda/gnutar-lists/bifrost_usr_0.new >sendbackup-gnutar: doing level 0 dump from date: 1970-01-01 0:00:00 GMT >sendbackup: spawning /usr/lib/amanda/runtar in pipeline >sendbackup: argument list: gtar --create --file - --directory /usr >--one-file-system --listed-incremental >/var/lib/amanda/gnutar-lists/bifrost_usr_0.new --sparse >--ignore-failed-read --totals . >sendbackup: started index creator: "/bin/tar -tf - 2>/dev/null | sed -e >'s/^\.//'" >sendbackup-gnutar: /usr/lib/amanda/runtar: pid 16590 >index tee cannot write [Connection reset by peer] >sendbackup: pid 16589 finish time Wed Feb 20 22:13:40 2002 > > > > > >Kasper Edwards >Ph.D. Stipendiat, Civilingeniør >Institut for Produktion og Ledelse >Danmarks Tekniske Universitet >Byg 423, rum 028 >2800 Lyngby >tlf. : +45 4525 6010 >Mobil: +45 2225 6320 >Fax. :+45 4593 4467 >Web : http://www.its.dtu.dk/ansat/ke/index_d.htm >Email: [EMAIL PROTECTED]
dumper is dying
I got the following error today: bifrost/usr lev 0 FAILED [dumper1 died] [snip] NOTES: planner: Adding new disk bifrost:/usr. driver: dumper0 pid 16521 is messed up, ignoring it. driver: dumper0 died while dumping bifrost:/usr lev 0. driver: dumper1 pid 16522 is messed up, ignoring it. taper: tape daily2 kb 0 fm 0 [OK] This happened after I changed from using localhost to hostname (bifrost) in the disklist. The hostname is recognised on the computer and dump starts fine, but somewhare in begining of the process I get the error. It works fine as long as I use localhost in the disk list, however localhost is no good to use. Im running Amanda 2.4.2p2 on redhat 7.1. sendbackup.debug is below. Thanks Kasper sendbackup: debug 1 pid 16586 ruid 33 euid 33 start time Wed Feb 20 21:56:25 2002 /usr/lib/amanda/sendbackup: version 2.4.2p2 sendbackup: got input request: GNUTAR /usr 0 1970:1:1:0:0:0 OPTIONS |;bsd-auth;srvcomp-best;index; parsed request as: program `GNUTAR' disk `/usr' lev 0 since 1970:1:1:0:0:0 opt `|;bsd-auth;srvcomp-best;index;' sendbackup: try_socksize: send buffer size is 65536 sendbackup: stream_server: waiting for connection: 0.0.0.0.33863 sendbackup: stream_server: waiting for connection: 0.0.0.0.33864 sendbackup: stream_server: waiting for connection: 0.0.0.0.33865 waiting for connect on 33863, then 33864, then 33865 sendbackup: stream_accept: connection from 192.168.1.1.33866 sendbackup: stream_accept: connection from 192.168.1.1.33867 sendbackup: stream_accept: connection from 192.168.1.1.33868 got all connections sendbackup-gnutar: doing level 0 dump as listed-incremental to /var/lib/amanda/gnutar-lists/bifrost_usr_0.new sendbackup-gnutar: doing level 0 dump from date: 1970-01-01 0:00:00 GMT sendbackup: spawning /usr/lib/amanda/runtar in pipeline sendbackup: argument list: gtar --create --file - --directory /usr --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/bifrost_usr_0.new --sparse --ignore-failed-read --totals . sendbackup: started index creator: "/bin/tar -tf - 2>/dev/null | sed -e 's/^\.//'" sendbackup-gnutar: /usr/lib/amanda/runtar: pid 16590 index tee cannot write [Connection reset by peer] sendbackup: pid 16589 finish time Wed Feb 20 22:13:40 2002 ------------ Kasper Edwards Ph.D. Stipendiat, Civilingeniør Institut for Produktion og Ledelse Danmarks Tekniske Universitet Byg 423, rum 028 2800 Lyngby tlf. : +45 4525 6010 Mobil: +45 2225 6320 Fax. :+45 4593 4467 Web : http://www.its.dtu.dk/ansat/ke/index_d.htm Email: [EMAIL PROTECTED]
Re: about amanda holding disk...
At 14:26 03-01-2002 -0500, Dengfeng Liu wrote: >Since my incremental backup is not so big(about 20G)per day. I want >amanda to put daily incremental backup to the holding disk first. and then >after 3 or 4 days, I flush it to one tape(100G capacity).That means the >holding disk will have 3 or 4 days of incremental backup. how can I do >this in configuration file or which command should I run? > >Another rookie question is: Currently I use Sony AIT2 50/100 tape device, >each time I run amdump manually to do the backup. Now I want amanda to do >it automatedly. Starting with the second question. Run amdump as a cronjob or a similar thing that will let you run commands at a specific time. With this working you dont have to do anything to get your dumps to the holding disk. If you dont put a tape in the drive amdump will complain a bit and dump to the holding disk. You can then flush to tape at when appropriate. >But, Amanda automatically schedules full/incremental dumps >to maintain balanced daily runtimes and tape usage, If I do a full backup >each month, then the backup machine is totally down in the middle of the >month, does that means the only backup I have is the backup of last >month?(since this month's full backup is not finished) As far as I know, No, you have what has been backed the first half of the month. Not knowing the detail I would guess that amanda gives priority to new and changed files so the damage is minimised - but others on this list will know better... Kasper
Re: Backup cycle
At 11:51 14-02-2002 +0100, Juanjo wrote: >I have 9 slot autoloader, on slot 9 I have cleaning tape, well, my >dumpcycle is one week, and tapecycle is 8. > >My idea was doing incrementals during weekdays and full backup on weekend. >I have been reading around and seems that amanda works different. So.. in >order to achieve such a configuration, what kind of dumptype should I >declare in amanda.conf ? That's a common thing when configuring amanda. You dont configure amanda to do full/incremental dump of disk Y at day X. Within a dumpcycle you are guarenteed a full dump of all disks plus incremental dumps. Amanda does a good job of planning the backup - let her do her thing ;) All you need to do is ensure that a dumpcycle contains ample room for a full dump of all disks plus, say, 10-20% extra for incrementals. (make sure the size of a single disk does not exceed capacity of single tape) Best, Kasper
Re: HP SureStore AutoLoader
At 11:34 13-02-2002 +0100, Juanjo wrote: >Well, I downloaded 2.4.3b2 cause got no success with Debian package which >was 2.4.2p2, so I thought that newer version might have better chg >scripts. Could this just be related to the packaged version? It seems that many people has problems with packaged versions of amanda. For that reason its always encuraged to compile and install from source. >Btw: I'm trying with chg-scsi (hard since it aint script) and it generated >a big big file (6gig and growing up), is it normal? > I have no experience with the chg scripts, but it sounds very wrong. best Kasper >-Original Message- >From: Kasper Edwards <[EMAIL PROTECTED]> >To: "Juanjo" <[EMAIL PROTECTED]> >Date: Wed, 13 Feb 2002 11:07:36 +0100 >Subject: Re: HP SureStore AutoLoader > > > At 10:37 13-02-2002 +0100, Juanjo wrote: > > >Hello, > > > > > >I'm trying to config a backup system with amanda-2.4.3b2. > > > > I hope you are aware that your are using the beta version. If you want > > this > > thing running urgent I would suggest Amanda-2.4.2p2. > > > > > > best, > > > > Kasper > >
dumper died
ted_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" got packet: Amanda 2.4 REQ HANDLE 000-A09D0708 SEQ 1013338258 SECURITY USER amanda SERVICE sendbackup OPTIONS hostname=bifrost; GNUTAR /usr 0 1970:1:1:0:0:0 OPTIONS |;bsd-auth;no-record; sending ack: Amanda 2.4 ACK HANDLE 000-A09D0708 SEQ 1013338258 bsd security: remote host bifrost.edwards.dk user amanda local user amanda amandahosts security check passed amandad: running service "/usr/lib/amanda/sendbackup" amandad: sending REP packet: Amanda 2.4 REP HANDLE 000-A09D0708 SEQ 1013338258 CONNECT DATA 32955 MESG 32956 INDEX -1 OPTIONS ;no-record;bsd-auth; amandad: got packet: Amanda 2.4 ACK HANDLE 000-A09D0708 SEQ 1013338258 amandad: pid 17985 finish time Sun Feb 10 11:51:55 2002 **AMANDAD debug end ***SELFCHECK..debug START*** bash-2.04$ cat selfcheck.20020210114957.debug selfcheck: debug 1 pid 17956 ruid 33 euid 33 start time Sun Feb 10 11:49:57 2002 /usr/lib/amanda/selfcheck: version 2.4.2p2 selfcheck: checking disk /usr selfcheck: device /usr selfcheck: OK selfcheck: pid 17956 finish time Sun Feb 10 11:49:57 2002 SELFCHECK..DEBUG end **RUNTAR..DEBUG start bash-2.04$ cat runtar.20020210115155.debug runtar: debug 1 pid 17987 ruid 33 euid 0 start time Sun Feb 10 11:51:55 2002 gtar: version 2.4.2p2 running: /bin/tar: gtar --create --file - --directory /usr --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/bifrost_usr_0.new --sparse --ignore-failed-read --totals . bash-2.04$ ** RUNTAR..debug end* Kasper Edwards Ph.D. Stipendiat, Civilingeniør Institut for Produktion og Ledelse Danmarks Tekniske Universitet Byg 423, rum 028 2800 Lyngby tlf. : +45 4525 6010 Mobil: +45 2225 6320 Fax. :+45 4593 4467 Web : http://www.its.dtu.dk/ansat/ke/index_d.htm Email: [EMAIL PROTECTED]
Re: GNUTAR program not available
I had a similar problem that meant amverify was not working. For some reason tar was not available. I had to delete configure.cache, make a symlink /usr/bin/gtar -> /bin/tar, chown amanda:disk /usr/bin/gtar and then ./comfigure bla.bla. -with-gnutar=/usr/bin/gtar versions: amanda 2.4.p2, redhat7.1 patched. For what its worth, Kasper At 10:55 04-02-2002 -0500, Davidson, Brian wrote: >Amanda Backup Client Hosts Check > >ERROR: db-test.ems.sat: [GNUTAR program not available] > >GNU tar exists on the client machine, I can log in as amanda, and gnu tar is >in amanda's path. I can also execute gnu tar as the amanda user. Owners for >tar are: > > -r-xr-xr-x 1 root other 901120 Feb 4 10:15 tar > >amanda runs as user amanda: group operator. What am I not doing correctly >here? > >Thanks, > >Brian Davidson >DynCorp Treasury Integration Group >11710 Plaza America Dr. >Reston, VA 20190 >703-261-4694 >[EMAIL PROTECTED]
Re: What if ... ( the index under /var/amanda is gone )
I have a cron job emailing me a sorted index list every night after backup has been performed. Look: date host disklv tape or file file status 2002-01-17 localhost /1 daily6 10 OK 2002-01-17 localhost /boot1 daily6 2 OK 2002-01-17 localhost /games 1 daily6 1 OK 2002-01-17 localhost /home/drivers1 daily6 7 OK 2002-01-17 localhost /home/ke 2 daily6 14 OK 2002-01-17 localhost /home/software 1 daily6 4 OK 2002-01-17 localhost /tmp 1 daily6 3 OK 2002-01-17 localhost /usr 1 daily6 13 OK 2002-01-17 localhost /var 1 daily6 12 OK 2002-01-16 localhost /1 daily5 4 OK 2002-01-16 localhost /boot0 daily5 10 OK 2002-01-16 localhost /games 0 daily5 7 OK 2002-01-16 localhost /home/drivers0 daily5 12 OK It's sortet by date rather than disk so that I can find the latest full and incremental backup in a hurry. It gives me complete oversight of where to find the tapes of backed up disks. The list also has the filemark numbers to one could easily restore from a floppy with minimum system and tar. One could also tar the amanda database and also email/baskup this on another machine. In my case that would be overkill, the anamda database would quickly be recovered from the tape containing /var with the above list. All that is left to backup is metadata, amandaconfig (to know dumptype etc.) and the boot block. Get the new disk(s), full recover and back in business. I have a small script that collects most of these (except the bootblock) and send me an email, I run it after any change. ps. If you spot any problems in the above please let me know. I hate to find out the hard way. It's a new setup and full recover will be tested for the first time this weekend, exiting ;). As you know there's no points for backing up, only restoring. best, Kasper At 10:15 17-01-2002 +0100, you wrote: >Hi all, > >perhaps you asked yourself too, I don´t get the clue: > >The index is stored under /var/amanda... and the index stores all places >where to find backups on the different tapes - so far am I right? > >Now, the server dies and all disks go south, so /var/amanda --- the index >must be gone - so far am I right ? > >I now would have to figure out by hand on what type I can find the level 0 >dump for my /var/amanda directory, then I will have to figure out the last >incremental, then I can restore the amanda-index and can then continue to >restore the rest of the amanda-server - am I right here? > >What do you do, in case there is a real emergency that you don´t have to >figure out, on what tape which dump was written without having access to >the index ??? > >Best regards > > >-- >Andreas Baier >MindMatics AG fon: +49 (0)89 322986-0 >Frankfurter Ring 193a fax: +49 (0)89 9227 9897 >80807 Munichinternet: www.mindmatics.de >Germany
Re: amrecover - dealing with whitespace in names
At 09:42 04-01-2002 -0500, Jean-Louis Martineau wrote: >On Fri, Jan 04, 2002 at 01:13:56AM -0500, Jon LaBadie wrote: > > amrecover doesn't seem to have a way to deal with > > whitespace in directory/file names. I've tried > > wildcards (*, ., ?), quoting (single and double) > > and ignoring the spaces actually there. > >You can 'add' or 'addx' files with space using wildcards or regex. >If you want to cd to a directory with space you need the latest >2.4.3b1 from http://www.iro.umontreal.ca/~martinea/amanda Im using amanda 2.4.3b2. It sems that there are still problems cd'ing to directories containing whitespace: AMRECOVER Version 2.4.3b2. Contacting server on .. amrecover> setdisk /home/drivers 200 Disk set to /home/drivers. amrecover> ls 2002-01-11 HP4000/ 2002-01-11 HP890 Color/ 2002-01-11 wacom/ 2002-01-11 webcam3/ amrecover> cd HP890 Color/ Invalid directory - HP890 Invalid command - parse error amrecover> This is consistent with all directories containing whitespace. The disk above is a ext3 directory on a RH7.1 box. Fun thing is that filenamecompletion (tab) works perfectly, the part after whitespace. I can add using wildcards so it more annoying than an actual problem. Best Kasper
To hardware compress or not?
Hi, Im using amanda on a linux box with an old SONY-SDT5000 DDDS2 drive. Everything works like a charm - I have actually restored some files ;) The question: Is it recommended to use hardware compression or should I leave it off? When I first configured the thing a few month ago I left compression ON, but now im not sure if it actually were a good idea. best, Kasper Kasper Edwards Ph.D. Stipendiat, Civilingeniør Institut for Produktion og Ledelse Danmarks Tekniske Universitet Byg 423, rum 028 2800 Lyngby tlf. : +45 4525 6010 Mobil: +45 2225 6320 Fax. :+45 4593 4467 Web : http://www.its.dtu.dk/ansat/ke/index_d.htm Email: [EMAIL PROTECTED]
Follow symlinks - possible?
Is it possible to make amanda follow symlinks? I have a disk that has grown larger than the tape used and need a way to backup this disk without splitting it into different disks. I made a script that creates a few directories and populate these with symlinks to the large disk. Treating these directories as seperate disks should work if I could only get amanda to follow symlinks. The faq has a mention about creating a wrapper around tar - amtar. But, if I understand correct, this will make amanda follow symlinks in all situations. What is needed is an option that will pass "--dereference" to tar. Any suggestions? Thanks, Kasper (Im running amanda 2.4.3b1)
Re: about amanda holding disk...
At 14:26 03-01-2002 -0500, Dengfeng Liu wrote: >Since my incremental backup is not so big(about 20G)per day. I want >amanda to put daily incremental backup to the holding disk first. and then >after 3 or 4 days, I flush it to one tape(100G capacity).That means the >holding disk will have 3 or 4 days of incremental backup. how can I do >this in configuration file or which command should I run? > >Another rookie question is: Currently I use Sony AIT2 50/100 tape device, >each time I run amdump manually to do the backup. Now I want amanda to do >it automatedly. Starting with the second question. Run amdump as a cronjob or a similar thing that will let you run commands at a specific time. With this working you dont have to do anything to get your dumps to the holding disk. If you dont put a tape in the drive amdump will complain a bit and dump to the holding disk. You can then flush to tape at when appropriate. >But, Amanda automatically schedules full/incremental dumps >to maintain balanced daily runtimes and tape usage, If I do a full backup >each month, then the backup machine is totally down in the middle of the >month, does that means the only backup I have is the backup of last >month?(since this month's full backup is not finished) As far as I know, No, you have what has been backed the first half of the month. Not knowing the detail I would guess that amanda gives priority to new and changed files so the damage is minimised - but others on this list will know better... Kasper
