Re: Using amrecover - strange happenings
On Thursday 29 September 2005 23:01, Steve H wrote: >Gene, > Yes, the index file does exist, and I have two good backups to > attempt to restore from. However, in checking the Index files, I > noticed that the actual files had a different date on them (august 5th) > while all the directories have august 11th. This is bothering me > because that shouldn't happen. Would Amanda backup only the > directories if the tape becomes full? Either way, I have the tape from > August 5th, and when I do a Setdate 2005-05-08, everything shows up in > the index file as it should. I just can't restore files from > it...directories work great...LOL. > >Any help is greatly apprecaited Gene, >Steve Can you read the tape with dd & tar + gunzip according to the instructions in the first block of every file? I'm hitting the sack now, dunno who's still up, Steve. Jon's been known to be a night owl too. Right now I'm half disgusted, my less than a year old, only a 100 pack of cd's thru it, LiteOn dvd/cdr burner just went toes up. The cheaper they get, the cheaper they are... >--- Gene Heskett <[EMAIL PROTECTED]> wrote: >> On Thursday 29 September 2005 22:21, Steve H wrote: >> >I checked the amanda.conf file, and yes, I am indexing. >> > >> >Thanks, >> >Steve >> >> I'll be up for a little bit yet. Does the index file exist? >> >> >--- Gene Heskett <[EMAIL PROTECTED]> wrote: >> >> On Thursday 29 September 2005 21:26, Steve H wrote: >> >> >I am on a Red Hat 9 box. Pervious tar verion was 1.13, just >> >> > upgraded to 1.15 and it didn't fix the issue. What do you mean by >> >> > indexing DLE? >> >> > >> >> >Thanks, >> >> >Steve >> >> >> >> I think he was referring to the DLE (DiskList Entry) pointing to a >> >> dumptype that had a line saying "index yes". >> >> >> >> You can set this once in the global section of your amanda.conf as >> >> long as the final dumptype chosen does an "include global" >> >> >> >> >--- Vera <[EMAIL PROTECTED]> wrote: >> >> >> I do not remember exactly what was a reason for this error, but >> >> >> I saw it before :-) >> >> >> >> >> >> 1. Are you indexing this DLE? >> >> >> 2. What OS are you using? FC3 distributive had tar 1.14 with a >> >> >> bug - > check the amrecover log file and if error happens at the >> >> >> "tar" point, then simple upgrade your tar RPM or reinstall it >> >> >> from sources >> >> >> >> >> >> - Original Message - >> >> >> From: "Steve H" <[EMAIL PROTECTED]> >> >> >> To: >> >> >> Sent: Thursday, September 29, 2005 5:42 PM >> >> >> Subject: Using amrecover - strange happenings >> >> >> >> >> >> > Guys, >> >> >> > >> >> >> > I would appreciate some help with this one, as it's freaking >> >> >> > me out. I have >> >> >> > been getting backups for a while now of a particular host and >> >> >> > file system. I >> >> >> > have tested the recovery before and it worked great. >> >> >> > This time, I put the necessary tape in, and run amrecover >> >> >> > and it will only >> >> >> > restore the directories. The files will not restore, and I >> >> >> > keep getting the >> >> >> > error: >> >> >> > >> >> >> > ./laptopBackups/Documents and Settings/My Documents/ >> >> >> > tar: Unexpected EOF in archive >> >> >> > tar: Error is not recoverable: exiting now >> >> >> > extract_list - child returned non-zero status: 2 >> >> >> > Continue [?/Y/n]? >> >> >> > >> >> >> > so I started looking at the actual index for that and their >> >> >> > are no files listed >> >> >> > in the index, only directories. >> >> >> > >> >> >> > I started checking the dates, and it seems like the >> >> >> > directories have been backed up, and they all have the same >> >> >> > date of backup, but the actual documents >> >> >> > have a different date. It's like they were backed up once, >> >> >> > but never got backed up again. >> >> >> > >> >> >> > Does this have to do with the tape rotation? what am I >> >> >> > missing? I have the >> >> >> > tape that lists the documents, and it even lists them when I >> >> >> > browse the tape >> >> >> > with amrecover, but I can't extract them, I get the error >> >> >> > above. >> >> >> > >> >> >> > Please help, >> >> >> > Steve >> >> >> > >> >> >> > >> >> >> > >> >> >> > __ >> >> >> > Yahoo! Mail - PC Magazine Editors' Choice 2005 >> >> >> > http://mail.yahoo.com >> >> > >> >> >__ >> >> >Yahoo! Mail - PC Magazine Editors' Choice 2005 >> >> >http://mail.yahoo.com >> >> >> >> -- >> >> Cheers, Gene >> >> "There are four boxes to be used in defense of liberty: >> >> soap, ballot, jury, and ammo. Please use in that order." >> >> -Ed Howdershelt (Author) >> >> 99.35% setiathome rank, not too shabby for a WV hillbilly >> >> Yahoo.com and AOL/TW attorneys please note, additions to the above >> >> message by Gene Heskett are: >> >> Copyright 2005 by Maurice Eugene Heskett, all rights reserved. >> > >> >__ >> >Yahoo! Mail - PC Magazine Editors' Choice 2005 >> >http://m
Re: Using amrecover - strange happenings
One more item to note. I attempted to use amrestore instead of amrecover, and after specifying the command: amrestore -p /dev/nst0 host.domain /home/public | restore -ivf - I got this error: Input block size is 32 restore: Tape is not a dump tape Error 32 (Broken pipe) offset 32768+32768, wrote 0 amrestore: pipe reader has quit in middle of file. Any Ideas? Why would it error with "tape is not a dump tape"? Thanks, Steve __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
Re: Using amrecover - strange happenings
Gene, Yes, the index file does exist, and I have two good backups to attempt to restore from. However, in checking the Index files, I noticed that the actual files had a different date on them (august 5th) while all the directories have august 11th. This is bothering me because that shouldn't happen. Would Amanda backup only the directories if the tape becomes full? Either way, I have the tape from August 5th, and when I do a Setdate 2005-05-08, everything shows up in the index file as it should. I just can't restore files from it...directories work great...LOL. Any help is greatly apprecaited Gene, Steve --- Gene Heskett <[EMAIL PROTECTED]> wrote: > On Thursday 29 September 2005 22:21, Steve H wrote: > >I checked the amanda.conf file, and yes, I am indexing. > > > >Thanks, > >Steve > > I'll be up for a little bit yet. Does the index file exist? > > > >--- Gene Heskett <[EMAIL PROTECTED]> wrote: > >> On Thursday 29 September 2005 21:26, Steve H wrote: > >> >I am on a Red Hat 9 box. Pervious tar verion was 1.13, just upgraded > >> > to 1.15 and it didn't fix the issue. What do you mean by indexing > >> > DLE? > >> > > >> >Thanks, > >> >Steve > >> > >> I think he was referring to the DLE (DiskList Entry) pointing to a > >> dumptype that had a line saying "index yes". > >> > >> You can set this once in the global section of your amanda.conf as > >> long as the final dumptype chosen does an "include global" > >> > >> >--- Vera <[EMAIL PROTECTED]> wrote: > >> >> I do not remember exactly what was a reason for this error, but I > >> >> saw it before :-) > >> >> > >> >> 1. Are you indexing this DLE? > >> >> 2. What OS are you using? FC3 distributive had tar 1.14 with a bug > >> >> - > check the amrecover log file and if error happens at the "tar" > >> >> point, then simple upgrade your tar RPM or reinstall it from > >> >> sources > >> >> > >> >> - Original Message - > >> >> From: "Steve H" <[EMAIL PROTECTED]> > >> >> To: > >> >> Sent: Thursday, September 29, 2005 5:42 PM > >> >> Subject: Using amrecover - strange happenings > >> >> > >> >> > Guys, > >> >> > > >> >> > I would appreciate some help with this one, as it's freaking me > >> >> > out. I have > >> >> > been getting backups for a while now of a particular host and > >> >> > file system. I > >> >> > have tested the recovery before and it worked great. > >> >> > This time, I put the necessary tape in, and run amrecover and > >> >> > it will only > >> >> > restore the directories. The files will not restore, and I keep > >> >> > getting the > >> >> > error: > >> >> > > >> >> > ./laptopBackups/Documents and Settings/My Documents/ > >> >> > tar: Unexpected EOF in archive > >> >> > tar: Error is not recoverable: exiting now > >> >> > extract_list - child returned non-zero status: 2 > >> >> > Continue [?/Y/n]? > >> >> > > >> >> > so I started looking at the actual index for that and their are > >> >> > no files listed > >> >> > in the index, only directories. > >> >> > > >> >> > I started checking the dates, and it seems like the directories > >> >> > have been backed up, and they all have the same date of backup, > >> >> > but the actual documents > >> >> > have a different date. It's like they were backed up once, but > >> >> > never got backed up again. > >> >> > > >> >> > Does this have to do with the tape rotation? what am I missing? > >> >> > I have the > >> >> > tape that lists the documents, and it even lists them when I > >> >> > browse the tape > >> >> > with amrecover, but I can't extract them, I get the error above. > >> >> > > >> >> > Please help, > >> >> > Steve > >> >> > > >> >> > > >> >> > > >> >> > __ > >> >> > Yahoo! Mail - PC Magazine Editors' Choice 2005 > >> >> > http://mail.yahoo.com > >> > > >> >__ > >> >Yahoo! Mail - PC Magazine Editors' Choice 2005 > >> >http://mail.yahoo.com > >> > >> -- > >> Cheers, Gene > >> "There are four boxes to be used in defense of liberty: > >> soap, ballot, jury, and ammo. Please use in that order." > >> -Ed Howdershelt (Author) > >> 99.35% setiathome rank, not too shabby for a WV hillbilly > >> Yahoo.com and AOL/TW attorneys please note, additions to the above > >> message by Gene Heskett are: > >> Copyright 2005 by Maurice Eugene Heskett, all rights reserved. > > > >__ > >Yahoo! Mail - PC Magazine Editors' Choice 2005 > >http://mail.yahoo.com > > -- > Cheers, Gene > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author) > 99.35% setiathome rank, not too shabby for a WV hillbilly > Yahoo.com and AOL/TW attorneys please note, additions to the above > message by Gene Heskett are: > Copyright 2005 by Maurice Eugene Heskett, all rights reserved. > > __ Yahoo! for Good Donate to the Hurricane Katrina relief effo
Re: Using amrecover - strange happenings
On Thursday 29 September 2005 22:21, Steve H wrote: >I checked the amanda.conf file, and yes, I am indexing. > >Thanks, >Steve I'll be up for a little bit yet. Does the index file exist? > >--- Gene Heskett <[EMAIL PROTECTED]> wrote: >> On Thursday 29 September 2005 21:26, Steve H wrote: >> >I am on a Red Hat 9 box. Pervious tar verion was 1.13, just upgraded >> > to 1.15 and it didn't fix the issue. What do you mean by indexing >> > DLE? >> > >> >Thanks, >> >Steve >> >> I think he was referring to the DLE (DiskList Entry) pointing to a >> dumptype that had a line saying "index yes". >> >> You can set this once in the global section of your amanda.conf as >> long as the final dumptype chosen does an "include global" >> >> >--- Vera <[EMAIL PROTECTED]> wrote: >> >> I do not remember exactly what was a reason for this error, but I >> >> saw it before :-) >> >> >> >> 1. Are you indexing this DLE? >> >> 2. What OS are you using? FC3 distributive had tar 1.14 with a bug >> >> - > check the amrecover log file and if error happens at the "tar" >> >> point, then simple upgrade your tar RPM or reinstall it from >> >> sources >> >> >> >> - Original Message - >> >> From: "Steve H" <[EMAIL PROTECTED]> >> >> To: >> >> Sent: Thursday, September 29, 2005 5:42 PM >> >> Subject: Using amrecover - strange happenings >> >> >> >> > Guys, >> >> > >> >> > I would appreciate some help with this one, as it's freaking me >> >> > out. I have >> >> > been getting backups for a while now of a particular host and >> >> > file system. I >> >> > have tested the recovery before and it worked great. >> >> > This time, I put the necessary tape in, and run amrecover and >> >> > it will only >> >> > restore the directories. The files will not restore, and I keep >> >> > getting the >> >> > error: >> >> > >> >> > ./laptopBackups/Documents and Settings/My Documents/ >> >> > tar: Unexpected EOF in archive >> >> > tar: Error is not recoverable: exiting now >> >> > extract_list - child returned non-zero status: 2 >> >> > Continue [?/Y/n]? >> >> > >> >> > so I started looking at the actual index for that and their are >> >> > no files listed >> >> > in the index, only directories. >> >> > >> >> > I started checking the dates, and it seems like the directories >> >> > have been backed up, and they all have the same date of backup, >> >> > but the actual documents >> >> > have a different date. It's like they were backed up once, but >> >> > never got backed up again. >> >> > >> >> > Does this have to do with the tape rotation? what am I missing? >> >> > I have the >> >> > tape that lists the documents, and it even lists them when I >> >> > browse the tape >> >> > with amrecover, but I can't extract them, I get the error above. >> >> > >> >> > Please help, >> >> > Steve >> >> > >> >> > >> >> > >> >> > __ >> >> > Yahoo! Mail - PC Magazine Editors' Choice 2005 >> >> > http://mail.yahoo.com >> > >> >__ >> >Yahoo! Mail - PC Magazine Editors' Choice 2005 >> >http://mail.yahoo.com >> >> -- >> Cheers, Gene >> "There are four boxes to be used in defense of liberty: >> soap, ballot, jury, and ammo. Please use in that order." >> -Ed Howdershelt (Author) >> 99.35% setiathome rank, not too shabby for a WV hillbilly >> Yahoo.com and AOL/TW attorneys please note, additions to the above >> message by Gene Heskett are: >> Copyright 2005 by Maurice Eugene Heskett, all rights reserved. > >__ >Yahoo! Mail - PC Magazine Editors' Choice 2005 >http://mail.yahoo.com -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.35% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Using amrecover - strange happenings
I checked the amanda.conf file, and yes, I am indexing. Thanks, Steve --- Gene Heskett <[EMAIL PROTECTED]> wrote: > On Thursday 29 September 2005 21:26, Steve H wrote: > >I am on a Red Hat 9 box. Pervious tar verion was 1.13, just upgraded to > > 1.15 and it didn't fix the issue. What do you mean by indexing DLE? > > > >Thanks, > >Steve > > > I think he was referring to the DLE (DiskList Entry) pointing to a > dumptype that had a line saying "index yes". > > You can set this once in the global section of your amanda.conf as > long as the final dumptype chosen does an "include global" > > >--- Vera <[EMAIL PROTECTED]> wrote: > >> I do not remember exactly what was a reason for this error, but I saw > >> it before :-) > >> > >> 1. Are you indexing this DLE? > >> 2. What OS are you using? FC3 distributive had tar 1.14 with a bug - > > >> check the amrecover log file and if error happens at the "tar" point, > >> then simple upgrade your tar RPM or reinstall it from sources > >> > >> - Original Message - > >> From: "Steve H" <[EMAIL PROTECTED]> > >> To: > >> Sent: Thursday, September 29, 2005 5:42 PM > >> Subject: Using amrecover - strange happenings > >> > >> > Guys, > >> > > >> > I would appreciate some help with this one, as it's freaking me > >> > out. I have > >> > been getting backups for a while now of a particular host and file > >> > system. I > >> > have tested the recovery before and it worked great. > >> > This time, I put the necessary tape in, and run amrecover and it > >> > will only > >> > restore the directories. The files will not restore, and I keep > >> > getting the > >> > error: > >> > > >> > ./laptopBackups/Documents and Settings/My Documents/ > >> > tar: Unexpected EOF in archive > >> > tar: Error is not recoverable: exiting now > >> > extract_list - child returned non-zero status: 2 > >> > Continue [?/Y/n]? > >> > > >> > so I started looking at the actual index for that and their are no > >> > files listed > >> > in the index, only directories. > >> > > >> > I started checking the dates, and it seems like the directories have > >> > been backed up, and they all have the same date of backup, but the > >> > actual documents > >> > have a different date. It's like they were backed up once, but > >> > never got backed up again. > >> > > >> > Does this have to do with the tape rotation? what am I missing? I > >> > have the > >> > tape that lists the documents, and it even lists them when I browse > >> > the tape > >> > with amrecover, but I can't extract them, I get the error above. > >> > > >> > Please help, > >> > Steve > >> > > >> > > >> > > >> > __ > >> > Yahoo! Mail - PC Magazine Editors' Choice 2005 > >> > http://mail.yahoo.com > > > >__ > >Yahoo! Mail - PC Magazine Editors' Choice 2005 > >http://mail.yahoo.com > > -- > Cheers, Gene > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author) > 99.35% setiathome rank, not too shabby for a WV hillbilly > Yahoo.com and AOL/TW attorneys please note, additions to the above > message by Gene Heskett are: > Copyright 2005 by Maurice Eugene Heskett, all rights reserved. > > __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
Re: Using amrecover - strange happenings
On Thursday 29 September 2005 21:26, Steve H wrote: >I am on a Red Hat 9 box. Pervious tar verion was 1.13, just upgraded to > 1.15 and it didn't fix the issue. What do you mean by indexing DLE? > >Thanks, >Steve > I think he was referring to the DLE (DiskList Entry) pointing to a dumptype that had a line saying "index yes". You can set this once in the global section of your amanda.conf as long as the final dumptype chosen does an "include global" >--- Vera <[EMAIL PROTECTED]> wrote: >> I do not remember exactly what was a reason for this error, but I saw >> it before :-) >> >> 1. Are you indexing this DLE? >> 2. What OS are you using? FC3 distributive had tar 1.14 with a bug - > >> check the amrecover log file and if error happens at the "tar" point, >> then simple upgrade your tar RPM or reinstall it from sources >> >> - Original Message - >> From: "Steve H" <[EMAIL PROTECTED]> >> To: >> Sent: Thursday, September 29, 2005 5:42 PM >> Subject: Using amrecover - strange happenings >> >> > Guys, >> > >> > I would appreciate some help with this one, as it's freaking me >> > out. I have >> > been getting backups for a while now of a particular host and file >> > system. I >> > have tested the recovery before and it worked great. >> > This time, I put the necessary tape in, and run amrecover and it >> > will only >> > restore the directories. The files will not restore, and I keep >> > getting the >> > error: >> > >> > ./laptopBackups/Documents and Settings/My Documents/ >> > tar: Unexpected EOF in archive >> > tar: Error is not recoverable: exiting now >> > extract_list - child returned non-zero status: 2 >> > Continue [?/Y/n]? >> > >> > so I started looking at the actual index for that and their are no >> > files listed >> > in the index, only directories. >> > >> > I started checking the dates, and it seems like the directories have >> > been backed up, and they all have the same date of backup, but the >> > actual documents >> > have a different date. It's like they were backed up once, but >> > never got backed up again. >> > >> > Does this have to do with the tape rotation? what am I missing? I >> > have the >> > tape that lists the documents, and it even lists them when I browse >> > the tape >> > with amrecover, but I can't extract them, I get the error above. >> > >> > Please help, >> > Steve >> > >> > >> > >> > __ >> > Yahoo! Mail - PC Magazine Editors' Choice 2005 >> > http://mail.yahoo.com > >__ >Yahoo! Mail - PC Magazine Editors' Choice 2005 >http://mail.yahoo.com -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.35% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Using amrecover - strange happenings
On Thu, Sep 29, 2005 at 06:08:23PM -0600, Vera wrote: > I do not remember exactly what was a reason for this error, but I saw it > before :-) > I'm going to sound just like Vera :( > - Original Message - > From: "Steve H" <[EMAIL PROTECTED]> > To: > Sent: Thursday, September 29, 2005 5:42 PM > Subject: Using amrecover - strange happenings > > > >Guys, > > > > I would appreciate some help with this one, as it's freaking me out. I > >have > >been getting backups for a while now of a particular host and file system. > >I > >have tested the recovery before and it worked great. > > This time, I put the necessary tape in, and run amrecover and it will > >only > >restore the directories. The files will not restore, and I keep getting > >the > >error: > > > >./laptopBackups/Documents and Settings/My Documents/ > >tar: Unexpected EOF in archive > >tar: Error is not recoverable: exiting now > >extract_list - child returned non-zero status: 2 > >Continue [?/Y/n]? > > > >so I started looking at the actual index for that and their are no files > >listed > >in the index, only directories. > > > >I started checking the dates, and it seems like the directories have been > >backed up, and they all have the same date of backup, but the actual > >documents > >have a different date. It's like they were backed up once, but never got > >backed up again. > > > >Does this have to do with the tape rotation? what am I missing? I have > >the > >tape that lists the documents, and it even lists them when I browse the > >tape > >with amrecover, but I can't extract them, I get the error above. > > > >Please help, > >Steve I recall having a similar problem a couple of years ago. It was one of two scenarios (I think). Either I was trying a different version of tar or I was trying the cygwin version of amanda. It might have been both, because I recall one thing I had to do to get the cygwin version working was download and compile 1.13.25 gnutar under cygwin. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Using amrecover - strange happenings
I am on a Red Hat 9 box. Pervious tar verion was 1.13, just upgraded to 1.15 and it didn't fix the issue. What do you mean by indexing DLE? Thanks, Steve --- Vera <[EMAIL PROTECTED]> wrote: > I do not remember exactly what was a reason for this error, but I saw it > before :-) > > 1. Are you indexing this DLE? > 2. What OS are you using? FC3 distributive had tar 1.14 with a bug - > check > the amrecover log file and if error happens at the "tar" point, then simple > upgrade your tar RPM or reinstall it from sources > > - Original Message - > From: "Steve H" <[EMAIL PROTECTED]> > To: > Sent: Thursday, September 29, 2005 5:42 PM > Subject: Using amrecover - strange happenings > > > > Guys, > > > > I would appreciate some help with this one, as it's freaking me out. I > > have > > been getting backups for a while now of a particular host and file system. > > I > > have tested the recovery before and it worked great. > > This time, I put the necessary tape in, and run amrecover and it will > > only > > restore the directories. The files will not restore, and I keep getting > > the > > error: > > > > ./laptopBackups/Documents and Settings/My Documents/ > > tar: Unexpected EOF in archive > > tar: Error is not recoverable: exiting now > > extract_list - child returned non-zero status: 2 > > Continue [?/Y/n]? > > > > so I started looking at the actual index for that and their are no files > > listed > > in the index, only directories. > > > > I started checking the dates, and it seems like the directories have been > > backed up, and they all have the same date of backup, but the actual > > documents > > have a different date. It's like they were backed up once, but never got > > backed up again. > > > > Does this have to do with the tape rotation? what am I missing? I have > > the > > tape that lists the documents, and it even lists them when I browse the > > tape > > with amrecover, but I can't extract them, I get the error above. > > > > Please help, > > Steve > > > > > > > > __ > > Yahoo! Mail - PC Magazine Editors' Choice 2005 > > http://mail.yahoo.com > > __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
Re: Using amrecover - strange happenings
I do not remember exactly what was a reason for this error, but I saw it before :-) 1. Are you indexing this DLE? 2. What OS are you using? FC3 distributive had tar 1.14 with a bug - > check the amrecover log file and if error happens at the "tar" point, then simple upgrade your tar RPM or reinstall it from sources - Original Message - From: "Steve H" <[EMAIL PROTECTED]> To: Sent: Thursday, September 29, 2005 5:42 PM Subject: Using amrecover - strange happenings Guys, I would appreciate some help with this one, as it's freaking me out. I have been getting backups for a while now of a particular host and file system. I have tested the recovery before and it worked great. This time, I put the necessary tape in, and run amrecover and it will only restore the directories. The files will not restore, and I keep getting the error: ./laptopBackups/Documents and Settings/My Documents/ tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now extract_list - child returned non-zero status: 2 Continue [?/Y/n]? so I started looking at the actual index for that and their are no files listed in the index, only directories. I started checking the dates, and it seems like the directories have been backed up, and they all have the same date of backup, but the actual documents have a different date. It's like they were backed up once, but never got backed up again. Does this have to do with the tape rotation? what am I missing? I have the tape that lists the documents, and it even lists them when I browse the tape with amrecover, but I can't extract them, I get the error above. Please help, Steve __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
Using amrecover - strange happenings
Guys, I would appreciate some help with this one, as it's freaking me out. I have been getting backups for a while now of a particular host and file system. I have tested the recovery before and it worked great. This time, I put the necessary tape in, and run amrecover and it will only restore the directories. The files will not restore, and I keep getting the error: ./laptopBackups/Documents and Settings/My Documents/ tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now extract_list - child returned non-zero status: 2 Continue [?/Y/n]? so I started looking at the actual index for that and their are no files listed in the index, only directories. I started checking the dates, and it seems like the directories have been backed up, and they all have the same date of backup, but the actual documents have a different date. It's like they were backed up once, but never got backed up again. Does this have to do with the tape rotation? what am I missing? I have the tape that lists the documents, and it even lists them when I browse the tape with amrecover, but I can't extract them, I get the error above. Please help, Steve __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
Re: Disable Tape Compression
On Thursday 29 September 2005 17:06, Christopher Davis wrote: >The drive doesn't have any dip switches - I even took the drive out of > the encosure and couldn't find anything. > >I copied the wrong mt command over - > >Where I'm at now is looking at stinit ant the /etc/stinig.def file to > create a /dev/nst0l device which disables compression - I'm in the > middle of another test right now and can't try it out just yet - but if > this works for me I'll send it to the list. We have a ton of these Sun > SDLT 220 drives floating around and want to use them. > > >I ran some tests using hardware compression and wasn't impressed with > the results so I'm trying it with it off. > Be aware that for many tape formats, the compression status is saved in a hidden header of the tape, so that once its been written in the compression on mode, that will be restored to on when the tape is loaded regardless of your wishes unless specifically disabled. I had a script at one time that turned these flags off, and it looked something like this: #!/bin/sh mt -f /dev/nst0 rewind dd if=/dev/st0 of=./scratch count=1 mt -f /dev/nst0 defcompression off (or 0 depending on your mt) mt -f /dev/nst0 compression off (or 0 depending on your mt) dd if=./scratch of =/dev/nst0 dd if=/dev/zero of=/dev/st0 count=(your drives buffer size plus 1) dd if=/dev/st0 (should show the tape label unchanged from ./scratch) Note use of /dev/st0 for its automatic rewind in places. simplifies the script.. > >-- Original Message -- >Received: Thu, 29 Sep 2005 02:29:47 PM MDT >From: Gene Heskett <[EMAIL PROTECTED]> >To: amanda-users@amanda.org >Subject: Re: Disable Tape Compression > >> On Thursday 29 September 2005 12:08, Christopher Davis wrote: >> >I'm using Amanda on Fedora Core 4 with a Quantum SDLT 220 tape drive >> > - I want to disable hardware compression but I'm not sure of the >> > best way to do that. >> > >> >I can issue a command mt -f /dev/nst0 defcompression 1 which seems to >> > work (amtapetype doesn't give me the warning about hardware >> > compresion) but as I understand it this change goes away as soon as >> > I change tapes. Meaning each time I insert a new tape I have to >> > re-enter this command? >> >> defcompression 1 turns it on, not off. And there is probably a >> dipswitch of jumper setting someplace on the drive to turn it on >> permanently IF thats what you want. Check your docs on the drive. >> >> However, running hardware compression hides the tapes true size from >> amanda, so you have to make an educated guess in setting the >> tapetypes 'size'. Amanda meas7ures the amount of data sent down the >> cable to the drive, and if amanda is doing the compression, which can >> handily beat the hardwares compression ratio in many cases, then >> amanda knows exactly how much the tape can hold. >> >> So, generally speaking, we don't recommend hardware compression. To >> give you an idea of how good the 'compress best' can be, I have a >> report of from of my recent runs that, with a 48 entry disklist, some >> compressed and some not, still put a bit over 17GB of real data in >> about 7.5GB of storage space used. It won't do that every night of >> course, but often enough to pay for the cpu power it takes. >> >> >How can I make the change permanent so that I don't have to worry >> > about manually changing a settting? >> > >> > >> >Any ideas or help would be much appreciated. >> > >> > >> >Chris >> >> -- >> Cheers, Gene >> "There are four boxes to be used in defense of liberty: >> soap, ballot, jury, and ammo. Please use in that order." >> -Ed Howdershelt (Author) >> 99.35% setiathome rank, not too shabby for a WV hillbilly >> Yahoo.com and AOL/TW attorneys please note, additions to the above >> message by Gene Heskett are: >> Copyright 2005 by Maurice Eugene Heskett, all rights reserved. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.35% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Disable Tape Compression
On Thu, Sep 29, 2005 at 03:06:44PM -0600, Christopher Davis wrote: > > Where I'm at now is looking at stinit ant the /etc/stinig.def file to create a > /dev/nst0l device which disables compression - I'm in the middle of another > test right now and can't try it out just yet - but if this works for me I'll > send it to the list. That would be a nice addition to the list archives. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Disable Tape Compression
The drive doesn't have any dip switches - I even took the drive out of the encosure and couldn't find anything. I copied the wrong mt command over - Where I'm at now is looking at stinit ant the /etc/stinig.def file to create a /dev/nst0l device which disables compression - I'm in the middle of another test right now and can't try it out just yet - but if this works for me I'll send it to the list. We have a ton of these Sun SDLT 220 drives floating around and want to use them. I ran some tests using hardware compression and wasn't impressed with the results so I'm trying it with it off. -- Original Message -- Received: Thu, 29 Sep 2005 02:29:47 PM MDT From: Gene Heskett <[EMAIL PROTECTED]> To: amanda-users@amanda.org Subject: Re: Disable Tape Compression > On Thursday 29 September 2005 12:08, Christopher Davis wrote: > >I'm using Amanda on Fedora Core 4 with a Quantum SDLT 220 tape drive - I > > want to disable hardware compression but I'm not sure of the best way > > to do that. > > > >I can issue a command mt -f /dev/nst0 defcompression 1 which seems to > > work (amtapetype doesn't give me the warning about hardware compresion) > > but as I understand it this change goes away as soon as I change tapes. > > Meaning each time I insert a new tape I have to re-enter this command? > > > defcompression 1 turns it on, not off. And there is probably a > dipswitch of jumper setting someplace on the drive to turn it on > permanently IF thats what you want. Check your docs on the drive. > > However, running hardware compression hides the tapes true size from > amanda, so you have to make an educated guess in setting the > tapetypes 'size'. Amanda meas7ures the amount of data sent down the > cable to the drive, and if amanda is doing the compression, which can > handily beat the hardwares compression ratio in many cases, then > amanda knows exactly how much the tape can hold. > > So, generally speaking, we don't recommend hardware compression. To > give you an idea of how good the 'compress best' can be, I have a > report of from of my recent runs that, with a 48 entry disklist, some > compressed and some not, still put a bit over 17GB of real data in > about 7.5GB of storage space used. It won't do that every night of > course, but often enough to pay for the cpu power it takes. > > > >How can I make the change permanent so that I don't have to worry about > >manually changing a settting? > > > > > >Any ideas or help would be much appreciated. > > > > > >Chris > > -- > Cheers, Gene > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author) > 99.35% setiathome rank, not too shabby for a WV hillbilly > Yahoo.com and AOL/TW attorneys please note, additions to the above > message by Gene Heskett are: > Copyright 2005 by Maurice Eugene Heskett, all rights reserved. > >
Re: Disable Tape Compression
On Thursday 29 September 2005 12:08, Christopher Davis wrote: >I'm using Amanda on Fedora Core 4 with a Quantum SDLT 220 tape drive - I > want to disable hardware compression but I'm not sure of the best way > to do that. > >I can issue a command mt -f /dev/nst0 defcompression 1 which seems to > work (amtapetype doesn't give me the warning about hardware compresion) > but as I understand it this change goes away as soon as I change tapes. > Meaning each time I insert a new tape I have to re-enter this command? > defcompression 1 turns it on, not off. And there is probably a dipswitch of jumper setting someplace on the drive to turn it on permanently IF thats what you want. Check your docs on the drive. However, running hardware compression hides the tapes true size from amanda, so you have to make an educated guess in setting the tapetypes 'size'. Amanda meas7ures the amount of data sent down the cable to the drive, and if amanda is doing the compression, which can handily beat the hardwares compression ratio in many cases, then amanda knows exactly how much the tape can hold. So, generally speaking, we don't recommend hardware compression. To give you an idea of how good the 'compress best' can be, I have a report of from of my recent runs that, with a 48 entry disklist, some compressed and some not, still put a bit over 17GB of real data in about 7.5GB of storage space used. It won't do that every night of course, but often enough to pay for the cpu power it takes. > >How can I make the change permanent so that I don't have to worry about >manually changing a settting? > > >Any ideas or help would be much appreciated. > > >Chris -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.35% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: FAILURE AND STRANGE DUMP SUMMARY:
On Thursday 29 September 2005 07:15, 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. That was the holding disk Jon. It should either be excluded, or specifically not named in a disklist entry. He's probably backing up '/', rather than naming the subdirs in his disklist. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.35% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Amanda/firewall --with-portrange
Brenckle, Nicholas wrote: > > Finally worked with different ranges for udp and tcp (udp 850-854 and tcp > 1 to 10100). Now it's happy. My standard configure-script uses --with-tcpportrange=5,50040 --with-udpportrange=890,899 which points to the same solution you just found. Greets, Stefan.
RE: Amanda/firewall --with-portrange
I searched the archives and found your posts. I made it work, and I'll give a quick rundown of what did not work until what did. Default config, no go. Tried --with-(tcp/udp)portrange=1,10100 also no go. The Amanda software complained about insecure ports. Not much to go on there. Tried --with-(tcp/udp)portrange=850,854 no go. No more complaints about secure port, but still tried backup connections on high numbered ports, so that didn't work. Couldn't figure out why it insisted on using high numbers. Sooo... Finally worked with different ranges for udp and tcp (udp 850-854 and tcp 1 to 10100). Now it's happy. Thanks for the advice. -Nick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Leangen Sent: Thursday, September 29, 2005 1:25 PM To: amanda-users@amanda.org Subject: RE: Amanda/firewall --with-portrange I recently had similar issues. Look for a post in the archives about 2 weeks ago that discussed the same topic. A few people gave very helpful replies already that should apply in your case, too. Brief summary: - --with-tcp-portrange is not needed - you must configure the same values on both client and server Those were the main points. Otherwise, depending on the number of clients you have, you may need to allocate more ports than you did. Good luck! Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Brenckle, Nicholas Sent: 30 September 2005 02:07 To: 'amanda-users@amanda.org' Subject: Amanda/firewall --with-portrange I am having a weird problem with the portrange specification. My situation is reversed from most configurations in the FAQ as my host is behind the fw, while the backup server sits in front of it. There is no NAT going on. Amanda was compile from the source RPM, I added the following to the SPEC file: --with-portrange=850,854 \ --with-tcpportrange=850,854 \ --with-udpportrange=850,854 I put the server and client RPMS on my backup/tape server, and the client RPM on the client. Both are running Fedora Core 1 if that matters. Amcheck will work, and I can see the traffic (using tcpdump) running mostly on port 850, sometimes on port 851. The problem is when I run amdump, I get a few things going back/forth on the 850-854 range, and then the server tries to connect to the client some high number port, in this test, 48111. That isn't going to work. J Why does it do this? Only ports 850-854 are allowed, that's why I specified them in the compile. Suggestions? Tcpdump output from the server shown below. If I open all ports up at the firewall the software works, so I don't think it's a network/server problem, it has to be related to the allowed ports of the firewall. Thanks, Nick 12:39:02.178374 backup01.mynetwork.net.851 > client-station.mynetwork.net.amanda: udp 117 (DF) 12:39:02.190269 client-station.mynetwork.net.amanda > backup01.mynetwork.net.851: udp 50 (DF) 12:39:02.211152 client-station.mynetwork.net.amanda > backup01.mynetwork.net.851: udp 83 (DF) 12:39:02.211381 backup01.mynetwork.net.851 > client-station.mynetwork.net.amanda: udp 50 (DF) 12:39:02.221191 backup01.mynetwork.net.851 > client-station.mynetwork.net.amanda: udp 309 (DF) 12:39:02.235417 client-station.mynetwork.net.amanda > backup01.mynetwork.net.851: udp 50 (DF) 12:39:04.508871 client-station.mynetwork.net.amanda > backup01.mynetwork.net.851: udp 118 (DF) 12:39:04.509057 backup01.mynetwork.net.851 > client-station.mynetwork.net.amanda: udp 50 (DF) 12:39:04.527624 backup01.mynetwork.net.854 > client-station.mynetwork.net.amanda: udp 223 (DF) 12:39:04.540252 client-station.mynetwork.net.amanda > backup01.mynetwork.net.854: udp 50 (DF) 12:39:04.571890 client-station.mynetwork.net.amanda > backup01.mynetwork.net.854: udp 125 (DF) 12:39:04.571983 backup01.mynetwork.net.854 > client-station.mynetwork.net.amanda: udp 50 (DF) 12:39:04.580725 backup01.mynetwork.net.40590 > client-station.mynetwork.net.48111: S 3871447985:3871447985(0) win 5840 (DF) 12:39:07.574415 backup01.mynetwork.net.40590 > client-station.mynetwork.net.48111: S 3871447985:3871447985(0) win 5840 (DF) 12:39:13.574422 backup01.mynetwork.net.40590 > client-station.mynetwork.net.48111: S 3871447985:3871447985(0) win 5840 (DF) 12:39:25.574414 backup01.mynetwork.net.40590 > client-station.mynetwork.net.48111: S 3871447985:3871447985(0) win 5840 (DF) 12:39:49.574418 backup01.mynetwork.net.40590 > client-station.mynetwork.net.48111: S 3871447985:3871447985(0) win 5840 (DF)
RE: Disable Tape Compression
There are no DIP switches that I can find - its a Sun Enclure (SDLT 220 unit) around a Quantum TR-S13AA. Chris -- Original Message -- Received: Thu, 29 Sep 2005 10:33:50 AM MDT From: "Scott R. Burns" <[EMAIL PROTECTED]> To: "Christopher Davis" <[EMAIL PROTECTED]>, Subject: RE: Disable Tape Compression > Are there any dip switches on the drive ? My HP DAT24x6 has a dip switch > bank on the bottom which turns off compression in the HW. I don't see any > indication of that in your drives manual. > > 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 Christopher Davis > Sent: Thursday, September 29, 2005 12:09 PM > To: amanda-users@amanda.org > Subject: Disable Tape Compression > > > I'm using Amanda on Fedora Core 4 with a Quantum SDLT 220 tape drive - I > want > to disable hardware compression but I'm not sure of the best way to do that. > > I can issue a command mt -f /dev/nst0 defcompression 1 which seems to work > (amtapetype doesn't give me the warning about hardware compresion) but as I > understand it this change goes away as soon as I change tapes. Meaning each > time I insert a new tape I have to re-enter this command? > > > How can I make the change permanent so that I don't have to worry about > manually changing a settting? > > > Any ideas or help would be much appreciated. > > > Chris > > > > >
RE: Amanda/firewall --with-portrange
I recently had similar issues. Look for a post in the archives about 2 weeks ago that discussed the same topic. A few people gave very helpful replies already that should apply in your case, too. Brief summary: - --with-tcp-portrange is not needed - you must configure the same values on both client and server Those were the main points. Otherwise, depending on the number of clients you have, you may need to allocate more ports than you did. Good luck! Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Brenckle, Nicholas Sent: 30 September 2005 02:07 To: 'amanda-users@amanda.org' Subject: Amanda/firewall --with-portrange I am having a weird problem with the portrange specification. My situation is reversed from most configurations in the FAQ as my host is behind the fw, while the backup server sits in front of it. There is no NAT going on. Amanda was compile from the source RPM, I added the following to the SPEC file: --with-portrange=850,854 \ --with-tcpportrange=850,854 \ --with-udpportrange=850,854 I put the server and client RPMS on my backup/tape server, and the client RPM on the client. Both are running Fedora Core 1 if that matters. Amcheck will work, and I can see the traffic (using tcpdump) running mostly on port 850, sometimes on port 851. The problem is when I run amdump, I get a few things going back/forth on the 850-854 range, and then the server tries to connect to the client some high number port, in this test, 48111. That isn't going to work. J Why does it do this? Only ports 850-854 are allowed, that's why I specified them in the compile. Suggestions? Tcpdump output from the server shown below. If I open all ports up at the firewall the software works, so I don't think it's a network/server problem, it has to be related to the allowed ports of the firewall. Thanks, Nick 12:39:02.178374 backup01.mynetwork.net.851 > client-station.mynetwork.net.amanda: udp 117 (DF) 12:39:02.190269 client-station.mynetwork.net.amanda > backup01.mynetwork.net.851: udp 50 (DF) 12:39:02.211152 client-station.mynetwork.net.amanda > backup01.mynetwork.net.851: udp 83 (DF) 12:39:02.211381 backup01.mynetwork.net.851 > client-station.mynetwork.net.amanda: udp 50 (DF) 12:39:02.221191 backup01.mynetwork.net.851 > client-station.mynetwork.net.amanda: udp 309 (DF) 12:39:02.235417 client-station.mynetwork.net.amanda > backup01.mynetwork.net.851: udp 50 (DF) 12:39:04.508871 client-station.mynetwork.net.amanda > backup01.mynetwork.net.851: udp 118 (DF) 12:39:04.509057 backup01.mynetwork.net.851 > client-station.mynetwork.net.amanda: udp 50 (DF) 12:39:04.527624 backup01.mynetwork.net.854 > client-station.mynetwork.net.amanda: udp 223 (DF) 12:39:04.540252 client-station.mynetwork.net.amanda > backup01.mynetwork.net.854: udp 50 (DF) 12:39:04.571890 client-station.mynetwork.net.amanda > backup01.mynetwork.net.854: udp 125 (DF) 12:39:04.571983 backup01.mynetwork.net.854 > client-station.mynetwork.net.amanda: udp 50 (DF) 12:39:04.580725 backup01.mynetwork.net.40590 > client-station.mynetwork.net.48111: S 3871447985:3871447985(0) win 5840 (DF) 12:39:07.574415 backup01.mynetwork.net.40590 > client-station.mynetwork.net.48111: S 3871447985:3871447985(0) win 5840 (DF) 12:39:13.574422 backup01.mynetwork.net.40590 > client-station.mynetwork.net.48111: S 3871447985:3871447985(0) win 5840 (DF) 12:39:25.574414 backup01.mynetwork.net.40590 > client-station.mynetwork.net.48111: S 3871447985:3871447985(0) win 5840 (DF) 12:39:49.574418 backup01.mynetwork.net.40590 > client-station.mynetwork.net.48111: S 3871447985:3871447985(0) win 5840 (DF)
Amanda/firewall --with-portrange
I am having a weird problem with the portrange specification. My situation is reversed from most configurations in the FAQ as my host is behind the fw, while the backup server sits in front of it. There is no NAT going on. Amanda was compile from the source RPM, I added the following to the SPEC file: --with-portrange=850,854 \ --with-tcpportrange=850,854 \ --with-udpportrange=850,854 I put the server and client RPMS on my backup/tape server, and the client RPM on the client. Both are running Fedora Core 1 if that matters. Amcheck will work, and I can see the traffic (using tcpdump) running mostly on port 850, sometimes on port 851. The problem is when I run amdump, I get a few things going back/forth on the 850-854 range, and then the server tries to connect to the client some high number port, in this test, 48111. That isn't going to work. J Why does it do this? Only ports 850-854 are allowed, that's why I specified them in the compile. Suggestions? Tcpdump output from the server shown below. If I open all ports up at the firewall the software works, so I don't think it's a network/server problem, it has to be related to the allowed ports of the firewall. Thanks, Nick 12:39:02.178374 backup01.mynetwork.net.851 > client-station.mynetwork.net.amanda: udp 117 (DF) 12:39:02.190269 client-station.mynetwork.net.amanda > backup01.mynetwork.net.851: udp 50 (DF) 12:39:02.211152 client-station.mynetwork.net.amanda > backup01.mynetwork.net.851: udp 83 (DF) 12:39:02.211381 backup01.mynetwork.net.851 > client-station.mynetwork.net.amanda: udp 50 (DF) 12:39:02.221191 backup01.mynetwork.net.851 > client-station.mynetwork.net.amanda: udp 309 (DF) 12:39:02.235417 client-station.mynetwork.net.amanda > backup01.mynetwork.net.851: udp 50 (DF) 12:39:04.508871 client-station.mynetwork.net.amanda > backup01.mynetwork.net.851: udp 118 (DF) 12:39:04.509057 backup01.mynetwork.net.851 > client-station.mynetwork.net.amanda: udp 50 (DF) 12:39:04.527624 backup01.mynetwork.net.854 > client-station.mynetwork.net.amanda: udp 223 (DF) 12:39:04.540252 client-station.mynetwork.net.amanda > backup01.mynetwork.net.854: udp 50 (DF) 12:39:04.571890 client-station.mynetwork.net.amanda > backup01.mynetwork.net.854: udp 125 (DF) 12:39:04.571983 backup01.mynetwork.net.854 > client-station.mynetwork.net.amanda: udp 50 (DF) 12:39:04.580725 backup01.mynetwork.net.40590 > client-station.mynetwork.net.48111: S 3871447985:3871447985(0) win 5840 (DF) 12:39:07.574415 backup01.mynetwork.net.40590 > client-station.mynetwork.net.48111: S 3871447985:3871447985(0) win 5840 (DF) 12:39:13.574422 backup01.mynetwork.net.40590 > client-station.mynetwork.net.48111: S 3871447985:3871447985(0) win 5840 (DF) 12:39:25.574414 backup01.mynetwork.net.40590 > client-station.mynetwork.net.48111: S 3871447985:3871447985(0) win 5840 (DF) 12:39:49.574418 backup01.mynetwork.net.40590 > client-station.mynetwork.net.48111: S 3871447985:3871447985(0) win 5840 (DF)
RE: Disable Tape Compression
Are there any dip switches on the drive ? My HP DAT24x6 has a dip switch bank on the bottom which turns off compression in the HW. I don't see any indication of that in your drives manual. 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 Christopher Davis Sent: Thursday, September 29, 2005 12:09 PM To: amanda-users@amanda.org Subject: Disable Tape Compression I'm using Amanda on Fedora Core 4 with a Quantum SDLT 220 tape drive - I want to disable hardware compression but I'm not sure of the best way to do that. I can issue a command mt -f /dev/nst0 defcompression 1 which seems to work (amtapetype doesn't give me the warning about hardware compresion) but as I understand it this change goes away as soon as I change tapes. Meaning each time I insert a new tape I have to re-enter this command? How can I make the change permanent so that I don't have to worry about manually changing a settting? Any ideas or help would be much appreciated. Chris
RE: My Monthly archive config - issue
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
Disable Tape Compression
I'm using Amanda on Fedora Core 4 with a Quantum SDLT 220 tape drive - I want to disable hardware compression but I'm not sure of the best way to do that. I can issue a command mt -f /dev/nst0 defcompression 1 which seems to work (amtapetype doesn't give me the warning about hardware compresion) but as I understand it this change goes away as soon as I change tapes. Meaning each time I insert a new tape I have to re-enter this command? How can I make the change permanent so that I don't have to worry about manually changing a settting? Any ideas or help would be much appreciated. Chris
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: Howto add a new host and disk to my Amanda backup server WARNING Host down! (emailserver).
Chuck Amadi Systems Administrator wrote: > 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!. I can't believe that ;) Good luck, proper restores, Stefan.
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
Re: Howto add a new host and disk to my Amanda backup server WARNING Host down! (emailserver).
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
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).
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.
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: 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
Re: FAILURE AND STRANGE DUMP SUMMARY:
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. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Symbolic links
Jerome Pioux wrote: Load tape monthly4 now Continue [?/Y/n/s/t]? EOF, check amidxtaped..debug file on reddog. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 So I suppose that tar 1.13 can't read a backup that was done by 1.15 - am I correct? That error message above sounds more like an amanda permissions problem. I don't think there has been any data sent to tar, so don't jump to conclusions about tar compatibility. In fact, apart slight differences in border cases, tar 1.13 should be able to read tar 1.15 archives just fine. Alex -- Alexander Jolk * BUF Compagnie * [EMAIL PROTECTED] Tel +33-1 42 68 18 28 * Fax +33-1 42 68 18 29
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
