question about new disks
I recently broke a disk up into subfolders to (hopefully) allow amanda
to do a better job fitting things onto daily single-tape backups. But I
keep getting the following errors.
HOSTNAME /files6/vol/speech7lev 0 FAILED [disk /files6/vol/speech7, all
estimate failed]
HOSTNAME /files6/vol/spdata2lev 0 FAILED [disk /files6/vol/spdata2, all
estimate failed]
HOSTNAME /files6/vol/spdata1lev 0 FAILED [disk /files6/vol/spdata1, all
estimate failed]
HOSTNAME /files6/vol/bvdlev 0 FAILED [disk /files6/vol/bvd, all
estimate failed]
HOSTNAME /files6/vol/Voiceware lev 0 FAILED [disk /files6/vol/Voiceware, all
estimate failed]
HOSTNAME /files6/vol/Synth lev 0 FAILED [disk /files6/vol/Synth, all
estimate failed]
Is there something else I had to do besides change the disklist file.
BTW, the dumptype is
define dumptype asel-gnutar {
comment ASEL backups using gnutar
options compress-fast
program GNUTAR
tape_splitsize 5 Gb
exclude list /etc/backup-excludes.txt
index yes
}
Thanks,
Steve
Also (unrelated), I have sent a few emails to the list that never seem
to make it out. Is this a known issue?
Re: question about new disks
On 2006-10-20 15:05, Steven Settlemyre wrote: I recently broke a disk up into subfolders to (hopefully) allow amanda to do a better job fitting things onto daily single-tape backups. But I keep getting the following errors. HOSTNAME /files6/vol/speech7lev 0 FAILED [disk /files6/vol/speech7, all estimate failed] [...] Any useful error message in one of the debug files: have a look in: amdump.1 (in directory ~amanda/TheConfig) planner.datetime.debug (only 2.5.1+; in /tmp/amanda probably) What version of Amanda do have have on client/server. And version of gnutar on client? -- Paul Bijnens, xplanation Technology ServicesTel +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, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: question about new disks
On Fri, Oct 20, 2006 at 09:05:50AM -0400, Steven Settlemyre wrote: Also (unrelated), I have sent a few emails to the list that never seem to make it out. Is this a known issue? Failure to make it out would suggest problems at your end or failure to connect to the receiving end. I'm guessing you mean they went out but did not get received back as a posting to the list. I have received 11 postings of yours in the last 10 days. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: question about new disks
Server: Debian (sarge) Linux. amanda version: 2.5.0p2 Client: tar: (GNU tar) 1.13.19 amanda-client: ? how do i find this? Paul Bijnens wrote: On 2006-10-20 15:05, Steven Settlemyre wrote: I recently broke a disk up into subfolders to (hopefully) allow amanda to do a better job fitting things onto daily single-tape backups. But I keep getting the following errors. HOSTNAME /files6/vol/speech7lev 0 FAILED [disk /files6/vol/speech7, all estimate failed] [...] Any useful error message in one of the debug files: have a look in: amdump.1 (in directory ~amanda/TheConfig) planner.datetime.debug (only 2.5.1+; in /tmp/amanda probably) What version of Amanda do have have on client/server. And version of gnutar on client?
Re: question about new disks
On Friday 20 October 2006 10:15, Steven Settlemyre wrote: Server: Debian (sarge) Linux. amanda version: 2.5.0p2 Client: tar: (GNU tar) 1.13.19 amanda-client: ? how do i find this? Any machine being backed up is a client. This includes the server itself. Building the client version is as simple as the whole thing, I use this script to build the install for the server: == #!/bin/sh # since I'm always forgetting to su amanda... if [ `whoami` != 'amanda' ]; then echo echo Warning echo Amanda needs to be configured and built by the user amanda, echo but must be installed by user root. echo exit 1 fi make clean rm -f config.status config.cache ./configure --with-user=amanda \ --with-group=disk \ --with-owner=amanda \ --with-gnu-ld \ --prefix=/usr/local \ --with-tapedev=FILE:/amandatapes \ --with-debugging=/tmp/amanda-dbg/ \ --with-tape-server=coyote.coyote.den \ --with-bsdtcp-security --with-amandahosts \ --with-configdir=/usr/local/etc/amanda \ --with-config=Daily \ --with-gnutar=/usr/local/bin/tar make == Adjust to suit of course... And this one to build just the client pieces: == #!/bin/sh # since I'm always forgetting to su amanda... if [ `whoami` != 'amanda' ]; then echo echo Warning echo Amanda needs to be configured and built by the user amanda, echo but must be installed by user root. echo exit 1 fi make clean rm -f config.status config.cache ./configure --with-user=amanda \ --with-group=disk \ --with-owner=amanda \ --without-server \ --with-gnu-ld --prefix=/usr/local \ --with-debugging=/tmp/amanda-dbg/ \ --with-tape-server=coyote.coyote.den \ --with-bsdtcp-security --with-amandahosts make == I haven't adjusted either of those scripts since I changed to using the FILE: device. Consistency is the keyword, so amanda versions in use often get updated 2-4 times a month, but forward compatibility is maintained. Paul Bijnens wrote: On 2006-10-20 15:05, Steven Settlemyre wrote: I recently broke a disk up into subfolders to (hopefully) allow amanda to do a better job fitting things onto daily single-tape backups. But I keep getting the following errors. HOSTNAME /files6/vol/speech7lev 0 FAILED [disk /files6/vol/speech7, all estimate failed] [...] Any useful error message in one of the debug files: have a look in: amdump.1 (in directory ~amanda/TheConfig) planner.datetime.debug (only 2.5.1+; in /tmp/amanda probably) What version of Amanda do have have on client/server. And version of gnutar on client? -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: question about new disks
On Fri, Oct 20, 2006 at 10:15:04AM -0400, Steven Settlemyre wrote: Server: Debian (sarge) Linux. amanda version: 2.5.0p2 Client: tar: (GNU tar) 1.13.19 amanda-client: ? how do i find this? On any amanda installation, amadmin - version For amanda developers, an RFE, amadmin syntax is: amadmin config cmd cmd_args So for the version cmd you have to supply a config argument. Thus my - in the above command line. It would make sense (to me) to allow the version cmd as an exception to the general syntax and allow amadmin version (i.e. with or without a config named). Config doesn't make much sense for the version cmd. Nor on clients prior to recent releases. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: question about new disks
someone hinted to me that since my client is a solaris machine, the GNUTAR program specified in my dumptype might not be correct. I know on my Linux machines, gnutar is /bin/tar, but my solaris machine is at /usr/local/bin/tar. could this be the problem? also, how would I get my dumptype to use this path? Thanks Jon LaBadie wrote: On Fri, Oct 20, 2006 at 10:15:04AM -0400, Steven Settlemyre wrote: Server: Debian (sarge) Linux. amanda version: 2.5.0p2 Client: tar: (GNU tar) 1.13.19 amanda-client: ? how do i find this? On any amanda installation, amadmin - version For amanda developers, an RFE, amadmin syntax is: amadmin config cmd cmd_args So for the version cmd you have to supply a config argument. Thus my - in the above command line. It would make sense (to me) to allow the version cmd as an exception to the general syntax and allow amadmin version (i.e. with or without a config named). Config doesn't make much sense for the version cmd. Nor on clients prior to recent releases.
Re: question about new disks
On Friday 20 October 2006 11:25, Gene Heskett wrote: On Friday 20 October 2006 10:15, Steven Settlemyre wrote: Server: Debian (sarge) Linux. amanda version: 2.5.0p2 Client: tar: (GNU tar) 1.13.19 amanda-client: ? how do i find this? Any machine being backed up is a client. This includes the server itself. Building the client version is as simple as the whole thing, I use this script to build the install for the server: == #!/bin/sh # since I'm always forgetting to su amanda... if [ `whoami` != 'amanda' ]; then echo echo Warning echo Amanda needs to be configured and built by the user amanda, echo but must be installed by user root. echo exit 1 fi make clean rm -f config.status config.cache ./configure --with-user=amanda \ --with-group=disk \ --with-owner=amanda \ --with-gnu-ld \ --prefix=/usr/local \ --with-tapedev=FILE:/amandatapes \ --with-debugging=/tmp/amanda-dbg/ \ --with-tape-server=coyote.coyote.den \ --with-bsdtcp-security --with-amandahosts \ --with-configdir=/usr/local/etc/amanda \ --with-config=Daily \ --with-gnutar=/usr/local/bin/tar make == Adjust to suit of course... And this one to build just the client pieces: == #!/bin/sh # since I'm always forgetting to su amanda... if [ `whoami` != 'amanda' ]; then echo echo Warning echo Amanda needs to be configured and built by the user amanda, echo but must be installed by user root. echo exit 1 fi make clean rm -f config.status config.cache ./configure --with-user=amanda \ --with-group=disk \ --with-owner=amanda \ --without-server \ --with-gnu-ld --prefix=/usr/local \ --with-debugging=/tmp/amanda-dbg/ \ --with-tape-server=coyote.coyote.den \ --with-bsdtcp-security --with-amandahosts make == I haven't adjusted either of those scripts since I changed to using the FILE: device. Consistency is the keyword, so amanda versions in use often get updated 2-4 times a month, but forward compatibility is maintained. And I fibbed, I did add the bsdsecurity stuff recently, but it was so easy I'd forgotten about it. Paul Bijnens wrote: On 2006-10-20 15:05, Steven Settlemyre wrote: I recently broke a disk up into subfolders to (hopefully) allow amanda to do a better job fitting things onto daily single-tape backups. But I keep getting the following errors. HOSTNAME /files6/vol/speech7lev 0 FAILED [disk /files6/vol/speech7, all estimate failed] [...] Any useful error message in one of the debug files: have a look in: amdump.1 (in directory ~amanda/TheConfig) planner.datetime.debug (only 2.5.1+; in /tmp/amanda probably) What version of Amanda do have have on client/server. And version of gnutar on client? -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: question about new disks
actually, i couldnt find amadmin anywhere on my client. I did just come across the fact that /bin/tar is where GNUTAR is looking. I now see it by using your command (on the amanda server), but i found it by doing strings /usr/lib/amanda/runtar. I guess the easiest way for me to fix this problem is to make a symlink from the /usr/local/bin/tar to /bin/tar (of course I'll backup the existing tar first). With a little foresight, the best way to handle this is to configure amanda for gnutar somewhere in the amanda dir and create a symlink on each client machine? Thanks again. Steve Jon LaBadie wrote: On Fri, Oct 20, 2006 at 12:07:03PM -0400, Steven Settlemyre wrote: someone hinted to me that since my client is a solaris machine, the GNUTAR program specified in my dumptype might not be correct. I know on my Linux machines, gnutar is /bin/tar, but my solaris machine is at /usr/local/bin/tar. could this be the problem? also, how would I get my dumptype to use this path? Thanks Jon LaBadie wrote: On Fri, Oct 20, 2006 at 10:15:04AM -0400, Steven Settlemyre wrote: Server: Debian (sarge) Linux. amanda version: 2.5.0p2 Client: tar: (GNU tar) 1.13.19 amanda-client: ? how do i find this? On any amanda installation, amadmin - version You thanked me but probably did not run my suggestion. Lots of other things print out with the version cmd including the path to gnutar that will be used. It is hardcoded at compile time, not a runtime setting. For that reason I always run configure with the option to specify where gnutar lives and say it lives in /usr/local/libexec/amgtar. Then I make amgtar be a copy or a link of whichever tar I wish to use.
