Re: Any amanda gui tools?
Thanks Chris and all who replied. I'm a little snowed over, but next week I'll give it a shot, better chance now that all my guns are loaded. Chow, Trevor. - Original Message - From: Chris Herrmann [EMAIL PROTECTED] To: 'Trevor Fraser' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Friday, September 06, 2002 1:15 AM Subject: RE: Any amanda gui tools? can you do something like this with amrecover? I usually use that when I need to pull a file off a tape, but I don't know if it'll easily drop out a list of files for you to compare / diff / etc |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Trevor Fraser |Sent: Thursday, 5 September 2002 21:45 |To: [EMAIL PROTECTED] |Subject: Any amanda gui tools? | | |Hello all. | |I was asked if there was a tool, not necessarily graphical, |but that will be |better, that can compare what is on a tape to the directory |the information |on the tape comes from and notify the user of any missing |files. Is there |anything like this around? | |The aim is to find an efficient way of seeing what file was |accidentally |deleted (don't know name/location), without going through a |pain staking |process of checking 20 GB of files against a tape. | | |Let me know. |Thanks, Trevor. | |= |Stussy said:Knowledge is King! |= | |
Tape technology
Hi all, Perhaps this is not quite the place for this question, but I hope it won't offend anyone ;) I will be looking to get a new tape drive, but am not very familiar with the current technology. I have heard of DDS, DAT and have used Travan. As far as I'm concerned, the Travan is out of the question, 'cause the tapes are so expensive (and apparently they are now obsolete?). So; what are the opinions of this list? (BEGIN FLAME...?) ..Brian -- Init Systems - Linux consulting 031 767-0139082 769-2320[EMAIL PROTECTED]
Re: gnutar dies on RedHat 6.2
At 07:11 9/4/2002 -0400, Gene Heskett wrote: On Wednesday 04 September 2002 01:52, Per olof Ljungmark wrote: Hi all, Got a working amanda 2.4.3b2 installation running on a FreeBSD 4.6 server. AFAICS everything is OK except for one thing, backing up RedHat 6.2 systems with gnutar. The only trace of the failure I have is the following in /tmp/amanda/: sendsize: asking killpgrp to terminate sendsize: calculating for amname '/etc', dirname '/etc' sendsize: getting size via gnutar for /etc level 0 and then nothing. Dump is fine from same machine. Grateful for a hint, Per olof Upgrade your 6.2 boxes gnutar to at least 1.13-19? 1.13-25 is the latest, on alpha.gnu.org. Thanks everybody for your tips. However, I still get the error (or absence of error) above after upgrading to 1.13.25. Is there a way to increase the verbosity of the debug files to find out what is going on? Or can I use sendsize manually on the client? I'm stuck at the moment. Thanks, Per olof
HP Colorado, ide-scsi
Hi all,
I'm getting this in my kern.log's:
---
Sep 6 00:45:01 valhalla kernel: st: Version 20020205, bufsize 32768, wrt 30720, max
init. bufs 4, s/g segs 16
Sep 6 00:45:01 valhalla kernel: Attached scsi tape st0 at scsi0, channel 0, id 0, lun 0
Sep 6 00:45:01 valhalla kernel: st0: Block limits 25976 - 6841632 bytes.
Sep 6 01:18:39 valhalla kernel: st0: Error with sense data: Info fld=0x10200,
Deferred st09:00: sense key Medium Error
Sep 6 01:18:39 valhalla kernel: Additional sense indicates Sequential positioning
error
Sep 6 01:30:01 valhalla kernel: st: Unloaded.
---
This was from an amdump, which failed after 64kb written.
A little bit later, running an amcheck:
---
Sep 6 09:54:45 valhalla kernel: st: Version 20020205, bufsize 32768, wrt 30720, max
init. bufs 4, s/g segs 16
Sep 6 09:54:45 valhalla kernel: Attached scsi tape st0 at scsi0, channel 0, id 0, lun 0
Sep 6 09:54:45 valhalla kernel: st0: Block limits 11268 - 112641 bytes.
Sep 6 10:09:45 valhalla kernel: scsi : aborting command due to timeout : pid 72600,
scsi0, channel 0, id 0, lun 0 Read (6) 01 00 00 40 00
Sep 6 10:09:45 valhalla kernel: hdd: irq timeout: status=0xc0 { Busy }
Sep 6 10:09:45 valhalla kernel: hdd: ATAPI reset complete
Sep 6 10:09:45 valhalla kernel: hdd: irq timeout: status=0x80 { Busy }
Sep 6 10:09:46 valhalla kernel: hdd: ATAPI reset complete
Sep 6 10:09:46 valhalla kernel: hdd: irq timeout: status=0x80 { Busy }
Sep 6 10:09:46 valhalla kernel: st0: Error 2707 (sugg. bt 0x20, driver bt 0x7,
host bt 0x7).
Sep 6 10:20:01 valhalla kernel: st: Unloaded.
---
Pulled the tape out, plugged it back in, and now its dumping fine. Can anyone make
sense of this?
BTW is there a way of getting amanda to put level 0's in degraded mode? I'd still
like full dumps when I have to manually run amdump.
Regards,
Brian Jonnes
--
Init Systems - Linux consulting
031 767-0139082 769-2320[EMAIL PROTECTED]
Newbie tape drive install
Title: Newbie tape drive install Yhello all, Amanda is great! Been using it for about a week now on our production servers (e250's). I now want to put another tape drive onto an Ultra10 I have for off-site backups. It's all connected but I can't get solaris to detect the tape drive - obviously I'm doing something wrong. Even tried updating /kernel/drv/st.conf and booting with boot -vr but the e250's didn't need to. Maybe I need to add the tape alias? The major difference is the e250's connect, via wide scsi cables, to the controller on-board. I've grabbed a scsi controller and put it into a pci slot of this ultra10. However, the connector to the ultra10 is thin so perhaps I'm trying to fit a square into a circle? Anyways, I know this is not exactly an amanda question but a Solaris config issue and any help in pointing me in the right direction would be greatly appreciated. I can't find much info out there. uname -a: SunOS crafty 5.8 Generic 108528-13 sun4u sparc SUNW,Ultra-5_10 tape unit: Sony SDX-S300C (AIT Drive) Cheers, Gordon ([EMAIL PROTECTED])
amdump only to holding disk - how to do
Is there any option to switch amdump only to dump to the (large enough) holding disk? We have the problem that our tape drive (Onstream ADR-50) has a frimware problem, as recognized by some people in this group, so that the normal way which amdump uses to write to teh tape, produces hardware errors, when reading the tape. The firmware has problems with the large breaks between writing different tape blocks, which is an usual feature of amanda. So I thought of 1. using amdump to produce the holding disk 2. after amdump has completely finished writing to the holding disk, to use amflush to save the whole thing on tape. This should work, because in this case the tape is written in one large amount without any break. Walter Willmertinger, Germany, Muenchen P.S. A idea I have is to change the amanda.conf by a sed or ed- script for the amdump, and after amdump, change it again to allow writing to tape?
Half Price Cigarettes and Tobacco
Dear Sir or Madam In the past you have requested information on discounted products. We hope that you find this of interest. If you are not a smoker, and find this email offensive, we sincerely apologise! We will be only too happy to take you off our mailing list. If you are a smoker, however, and are fed up with paying high prices for your cigarettes and tobacco, take a look at what we have to offer by clicking on this link. http://www.smokersunited.co.uk/?S=23ID=2 We can send you, legally, by registered air mail, direct to your door, 4 cartons of cigarettes or 40 pouches of rolling tobacco (all brands are available) from only 170 Euros - about 105 pounds - fully inclusive of postage and packing. Why pay more? To remove yourself from our mailing list, please click below mailto:[EMAIL PROTECTED] Yours faithfully. Smokers United http://www.smokersunited.co.uk/?S=23ID=2 xay1y
Re: Tape technology
On Friday 06 September 2002 04:43, Brian Jonnes wrote: Hi all, Perhaps this is not quite the place for this question, but I hope it won't offend anyone ;) I will be looking to get a new tape drive, but am not very familiar with the current technology. I have heard of DDS, DAT and have used Travan. As far as I'm concerned, the Travan is out of the question, 'cause the tapes are so expensive (and apparently they are now obsolete?). So; what are the opinions of this list? (BEGIN FLAME...?) In most cases, the terms DDS and DAT mean essentially the same thing, as in a small cassette used in a helical track technology drive, a smaller version of your home vcr mechanism. Such DDS# numbers as you see indicate the density ability of the formulation, with DDS4 being the current top of the line, and holding (IIRC) 20gb uncompressed. Here at home, I use DDS2, which puts 4gb uncompressed on a 120 meter tape, in a changer mechanism that holds 4 tapes. This, backing up 50 some gigs, using software compression where it does some good, seems to be averaging about 60% useage per tape, so I have a little room for expansion yet. IMO, the driving force behind the DAT/DDS style is the relative price of the tapes. A 10 pack of 120 meter DDS2's, from some ebay dealer, will generaly cost you around 50 USD including the rediculous shipping some tag on. The service life of the tape is something I can't testify to yet, I put 20 tapes into a 7 day dumpcycle about a year ago, in a then brand new Seagate/Compaq 4586np drive and they are still in service with no failures. I've had to hand cycle the cleaning tape in the 4th slot into use maybe 4 times in this same time frame. IMO its a decent method for the home user just because its an affordable format, and with all the other formats either not having enough capacity, or costing 50+ USD per tape, its the only format on the radar screen. Would I attempt to do a commercial business with it? Today, a strong yes given a robot changer with enough slots, no for single tape only decks as they just wouldn't have the capacity. But for the small business with say 5-10 major machines to backup, a dedicated software raid server with a rack of big drives, running rsync, also has a cost and speed advantage. I know of one such setup with a capacity of 320 gigs in 4 160 gig drives that does its nightly thing in lots less time than tape could since its on a 100baseT and can r/w at 50+megs a second. Built inhouse, it cost about 1600 USD at the time. Is it as dependable as tape? Time will tell. Can you take it offsite? In a sense, yes, by cycling enough drives thru each slot in the array and letting the raid rebuild itself while that removed drive goes offsite to join 3 others on a regular rotation schedule. Its not being at this site (yet). -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.14% setiathome rank, not too shabby for a WV hillbilly
connection times out every night?
Hi again group, My amanda configuration is finally working pretty good. But I seem to be having trouble with a couple of hosts on my network. Two of my servers always time out when running 'amdump'. They check ok (amcheck -c) but will never transfer the dump. Both of the machines are compaq proliant computers using the buil-on network cards (tlan.o module). Most of my servers use dual intel Pro cards but I do have one other machine with the same nic and he always backups just fine. From what I can tell all the systems are setup the same and I even compiled the client from the newest source on both of the problem children. From what I've seen the logs have no usefull info. Has anyone seen any problems like this? I'm thinking it's the nic card but I'm not sure? first I get this error for both machines. jax.sebis. /usr lev 0 FAILED [mesg read: Connection timed out] then I get this for the rest of the filesystems. jax.sebis. /var lev 1 FAILED [could not connect to jax.sebis.com] Thanks to all, chrisj
Re: gnutar dies on RedHat 6.2
On Fri, Sep 06, 2002 at 10:55:35AM +0200, Per olof Ljungmark wrote: At 07:11 9/4/2002 -0400, Gene Heskett wrote: On Wednesday 04 September 2002 01:52, Per olof Ljungmark wrote: Hi all, Got a working amanda 2.4.3b2 installation running on a FreeBSD 4.6 server. AFAICS everything is OK except for one thing, backing up RedHat 6.2 systems with gnutar. The only trace of the failure I have is the following in /tmp/amanda/: sendsize: asking killpgrp to terminate sendsize: calculating for amname '/etc', dirname '/etc' sendsize: getting size via gnutar for /etc level 0 and then nothing. Dump is fine from same machine. Grateful for a hint, Per olof Upgrade your 6.2 boxes gnutar to at least 1.13-19? 1.13-25 is the latest, on alpha.gnu.org. Thanks everybody for your tips. However, I still get the error (or absence of error) above after upgrading to 1.13.25. Is there a way to increase the verbosity of the debug files to find out what is going on? Or can I use sendsize manually on the client? I'm stuck at the moment. If you look at the runtar debugging files you should see the exact command lines for tar executed by sendsize. Note, the tar commands used for size calculations have their output going to /dev/null. The nearly identical ones used to do the actual backups would be going to stdout, and thus the filename for output would be - (just a dash). I think they would have to be executed as root on the client. There are /tmp/amanda debug files on both the client and server. Have you checked through both for clues? Just for info, are you also running version 2.4.3b2 amanda on the client system? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: HP Colorado, ide-scsi
On Fri, Sep 06, 2002 at 11:01:45AM +0200, Brian Jonnes wrote:
Hi all,
I'm getting this in my kern.log's:
---
Sep 6 00:45:01 valhalla kernel: st: Version 20020205, bufsize 32768, wrt 30720, max
init. bufs 4, s/g segs 16
Sep 6 00:45:01 valhalla kernel: Attached scsi tape st0 at scsi0, channel 0, id 0,
lun 0
Sep 6 00:45:01 valhalla kernel: st0: Block limits 25976 - 6841632 bytes.
Sep 6 01:18:39 valhalla kernel: st0: Error with sense data: Info fld=0x10200,
Deferred st09:00: sense key Medium Error
Sep 6 01:18:39 valhalla kernel: Additional sense indicates Sequential positioning
error
Sep 6 01:30:01 valhalla kernel: st: Unloaded.
---
This was from an amdump, which failed after 64kb written.
A little bit later, running an amcheck:
---
Sep 6 09:54:45 valhalla kernel: st: Version 20020205, bufsize 32768, wrt 30720, max
init. bufs 4, s/g segs 16
Sep 6 09:54:45 valhalla kernel: Attached scsi tape st0 at scsi0, channel 0, id 0,
lun 0
Sep 6 09:54:45 valhalla kernel: st0: Block limits 11268 - 112641 bytes.
Sep 6 10:09:45 valhalla kernel: scsi : aborting command due to timeout : pid 72600,
scsi0, channel 0, id 0, lun 0 Read (6) 01 00 00 40 00
Sep 6 10:09:45 valhalla kernel: hdd: irq timeout: status=0xc0 { Busy }
Sep 6 10:09:45 valhalla kernel: hdd: ATAPI reset complete
Sep 6 10:09:45 valhalla kernel: hdd: irq timeout: status=0x80 { Busy }
Sep 6 10:09:46 valhalla kernel: hdd: ATAPI reset complete
Sep 6 10:09:46 valhalla kernel: hdd: irq timeout: status=0x80 { Busy }
Sep 6 10:09:46 valhalla kernel: st0: Error 2707 (sugg. bt 0x20, driver bt 0x7,
host bt 0x7).
Sep 6 10:20:01 valhalla kernel: st: Unloaded.
---
Pulled the tape out, plugged it back in, and now its dumping fine. Can anyone make
sense of this?
I don't use your systems but ISTR people mentioning using mt to set the block size to
32K.
BTW is there a way of getting amanda to put level 0's in degraded mode? I'd still
like full dumps when I have to manually run amdump.
level 0 and degraded mode? Aren't these non-sequitors? I thought degraded mode meant
falling back to incrementals because there was no place to put the level 0's. I.e.
the tape was not working and the holding disk did not have enough unreserved space
to hold the level 0's. So where would you like amanda to put your huge level 0's
if it can't put it to tape or to disk?
What's your holding disk space and reserve % situation?
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: gnutar dies on RedHat 6.2
Per, increase the time-out values in your amanda.conf. Tar takes much longer to get an estimate to the scheduler that dump. I had to set my etimeout to 7200 and dtimeout to 1. This may be too much for your filesystems but keep doubling it until it works. hope this helps, chrisj Per olof Ljungmark wrote: At 07:11 9/4/2002 -0400, Gene Heskett wrote: On Wednesday 04 September 2002 01:52, Per olof Ljungmark wrote: Hi all, Got a working amanda 2.4.3b2 installation running on a FreeBSD 4.6 server. AFAICS everything is OK except for one thing, backing up RedHat 6.2 systems with gnutar. The only trace of the failure I have is the following in /tmp/amanda/: sendsize: asking killpgrp to terminate sendsize: calculating for amname '/etc', dirname '/etc' sendsize: getting size via gnutar for /etc level 0 and then nothing. Dump is fine from same machine. Grateful for a hint, Per olof Upgrade your 6.2 boxes gnutar to at least 1.13-19? 1.13-25 is the latest, on alpha.gnu.org. Thanks everybody for your tips. However, I still get the error (or absence of error) above after upgrading to 1.13.25. Is there a way to increase the verbosity of the debug files to find out what is going on? Or can I use sendsize manually on the client? I'm stuck at the moment. Thanks, Per olof
Re: Amanda changes her mind after tape removed from rotation.
On Fri, Sep 06, 2002 at 08:22:53AM -0400, Doug Johnson wrote: These dumps were to tape DailySet106. The next tape Amanda expects to use is: DailySet108. So our procedure here is to remove DailySet106. You use amrmtape, correct? and add a new tape, say DailySet115. This happens without a problem but where we run into issues is now Amanda doesn't want DailySet108 anymore, she wants DailySet115. The only way to know she has changed her mind is to run a amcheck to see what she expects. Sounds like you just need to hand-edit tapelist until it looks the way you want. The last tape on the list is the one Amanda wants to use next. The top tape on the list is the one Amanda used last night. -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
Re: Amanda changes her mind after tape removed from rotation.
On Fri, Sep 06, 2002 at 08:22:53AM -0400, Doug Johnson wrote: dumpcycle 0 # the number of days in the normal dump cycle runspercycle 0 # the number of amdump runs in dumpcycle days Gee I would have expected runspercycle of 0 to cause problems. Live and learn. tapecycle 5 tapes # the number of tapes in rotation I think amanda is quite happy working with more tapes than you mention in tapecycle. Why not set tapecycle to 1. I think it will then go with any tape that matches the labeling spec. Even the one it just used the day before. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Debian amanda: changing backup operator?
I'm trying to get the Debian distribution of amanda to work with my compiled-from-scratch version on the tapehost. I know that the general advice of this group is to ignore the various distribution versions and compile from scratch, but I like the idea of keeping a host within it's package maintenance system, for the ease of updating. The Debian version was compiled with the backup operator at backup. I compiled the tapehost and many of my clients with amanda as the backup operator. With amanda in both the /home/amanda/.amandahosts lists on the tapehost and client, I get this message in the debug file: bsd security: remote host admin.jhuccp.org user amanda local user backup check failed: [access as backup not allowed from [EMAIL PROTECTED]] amandahostsauth failed I've also tried all the combinations of amanda and backup in both the tapehost and clients .amandahosts files. All return the same error. Is there an easy solution, short of recompiling amanda? I thought the purpose of putting the backup operator with the client's hostname in the tapehost's .amandahosts file was to deal with this exact situation. I'd normally check the archives for this, as I'm pretty sure this is a FAQ, but the www.amanda.org site seems to be down, and I'm anxious for a solution. Thanks for your time, help and patience. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Never mind: Debian amanda: changing backup operator?
Hope nobody put much time into this. Once I discovered that the backup user's home directory is /var/backups, and that /var/backups/.amandahosts is aliased to /etc/amandahosts, when I changed the entry in /etc/amandahosts to the proper tapehost hostname and the backup name that the tapehost was compiled with, everything seemed to work. Thanks for your patience. -Kevin I'm trying to get the Debian distribution of amanda to work with my compiled-from-scratch version on the tapehost. I know that the general advice of this group is to ignore the various distribution versions and compile from scratch, but I like the idea of keeping a host within it's package maintenance system, for the ease of updating. The Debian version was compiled with the backup operator at backup. I compiled the tapehost and many of my clients with amanda as the backup operator. With amanda in both the /home/amanda/.amandahosts lists on the tapehost and client, I get this message in the debug file: bsd security: remote host admin.jhuccp.org user amanda local user backup check failed: [access as backup not allowed from [EMAIL PROTECTED]] amandahostsauth failed I've also tried all the combinations of amanda and backup in both the tapehost and clients .amandahosts files. All return the same error. Is there an easy solution, short of recompiling amanda? I thought the purpose of putting the backup operator with the client's hostname in the tapehost's .amandahosts file was to deal with this exact situation. I'd normally check the archives for this, as I'm pretty sure this is a FAQ, but the www.amanda.org site seems to be down, and I'm anxious for a solution. Thanks for your time, help and patience. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Re: Tape technology
On Fri, 6 Sep 2002, Brian Jonnes wrote: I will be looking to get a new tape drive, but am not very familiar with the current technology. I have heard of DDS, DAT and have used Travan. As far as I'm concerned, the Travan is out of the question, 'cause the tapes are so expensive (and apparently they are now obsolete?). As Gene Heskett indicated elsewhere in the thread the appropriate tape technology depends on your budget and intended use. DAT/DDS is perfect for a home user. Far better than QIC/Travan ever was in terms of the price to performance ratio. However, I wouldn't currently sink any money into it as a new solution for commerical/business use. Sony has announced that DDS4 is the end of the road for DAT based backup technology. They're transitioning entirely to AIT. I've been using AIT for going on three years now and I've been extremely happy with it. It's more expensive than DAT formats, but it's getting cheaper. I've used AIT1 for the past three years and am currently transitioning to AIT3 technology. AIT1 is 35GB native capacity, AIT2 is 50GB and AIT3 is 100GB native capacity. With the release of AIT3 drives and tapes the prices on AIT1 are falling to where they can begin to compete with DDS4 -- which is limited to 20GB. Plus AIT drives can stream at or near the speed of a conventional hard disk in my experience. Amanda does an excellent job of keeping the drive busy via taper. DDS is a 4mm tape format and AIT is an 8mm tape format. Both of these are rather small form factor cartridges which make for easy storage. Both technologies achieve their capacity through helical scan technology and use double-reel cartridges. LTO is currently positioned to replace DLT in the high-end tape market. LTO stands for linear tape-open and the cartridges contain a single reel of tape which is wound onto a reel in the drive instead of remaining in the cartridge. Linear tape technologies like this achieve their density by cramming a whole buncha tape into a really big cartridge, leaving no room for a second reel. I get the willies at the thought of my tape being wound out of the cartridge and into the drive, but it seesm to work fairly reliably. It it's high-capacity format, Ultrium, LTO currently supports tapes of 100GB or 200GB native capacity. Personally at the prices they want for those suckers I'd just as soon buy a 100GB native capacity AIT3 drive with a fat stack of tapes. The AIT3 cartridges are small and easy to store and if you're planning to use amanda -- where you likely rewrite the tapes every couple of weeks -- it's hard to beat AIT's Advanced Metal Evaporate tape medium and the fact that you can actually afford to replace AIT tapes when, not if, you have one wear out. Also, Sony will release SAIT-1 towards the end of this year which is their own single-reel cartridge format -- though they're sticking with helical scan instead of linear tape technology. SAIT-1 will debut at 500GB native capacity in a cartridge whose size is equivalent to that of an LTO cartridge. They're roadmap takes them up to SAIT-4 at 4GB native capacity by 2010. Crazy man. Hope I've provided some food for thought, -- Brandon D. Valentine [EMAIL PROTECTED] Computer Geek, Center for Structural Biology This isn't rocket science -- but it _is_ computer science. - Terry Lambert on [EMAIL PROTECTED]
RE: tape rotation and no space left
On Thu, 5 Sep 2002, Bort, Paul wrote: Out of tape really means out of tape. Appends are really unlikely, as AMANDA starts the tape write with a rewind followed by a write. No seek, no foul, no append. (Unless you have the append patch.) Is it possible you have hardware compression turned on? This can cause problems if you also use software compression: the dumps tend to take more space. I'll have to check when I get back to work monday. DDS3 is supposed to be good for 12Gb. Is it possible you have some DDS2 tapes mixed in? (This can happen with inherited systems) No, their all DDS3. If it were my tape, I'd put a note on the hard copy of the report, and watch that tape next time it runs. If it gets the same error, I'd replace the media. A reformat/retension might work, but those tapes are cheap enough that it's not worth it. Will do. Thanks for the help, Keith
amverify and tapeless backups??
Hi all,I have a question. Can you run amverify on a tapeless backup in Amanda. I have no tape drives or tape changes and I am backing up my machines completely on my amanda server.When I run:amverify DailySet1I get:No tape changer...Not a character special device: file:/home/backupAny help would be greatly appreciatedAdnan
tapeless and amverify
Hi all, I have a question. Can you run amverify on a tapeless backup in Amanda. I have no tape drives or tape changes and I am backing up my machines completely on my amanda server. When I run: amverify DailySet1 I get: No tape changer... Not a character special device: file:/home/backup Any help would be greatly appreciated Adnan __ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com
amrestore - back to the windows client
Hi, Can amrestore , restore the files back on the windows share. I have read everything I can but it is still not clear. Thanks Azam
Re: gnutar dies on RedHat 6.2
Jon LaBadie wrote: On Fri, Sep 06, 2002 at 10:55:35AM +0200, Per olof Ljungmark wrote: At 07:11 9/4/2002 -0400, Gene Heskett wrote: On Wednesday 04 September 2002 01:52, Per olof Ljungmark wrote: Hi all, Got a working amanda 2.4.3b2 installation running on a FreeBSD 4.6 server. AFAICS everything is OK except for one thing, backing up RedHat 6.2 systems with gnutar. The only trace of the failure I have is the following in /tmp/amanda/: sendsize: asking killpgrp to terminate sendsize: calculating for amname '/etc', dirname '/etc' sendsize: getting size via gnutar for /etc level 0 and then nothing. Dump is fine from same machine. Grateful for a hint, Per olof Upgrade your 6.2 boxes gnutar to at least 1.13-19? 1.13-25 is the latest, on alpha.gnu.org. Thanks everybody for your tips. However, I still get the error (or absence of error) above after upgrading to 1.13.25. Is there a way to increase the verbosity of the debug files to find out what is going on? Or can I use sendsize manually on the client? I'm stuck at the moment. If you look at the runtar debugging files you should see the exact command lines for tar executed by sendsize. Note, the tar commands used for size calculations have their output going to /dev/null. The nearly identical ones used to do the actual backups would be going to stdout, and thus the filename for output would be - (just a dash). I think they would have to be executed as root on the client. There are /tmp/amanda debug files on both the client and server. Have you checked through both for clues? Just for info, are you also running version 2.4.3b2 amanda on the client system? Gentlemen, On the client there are no runtar debugging files, tar is never started AFAICS. On the server, it is just content that those disks are not available and goes on. For the timeout, this is small non-root partitions on RH 6.2 systems on a diet with very fast disk subsystems. We should be talking a second or two maximum? Hmmm..., version is 2.4.3b3 on the client... One thing that could possibly be the cause is the fact that I have tried to persuade the RH systems to have operator as the amanda user as we are mainly on BSD and left something out in doing this. Then the question would be the difference in permissions requirements between dump that works and tar that does not. Unfortunately I'll be travelling for a few days now so this matter have to rest for a few days... thank you for all your input. Per olof
Re: Tape technology
On Friday 06 September 2002 13:24, Brandon D. Valentine wrote: On Fri, 6 Sep 2002, Brandon D. Valentine wrote: They're roadmap takes them up to SAIT-4 at 4GB native capacity by 2010. s/They're/Their/ s/GB/TB/ =) You've been using vi too long, we can tell. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.14% setiathome rank, not too shabby for a WV hillbilly
simple query
OK...I'm still reading as much documentation as I can find before I really decide I'm ready to tackle Amanda...One thing that keeps cropping up is that if Amanda hits the end of tape during a dump, it jumps to the next tape and starts over. This brings up the situation where the dump itself is greater than an empty tape. Let's say it crops up (worse case) at the beginning of a run...wouldn't this seem to be antithetical to running a backup? If followed to it's logical conclusion, you could potentially run through your entire tapeset without backing anything up, even though the other backups following the runaway backup might happily fit on the tapes. Or am I missing something? I realize this may not be a critical problem (just readjust your disklists the next day) but does seem possible (not to mention a nuisance). =G=
RE: Newbie tape drive install
Title: RE: Newbie tape drive install Amanda is great! Been using it for about a week now on our production servers (e250's). I now want to put another tape drive onto an Ultra10 I have for off-site backups. It's all connected but I can't get solaris to detect the tape drive - obviously I'm doing something wrong. Even tried updating /kernel/drv/st.conf and booting with boot -vr but the e250's didn't need to. Maybe I need to add the tape alias? The major difference is the e250's connect, via wide scsi cables, to the controller on-board. I've grabbed a scsi controller and put it into a pci slot of this ultra10. However, the connector to the ultra10 is thin so perhaps I'm trying to fit a square into a circle? Anyways, I know this is not exactly an amanda question but a Solaris config issue and any help in pointing me in the right direction would be greatly appreciated. I can't find much info out there. uname -a: SunOS crafty 5.8 Generic 108528-13 sun4u sparc SUNW,Ultra-5_10 tape unit: Sony SDX-S300C (AIT Drive) Do you have evidence that the scsi controller is functional? Nope, never tried it before unfortunately Do you get boot messages about scsi? Is the tape drive, or anything at its scsi id number, mentioned in any of those messages? Does prtconf -v show anything related to the scsi devices and st...? No. Only the SD's show up. I don't us sparc's much, but I seem to recall something called probe_scsi (maybe with a dash or nothing instead of underscore). A probe-scsi-all seems to search through the controllers but shows nothing is attached. It may be part of the prom monitor rather than a command after boot. Is the drive terminated? All the scsi connections are usable with the others, but it may involve mating connectors or cables and special terminators. Nah there's no connectors. For example, the wide carries extra data lines. If you use a standard cable to a narrow device those extra lines will be dangling unconnected. So some cables have a terminator built in for those extra lines as it goes wide to narrow. Also, after a narrow device in the chain, the rest of the chain is narrow. H, good point. I don't really know a heck of a lot about scsi devices so I'm not really sure. The configuration is basically: (tape drive)(wide-scsi) (thin-scsi)(pci-slot)
