Re: NFS mounted holding disk
To: Anthony Worrall [EMAIL PROTECTED] cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: NFS mounted holding disk Date: Tue, 17 Apr 2001 10:51:17 -0400 From: Paul Lussier [EMAIL PROTECTED] X-Scanner: exiscan *14pWpZ-BM-00*1pxFlM.Ffuc* http://duncanthrax.net/exiscan/ In a message dated: Tue, 17 Apr 2001 10:42:13 BST Anthony Worrall said: One reason would be the NFS server has a 1Gb interface and the clients and tape server have only 100Mb. Okay, so now you're saturating the 100Mb interface on the tape server twice? I still don't see the advantage in this. That is why I would like the clients to dump directly to the holding disk without the data going via the tape server. Even so give the choice between dumping to an NFS mounted holding disk and dumping directly to tape the former seems to be faster. Of course having a big holding disk on the tape server would be even better. -- Seeya, Paul It may look like I'm just sitting here doing nothing, but I'm really actively waiting for all my problems to go away. If you're not having fun, you're not doing it right! Anthony Worrall The University of Reading, Department of Computer Science, Whiteknights, PO Box 225 Reading, Berkshire, UK RG6 6AY Tel: +44 (0)1189 318610 Fax: +44 (0)1189 751994 Email: [EMAIL PROTECTED]
Re: want only full dumps (strategy noinc)
John, Thanks for your further comments. Thanks. Yes I have upgraded to 2.4.2p2 (the advfs.patch is not applicable). The advfs.patch does more than just fix problems with advfs. It also deals with some Linux LABEL= issues in /etc/fstab. It may still not apply to your setup, but just in case. I am running Solaris-8. So the advfs patch really is not relevant. My reading of the amanda man page for runtapes is that it it only applicable when using a tape changer, which we are not. You can use chg-manual to emulate a changer with a human. Ahhh. Perhaps that's the way to go. I'll investigate. Also I will copy amdump to amdump0 and edit to stop at the planner output stage to speed up the testing cycle! Aside from not doing incrementals, what did you expect Amanda to do with the dumps that would not fit on your single tape? Defer them until the next run? Yes. I hope to do a run once a week each of which does a full backup of 20-25% of the filesystems. Is this feasible? I think you're going to have to split your configuration up by hand into groups of clients/disks that fit on a single tape. Or else use chg-manual. I really don't want to split my clients into groups like that. I see one of the great advantages of Amanda as letting it handle which filesystems to dump on which tapes. I am running 2.4.2p2 with strategy noinc but amstatus output appears to show incrementals :-(. You've backed Amanda into a corner by not giving it enough tape to do what you insist it does. It's doing the best it can :-). How do others archive a set of large filesystems onto a set of small tapes? I'd need to see the planner section of amdump.NN to dig more into why strategy noinc didn't do as expected. To avoid cloging the amanda mailing-list, I have put this on my website: http://www.dcs.shef.ac.uk/~julian/amdump.20010417 Thanks Julian -- Julian Briggs, System Administrator, Department of Computer Science, University of Sheffield, Regent Court, 211 Portobello St, Sheffield S1 4DP, UK Phone +44 (0) 114-222-1851. Fax +44 (0) 114-222-1810 [EMAIL PROTECTED] http://www.dcs.shef.ac.uk/~julian
amstatus
Hi, I've looked at the man pages, the Faq-o-matic, etc and find very little describibg the output of amstatus. Could someone give me some insight into the output? ...SUMMARY part real estimated size size partition : 49 estimated : 48 80846764k failed : 10 19359389k ( 23.95%) wait for dumping: 7 47852467k ( 59.19%) dumping to tape : 0 0k ( 0.00%) dumping : 3 1351520k 6809615k ( 19.85%) ( 1.67%) dumped : 29 1346528k 6825293k ( 19.73%) ( 1.67%) wait for writing: 00k0k ( 0.00%) ( 0.00%) writing to tape : 00k0k ( 0.00%) ( 0.00%) failed to tape : 00k0k ( 0.00%) ( 0.00%) taped : 29 1346528k 6825293k ( 19.73%) ( 1.67%) 5 dumpers idle : no-diskspace taper idle network free kps: 7310 holding space : 562880k ( 7.63%) dumper0 busy : 0:22:12 ( 67.78%) dumper1 busy : 0:03:16 ( 10.01%) dumper2 busy : 0:21:49 ( 66.57%) dumper3 busy : 0:32:46 (100.00%) dumper4 busy : 0:14:58 ( 45.72%) dumper5 busy : 0:11:14 ( 34.29%) dumper6 busy : 0:01:17 ( 3.96%) dumper7 busy : 0:01:21 ( 4.15%) taper busy : 0:04:53 ( 14.92%) 0 dumpers busy : 0:00:00 ( 0.00%) 1 dumper busy : 0:00:00 ( 0.00%) 2 dumpers busy : 0:01:24 ( 4.30%)no-diskspace: 0:01:24 (100.00%) 3 dumpers busy : 0:24:44 ( 75.50%)no-diskspace: 0:24:44 (100.00%) 4 dumpers busy : 0:03:56 ( 12.05%)no-diskspace: 0:03:56 (100.00%) 5 dumpers busy : 0:01:18 ( 3.99%)no-diskspace: 0:01:18 (100.00%) 6 dumpers busy : 0:00:27 ( 1.41%)no-diskspace: 0:00:27 (100.00%) 7 dumpers busy : 0:00:23 ( 1.22%)no-diskspace: 0:00:23 (100.00%) 8 dumpers busy : 0:00:30 ( 1.53%) no-dumpers: 0:00:16 ( 53.79%) not-idle: 0:00:13 ( 46.21%) TIA William Find the best deals on the web at AltaVista Shopping! http://www.shopping.altavista.com
Re: Getting estimates, request times out ... ?
On 18 Apr 2001, Alexandre Oliva wrote: On Apr 18, 2001, The Hermit Hacker [EMAIL PROTECTED] wrote: error result for host hub.org disk da1s1a: Request to hub.org timed out. [snip] error result for host hub.org disk da0s1a: Request to hub.org timed out. See how long it took in /tmp/amanda/sendsize.debug, and compare it with the definition of etimeout in amanda.conf 3hrs, and 46min??? egrep "start|finish" sendsize.42714.debug sendsize: debug 1 pid 42714 ruid 1009 euid 1009 start time Wed Apr 18 01:00:01 2001 sendsize: pid 42714 finish time Wed Apr 18 03:46:29 2001 First, thanks, I didn't know about those files :( In the file for last night was a bunch of: DUMP: Unknown intermediate format in /etc/dumpdates, line 1 I looked at /etc/dumpdates and the "error" was obvious in there ... how many times should it be doing the estimations? sendsize: running "/sbin/dump 0hsf 0 1048576 - /dev/rda0s1a" sendsize: running "/sbin/dump 0hsf 0 1048576 - /dev/rda0s1d" sendsize: running "/sbin/dump 0hsf 0 1048576 - /dev/rda0s1e" sendsize: running "/sbin/dump 0hsf 0 1048576 - /dev/rda0s1g" sendsize: running "/sbin/dump 0hsf 0 1048576 - /dev/rda0s1h" sendsize: running "/sbin/dump 0hsf 0 1048576 - /dev/rda1s1a" sendsize: running "/sbin/dump 0hsf 0 1048576 - /dev/rda2s1d" sendsize: running "/sbin/dump 0hsf 0 1048576 - /dev/rda3s1a" sendsize: running "/sbin/dump 0hsf 0 1048576 - /dev/rda3s1e" sendsize: running "/sbin/dump 0hsf 0 1048576 - /dev/rda4s1a" sendsize: running "/sbin/dump 0hsf 0 1048576 - /dev/rda4s1e" sendsize: running "/sbin/dump 1hsf 0 1048576 - /dev/rda0s1a" sendsize: running "/sbin/dump 1hsf 0 1048576 - /dev/rda0s1d" sendsize: running "/sbin/dump 1hsf 0 1048576 - /dev/rda0s1e" sendsize: running "/sbin/dump 1hsf 0 1048576 - /dev/rda0s1g" sendsize: running "/sbin/dump 1hsf 0 1048576 - /dev/rda0s1h" sendsize: running "/sbin/dump 1hsf 0 1048576 - /dev/rda1s1a" sendsize: running "/sbin/dump 1hsf 0 1048576 - /dev/rda3s1a" sendsize: running "/sbin/dump 1hsf 0 1048576 - /dev/rda4s1a" sendsize: running "/sbin/dump 1hsf 0 1048576 - /dev/rda4s1e" sendsize: running "/sbin/dump 2hsf 0 1048576 - /dev/rda0s1a" sendsize: running "/sbin/dump 2hsf 0 1048576 - /dev/rda0s1g" sendsize: running "/sbin/dump 2hsf 0 1048576 - /dev/rda1s1a" sendsize: running "/sbin/dump 2hsf 0 1048576 - /dev/rda4s1a" sendsize: running "/sbin/dump 3hsf 0 1048576 - /dev/rda2s1d" sendsize: running "/sbin/dump 3hsf 0 1048576 - /dev/rda3s1e" sendsize: running "/sbin/dump 4hsf 0 1048576 - /dev/rda2s1d" seems to do one per line in /etc/dumpdates?
About balance of full backups
Hi, Throughout the dump schedule we can see the distribution of full backups. I use : dumpcycle 5 days runspercycle 5 tapecycle 6 tapes But I get the "unbalanced" backups over 6 tapes. One tapes is full, and other tapes is just half full. How to balance the backups that enable the backups are written fairly equally to six tapes? Thanks, --weihai
RE: NFS mounted holding disk
Here's a bad idea for you: Install Amanda server on both the NFS server and the tape server; Run amdump on the NFS server using whatever configuration you'd like, but don't let it dump to tape; use the tape server to back up the NFS server at level 0 every time; after the tape server is done, tell the NFS server to amflush to /dev/null. It's not pretty, and restores are cumbersome, but it would accomplish the mission. Of course, so would moving the tape drive(s) to the NFS server. Is that a possibility? -Original Message- From: Anthony Worrall [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 18, 2001 5:17 AM To: [EMAIL PROTECTED] Subject: Re: NFS mounted holding disk To: Anthony Worrall [EMAIL PROTECTED] cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: NFS mounted holding disk Date: Tue, 17 Apr 2001 10:51:17 -0400 From: Paul Lussier [EMAIL PROTECTED] X-Scanner: exiscan *14pWpZ-BM-00*1pxFlM.Ffuc* http://duncanthrax.net/exiscan/ In a message dated: Tue, 17 Apr 2001 10:42:13 BST Anthony Worrall said: One reason would be the NFS server has a 1Gb interface and the clients and tape server have only 100Mb. Okay, so now you're saturating the 100Mb interface on the tape server twice? I still don't see the advantage in this. That is why I would like the clients to dump directly to the holding disk without the data going via the tape server. Even so give the choice between dumping to an NFS mounted holding disk and dumping directly to tape the former seems to be faster. Of course having a big holding disk on the tape server would be even better. -- Seeya, Paul It may look like I'm just sitting here doing nothing, but I'm really actively waiting for all my problems to go away. If you're not having fun, you're not doing it right! Anthony Worrall The University of Reading, Department of Computer Science, Whiteknights, PO Box 225 Reading, Berkshire, UK RG6 6AY Tel: +44 (0)1189 318610 Fax: +44 (0)1189 751994 Email: [EMAIL PROTECTED]
RE: NFS mounted holding disk
Hi Unfortunately the NFS server is a NAS device on which I can not run amanda :-(. Now if amanda could talk NDMP I could use the tape device on the NAS server, but I would still need another box to run amanda and the data would be going in and out of this box. Still that would be better than in, out and back again :-). I would think if I had the same config on the tape server as the holding-disk server up to the tape device, then I could just run amflush on the tape server. From: "Bort, Paul" [EMAIL PROTECTED] To: "'Anthony Worrall'" [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: RE: NFS mounted holding disk Date: Wed, 18 Apr 2001 10:32:03 -0400 X-Scanner: exiscan *14pt4u-0004vx-00*ccNglIAG/2M* http://duncanthrax.net/exiscan/ Here's a bad idea for you: Install Amanda server on both the NFS server and the tape server; Run amdump on the NFS server using whatever configuration you'd like, but don't let it dump to tape; use the tape server to back up the NFS server at level 0 every time; after the tape server is done, tell the NFS server to amflush to /dev/null. It's not pretty, and restores are cumbersome, but it would accomplish the mission. Of course, so would moving the tape drive(s) to the NFS server. Is that a possibility? -Original Message- From: Anthony Worrall [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 18, 2001 5:17 AM To: [EMAIL PROTECTED] Subject: Re: NFS mounted holding disk To: Anthony Worrall [EMAIL PROTECTED] cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: NFS mounted holding disk Date: Tue, 17 Apr 2001 10:51:17 -0400 From: Paul Lussier [EMAIL PROTECTED] X-Scanner: exiscan *14pWpZ-BM-00*1pxFlM.Ffuc* http://duncanthrax.net/exiscan/ In a message dated: Tue, 17 Apr 2001 10:42:13 BST Anthony Worrall said: One reason would be the NFS server has a 1Gb interface and the clients and tape server have only 100Mb. Okay, so now you're saturating the 100Mb interface on the tape server twice? I still don't see the advantage in this. That is why I would like the clients to dump directly to the holding disk without the data going via the tape server. Even so give the choice between dumping to an NFS mounted holding disk and dumping directly to tape the former seems to be faster. Of course having a big holding disk on the tape server would be even better. -- Seeya, Paul It may look like I'm just sitting here doing nothing, but I'm really actively waiting for all my problems to go away. If you're not having fun, you're not doing it right! Anthony Worrall The University of Reading, Department of Computer Science, Whiteknights, PO Box 225 Reading, Berkshire, UK RG6 6AY Tel: +44 (0)1189 318610 Fax: +44 (0)1189 751994 Email: [EMAIL PROTECTED] Anthony Worrall The University of Reading, Department of Computer Science, Whiteknights, PO Box 225 Reading, Berkshire, UK RG6 6AY Tel: +44 (0)1189 318610 Fax: +44 (0)1189 751994 Email: [EMAIL PROTECTED]
can find the disk
Hi, I am running Amanda-2.4.2p1 the server is Linux RH6.2 Client Sun E450, Solaris 2.7 I have setup amanda, and it is backing up the system disk (I am using tar, dump failed), but Amanda can not recognize the non system disks. ERROR: myserver.mydomain.com: [can not access /dev/dsk/c0t1d0s6 (/dev/dsk/c0t1d0s6): No such file or directory] ERROR: myserver.mydomain.com: [can not access /disc2 (/disc2): No such file or directory] ERROR: myserver.mydomain.com: [can not access /disc1 (/disc1): No such file or directory] any ideas? -- Tal Ovadia Jalan Network Services Inc. Phone: (818)-262-3895 --- Why Oh Why didn't I take the Blue Pill...
Changer don't run after installing a new hard drive
Hi All! Amanda, Version 2.4.2-19991216-beta1, runs a lot of time very well. Now i have installed a new SCSI Hard Drive, and than i want to start amanda. But amanda don't run. Amanda Tape Server Host Check - Holding disk /dumps/amanda: 2095692 KB disk space available, that's plenty amcheck-server: could not get changer info: error could not read result from "/usr/local/libexec/chg-scsi" (got signal 11) Amanda Backup Client Hosts Check Client check: 2 hosts checked in 0.042 seconds, 0 problems found (brought to you by Amanda 2.4.2-19991216-beta1) amanda@fileserver:/usr/bin Who can help me? Bye Juergen -- Dies ist eine Microsoft freie Mail!
Re: Changer don't run after installing a new hard drive
Juergen Knott wrote: Hi All! Amanda, Version 2.4.2-19991216-beta1, runs a lot of time very well. Now i have installed a new SCSI Hard Drive, and than i want to start amanda. But amanda don't run. Amanda Tape Server Host Check - Holding disk /dumps/amanda: 2095692 KB disk space available, that's plenty amcheck-server: could not get changer info: error could not read result from "/usr/local/libexec/chg-scsi" (got signal 11) Odds are excellent that you have set the SCSI ID of your new drive to the same as either the tape drive or the changer. Remember that the changer typically uses an ID different from the actual tape drive Amanda Backup Client Hosts Check Client check: 2 hosts checked in 0.042 seconds, 0 problems found (brought to you by Amanda 2.4.2-19991216-beta1) amanda@fileserver:/usr/bin Who can help me? Bye Juergen -- Dies ist eine Microsoft freie Mail! -- Marty Shannon, RHCE, Independent Computing Consultant mailto:[EMAIL PROTECTED]
amanda archive config
Hello, Just wanted to double check my configuration here. What I want to do aside from my production backups is to have a separate config for archival purposes. I've checked the list archives and have done the following: a)Made a separate config for archive b)edited amanda.conf //dumpcycle dumpcycle 1 days runspercycle 1 days tapecycle 1000 tapes //on all dumptypes record no c) created separate directories for log,index,info Any pointers/corrections are appreciated. Thanks, -Ben
Re: amstatus
I've looked at the man pages, the Faq-o-matic, etc and find very little descri bibg the output of amstatus. ... Does "etc" include "the chapter" at www.backupcentral.com/amanda.html? I tried to describe some of it in there. SUMMARY part real estimated size size partition : 49 There are 49 entries in your disklist. estimated : 48 80846764k Amanda got estimates for 48 of them and the total size is ~80 GBytes. failed : 10 19359389k ( 23.95%) 10 backups have failed and their estimated size was ~20 GBytes, which is ~24% of the total estimated size. wait for dumping: 7 47852467k ( 59.19%) 7 backups are still waiting to be dumped and their estimated size is ~47 GBYtes, which is ~60% of the total estimate. dumping to tape : 0 0k ( 0.00%) No dumps are currently being written directly to tape. dumping : 3 1351520k 6809615k ( 19.85%) ( 1.67%) 3 dumps are currently running. The actual size in the holding disk so far is 1.3 GBytes, which is ~20% of the estimated size of 6.8 GBytes and ~2% of the total estimated size. dumped : 29 1346528k 6825293k ( 19.73%) ( 1.67%) 29 dumps have been completed totalling 1.3 GBytes ... wait for writing: 00k0k ( 0.00%) ( 0.00%) No dumps are in the holding disk waiting to be written to tape. writing to tape : 00k0k ( 0.00%) ( 0.00%) No dumps are currently being written to tape from the holding disk. failed to tape : 00k0k ( 0.00%) ( 0.00%) No dumps that were being written to tape have failed. taped : 29 1346528k 6825293k ( 19.73%) ( 1.67%) 29 dumps have made it completely to tape. 5 dumpers idle : no-diskspace 5 of your dumpers are idle, and at least one reason they are not doing anything is there is no more holding disk space (other constraints may also apply, this is just the first one that stopped Amanda from assigning them more work). taper idle Taper (the process that writes things to tape) is not doing anything. network free kps: 7310 This line is mostly bogus. It says there is this much available bandwidth for Amanda to pick from, but I don't think it takes into account the multiple "interfaces" Amanda could use or which interface is used by which dump. holding space : 562880k ( 7.63%) You have 5.6 GBytes free in your holding disk, which is 7% of the total size. dumper0 busy : 0:22:12 ( 67.78%) Dumper number 0 has been busy doing things ~22 minutes, which is ~68% of the total run time so far. taper busy : 0:04:53 ( 14.92%) Taper has been busy doing things ~5 minutes, which is ~15% of the total run time so far. 0 dumpers busy : 0:00:00 ( 0.00%) You've never had no dumpers busy (i.e. all of them idle). 2 dumpers busy : 0:01:24 ( 4.30%)no-diskspace: 0:01:24 (100.00%) You've had 2 dumpers working about 1 minute of the total run time, and one reason you could not go to 3 dumpers was not enough holding disk space. 8 dumpers busy : 0:00:30 ( 1.53%) no-dumpers: 0:00:16 ( 53.79%) not-idle: 0:00:13 ( 46.21%) You've had 8 dumpers busy 30 seconds, and of that 30 seconds, the reason you could not go to 9 was no more dumpers configured 16 seconds and nothing to do (not-idle) 13 seconds. William John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amanda archive config
On Apr 18, 2001, "Ben Hyatt" [EMAIL PROTECTED] wrote:
I've checked the list archives and have done the following:
It looks ok to me.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: Getting estimates, request times out ... ?
3hrs, and 46min??? Right. Note that you did estimates of 11 separate disks, and the default etimeout is 5 minutes per disk, which is 55 minutes, hence the timeout errors. You need to crank that way up, or it might indicate there is a problem with that client (bad disk, etc) that needs to be investiaged. In the file for last night was a bunch of: DUMP: Unknown intermediate format in /etc/dumpdates, line 1 I looked at /etc/dumpdates and the "error" was obvious in there ... I'm not clear. Are you saying the error was obvious and you fixed it, or that the file contained a bunch of "sendsize: running" lines (which would be very bad)? how many times should it be doing the estimations? Planner will ask for a level 0 estimate of everything in your disklist, and then it will ask for the same level it ran last time and then it may also ask for the next level. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: About balance of full backups
Throughout the dump schedule we can see the distribution of full backups. I use : dumpcycle 5 days runspercycle 5 tapecycle 6 tapes But I get the "unbalanced" backups over 6 tapes. One tapes is full, and other tapes is just half full. How many times have you run through the cycle? Just a couple or "lots"? How to balance the backups that enable the backups are written fairly equally to six tapes? Can your setup be balanced? For instance, if you have one very large file system, it's going to have to get a full dump during the cycle at some point, and that may be causing your peak. What does "amadmin config balance" say? --weihai John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: can find the disk
I have setup amanda, and it is backing up the system disk (I am using tar, dump failed) ... What do you mean by "dump failed"? , but Amanda can not recognize the non system disks. ERROR: myserver.mydomain.com: [can not access /dev/dsk/c0t1d0s6 (/dev/dsk/c0t1d0s6): No such file or directory] ERROR: myserver.mydomain.com: [can not access /disc2 (/disc2): No such file or directory] What was Amanda trying to get to when it went after c0t1d0s6? In particular, what does the /etc/vfstab entry look like for that disk? Ditto for /disc2. Is there a "/disc2" on "myserver.mydomain.com"? Tal Ovadia John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: HP 12000E + Amanda...
I have an HP SureStore 12000E ... how about the tapetype? The default is HP-DAT, should this be modified? ... That depends. Does the 12000E have DAT tape drives? More specifically, what kind of tape drives does it have? Once you figure that out, go to the FAQ at www.amanda.org and look for the drive type (or something close enough). daniel. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Amanda backup
Hi everybody, I am backing up 3 systems using amanda. My /etc/dumpdates on 3 systems ( total 12 files)shows that al the files were backed up. But the amverify shows less file systems than what /etc/dumpdates indicate( only 4 files). I'd appreciate if anybody can tell what is happening. Thanks,
chg-manual poor man's changer problems
Dear Sirs. I already set up a HP SureStore 6x40i changer based tape device backing up our main server, now I tried to install on a secondary machine with a simple HP DAT drive a second piece of amanda, but without success. I followed the steps described in the really confusing manuals and other FAQ-based stuff. If I'm right, I have to setup the following in amanda.conf: (here are only the relevant entries) tpchanger "chg-manual" tapedev "/dev/nsa0" changerfile "/usr/local/perfector/amanda/services-backup/changer.conf" The entry "changerfile" should be set due the fact, that chg-manual driver script searches for several status-semaphores created with the name of the base changerfile. If I omit this, I receive an error. The targeted changerfile is either empty or I configure some parameters like slot /dev/nsa0 etc. But I receive allways the same result. After typing "amlabel -f CONFIG CONFIGLABEL slot [0-9] (I tried slot 0 to 9, but configured either slot 0 or 1, for testing purposes to see whether the result changes) I get the message that I'm to be to insert a cartridge into drive 0 or drive 1 (depends on what I configured or what slot I gave amlabel). I inserted already a cartridge, but I always get the same message after hitting RETURN. I checked /tmp/amanda/ amlabel.debug and there is a mt output I receive by 'mt status' - and this seems absolutely normal as it shows some informations about the used tape (DDS-2 and so on). Can anybody help? What to be aware of when configuring a chg-manual device? -- MfG O. Hartmann [EMAIL PROTECTED] IT-Administration des Institut fuer Physik der Atmosphaere (IPA) Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinensaal) Tel: +496131/3924144 FAX: +496131/3923532
Re: cant find the disk
"John R. Jackson" wrote: I have setup amanda, and it is backing up the system disk (I am using tar, dump failed) ... What do you mean by "dump failed"? amcheck give an error, so does amdump , but Amanda can not recognize the non system disks. ERROR: myserver.mydomain.com: [can not access /dev/dsk/c0t1d0s6 (/dev/dsk/c0t1d0s6): No such file or directory] ERROR: myserver.mydomain.com: [can not access /disc2 (/disc2): No such file or directory] What was Amanda trying to get to when it went after c0t1d0s6? In particular, what does the /etc/vfstab entry look like for that disk? /dev/dsk/c0t1d0s6 is /disc1 Ditto for /disc2. Is there a "/disc2" on "myserver.mydomain.com"? yes, but amanda still can find it. -- Tal Ovadia Jalan Network Services Inc. Phone: (818)-262-3895 --- Why Oh Why didn't I take the Blue Pill...
RE: chg-manual poor man's changer problems
The config stuff looks OK to me, I would suggest leaving off the slot part of the amlabel command. When I label tapes through chg-manual, I always just `amlabel Config2 NextTapeName`, and if it asks me to put a tape in a specific slot, I just re-insert the tape in the drive, wait for it to settle down (it's an EXB-8505, they take a while) and hit enter. Solid as a rock. The only other thing that comes to mind is to make sure that the amanda user has read and write permissions on the changerfile. Good Luck. -Original Message- From: Hartmann, O. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 18, 2001 4:03 PM To: [EMAIL PROTECTED] Subject: chg-manual "poor man's" changer problems Dear Sirs. I already set up a HP SureStore 6x40i changer based tape device backing up our main server, now I tried to install on a secondary machine with a simple HP DAT drive a second piece of amanda, but without success. I followed the steps described in the really confusing manuals and other FAQ-based stuff. If I'm right, I have to setup the following in amanda.conf: (here are only the relevant entries) tpchanger "chg-manual" tapedev "/dev/nsa0" changerfile "/usr/local/perfector/amanda/services-backup/changer.conf" The entry "changerfile" should be set due the fact, that chg-manual driver script searches for several status-semaphores created with the name of the base changerfile. If I omit this, I receive an error. The targeted changerfile is either empty or I configure some parameters like slot /dev/nsa0 etc. But I receive allways the same result. After typing "amlabel -f CONFIG CONFIGLABEL slot [0-9] (I tried slot 0 to 9, but configured either slot 0 or 1, for testing purposes to see whether the result changes) I get the message that I'm to be to insert a cartridge into drive 0 or drive 1 (depends on what I configured or what slot I gave amlabel). I inserted already a cartridge, but I always get the same message after hitting RETURN. I checked /tmp/amanda/ amlabel.debug and there is a mt output I receive by 'mt status' - and this seems absolutely normal as it shows some informations about the used tape (DDS-2 and so on). Can anybody help? What to be aware of when configuring a chg-manual device? -- MfG O. Hartmann [EMAIL PROTECTED] IT-Administration des Institut fuer Physik der Atmosphaere (IPA) Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinensaal) Tel: +496131/3924144 FAX: +496131/3923532
Re: sendsize prob
DUMP: (This should not happen)bread from /dev/rdsk/c2t4d0 [block -402651472]: count=-1216308224, got=-1. This message typically indicates an active file system, i.e. the data changed from underneath dump while it was running. You may have to change the timing of when that data is hitting the server, or when Amanda is run, or where the data is stored, or possibly switch to using GNU tar for that file system. Larry Shanabrook John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: cant find the disk
amcheck give an error, so does amdump I figured that. Sheesh! The question is, what was the error message, i.e. what **exactly** did it say? Without that information, nobody is going to be able to guess what was wrong. /dev/dsk/c0t1d0s6 is /disc1 OK, then what do you get for these commands: df -k /disc1 ls -ld /disc1 ls -lLd /disc1 ls -l /dev/dsk/c0t1d0s6 ls -lL /dev/dsk/c0t1d0s6 ls -l /dev/rdsk/c0t1d0s6 ls -lL /dev/rdsk/c0t1d0s6 grep /disc1 /etc/vfstab yes, but amanda still can find it. Then run these commands and post the results: df -k /disc2 ls -ld /disc2 ls -lLd /disc2 grep /disc2 /etc/vfstab Tal Ovadia John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: error with amlabel
Hi, I've been trying unsuccesfully to label a exabyte 160mXL tape on a EXB-8500 drive. I run amlable as amanda user. backup server is solaris 2.6 with Amanda 2.4.2. $ id uid=301(amanda) gid=301(backup) $ /usr/local/sbin/amlabel DailySet1 DailySet1-000 rewinding, reading label, not an amanda tape rewinding, writing label DailySet1-000 amlabel: writing endmark: I/O error $ mt -f /dev/rmt/0cbn status Exabyte EXB-8500 8mm Helical Scan tape drive: sense key(0x0)= No Additional Sense residual= 0 retries= 0 file no= 0 block no= 0 then if I run amcheck $ amcheck DailySet1 Amanda Tape Server Host Check - Holding disk /d03/amanda: 14674376 KB disk space available, that's plenty ERROR: /dev/rmt/0bn: reading label: I/O error (expecting a new tape) NOTE: skipping tape-writable test ... so it is expecting a new tape, but I can not label a tape as It give me strange I/o error, showning above I know the tape are good because it have been used before ( not used under amanda,but have been used to dump/tar files on it) and i tried more then a few tape , all same kind of error. what do I missed ? TIA, Thanks, jason
RE: chg-manual poor man's changer problems
On Wed, 18 Apr 2001, Bort, Paul wrote: Hello. Thanks for responding. Our systems are all based on FreeBSD 4.3-RC3, I forgot to mention that. well, the backup operator is 'operator' and this user has full read/write permissions to the tape device (/dev/nsa0, /dev/nrsa0). whenever I put any line into "changer.conf" as configured with "changerfile" in amanda.conf I receive errors about that line - so I omit all lines, I simple "touch" a changerfile 'changer.conf' to get the control files as expected from "chg-manual". When trying 'amcheck config' I get some infos about the holding disk and I was offered to insert a tape in slot 0 - and I should hit return. either I do immediately while the tape is already loaded into the HP DAT (4 GB DDS-2 drive) or I eject and reload it again, wait for the tape to be initialised and the hit return. Always with the same effect: I was offered to hit return again and load a tape into slot 0 - but nothing happened to the tape inserted into the tapedrive. When checking /tmp/amanda/changer.debug then I get a big file with this: Mode Density Blocksize bpi Compression Current: 0x24:DDS-2 variable 61000DCLZ -available modes- 0:0x24:DDS-2 variable 61000DCLZ 1:0x24:DDS-2 variable 61000DCLZ 2:0x24:DDS-2 variable 61000DCLZ 3:0x24:DDS-2 variable 61000DCLZ - Current Driver State: at rest. - File Number: 0 Record Number: 0Residual Count 0 - loaded - rewind /dev/nsa0 - status /dev/nsa0 Mode Density Blocksize bpi Compression Current: 0x24:DDS-2 variable 61000DCLZ -available modes- 0:0x24:DDS-2 variable 61000DCLZ 1:0x24:DDS-2 variable 61000DCLZ 2:0x24:DDS-2 variable 61000DCLZ 3:0x24:DDS-2 variable 61000DCLZ - Current Driver State: at rest. - File Number: 0 Record Number: 0Residual Count 0 - loaded - rewind /dev/nsa0 - status /dev/nsa0 Mode Density Blocksize bpi Compression Current: 0x24:DDS-2 variable 61000DCLZ -available modes- 0:0x24:DDS-2 variable 61000DCLZ 1:0x24:DDS-2 variable 61000DCLZ 2:0x24:DDS-2 variable 61000DCLZ 3:0x24:DDS-2 variable 61000DCLZ - Current Driver State: at rest. - File Number: 0 Record Number: 0Residual Count 0 - loaded -END- Well, it seems to be all right, tape is loaded, clear to be written on - but whats going on with the changer? It seems not to be willing to write anything :-( A normal tar, mt operations and so on work well with the tape and as user 'operator', so that is not a kind of a permission issue. :The config stuff looks OK to me, I would suggest leaving off the slot part :of the amlabel command. When I label tapes through chg-manual, I always just :`amlabel Config2 NextTapeName`, and if it asks me to put a tape in a :specific slot, I just re-insert the tape in the drive, wait for it to settle :down (it's an EXB-8505, they take a while) and hit enter. Solid as a rock. : :The only other thing that comes to mind is to make sure that the amanda user :has read and write permissions on the changerfile. : :Good Luck. : : :-Original Message- :From: Hartmann, O. [mailto:[EMAIL PROTECTED]] :Sent: Wednesday, April 18, 2001 4:03 PM :To: [EMAIL PROTECTED] :Subject: chg-manual "poor man's" changer problems : : :Dear Sirs. : :I already set up a HP SureStore 6x40i changer based tape device :backing up our main server, now I tried to install on a secondary :machine with a simple HP DAT drive a second piece of amanda, but :without success. : :I followed the steps described in the really confusing manuals and :other FAQ-based stuff. : :If I'm right, I have to setup the following in amanda.conf: : :(here are only the relevant entries) : :tpchanger "chg-manual" :tapedev "/dev/nsa0" :changerfile :"/usr/local/perfector/amanda/services-backup/changer.conf" : :The entry "changerfile" should be set due the fact, that chg-manual driver :script :searches for several status-semaphores created with the name of the base :changerfile. :If I omit this, I receive an error. The targeted changerfile is either empty :or :I configure some parameters like slot /dev/nsa0 etc. : :But I receive allways the same result. After typing "amlabel -f CONFIG :CONFIGLABEL slot [0-9] :(I tried slot 0 to 9, but configured either slot 0 or 1, for testing :purposes to see whether :the
Re: cant find the disk
"John R. Jackson" wrote: amcheck give an error, so does amdump I figured that. Sheesh! The question is, what was the error message, i.e. what **exactly** did it say? Without that information, nobody is going to be able to guess what was wrong. That was the exact error msg from amcheck: ERROR: myserver.mydomain.com: [can not access /dev/dsk/c0t1d0s6 (/dev/dsk/c0t1d0s6): No such file or directory] * I put /dev/dsk/c0t1d0s6 just to test if it will find the device since it failed on the name. It is the same as disc1 ERROR: myserver.mydomain.com: [can not access /disc2 (/disc2): No such file or directory] ERROR: myserver.mydomain.com: [can not access /disc1 (/disc1): No such file or directory] * disc1 2 are two additional disks, the strange thing is that I have no problem with the system disk. /dev/dsk/c0t1d0s6 is /disc1 OK, then what do you get for these commands: df -k /disc1 ls -ld /disc1 ls -lLd /disc1 ls -l /dev/dsk/c0t1d0s6 ls -lL /dev/dsk/c0t1d0s6 ls -l /dev/rdsk/c0t1d0s6 ls -lL /dev/rdsk/c0t1d0s6 grep /disc1 /etc/vfstab yes, but amanda still can find it. Then run these commands and post the results: df -k /disc2 bash-2.03# df -k /disk1 df: (/disk1) not a block device, directory or mounted resource ls -ld /disc2 bash-2.03# ls -ld /disc2 drwxr-xr-x 8 root root 512 Apr 4 16:46 /disc2 ls -lLd /disc2 bash-2.03# ls -lLd /disc2 drwxr-xr-x 8 root root 512 Apr 4 16:46 /disc2 grep /disc2 /etc/vfstab bash-2.03# grep /disc2 /etc/vfstab /dev/dsk/c0t2d0s6 /dev/dsk/c0t2d0s6 /disc2 ufs 1 yes - Tal Ovadia John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -- Tal Ovadia Jalan Network Services Inc. Phone: (818)-262-3895 --- Why Oh Why didn't I take the Blue Pill...
RE: chg-manual poor man's changer problems
Usually if AMANDA kicks out a tape during amcheck it is either because the tape isn't labeled or isn't the labeled tape she was expecting (for example, if you forgot to change the tape.) With no offense intended, have you already amlabel'ed the tape you are inserting during amcheck? Could you post everything that amcheck returns up (and including) the insert message? This might give a clue about why it is deciding to reject that tape and ask for another one. -Original Message- From: Hartmann, O. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 18, 2001 4:50 PM To: Bort, Paul Cc: [EMAIL PROTECTED] Subject: RE: chg-manual "poor man's" changer problems On Wed, 18 Apr 2001, Bort, Paul wrote: Hello. Thanks for responding. Our systems are all based on FreeBSD 4.3-RC3, I forgot to mention that. well, the backup operator is 'operator' and this user has full read/write permissions to the tape device (/dev/nsa0, /dev/nrsa0). whenever I put any line into "changer.conf" as configured with "changerfile" in amanda.conf I receive errors about that line - so I omit all lines, I simple "touch" a changerfile 'changer.conf' to get the control files as expected from "chg-manual". When trying 'amcheck config' I get some infos about the holding disk and I was offered to insert a tape in slot 0 - and I should hit return. either I do immediately while the tape is already loaded into the HP DAT (4 GB DDS-2 drive) or I eject and reload it again, wait for the tape to be initialised and the hit return. Always with the same effect: I was offered to hit return again and load a tape into slot 0 - but nothing happened to the tape inserted into the tapedrive. When checking /tmp/amanda/changer.debug then I get a big file with this: Mode Density Blocksize bpi Compression Current: 0x24:DDS-2 variable 61000DCLZ -available modes- 0:0x24:DDS-2 variable 61000DCLZ 1:0x24:DDS-2 variable 61000DCLZ 2:0x24:DDS-2 variable 61000DCLZ 3:0x24:DDS-2 variable 61000DCLZ - Current Driver State: at rest. - File Number: 0 Record Number: 0Residual Count 0 - loaded - rewind /dev/nsa0 - status /dev/nsa0 Mode Density Blocksize bpi Compression Current: 0x24:DDS-2 variable 61000DCLZ -available modes- 0:0x24:DDS-2 variable 61000DCLZ 1:0x24:DDS-2 variable 61000DCLZ 2:0x24:DDS-2 variable 61000DCLZ 3:0x24:DDS-2 variable 61000DCLZ - Current Driver State: at rest. - File Number: 0 Record Number: 0Residual Count 0 - loaded - rewind /dev/nsa0 - status /dev/nsa0 Mode Density Blocksize bpi Compression Current: 0x24:DDS-2 variable 61000DCLZ -available modes- 0:0x24:DDS-2 variable 61000DCLZ 1:0x24:DDS-2 variable 61000DCLZ 2:0x24:DDS-2 variable 61000DCLZ 3:0x24:DDS-2 variable 61000DCLZ - Current Driver State: at rest. - File Number: 0 Record Number: 0Residual Count 0 - loaded -END- Well, it seems to be all right, tape is loaded, clear to be written on - but whats going on with the changer? It seems not to be willing to write anything :-( A normal tar, mt operations and so on work well with the tape and as user 'operator', so that is not a kind of a permission issue. :The config stuff looks OK to me, I would suggest leaving off the slot part :of the amlabel command. When I label tapes through chg-manual, I always just :`amlabel Config2 NextTapeName`, and if it asks me to put a tape in a :specific slot, I just re-insert the tape in the drive, wait for it to settle :down (it's an EXB-8505, they take a while) and hit enter. Solid as a rock. : :The only other thing that comes to mind is to make sure that the amanda user :has read and write permissions on the changerfile. : :Good Luck. : : :-Original Message- :From: Hartmann, O. [mailto:[EMAIL PROTECTED]] :Sent: Wednesday, April 18, 2001 4:03 PM :To: [EMAIL PROTECTED] :Subject: chg-manual "poor man's" changer problems : : :Dear Sirs. : :I already set up a HP SureStore 6x40i changer based tape device :backing up our main server, now I tried to install on a secondary :machine with a simple HP DAT drive a second piece of amanda, but :without success. : :I followed the steps described in the really confusing manuals and :other FAQ-based stuff. : :If I'm right, I have to setup the following in amanda.conf: : :(here are only the
Re: Getting estimates, request times out ... ?
On Wed, 18 Apr 2001, John R. Jackson wrote:
3hrs, and 46min???
Right. Note that you did estimates of 11 separate disks, and the default
etimeout is 5 minutes per disk, which is 55 minutes, hence the timeout
errors. You need to crank that way up, or it might indicate there is
a problem with that client (bad disk, etc) that needs to be investiaged.
Okay, I cranked her up to 900 secs and last night's appeared to have gone
though ...
In the file for last night was a bunch of:
DUMP: Unknown intermediate format in /etc/dumpdates, line 1
I looked at /etc/dumpdates and the "error" was obvious in there ...
I'm not clear. Are you saying the error was obvious and you fixed it,
or that the file contained a bunch of "sendsize: running" lines (which
would be very bad)?
Sorry, it had a 'bad' line at the top of the file ... looked like a
control character and a time stamp ... removed that ...
how many times should it be doing the estimations?
Planner will ask for a level 0 estimate of everything in your
disklist, and then it will ask for the same level it ran last time and
then it may also ask for the next level.
Ah, okay ... sounds painful *but* understanding how amanda tries to
balance its backups, understandable ...
Thanks ...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
Greetings and questions
Hello all-
I'm new to list, having subscribed myself today because I'm having problems
with an Amanda backup system I'm administering for a co-worker while he's on
vacation. Here's the situation:
The system has been running fine for about a month. On monday, we added a
new machine to the disks list. Since then, the backups keep failing. I
believe I've traced the problem to an error I found in the amdump files:
dumper: error [bad command after NO-ROOM: 5]
dumper: error [bad command after NO-ROOM: 5]
Unfortunately, the result of this is that Amanda dies with the holding disk
full. To further complicate matters, the holding disk specified is a
subdirectory on the /var partition which means (you guessed it) neither
Amanda nor indeed anything that needs to write to /var in order to function
can do so. Subsequently, not only does Amanda die, it dies in such a way
that it can't let anyone know.
Now, the strange parts. The amount of space alloted to the holding disk is
supposed to be 1290M, as dictated (I believe) by these lines in the
amanda.conf.main file:
holdingdisk hd1 {
comment "main holding disk"
directory "/var/tmp"# where the holding disk is
use 1290 Mb # how much space can we use on it
# a negative value mean:
#use all space except that value
chunksize -1# size of chunk if you want big dump to be
# dumped on multiple files on holding disks
# N Kb/Mb/Gb split disks in chunks of size N
# 0 split disks in INT_MAX/1024 Kb chunks
# -1 same as -INT_MAX/1024 (see below)
# -N Kb/Mb/Gb dont split, dump larger
# filesystems directly to tape
# (example: -2 Gb)
# chunksize 2 Gb
}
However, I've seen Amanda use more than 1290Mb. In fact, it uses as much as
it can, which goes well over 1500Mb until it simply runs out of space (the
partition is only 1700Mb total, and usually has ~1500Mb available when
Amanda runs)
I've since commented out the disks that were added on Monday, and am running
a backup now; we'll see if it suceeds. My questions are:
1) Why is amanda ignoring the 1290Mb allocation?
2) Why is it dying with the NO-ROOM bad command error? (NOTE: I believe this
may be fixed with a patch of the server...is that true?)
3) Why is it dying at all? Out of space on the disk? I don't think the
tapes are filling up...
I'm thinking of using a -250M for the "use" directive in the conf file,
hoping maybe then it would pay attention. Also thinking of setting the
comprate to 100%; perhaps Amanda underestimated the new disks, and that's
why it failed? I'm going to attempt these things after the current forced
dump finishes. However IMHO they're work-arounds, not really solutions.
Let me know any opinions you've got. Below, you can find other snippets of
log config files I thought might be helpful. I apologize if this is too
basic a question; I am not the regular administrator of this system, and
have had to learn amanda "on-the-fly" today.
Thanks in advance,
Brian
RELEVANT LOGS:
--
***
***Summary of the amdump log that was noted with the NO-ROOM error above***
***
SUMMARY part real estimated
size size
partition : 86
estimated : 86 14614544k
failed : 3 98230k
wait for dumping: 12 11734148k
dumping to tape : 0 0k
dumping : 30k 1552826k
dumped : 68 1232320k 1229340k
wait for writing: 00k0k
writing to tape : 00k0k
failed to tape : 00k0k
taped : 68 1232320k 1229340k
1 dumpers idle : file-too-large
taper writing, tapeq: 0
network free kps: 13509
holding space : 43918
***
***Tail end of the log amdump file above
***
***
driver: state time 2572.384 free kps: 13509 space: 95590 taper: writing
idle-dumpers: 1 qlen tapeq: 0 runq: 12 stoppedq: 0 wakeup: 86400
driver-idle: file-too-large
driver: interface-state time 2572.384 if : free 8509 if ETH0: free 1 if
LOCAL: free 1
driver: hdisk-state time 2572.384 hdisk 0: free 43918 dumpers 1 hdisk 1:
free 51672 dumpers 2
driver: result time 2585.151 from dumper0: NO-ROOM 01-00139
driver: state time 2585.152 free kps: 13509 space: 95590 taper: writing
idle-dumpers: 1 qlen tapeq: 0 runq: 12 stoppedq: 1 wakeup: 86400
driver-idle: file-too-large
driver: interface-state time 2585.152 if
Re: Greetings and questions
Hello Brian, You are using an old version, tell your co-worker to upgrade :-) In this old release, amanda will use all space on the holding disk if the dump size is larger than the estimate. You can temporarily create a dumptype for this disk with "holdingdisk no". Jean-Louis On Wed, Apr 18, 2001 at 05:45:23PM -0700, Brian Sweeney wrote: Hello all- I'm new to list, having subscribed myself today because I'm having problems with an Amanda backup system I'm administering for a co-worker while he's on vacation. Here's the situation: The system has been running fine for about a month. On monday, we added a new machine to the disks list. Since then, the backups keep failing. I believe I've traced the problem to an error I found in the amdump files: -- 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: Greetings and questions
I'll tell him to upgrade when he gets back; I'm sure he'll be thrilled (it worked FINE when I left...) ;-) In the meanwhile, do you think setting the comprate to something like 95% would help it estimate better, thus solving this problem? Or is there another way to get it to make more accurate estimates? I ask because though I could set the holdingdisk no, that would be for the whole dump in amanda, which is actually responsible for dumping a whole slew of machines and I don't want them all to operate with holdingdisk turned off. Thanks again, Brian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jean-Louis Martineau Sent: Wednesday, April 18, 2001 6:59 PM To: Brian Sweeney Cc: [EMAIL PROTECTED] Subject: Re: Greetings and questions Hello Brian, You are using an old version, tell your co-worker to upgrade :-) In this old release, amanda will use all space on the holding disk if the dump size is larger than the estimate. You can temporarily create a dumptype for this disk with "holdingdisk no". Jean-Louis On Wed, Apr 18, 2001 at 05:45:23PM -0700, Brian Sweeney wrote: Hello all- I'm new to list, having subscribed myself today because I'm having problems with an Amanda backup system I'm administering for a co-worker while he's on vacation. Here's the situation: The system has been running fine for about a month. On monday, we added a new machine to the disks list. Since then, the backups keep failing. I believe I've traced the problem to an error I found in the amdump files: -- 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: Changer don't run after installing a new hard drive
Am Mittwoch, 18. April 2001 19:10 schrieben Sie: Holding disk /dumps/amanda: 2095692 KB disk space available, that's plenty amcheck-server: could not get changer info: error could not read result from "/usr/local/libexec/chg-scsi" (got signal 11) Odds are excellent that you have set the SCSI ID of your new drive to the same as either the tape drive or the changer. Remember that the changer typically uses an ID different from the actual tape drive Another user found the error. The changer device ist /dev/sg6 and the new hard drive have an ID bevor the changer. Also the SG-Device is changed to /dev/sg7 (+1) Bye Juergen -- Dies ist eine Microsoft freie Mail!
