Re: tape hardware choices
On Thursday 05 June 2003 07:37, Tom Brown wrote: Our DDS4 autoloader has just died and we are looking at alternatives. Has anyone had any joy with SDLT as we need added capacity now and we were planning an upgrade anyway so this is just 'assisting' in us getting a move on with this! following this up. this is the error i get when i try and change tapes - $ mtx -f /dev/sg4 status Storage Changer /dev/sg4:1 Drives, 6 Slots ( 0 Import/Export ) Data Transfer Element 0:Empty Storage Element 1:Full Storage Element 2:Full Storage Element 3:Full Storage Element 4:Full Storage Element 5:Full Storage Element 6:Full I'm noting that it DOESN'T say that 0 is loaded! and change tapes... $ mtx -f /dev/sg4 load 1 mtx: Request Sense: Long Report=yes mtx: Request Sense: Valid Residual=no mtx: Request Sense: Error Code=70 (Current) mtx: Request Sense: Sense Key=Hardware Error mtx: Request Sense: FileMark=no mtx: Request Sense: EOM=no mtx: Request Sense: ILI=no mtx: Request Sense: Additional Sense Code = 44 mtx: Request Sense: Additional Sense Qualifier = 00 mtx: Request Sense: BPV=no mtx: Request Sense: Error in CDB=no mtx: Request Sense: SKSV=no MOVE MEDIUM from Element Address 2 to 1 Failed Which outputs nothing here, it just loads the tape. anyone seen anything like this before? It was working fine for over 2 years before this? If you are mechanically inclined, remove the changer from its normal location and re-attach the cables so that you can see what its doing. It might be something so simple as a rubber roller thats become polished up and is now slipping someplace in the robotics. Or even a very bad case of dust bunnies. Rubber belts will lose their tension and grip also, leaving the motor spinning its wheels and the device times out reporting the error chain above. Home vcr's are infamous for that, to the point of the belts being designed out of them in recent times. thanks - although i suspect broken hardware i thought i just pass this to the group to see if anyone else knew what it might be Tom -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: tape hardware choices
If you are mechanically inclined, remove the changer from its normal location and re-attach the cables so that you can see what its doing. It might be something so simple as a rubber roller thats become polished up and is now slipping someplace in the robotics. Or even a very bad case of dust bunnies. Rubber belts will lose their tension and grip also, leaving the motor spinning its wheels and the device times out reporting the error chain above. Home vcr's are infamous for that, to the point of the belts being designed out of them in recent times. i might plan a trip to the IDC then and take the thing apart - its in its own external enclosure so its prety easy to get at. thanks
Re: tape hardware choices
On Thu, Jun 05, 2003 at 12:37:14PM +0100, Tom Brown wrote: following this up. this is the error i get when i try and change tapes - $ mtx -f /dev/sg4 status Storage Changer /dev/sg4:1 Drives, 6 Slots ( 0 Import/Export ) Data Transfer Element 0:Empty Storage Element 1:Full Storage Element 2:Full Storage Element 3:Full so the read/write (data transfer) element is numbered zero and change tapes... $ mtx -f /dev/sg4 load 1 which says to my silly mind, more the tape in element 1 to element 0. yet ... ... mtx: Request Sense: Error in CDB=no mtx: Request Sense: SKSV=no MOVE MEDIUM from Element Address 2 to 1 Failed Why is it complaining about a 2 - 1 move when it should be doing a 1 - 0 move? If you do a load 0 does it do the desired 1 - 0 move? Doesn't make sense, but if this was in a shell script I was debugging I would be looking at an off by one type error. Maybe one part of the system uses 0 base and another uses 1 base. But I can't see it happening when using mtx directly. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: SUN StorEdge L7 jukebox
On Thu, Jun 05, 2003 at 07:51:12AM -0400, Bean, N. Curt wrote: Does any one have a clue where I can find software to drive this beast on Solaris 2.6? Sparc or x86? Probably doesn't matter though. Depending on how you mean 'drive' it, for read/write /bin/dd, /bin/tar, ... for tape drive manipulation /bin/mt for changer manipulation freeware mtx, current source available at sourceforge.net precompiled, package format, older version at SunFreeware.com -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Missing files from Samba backup
Hi Amanda Users! This morning I noticed that a DLE which has been forced (Level 0) on a NT 4.0 Service Pack 6 computer via Samba did not completely backup all files. It seem that for any file/directory listed in Amanda's report (See below) which start with a ? SUCCESS - 0 statement were not archived or added to the index files. The reason I found that there was a serious problem is that a full should contain about 88 gigs of data while only about 20 gigs were taped. This caused me to look back through the full backup logs for other computers and found similar problems. At first I thought it was due to the NT box drive being a RAID configuration be alas the problem also occurs on Win 85 and Win 98 computers. A search of the archive did not point to any solutions. Anyone have an idea of what is going wrong? Amanda version 2.4.2p2 tar (GNU tar) 1.13.25 Thanks, Vytas These dumps were to tape Daily14. The next tape Amanda expects to use is: Daily15. FAILURE AND STRANGE DUMP SUMMARY vxa2 //nt-01/nt01-d lev 0 STRANGE /-- vxa2 //nt-01/nt01-d lev 0 STRANGE sendbackup: start [vxa2://nt-01/nt01-d level 0] sendbackup: info BACKUP=/usr/bin/smbclient sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... - sendbackup: info end ? NT_STATUS_SHARING_VIOLATION opening remote file \pagefile.sys (\) ? SUCCESS - 0 opening remote file \Project\AgCan\0_Ontario\ALCDB_Vytas.zip (\Project\AgCan\0_Ontario\) ? SUCCESS - 0 opening remote file \Project\AgCan\0_Ontario\Arc_Info_Generalize.bmp (\Project\AgCan\0_Ontario\) ? SUCCESS - 0 listing \Project\AgCan\0_Ontario\bend100\* ? SUCCESS - 0 listing \Project\AgCan\0_Ontario\bend15\* ? SUCCESS - 0 listing \Project\AgCan\0_Ontario\bend30\* ? SUCCESS - 0 listing \Project\AgCan\0_Ontario\bend300\* ? SUCCESS - 0 listing \Project\AgCan\0_Ontario\bend50\* ? SUCCESS - 0 listing \Project\AgCan\0_Ontario\test\* ? SUCCESS - 0 opening remote file \Project\AgCan\0_Ontario\Testdata.mxd ... ... ... ? SUCCESS - 0 listing \Proposal\* ? SUCCESS - 0 listing \restore\* ? SUCCESS - 0 opening remote file \ROND.DBF (\) ? SUCCESS - 0 listing \scan2cad\* ? SUCCESS - 0 listing \Scan2Vec\* ? SUCCESS - 0 listing \Seagate Software\* ? SUCCESS - 0 opening remote file \SQL.LOG (\) ? SUCCESS - 0 listing \System\* ? SUCCESS - 0 listing \TCWIN\* ? SUCCESS - 0 listing \wag\* ? SUCCESS - 0 listing \wagner_unix\* ? SUCCESS - 0 listing \WINNT\* ? SUCCESS - 0 listing \WorkSpace\* ? SUCCESS - 0 listing \yukon scans\* | tar: dumped 29441 files and directories | Total bytes written: 21413944832 sendbackup: size 20912056 sendbackup: end \ DUMP SUMMARY: DUMPER STATS TAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- -- vxa2 -nt-01/nt01-d 0 20912056 14609312 69.9 126:22 1926.7 39:11 6214.0 Window NT drive stats. Total Files Listed: 184354 File(s) 88,102,672,147 bytes 29,309,644,800 bytes free Vytas Janusauskas Dendron Resource Surveys Inc. 880 Lady Ellen Place, Suite 206 Ottawa, Ontario, Canada K1Z 5L9 Voice: (613) 725-2971 Fax: (613) 725-1716 mailto:[EMAIL PROTECTED]
Re: Amrecovering files/directories with blanks.
Hi Again, Some of my windows users are naming directories and files with space characters as separators between words. While doing a ls on amrecover displays these space containing files/directories how do you go about changing into these directories setdisk strange data directory does not work neither does setdisk strange\ data\ directory There must be a way to do it! I would prefer not to have to restore the full DLE if I can avoid it. Thanks again, Vytas Vytas Janusauskas Dendron Resource Surveys Inc. 880 Lady Ellen Place, Suite 206 Ottawa, Ontario, Canada K1Z 5L9 Voice: (613) 725-2971 Fax: (613) 725-1716 mailto:[EMAIL PROTECTED]
Re: tape hardware choices
If you do a load 0 does it do the desired 1 - 0 move? $ mtx -f /dev/sg4 status Storage Changer /dev/sg4:1 Drives, 6 Slots ( 0 Import/Export ) Data Transfer Element 0:Empty Storage Element 1:Full Storage Element 2:Full Storage Element 3:Full Storage Element 4:Full Storage Element 5:Full Storage Element 6:Full and... $ mtx -f /dev/sg4 load 0 No source specified so nope - Tom
Re: Amrecovering files/directories with blanks.
Hello Vytas, Hm, you may want to try: setdisk strange data directory does not work I hope this helps, Tim On Thu, 5 Jun 2003, Vytas Janusauskas wrote: Hi Again, Some of my windows users are naming directories and files with space characters as separators between words. While doing a ls on amrecover displays these space containing files/directories how do you go about changing into these directories setdisk strange data directory does not work neither does setdisk strange\ data\ directory There must be a way to do it! I would prefer not to have to restore the full DLE if I can avoid it. Thanks again, Vytas Vytas Janusauskas Dendron Resource Surveys Inc. 880 Lady Ellen Place, Suite 206 Ottawa, Ontario, Canada K1Z 5L9 Voice: (613) 725-2971 Fax: (613) 725-1716 mailto:[EMAIL PROTECTED]
Re: Amrecovering files/directories with blanks.
On Thu, Jun 05, 2003 at 01:21:47PM -0400, Vytas Janusauskas wrote: Hi Again, Some of my windows users are naming directories and files with space characters as separators between words. While doing a ls on amrecover displays these space containing files/directories how do you go about changing into these directories setdisk strange data directory does not work neither does setdisk strange\ data\ directory There must be a way to do it! I would prefer not to have to restore the full DLE if I can avoid it. Don't have a chance to try it, but from past threads I think quotes work. like: cd Program Files -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Amrecovering files/directories with blanks.
Don't have a chance to try it, but from past threads I think quotes work. we have this issue too on our main company fileserver. quotes work Tom
Re: SUN StorEdge L7 jukebox
if you're looking for a driver to control the device in amanda-2.x/contrib/sst is a scsi drive from sun that distributes with the writing device drivers documention. if you can i'd recommend upgrading to solaris 8 or 9 and using the sgen driver that included with the OS, it works much better the sst driver. Bean, N. Curt wrote: Does any one have a clue where I can find software to drive this beast on Solaris 2.6? Thanks in advance N. Curt Bean Sr. System/Network Administrator Raytheon 7700 Arlington Blvd. Fallschurch Va. 22042 Phone: 703.560.5000 Ext 4203 Fax: 703.849.1591 Email: [EMAIL PROTECTED] -- Darin Perusich Unix Systems Administrator Cognigen Corp. [EMAIL PROTECTED]
Re: Disk tape backup (was: RE: rait output driver)
On Thu, Jun 05, 2003 at 02:05:29AM -, [EMAIL PROTECTED] wrote: I wanted to have backups going to an online disk, for onsite fast recovery, and to tape for off-site and longer term historic storage. I think this can be accomplished by configuring amanda with no holding disk and using a disk file as one of the rait devices, though I have not yet tried it. Doing that would prevent Amanda from doing dumps in parallel; it'd be throttled back to effectively single-threaded operation. I've ended up using the idea that someone here (Jon?) has described: - a daily configuration that writes to file: pseudo-tapes -- runs Monday-Thursday nights - a weekly configuration that does all level-0's and writes to real tapes -- runs Friday night - a perm configuration that's just like weekly but uses a different tape series -- it runs *instead* of weekly on the first Friday of every other month The difference between weekly and perm is that the latter's tapes will never be overwritten -- they'll be kept as a permanent archive -- while weekly's tapes will cycle in the usual way. Some day, I'm sure that some day all those old perm-tape indexes will grow big enough that I'll have to start pruning them, but I'll cross that bridge when I come to it. Maybe burn them onto CD or something. I have to admit this is all new -- perm is scheduled for its first run tomorrow night, and neither daily nor weekly has been through a full tape-cycle yet. So I'm sure things will get tweaked before they settle down into a routine. -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / When I came back around from the dark side, there in front of me would be the landing area where the crew was, and the Earth, all in the view of my window. I couldn't help but think that there in front of me was all of humanity, except me. - Michael Collins, Apollo 11 Command Module Pilot
Re: tape hardware choices
On Thu, 5 Jun 2003, Olivier Nicole wrote: I have been using SLR (Tandberg) for a couple of years without problem. Working in difficult conditions (high humidity, lot of dust) I find linear reccording (SLR, DLT) better than helicoidal reccording: less density on the tape (more fault tolerant), much much simpler mechanic (less moving parts that could tear off). I used to swear by DLT, these days I'm swearing at it. I've had two DLT 8000s that the takeup motor died within a year. Sure, they were fixed under warranty, but that just means a little longer til the drive is dead. The whole spliting of the DLT roadmap leaves a bad taste in my mouth as well. With larger and larger capacities on the tapes, that comfort level of low density on the actual media is gone. $.02 Bill Carlson -- Systems Administrator[EMAIL PROTECTED] | Anything is possible, Virtual Hospital http://www.vh.org/ | given time and money. University of Iowa Hospitals and Clinics | Opinions are mine, not my employer's. |
exclude list optional broken?
Hallo!
The amanda man page states that the exclude list can be optional. So I defined
following dumtype:
define dumptype my-global {
comp-user-tar
exclude list optional .amanda.exclude.gtar
include list optional .amanda.include.gtar
}
But unfortunately, with this definition all the backups just fail on _all_
filesystems. Even those which actually contain such an exclude file failed.
Is this a known bug or am I just doing something very stupid? Any hints?
BTW: amanda-2.4.4, gnutar-1.13.25
--
-- Josef Wolf -- [EMAIL PROTECTED] --
Re: exclude list optional broken?
Josef Wolf wrote:
define dumptype my-global {
comp-user-tar
exclude list optional .amanda.exclude.gtar
include list optional .amanda.include.gtar
}
But unfortunately, with this definition all the backups just fail on _all_
filesystems. Even those which actually contain such an exclude file failed.
Is this a known bug or am I just doing something very stupid? Any hints?
Before doing complicated, does it work with only an exclude an no
include list?
I suppose you did put them on the client on the toplevel directory of
the DLE? What are the contents of these files?
What's in the debug files on the client in /tmp/amanda/*exclude?
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...*
* ... Are you sure? ... YES ... Phew ... I'm out *
***
Re: tape hardware choices
I used to swear by DLT, these days I'm swearing at it. I've had two DLT 8000s that the takeup motor died within a year. Sure, they were fixed That's why I choosed SLR, even less motors in those, the one that move the tape and the one that position the head (I beleive). Period. :) If I knew a tape drive with no mechanic at all, I'd jump for it right now. Olivier
Re: tape hardware choices
On Fri, Jun 06, 2003 at 07:45:38AM +0700, Olivier Nicole wrote: I used to swear by DLT, these days I'm swearing at it. I've had two DLT 8000s that the takeup motor died within a year. Sure, they were fixed That's why I choosed SLR, even less motors in those, the one that move the tape and the one that position the head (I beleive). Period. :) If I knew a tape drive with no mechanic at all, I'd jump for it right now. Digital camera memory cards? :) -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: recommendations for new changer for home user
On Fri, Jun 06, 2003 at 01:18:48AM -0400, Gene Heskett wrote: The Sony AIT-1 looks ok, but many of those are probably worn out by now. So does the AIT-2, but again, the $ slow me down. So what does the retired home user with a 600 dollar budget (500 for the deck, 100 for media) look for today when he goes touring on ebay? I had the same problem. I considered these alternatives and choose DVD. - older DLT tapes, e.g. 10GB are relatively cheap. I personally have so bad experiences with DDS, that i would also prefer AIT-1 to some kind of DDS. - DVD+RW or DVD-RW drives. They are not so nice to use with Amanda because they are not tapes. I use a dvd+rw with Amandas file driver and then running a script to burn a dvd. Ciao Dietmar -- Alles Gute / best wishes Dietmar Goldbeck E-Mail: [EMAIL PROTECTED] Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western Civilization? Gandhi: I think it would be a good idea.
Re: Missing files from Samba backup
First let me say that you have an old version of Amanda. But I don't know where your problem come from. I only thing I can say is that, in my case (amanda 2.4.3), I also have problems with Cygwin and index generation. Amanda does not tell me that there was a problem during the backup; but when I try to amrecover my cygwin files, the program sometimes tells me no index records for host and when I go and see the file, it tells me the gzip file for record is incorrect: --- cut here --- [EMAIL PROTECTED]:~$ amgetconf test indexdir /BACKUP/amanda/var/test/index [EMAIL PROTECTED]:~$ gzip -t /BACKUP/amanda/var/test/index/mdb0/_cygdrive_g_BACKUP__MDB1_Night__dump/20030606_0.gz gzip: /BACKUP/amanda/var/test/index/mdb0/_cygdrive_g_BACKUP__MDB1_Night__dump/20030606_0.gz: unexpected end of file --- cut here --- So, in my case, I am not able to amrecover the files, but they surely went to tape and I can amrestore them without problem... Try see if you don't have a similar problem to mine. On Thu, 05 Jun 2003 13:11:16 -0400 Vytas Janusauskas [EMAIL PROTECTED] wrote: Hi Amanda Users! This morning I noticed that a DLE which has been forced (Level 0) on a NT 4.0 Service Pack 6 computer via Samba did not completely backup all files. It seem that for any file/directory listed in Amanda's report (See below) which start with a ? SUCCESS - 0 statement were not archived or added to the index files. The reason I found that there was a serious problem is that a full should contain about 88 gigs of data while only about 20 gigs were taped. This caused me to look back through the full backup logs for other computers and found similar problems. At first I thought it was due to the NT box drive being a RAID configuration be alas the problem also occurs on Win 85 and Win 98 computers. A search of the archive did not point to any solutions. Anyone have an idea of what is going wrong? Amanda version 2.4.2p2 tar (GNU tar) 1.13.25 Thanks, Vytas These dumps were to tape Daily14. The next tape Amanda expects to use is: Daily15. FAILURE AND STRANGE DUMP SUMMARY vxa2 //nt-01/nt01-d lev 0 STRANGE /-- vxa2 //nt-01/nt01-d lev 0 STRANGE sendbackup: start [vxa2://nt-01/nt01-d level 0] sendbackup: info BACKUP=/usr/bin/smbclient sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... - sendbackup: info end ? NT_STATUS_SHARING_VIOLATION opening remote file \pagefile.sys (\) ? SUCCESS - 0 opening remote file \Project\AgCan\0_Ontario\ALCDB_Vytas.zip (\Project\AgCan\0_Ontario\) ? SUCCESS - 0 opening remote file \Project\AgCan\0_Ontario\Arc_Info_Generalize.bmp (\Project\AgCan\0_Ontario\) ? SUCCESS - 0 listing \Project\AgCan\0_Ontario\bend100\* ? SUCCESS - 0 listing \Project\AgCan\0_Ontario\bend15\* ? SUCCESS - 0 listing \Project\AgCan\0_Ontario\bend30\* ? SUCCESS - 0 listing \Project\AgCan\0_Ontario\bend300\* ? SUCCESS - 0 listing \Project\AgCan\0_Ontario\bend50\* ? SUCCESS - 0 listing \Project\AgCan\0_Ontario\test\* ? SUCCESS - 0 opening remote file \Project\AgCan\0_Ontario\Testdata.mxd ... ... ... ? SUCCESS - 0 listing \Proposal\* ? SUCCESS - 0 listing \restore\* ? SUCCESS - 0 opening remote file \ROND.DBF (\) ? SUCCESS - 0 listing \scan2cad\* ? SUCCESS - 0 listing \Scan2Vec\* ? SUCCESS - 0 listing \Seagate Software\* ? SUCCESS - 0 opening remote file \SQL.LOG (\) ? SUCCESS - 0 listing \System\* ? SUCCESS - 0 listing \TCWIN\* ? SUCCESS - 0 listing \wag\* ? SUCCESS - 0 listing \wagner_unix\* ? SUCCESS - 0 listing \WINNT\* ? SUCCESS - 0 listing \WorkSpace\* ? SUCCESS - 0 listing \yukon scans\* | tar: dumped 29441 files and directories | Total bytes written: 21413944832 sendbackup: size 20912056 sendbackup: end \ DUMP SUMMARY: DUMPER STATS TAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- -- vxa2 -nt-01/nt01-d 0 20912056 14609312 69.9 126:22 1926.7 39:11 6214.0 Window NT drive stats. Total Files Listed: 184354 File(s) 88,102,672,147 bytes 29,309,644,800 bytes free Vytas Janusauskas Dendron Resource Surveys Inc. 880 Lady Ellen Place, Suite 206 Ottawa, Ontario, Canada K1Z 5L9 Voice: (613) 725-2971 Fax: (613) 725-1716 mailto:[EMAIL PROTECTED] --- Jean-Christian SIMONETTIemail: [EMAIL PROTECTED] SysAdmin Wanadoo Portails phone: (+33)493004911 Sophia Antipolis, France ---
Problems with taper getting short writes
I've got a DLT8000 with amanda 2.4.2p2 from Red Hat's RH73 packages. Whenever I try to do an amflush, the dumps terminate with an out of tape error. This has been true for six tapes in a row. The amanda log contains: INFO taper tape Daily7 kb 1310944 fm 2 writing file: Input/output error FAIL taper vilya /BIG/oracle/oradata/SVIL1 1 [out of tape] and syslog notes: Jun 6 13:05:53 bunker kernel: st0: Error with sense data: Info fld=0x8000, Current st09:00: sense key Aborted Command Jun 6 13:05:53 bunker kernel: Additional sense indicates Scsi parity error I'd be inclined to suspect hardware, except that I can reliably and repeatably dd many gigs of junk from /dev/urandom to the tape (after having mt fsf'ed over the amanda header) without getting any write errors at all. Does anyone have any ideas what I might try to get a better feel for the error, and hopefully to fix the error? Tom Yates
[no subject]
I'm trying to do an amamda backup to a disk file. The disk I'm backing up has 3.1GB used (4GB total), while the output tape I'm writing to has a length of 5GB. It should fit, but I get the following error message in the report: FAILURE AND STRANGE DUMP SUMMARY: catwoman.b / lev 0 FAILED [out of tape] Why? I'm using amanda 2.4.4, backing up an Irix disk to a Linux amanda server. Dan
amanda and PowerVault 132T LTO-2
Hi! Any one using PowerVault 132T LTO-2 with amanda? Tape-type? Workning tape changer script? Cheers, Eric Eric Björkvall IT Manager Microbiology Tumor Biology Center (MTC) Karolinska Institutet Box 280 S-171 77 Stockholm, Sweden Office: +46 (0)8 728 63 09 http://www.mtc.ki.se
out of tape - why?
I'm trying to do an amamda backup to a disk file. The disk I'm backing up has 3.1GB used (4GB total), while the output tape I'm writing to has a length of 5GB. It should fit, but I get the following error message in the report: FAILURE AND STRANGE DUMP SUMMARY: catwoman.b / lev 0 FAILED [out of tape] Why? I'm using amanda 2.4.4, backing up an Irix disk to a Linux amanda server. Dan
RE: out of tape - why?
I'm trying to do an amamda backup to a disk file. The disk I'm backing up has 3.1GB used (4GB total), while the output tape I'm writing to has a length of 5GB. It should fit, but I get the following error message in the report: FAILURE AND STRANGE DUMP SUMMARY: catwoman.b / lev 0 FAILED [out of tape] Why? I'm using amanda 2.4.4, backing up an Irix disk to a Linux amanda server. Dan What else does the report say? What is the tape size and dump size listed in the report? (i.e. Output Size (meg) 11704.411704.40.0 Tape Size (meg) 11704.911704.90.0) What does your tapetype entry look like?
RE: out of tape - why?
The tapetype is as follows:
define tapetype HWDISK-FILE {
comment disk file
length 5000 mbytes
filemark 0 kbytes
}
In the amdump file I see these lines:
DELAYING DUMPS IF NEEDED, total_size 3168416, tape length 512 mark 0
delay: Total size now 3168416.
PROMOTING DUMPS IF NEEDED, total_lev0 3168320, balanced_size 3168320...
which seem to indicate enough tape.
Here's most of the report:
FAILURE AND STRANGE DUMP SUMMARY:
catwoman.b / lev 0 FAILED [out of tape]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:07
Run Time (hrs:min) 1:03
Dump Time (hrs:min)0:40 0:40 0:00
Output Size (meg)3093.7 3093.70.0
Original Size (meg) 3093.7 3093.70.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped1 1 0
Avg Dump Rate (k/s) 1306.3 1306.3--
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
USAGE BY TAPE:
Label Time Size %Nb
Rover_MonthlySetA01 0:00 0.00.0 0
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
catwoman.bsd / 0 31679703167970 -- 40:251306.3 FAILED
(brought to you by Amanda version 2.4.4)
At 09:31 AM 6/6/2003 -0500, Rebecca Pakish Crum wrote:
I'm trying to do an amamda backup to a disk file. The disk
I'm backing up has 3.1GB used (4GB total), while the output
tape I'm writing to has a length of 5GB. It should fit,
but I get the following error message in the
report:
FAILURE AND STRANGE DUMP SUMMARY:
catwoman.b / lev 0 FAILED [out of tape]
Why? I'm using amanda 2.4.4, backing up an Irix disk to a
Linux amanda server.
Dan
What else does the report say? What is the tape size and dump size
listed in the report?
(i.e.
Output Size (meg) 11704.411704.40.0
Tape Size (meg) 11704.911704.90.0)
What does your tapetype entry look like?
RE: out of tape - why?
On Fri, 6 Jun 2003 at 9:57am, Danny R Spelbring wrote DUMPER STATSTAPER STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - catwoman.bsd / 0 31679703167970 -- 40:251306.3 FAILED (brought to you by Amanda version 2.4.4) Ah ha. The dump to holding disk succeeded, but the taping didn't. I'm assuming your holding disk is on the same partition as your tapes? And it it's smaller than 6.2GB? You can turn off the holding disk for this dump, or put your holding disk somewhere else. With only one client, it isn't doing you any good anyway. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: out of tape - why?
Danny R Spelbring wrote: In the amdump file I see these lines: DELAYING DUMPS IF NEEDED, total_size 3168416, tape length 512 mark 0 delay: Total size now 3168416. PROMOTING DUMPS IF NEEDED, total_lev0 3168320, balanced_size 3168320... which seem to indicate enough tape. That's the theory. What's the reality? df -k /your/amanda/hwdiskdir I suppose your holdingdisk is not on the same partition as your hwdisk-file? If yes, do they BOTH fit at the same time with a complete image? Here's most of the report: *AL*most, you left you the NOTES section, which contains exactly where the end of tape was hit, like: NOTES: taper: tape ARCHIVE-038 kb 33907744 fm 29 writing file: No space left on device i.e. after writing almost 34 GByte. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: tape hardware choices
Just have to throw my 2 cents into this thread: I have been using a SpectraLogic 1 library with 40 slots and 4 AIT drives for a couple of years now and the performance has been so good that we are dumping DLT across the enterprise and switching to AIT. I even contacted SpectraLogic and had them add amanda under the a user has gotten it to work software category. ;) And for the beta remark about sony.mine still works, beta is still used by a great number of commercial organizations, and my 20 year old beta player still outperforms my 2 year old VHS machine. Just because your average consumer can't get their hands on it anymore doesn't mean anything, we after all, are not your average consumers. George Kelbley wrote: I'm looking into upgrading my tape hardware, and while a I know lots of sales types will give me lots of info, I was wondering what folks are using for amanda. -- Mike Taylor. GSEC/GCFW 'Non Impediti Ratione Cogitationis' Coordinator of Systems Administration and Network Security Indiana State University. Rankin Hall Rm 052 210 N 7th St. Terre Haute, IN. Voice: 812-237-8843
Re: Failed Backups
Steve, On Wed, Jun 04, 2003 at 02:29:20PM -, smw_purdue wrote: Chris, I'm having the same problem using a similar configuration of backups to disk without any holding disks. Every time Amanda drops into degraded mode it's because an error occurred with one of the clients (usually a timeout, indicating that a client system was unavailable). I would suspect that there's a bug in the code that puts Amanda into degraded mode on more errors than just a tape error. Notice in your log that you have an unknown response from gilgamesh. This error was probably what kicked Amanda into degraded mode. That is exactly what appears to be happening. I configured a holding disk in an attempt to eliminate that as a possible cause. In my case, the problem is intermittent with everything working fine for some time and then I a failure. The failure may be some file systems on a given host or most/all of the backup run. Today, I had two file systems fail on the again on gilgamesh and I began checking the various logs for issue. What I found in sendbackup.lotsofnumbers.debug is: ---[ begin ]--- sendbackup: time 0.002: stream_server: waiting for connection: 0.0.0.0.1496 sendbackup: time 0.002: stream_server: waiting for connection: 0.0.0.0.1497 sendbackup: time 0.002: stream_server: waiting for connection: 0.0.0.0.1498 sendbackup: time 0.003: waiting for connect on 1496, then 1497, then 1498 sendbackup: time 29.996: stream_accept: timeout after 30 seconds sendbackup: time 29.996: timeout on data port 1496 sendbackup: time 59.996: stream_accept: timeout after 30 seconds sendbackup: time 59.996: timeout on mesg port 1497 sendbackup: time 89.996: stream_accept: timeout after 30 seconds sendbackup: time 89.996: timeout on index port 1498 sendbackup: time 89.996: pid 5263 finish time Fri Jun 6 00:47:44 2003 ---[ end ]--- Anybody out there have time to debug the source? I may take a look at it but time is at a premium right now... (when isn't it???). Anyone have any ideas? This only happens occasionally and I haven't yet been able to draw a correlation. Thanks, Chris
RE: out of tape - why?
Yes, in my first attempt I was using a holding disk (of 4GB) on the same partition as the tapedisk (of 5GB), with a total of 9.5GB free in the par- tition. I tried it again without the holding disk and it still failed with out of tape. There's definitely enough free space on the disk. I'm using a chunk size of 1GB, so after two chunks (actually 2.14GB), it fails. I don't see that as an issue though. At 10:58 AM 6/6/2003 -0400, Joshua Baker-LePain wrote: On Fri, 6 Jun 2003 at 9:57am, Danny R Spelbring wrote DUMPER STATSTAPER STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - catwoman.bsd / 0 31679703167970 -- 40:251306.3 FAILED (brought to you by Amanda version 2.4.4) Ah ha. The dump to holding disk succeeded, but the taping didn't. I'm assuming your holding disk is on the same partition as your tapes? And it it's smaller than 6.2GB? You can turn off the holding disk for this dump, or put your holding disk somewhere else. With only one client, it isn't doing you any good anyway. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: out of tape - why?
Danny R Spelbring wrote: Yes, in my first attempt I was using a holding disk (of 4GB) on the same partition as the tapedisk (of 5GB), with a total of 9.5GB free in the par- tition. I tried it again without the holding disk and it still failed with out of tape. There's definitely enough free space on the disk. I'm using a chunk size of 1GB, so after two chunks (actually 2.14GB), it fails. I don't see that as an issue though. Strange. There is no chunking when you don't have a holdingdisk. How do you know it fails after two chunks? -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Amanda thru a firewall
I am attempting to backup a system that is on the other side of an iptables/netfilter firewall. I have opened ports 10080 10082 an 10083 for udp and tcp. The system passes amcheck, but the dump give me this report. (dogs is in fact offline, I am trying to backup ftp) FAILURE AND STRANGE DUMP SUMMARY: planner: ERROR Request to dogs timed out. ftp/ lev 0 FAILED 20030606[could not connect to ftp] ftp/home/ftp lev 0 FAILED 20030606[could not connect to ftp] dogs / RESULTS MISSING dogs /export/home RESULTS MISSING All the other systems in this set backup just fine. What am I missing here. -- Mike Taylor. GSEC/GCFW 'Non Impediti Ratione Cogitationis' Coordinator of Systems Administration and Network Security Indiana State University. Rankin Hall Rm 052 210 N 7th St. Terre Haute, IN. Voice: 812-237-8843
Re: Failed Backups
Chris,
I looked around a little in the Amanda source code and convinced myself
that there was a bug there. I sent a note to to the amanda-hackers
mailing list and received a prompt reply from Jean-Louis Martineau with
a patch that fixed the problem for me. I'll attach his message and patch.
Hope that helps!
Steve
Chris Gordon wrote:
Steve,
On Wed, Jun 04, 2003 at 02:29:20PM -, smw_purdue wrote:
Chris,
I'm having the same problem using a similar configuration of backups
to disk without any holding disks. Every time Amanda drops into
degraded mode it's because an error occurred with one of the clients
(usually a timeout, indicating that a client system was unavailable).
I would suspect that there's a bug in the code that puts Amanda into
degraded mode on more errors than just a tape error. Notice in your
log that you have an unknown response from gilgamesh. This error
was probably what kicked Amanda into degraded mode.
That is exactly what appears to be happening. I configured a holding
disk in an attempt to eliminate that as a possible cause. In my case,
the problem is intermittent with everything working fine for some time
and then I a failure. The failure may be some file systems on a given
host or most/all of the backup run.
Today, I had two file systems fail on the again on gilgamesh
and I began checking the various logs for issue. What I found in
sendbackup.lotsofnumbers.debug is:
---[ begin ]---
sendbackup: time 0.002: stream_server: waiting for connection:
0.0.0.0.1496
sendbackup: time 0.002: stream_server: waiting for connection:
0.0.0.0.1497
sendbackup: time 0.002: stream_server: waiting for connection:
0.0.0.0.1498
sendbackup: time 0.003: waiting for connect on 1496, then 1497, then
1498
sendbackup: time 29.996: stream_accept: timeout after 30 seconds
sendbackup: time 29.996: timeout on data port 1496
sendbackup: time 59.996: stream_accept: timeout after 30 seconds
sendbackup: time 59.996: timeout on mesg port 1497
sendbackup: time 89.996: stream_accept: timeout after 30 seconds
sendbackup: time 89.996: timeout on index port 1498
sendbackup: time 89.996: pid 5263 finish time Fri Jun 6 00:47:44 2003
---[ end ]---
Anybody out there have time to debug the source? I may take a look at
it but time is at a premium right now... (when isn't it???).
Anyone have any ideas? This only happens occasionally and I haven't
yet been able to draw a correlation.
Thanks,
Chris
--
Steven M. Wilson, Systems and Network Manager
Markey Center for Structural Biology
Purdue University
[EMAIL PROTECTED]765.496.1946
--- server-src/driver.c.orig2003-01-01 18:28:54.0 -0500
+++ server-src/driver.c 2003-06-04 15:54:44.0 -0400
@@ -2242,10 +,10 @@
error(error [dump to tape DONE result_argc != 5: %d], result_argc);
}
- free_serial(result_argv[2]);
-
if(failed == 1) goto tryagain; /* dump didn't work */
- else if(failed == 2) goto fatal;
+ else if(failed == 2) goto failed_dumper;
+
+ free_serial(result_argv[2]);
/* every thing went fine */
update_info_dumper(dp, origsize, dumpsize, dumptime);
@@ -2259,9 +2239,10 @@
case TRYAGAIN: /* TRY-AGAIN handle err mess */
tryagain:
+ headqueue_disk(runq, dp);
+failed_dumper:
update_failed_dump_to_tape(dp);
free_serial(result_argv[2]);
- headqueue_disk(runq, dp);
tape_left = tape_length;
break;
@@ -2269,7 +2250,6 @@
case TAPE_ERROR: /* TAPE-ERROR handle err mess */
case BOGUS:
default:
-fatal:
update_failed_dump_to_tape(dp);
free_serial(result_argv[2]);
failed = 2; /* fatal problem */
---BeginMessage---
Hi Steven,
Could you try this patch, It should apply to the latest 2.4.4
snapshot for http://www.iro.umontreal.ca/~martinea/amanda
Jean-Louis
On Wed, Jun 04, 2003 at 02:16:14PM -0500, Steven M. Wilson wrote:
I have a question for the Amanda development experts.
I'm using version 2.4.4 and backing up to hard disk directly (no tapes, no
holding disks). On several occasions, I've had a client error cause Amanda
to go into degraded mode. It appears that the dump_to_tape function
(server-src/driver.c) takes any FATAL dumper error and forces Amanda into
degraded mode. Shouldn't the code be more discerning as to what caused the
error? I would think that Amanda should go into degraded mode only if an
error were related to the output device. In my case the error was on the
client and unrelated to writing the backup to disk.
Here's some of the related amdump messages:
driver: result time 6754.491 from dumper0: FAILED 01-00368 [data timeout]
taper: reader-side: got label slot024 filenum 184
driver: result time 6754.492 from taper: DONE 00-00367 slot024 184 [sec
2174.408 kb 2061376 kps 948.0 {wr: writers 64419 rdwait 2166.220 wrwait
7.959 filemark 0.021}]
driver: error time 6754.503 serial gen mismatch dump of
Re: Amanda thru a firewall
If you run a Linux 2.5 kernel there is Amanda support built in to the kernel (actually its an option in the netfilter section of the kernel config, you have to enable it). On older kernels, your best bet is to rebuild your Amanda server and clients using the 'portrange' options to limit Amanda to a narrow range of ports and have your firewall rules allow traffic on those ports between the client and server. Another option is to rsync the desired directories on the remote server to somewhere local that you could then back up. Frank --On Friday, June 06, 2003 10:52:10 -0500 F.M. Taylor [EMAIL PROTECTED] wrote: I am attempting to backup a system that is on the other side of an iptables/netfilter firewall. I have opened ports 10080 10082 an 10083 for udp and tcp. The system passes amcheck, but the dump give me this report. (dogs is in fact offline, I am trying to backup ftp) FAILURE AND STRANGE DUMP SUMMARY: planner: ERROR Request to dogs timed out. ftp/ lev 0 FAILED 20030606[could not connect to ftp] ftp/home/ftp lev 0 FAILED 20030606[could not connect to ftp] dogs / RESULTS MISSING dogs /export/home RESULTS MISSING All the other systems in this set backup just fine. What am I missing here. -- Mike Taylor. GSEC/GCFW 'Non Impediti Ratione Cogitationis' Coordinator of Systems Administration and Network Security Indiana State University. Rankin Hall Rm 052 210 N 7th St. Terre Haute, IN. Voice: 812-237-8843 -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
out of tape - resolved
You're right about that. I just tried to create a 3.2GB file and it failed with file too large at the 2GB limit. It's an ext2. I have an ext3 sys- tem too. Is that also a problem there? I'll have to try/fix it if I can. At 11:50 AM 6/6/2003 -0400, Jon LaBadie wrote: On Fri, Jun 06, 2003 at 10:33:08AM -0500, Danny R Spelbring wrote: Yes, in my first attempt I was using a holding disk (of 4GB) on the same partition as the tapedisk (of 5GB), with a total of 9.5GB free in the par- tition. I tried it again without the holding disk and it still failed with out of tape. There's definitely enough free space on the disk. I'm using a chunk size of 1GB, so after two chunks (actually 2.14GB), it fails. I don't see that as an issue though. I think chunksize only relates to the holding disk. HOWEVER 2GB is veddy interesting. Does your filesystem and user environment support large files. Many filesystems have a limit on the largest file the file system will handle. 2GB just happens to be the common limit. In fact, the primary reason for chunk's on the holding disk is to avoid these filesystem limits. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Problems with taper getting short writes
On Fri, Jun 06, 2003 at 03:03:00PM +0100, [EMAIL PROTECTED] wrote: Jun 6 13:05:53 bunker kernel: Additional sense indicates Scsi parity error I'd be inclined to suspect hardware That's what it looks like to me -- specifically, data getting corrupted on the SCSI bus. except that I can reliably and repeatably dd many gigs of junk from /dev/urandom to the tape (after having mt fsf'ed over the amanda header) without getting any write errors at all. Your test is only giving the SCSI subsystem half the workout that amflush does. Try dd'ing from a disk on the same SCSI bus as the tape drive, instead of from /dev/urandom. I don't know if it matters whether you dd from files, e.g. the stuff still sitting in your holding disk, or from the device itself -- /dev/whatever. Couldn't hurt to try it both ways :-) -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / When I came back around from the dark side, there in front of me would be the landing area where the crew was, and the Earth, all in the view of my window. I couldn't help but think that there in front of me was all of humanity, except me. - Michael Collins, Apollo 11 Command Module Pilot
A doubt about Amanda
Hi, Sorry for the question but, if I have a 'dump cycle 7' and a 'runs per cycle 5', Amanda will do backup five days of a Week. What's happen if the server where I'm getting a backup down on the 3th day ? Could I recover the backup until the 2st day ? Thanks, ROberto Samarone Araujo
Re: A doubt about Amanda
--On Friday, June 06, 2003 19:39:39 -0300 Roberto Samarone Araujo (RSA) [EMAIL PROTECTED] wrote: Hi, Sorry for the question but, if I have a 'dump cycle 7' and a 'runs per cycle 5', Amanda will do backup five days of a Week. What's happen if the server where I'm getting a backup down on the 3th day ? Could I recover the backup until the 2st day ? You will be able to recover up to whenever Amanda last ran. So if you run Monday through Friday night and your disk dies early Monday, you will be able to restore the disk to the way it was Friday night. Frank Thanks, ROberto Samarone Araujo -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
rait output driver
I got these errors when running amverify using:
tapedev rait:{file:/holdingdisk/backup,tape:/dev/nst1}
This is with snapshot:
amanda-2.4.4-20030603.tar.gz
Thanks,
Dick
--- Start of forwarded message ---
Date: Fri, 6 Jun 2003 09:22:27 -0600
From: Amanda user [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: AmeriCom AMANDA VERIFY REPORT FOR Full5
Tapes: Full5
Errors found:
Full5 ():
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}: Input/output
error
** No header
0+0 in
0+0 out
Full5 ():
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}: Input/output
error
** No header
0+0 in
0+0 out
Full5 ():
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}: Input/output
error
** No header
0+0 in
0+0 out
Full5 ():
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}: Input/output
error
** No header
0+0 in
0+0 out
Full5 ():
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}: Input/output
error
** No header
0+0 in
0+0 out
Full5 ():
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}: Input/output
error
** No header
0+0 in
0+0 out
amverify Onstream
Fri Jun 6 07:53:22 MDT 2003
Using device rait:{file:/holdingdisk/backup,tape:/dev/nst1}
Volume Full5, Date 20030605
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
** Error detected ()
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}: Input/output
error
** No header
0+0 in
0+0 out
** Error detected ()
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}: Input/output
error
** No header
0+0 in
0+0 out
** Error detected ()
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}: Input/output
error
** No header
0+0 in
0+0 out
** Error detected ()
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}: Input/output
error
** No header
0+0 in
0+0 out
** Error detected ()
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}: Input/output
error
** No header
0+0 in
0+0 out
** Error detected ()
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}: Input/output
error
** No header
0+0 in
0+0 out
Too many errors.
--- End of forwarded message ---
Re: rait output driver
Dick,
What kind of tape drive do you have?
Try to configure amanda with '--with-broken-fsf'.
Jean-Louis
On Sat, Jun 07, 2003 at 12:40:27AM -, [EMAIL PROTECTED] wrote:
I got these errors when running amverify using:
tapedev rait:{file:/holdingdisk/backup,tape:/dev/nst1}
This is with snapshot:
amanda-2.4.4-20030603.tar.gz
Thanks,
Dick
--- Start of forwarded message ---
Date: Fri, 6 Jun 2003 09:22:27 -0600
From: Amanda user [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: AmeriCom AMANDA VERIFY REPORT FOR Full5
Tapes: Full5
Errors found:
Full5 ():
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
Full5 ():
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
Full5 ():
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
Full5 ():
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
Full5 ():
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
Full5 ():
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
amverify Onstream
Fri Jun 6 07:53:22 MDT 2003
Using device rait:{file:/holdingdisk/backup,tape:/dev/nst1}
Volume Full5, Date 20030605
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
** Error detected ()
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
** Error detected ()
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
** Error detected ()
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
** Error detected ()
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
** Error detected ()
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
** Error detected ()
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
Too many errors.
--- End of forwarded message ---
--
Jean-Louis Martineau email: [EMAIL PROTECTED]
Departement IRO, Universite de Montreal
C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529
Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: Amanda thru a firewall
On Friday 06 June 2003 12:21, Frank Smith wrote: If you run a Linux 2.5 kernel there is Amanda support built in to the kernel (actually its an option in the netfilter section of the kernel config, you have to enable it). On older kernels, your best bet is to rebuild your Amanda server and clients using the 'portrange' options to limit Amanda to a narrow range of ports and have your firewall rules allow traffic on those ports between the client and server. Another option is to rsync the desired directories on the remote server to somewhere local that you could then back up. Frank FWIW, that is also a function available in the last 3 or 4 of the 'rc' candidates for kernel 2.4.21. I haven't tried it myself as my firewall machine is on this side of the firewall as far as access to back it up is concerned. --On Friday, June 06, 2003 10:52:10 -0500 F.M. Taylor [EMAIL PROTECTED] wrote: I am attempting to backup a system that is on the other side of an iptables/netfilter firewall. I have opened ports 10080 10082 an 10083 for udp and tcp. The system passes amcheck, but the dump give me this report. (dogs is in fact offline, I am trying to backup ftp) FAILURE AND STRANGE DUMP SUMMARY: planner: ERROR Request to dogs timed out. ftp/ lev 0 FAILED 20030606[could not connect to ftp] ftp/home/ftp lev 0 FAILED 20030606[could not connect to ftp] dogs / RESULTS MISSING dogs /export/home RESULTS MISSING All the other systems in this set backup just fine. What am I missing here. -- Mike Taylor. GSEC/GCFW 'Non Impediti Ratione Cogitationis' Coordinator of Systems Administration and Network Security Indiana State University. Rankin Hall Rm 052 210 N 7th St. Terre Haute, IN. Voice: 812-237-8843 -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501 -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: rait output driver
Dick,
What kind of tape drive do you have?
Good point!
I am using an Onstream ADR50 for this test and forgot about the problems
this drive has with amanda. I also have an Ecrix, which works fine, and
I was ultimately planning to use both tape drives and a disk file.
I didn't want to disrupt our normal backups, so I used the Onstream for
this test. It has known issues with amanda so I don't even think
--with-broken-fsf will help.
I will retry with the Ecrix.
I apologize for the false alarm.
Thanks,
Dick
Try to configure amanda with '--with-broken-fsf'.
Jean-Louis
On Sat, Jun 07, 2003 at 12:40:27AM -, [EMAIL PROTECTED] wrote:
I got these errors when running amverify using:
tapedev rait:{file:/holdingdisk/backup,tape:/dev/nst1}
This is with snapshot:
amanda-2.4.4-20030603.tar.gz
Thanks,
Dick
--- Start of forwarded message ---
Date: Fri, 6 Jun 2003 09:22:27 -0600
From: Amanda user [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: AmeriCom AMANDA VERIFY REPORT FOR Full5
Tapes: Full5
Errors found:
Full5 ():
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
Full5 ():
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
Full5 ():
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
Full5 ():
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
Full5 ():
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
Full5 ():
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
amverify Onstream
Fri Jun 6 07:53:22 MDT 2003
Using device rait:{file:/holdingdisk/backup,tape:/dev/nst1}
Volume Full5, Date 20030605
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
Checked vulcan.internal.americom.com._boot.20030605.0
** Error detected ()
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
** Error detected ()
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
** Error detected ()
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
** Error detected ()
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
** Error detected ()
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf rait:{file:/holdingdisk/backup,tape:/dev/nst1}:
Input/output error
** No header
0+0 in
0+0 out
** Error detected ()
amrestore: 0: skipping start of tape: date 20030605 label Full5
amrestore: could not fsf
data timeout
Since I have converted from samba to cygwin clients on our windows machines, I occasionally get the error below: andorian.americom.com:/cygdrive/c 0 driver: [data timeout] (20:42:43) It happens on each of the windows machines with no particular order to it. I am wondering if there is a timeout parameter in amanda.conf which might affect this. Can anyone tell me if dtimeout is the parameter controlling this? It is currently set to 1800 which I would think would be plenty. Or is this error due to something else? Thanks, Dick
Re: data timeout
On Sat, Jun 07, 2003 at 03:22:33AM -, [EMAIL PROTECTED] wrote: Since I have converted from samba to cygwin clients on our windows machines, I occasionally get the error below: andorian.americom.com:/cygdrive/c 0 driver: [data timeout] (20:42:43) It happens on each of the windows machines with no particular order to it. I am wondering if there is a timeout parameter in amanda.conf which might affect this. Can anyone tell me if dtimeout is the parameter controlling this? It is currently set to 1800 which I would think would be plenty. Or is this error due to something else? Back when I was using Cygwin I found the performance of tar runing under cygwin was very poor. I attributed it (without evidence) to the need to translate all those unix style semantics (inodes, ...) to NTFS and back for each and every file. My backup of about 15GB of data on 4 partitions took 3 - 4 hours. Yes, dtimeout is the parameter. Unless the problem is during estimates and sometimes you get no schedule from planner (I got that too). Then it is etimeout. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: data timeout
Jon, Thanks for the reply. You say: Back when I was using Cygwin... Did you go back to samba, or don't you backup windows boxes anymore? And yes, I did have to increase etimeout to 3600. I guess I will increase dtimeout as well, though it is inconceivable that 30 minutes can pass without a reply from tar. Thanks again, Dick On Sat, Jun 07, 2003 at 03:22:33AM -, [EMAIL PROTECTED] wrote: Since I have converted from samba to cygwin clients on our windows machines, I occasionally get the error below: andorian.americom.com:/cygdrive/c 0 driver: [data timeout] (20:42:43) It happens on each of the windows machines with no particular order to it. I am wondering if there is a timeout parameter in amanda.conf which might affect this. Can anyone tell me if dtimeout is the parameter controlling this? It is currently set to 1800 which I would think would be plenty. Or is this error due to something else? Back when I was using Cygwin I found the performance of tar runing under cygwin was very poor. I attributed it (without evidence) to the need to translate all those unix style semantics (inodes, ...) to NTFS and back for each and every file. My backup of about 15GB of data on 4 partitions took 3 - 4 hours. Yes, dtimeout is the parameter. Unless the problem is during estimates and sometimes you get no schedule from planner (I got that too). Then it is etimeout. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: out of tape - resolved
On Fri, 6 Jun 2003 at 11:53am, Danny R Spelbring wrote You're right about that. I just tried to create a 3.2GB file and it failed with file too large at the 2GB limit. It's an ext2. I have an ext3 sys- tem too. Is that also a problem there? I'll have to try/fix it if I can. More important is the base distro. Both ext2 and ext3 can support large files, but glibc must to get the ball rolling. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
