Re: amrecover fails - problems loading correct tape
Oscar Ricardo Silva wrote: [amanda@amanda tmp]$ cat ./amanda/server/newbktest/amidxtaped.20110427135604.debug 1303930564.513325: amidxtaped: pid 933 ruid 511 euid 511 version 2.6.1p2: start at Wed Apr 27 13:56:04 2011 1303930564.513380: amidxtaped: amidxtaped: version 2.6.1p2 You are running the 2.6.1p2, fix the xinetd configuration to run 3.2.2. Jean-Louis Anybody else run into this? I couldn't find any related items in the list archives.
Re: amrecover fails - problems loading correct tape
On Wednesday, April 27, 2011 05:00:34 PM Oscar Ricardo Silva did opine:
I've been using amanda for awhile but because of some index not found
issues decided to try 3.2.2 (currently using 2.6.1p2). Right now
backups on the new version work fine. The backup runs, files are
created on the virtual tapes (writing backups to disk), mail is sent,
etc. The problem comes when I try to recover a file and it appears to
be an issue with the tape changer.
On the client I see:
Continue [?/Y/n/s/d]? Y
Got no header and data from server, check in amidxtaped.*.debug and
amandad.*.debug files on server
When I check the debug files on the server, I get:
[amanda@amanda tmp]$ cat
./amanda/server/newbktest/amidxtaped.20110427135604.debug
1303930564.513325: amidxtaped: pid 933 ruid 511 euid 511 version
2.6.1p2: start at Wed Apr 27 13:56:04 2011
1303930564.513380: amidxtaped: amidxtaped: version 2.6.1p2
1303930564.514121: amidxtaped: FEATURES=9ffe7f
1303930564.555152: amidxtaped: CONFIG=newbktest
1303930564.555165: amidxtaped: LABEL=newbktape-10:2
1303930564.555174: amidxtaped: append_to_tapelist(tapelist=(nil),
label='newbktape-10', file=-1, partnum=-1, isafile=0)
1303930564.555185: amidxtaped: append_to_tapelist(tapelist=0xc855a80,
label='newbktape-10', file=2, partnum=-1, isafile=0)
1303930564.555198: amidxtaped: FSF=2
1303930564.555208: amidxtaped: HEADER
1303930564.555217: amidxtaped: DEVICE=chg-disk:/amandatapes/newbktapes
1303930564.555225: amidxtaped: HOST=^networking.its.utexas.edu$
1303930564.555237: amidxtaped: DISK=^/boot$
1303930564.555245: amidxtaped: DATESTAMP=20110427132216
1303930564.555252: amidxtaped: END
1303930564.555971: amidxtaped: pid 933 ruid 511 euid 511 version
2.6.1p2: rename at Wed Apr 27 13:56:04 2011
1303930564.556098: amidxtaped: Restoring from changer, checking labels
1303930564.556108: amidxtaped: Locking devices
1303930564.556215: amidxtaped: Sending output to file descriptor 52
1303930564.558009: amidxtaped: changer: -info
1303930564.660259: amidxtaped: changer: EXITSTATUS 0
1303930564.660277: amidxtaped: changer: current 25 0 1
1303930564.660314: amidxtaped: changer: -slot current
1303930564.661268: amidxtaped: changer: EXITSTATUS 1
1303930564.661279: amidxtaped: changer: error Slot current not
found 1303930564.661286: amidxtaped: changer: ERROR error Slot
current not found 1303930564.661303: amidxtaped: changer: -info
1303930564.661602: amidxtaped: changer: EXITSTATUS 0
1303930564.661611: amidxtaped: changer: current 25 0 1
1303930564.661619: amidxtaped: changer_query: changer return was 25 0 1
1303930564.661628: amidxtaped: changer_query: searchable = 1
1303930564.661635: amidxtaped: changer_find: looking for newbktape-10
changer is searchable = 1
1303930564.661642: amidxtaped: changer_search: newbktape-10
1303930564.661651: amidxtaped: changer: -search newbktape-10
1303930564.663498: amidxtaped: changer: EXITSTATUS 0
1303930564.663510: amidxtaped: changer: 10
1303930564.663523: amidxtaped: changer: -slot current
1303930564.664820: amidxtaped: changer: EXITSTATUS 1
1303930564.664831: amidxtaped: changer: error Slot current not
found 1303930564.664838: amidxtaped: changer: ERROR error Slot
current not found 1303930564.664856: amidxtaped: critical (fatal):
loadlabel_slot: assertion `rc 1 || device_name != NULL' failed
amidxtaped: loadlabel_slot: assertion `rc 1 || device_name != NULL'
failed /usr/local/amanda/lib/libamanda-2.6.1p2.so[0x2b935a2b84e2]
/lib64/libglib-2.0.so.0(g_logv+0x26f)[0x32df634d5f]
/lib64/libglib-2.0.so.0(g_log+0x83)[0x32df634f33]
/usr/local/amanda/lib/librestore-2.6.1p2.so(loadlabel_slot+0x3f5)[0x2b93
59c54b25]
/usr/local/amanda/lib/libamserver-2.6.1p2.so(changer_find+0x1b8)[0x2b93
59e61f58]
/usr/local/amanda/lib/librestore-2.6.1p2.so(search_tapes+0x413)[0x2b935
9c570f3] /usr/local/amanda/libexec/amidxtaped(main+0xbd3)[0x403213]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x32db61d994]
/usr/local/amanda/libexec/amidxtaped[0x4020a9]
In amanda.conf I define this:
tapedev chg-disk:/amandatapes/newbktapes
tapetype vtape
define tapetype vtape {
length 500 mbytes
}
500 megs How many of these virtual tapes do you allow it to use per
run? That is runtapes in the amanda.conf.
I am a home usr, using a commodity 1 terrabyte drive for the vtapes, and my
tapetype is set for about 30Gb. I am backing up this machine, and pieces
of the one out in the shop that runs my cnc milling machine, on a 5 day
cycle, so each days runs vary from 12Gb to 25Gb. 500 megs I outgrew by
1998. ;-)
--
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)
http://tinyurl.com/ddg5bz
http://www.cantrip.org/gatto.html
audiophile, n:
Someone who listens to the equipment instead of the music.
Re: amrecover fails - problems loading correct tape
On 04/27/2011 04:10 PM, gene heskett wrote:
On Wednesday, April 27, 2011 05:00:34 PM Oscar Ricardo Silva did opine:
I've been using amanda for awhile but because of some index not found
issues decided to try 3.2.2 (currently using 2.6.1p2). Right now
backups on the new version work fine. The backup runs, files are
created on the virtual tapes (writing backups to disk), mail is sent,
etc. The problem comes when I try to recover a file and it appears to
be an issue with the tape changer.
On the client I see:
Continue [?/Y/n/s/d]? Y
Got no header and data from server, check in amidxtaped.*.debug and
amandad.*.debug files on server
When I check the debug files on the server, I get:
[amanda@amanda tmp]$ cat
./amanda/server/newbktest/amidxtaped.20110427135604.debug
1303930564.513325: amidxtaped: pid 933 ruid 511 euid 511 version
2.6.1p2: start at Wed Apr 27 13:56:04 2011
1303930564.513380: amidxtaped: amidxtaped: version 2.6.1p2
1303930564.514121: amidxtaped: FEATURES=9ffe7f
1303930564.555152: amidxtaped: CONFIG=newbktest
1303930564.555165: amidxtaped: LABEL=newbktape-10:2
1303930564.555174: amidxtaped: append_to_tapelist(tapelist=(nil),
label='newbktape-10', file=-1, partnum=-1, isafile=0)
1303930564.555185: amidxtaped: append_to_tapelist(tapelist=0xc855a80,
label='newbktape-10', file=2, partnum=-1, isafile=0)
1303930564.555198: amidxtaped: FSF=2
1303930564.555208: amidxtaped: HEADER
1303930564.555217: amidxtaped: DEVICE=chg-disk:/amandatapes/newbktapes
1303930564.555225: amidxtaped: HOST=^networking.its.utexas.edu$
1303930564.555237: amidxtaped: DISK=^/boot$
1303930564.555245: amidxtaped: DATESTAMP=20110427132216
1303930564.555252: amidxtaped: END
1303930564.555971: amidxtaped: pid 933 ruid 511 euid 511 version
2.6.1p2: rename at Wed Apr 27 13:56:04 2011
1303930564.556098: amidxtaped: Restoring from changer, checking labels
1303930564.556108: amidxtaped: Locking devices
1303930564.556215: amidxtaped: Sending output to file descriptor 52
1303930564.558009: amidxtaped: changer: -info
1303930564.660259: amidxtaped: changer: EXITSTATUS 0
1303930564.660277: amidxtaped: changer: current 25 0 1
1303930564.660314: amidxtaped: changer: -slot current
1303930564.661268: amidxtaped: changer: EXITSTATUS 1
1303930564.661279: amidxtaped: changer: error Slot current not
found 1303930564.661286: amidxtaped: changer: ERRORerror Slot
current not found 1303930564.661303: amidxtaped: changer: -info
1303930564.661602: amidxtaped: changer: EXITSTATUS 0
1303930564.661611: amidxtaped: changer: current 25 0 1
1303930564.661619: amidxtaped: changer_query: changer return was 25 0 1
1303930564.661628: amidxtaped: changer_query: searchable = 1
1303930564.661635: amidxtaped: changer_find: looking for newbktape-10
changer is searchable = 1
1303930564.661642: amidxtaped: changer_search: newbktape-10
1303930564.661651: amidxtaped: changer: -search newbktape-10
1303930564.663498: amidxtaped: changer: EXITSTATUS 0
1303930564.663510: amidxtaped: changer: 10
1303930564.663523: amidxtaped: changer: -slot current
1303930564.664820: amidxtaped: changer: EXITSTATUS 1
1303930564.664831: amidxtaped: changer: error Slot current not
found 1303930564.664838: amidxtaped: changer: ERRORerror Slot
current not found 1303930564.664856: amidxtaped: critical (fatal):
loadlabel_slot: assertion `rc 1 || device_name != NULL' failed
amidxtaped: loadlabel_slot: assertion `rc 1 || device_name != NULL'
failed /usr/local/amanda/lib/libamanda-2.6.1p2.so[0x2b935a2b84e2]
/lib64/libglib-2.0.so.0(g_logv+0x26f)[0x32df634d5f]
/lib64/libglib-2.0.so.0(g_log+0x83)[0x32df634f33]
/usr/local/amanda/lib/librestore-2.6.1p2.so(loadlabel_slot+0x3f5)[0x2b93
59c54b25]
/usr/local/amanda/lib/libamserver-2.6.1p2.so(changer_find+0x1b8)[0x2b93
59e61f58]
/usr/local/amanda/lib/librestore-2.6.1p2.so(search_tapes+0x413)[0x2b935
9c570f3] /usr/local/amanda/libexec/amidxtaped(main+0xbd3)[0x403213]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x32db61d994]
/usr/local/amanda/libexec/amidxtaped[0x4020a9]
In amanda.conf I define this:
tapedev chg-disk:/amandatapes/newbktapes
tapetype vtape
define tapetype vtape {
length 500 mbytes
}
500 megs How many of these virtual tapes do you allow it to use per
run? That is runtapes in the amanda.conf.
I am a home usr, using a commodity 1 terrabyte drive for the vtapes, and my
tapetype is set for about 30Gb. I am backing up this machine, and pieces
of the one out in the shop that runs my cnc milling machine, on a 5 day
cycle, so each days runs vary from 12Gb to 25Gb. 500 megs I outgrew by
1998. ;-)
This is just a test and I'm backing up /boot on a single system. Since
this is currently a test I didn't want to wait too long for a backup to
complete. My production backups are generally 400-500GB per night.
Oscar
Re: amrecover fails - problems loading correct tape
On 04/27/2011 03:58 PM, Jean-Louis Martineau wrote: Oscar Ricardo Silva wrote: [amanda@amanda tmp]$ cat ./amanda/server/newbktest/amidxtaped.20110427135604.debug 1303930564.513325: amidxtaped: pid 933 ruid 511 euid 511 version 2.6.1p2: start at Wed Apr 27 13:56:04 2011 1303930564.513380: amidxtaped: amidxtaped: version 2.6.1p2 You are running the 2.6.1p2, fix the xinetd configuration to run 3.2.2. Jean-Louis Anybody else run into this? I couldn't find any related items in the list archives. ARGH ... and this is what happens when you build multiple versions of amanda and are not careful of links and which binary is really being called I installed the 3.2.2 version of amanda in a different directory but the restore was calling the 2.6.1p2 version. Thank you.
Re: amrecover fails - problems loading correct tape
On Wednesday, April 27, 2011 05:33:53 PM Oscar Ricardo Silva did opine:
On 04/27/2011 04:10 PM, gene heskett wrote:
On Wednesday, April 27, 2011 05:00:34 PM Oscar Ricardo Silva did opine:
I've been using amanda for awhile but because of some index not
found issues decided to try 3.2.2 (currently using 2.6.1p2). Right
now backups on the new version work fine. The backup runs, files
are created on the virtual tapes (writing backups to disk), mail
is sent, etc. The problem comes when I try to recover a file and it
appears to be an issue with the tape changer.
On the client I see:
Continue [?/Y/n/s/d]? Y
Got no header and data from server, check in amidxtaped.*.debug and
amandad.*.debug files on server
When I check the debug files on the server, I get:
[amanda@amanda tmp]$ cat
./amanda/server/newbktest/amidxtaped.20110427135604.debug
1303930564.513325: amidxtaped: pid 933 ruid 511 euid 511 version
2.6.1p2: start at Wed Apr 27 13:56:04 2011
1303930564.513380: amidxtaped: amidxtaped: version 2.6.1p2
1303930564.514121: amidxtaped: FEATURES=9ffe7f
1303930564.555152: amidxtaped: CONFIG=newbktest
1303930564.555165: amidxtaped: LABEL=newbktape-10:2
1303930564.555174: amidxtaped: append_to_tapelist(tapelist=(nil),
label='newbktape-10', file=-1, partnum=-1, isafile=0)
1303930564.555185: amidxtaped: append_to_tapelist(tapelist=0xc855a80,
label='newbktape-10', file=2, partnum=-1, isafile=0)
1303930564.555198: amidxtaped: FSF=2
1303930564.555208: amidxtaped: HEADER
1303930564.555217: amidxtaped:
DEVICE=chg-disk:/amandatapes/newbktapes 1303930564.555225:
amidxtaped: HOST=^networking.its.utexas.edu$ 1303930564.555237:
amidxtaped: DISK=^/boot$
1303930564.555245: amidxtaped: DATESTAMP=20110427132216
1303930564.555252: amidxtaped: END
1303930564.555971: amidxtaped: pid 933 ruid 511 euid 511 version
2.6.1p2: rename at Wed Apr 27 13:56:04 2011
1303930564.556098: amidxtaped: Restoring from changer, checking
labels 1303930564.556108: amidxtaped: Locking devices
1303930564.556215: amidxtaped: Sending output to file descriptor 52
1303930564.558009: amidxtaped: changer: -info
1303930564.660259: amidxtaped: changer: EXITSTATUS 0
1303930564.660277: amidxtaped: changer: current 25 0 1
1303930564.660314: amidxtaped: changer: -slot current
1303930564.661268: amidxtaped: changer: EXITSTATUS 1
1303930564.661279: amidxtaped: changer: error Slot current not
found 1303930564.661286: amidxtaped: changer: ERRORerror Slot
current not found 1303930564.661303: amidxtaped: changer: -info
1303930564.661602: amidxtaped: changer: EXITSTATUS 0
1303930564.661611: amidxtaped: changer: current 25 0 1
1303930564.661619: amidxtaped: changer_query: changer return was 25 0
1 1303930564.661628: amidxtaped: changer_query: searchable = 1
1303930564.661635: amidxtaped: changer_find: looking for
newbktape-10 changer is searchable = 1
1303930564.661642: amidxtaped: changer_search: newbktape-10
1303930564.661651: amidxtaped: changer: -search newbktape-10
1303930564.663498: amidxtaped: changer: EXITSTATUS 0
1303930564.663510: amidxtaped: changer: 10
1303930564.663523: amidxtaped: changer: -slot current
1303930564.664820: amidxtaped: changer: EXITSTATUS 1
1303930564.664831: amidxtaped: changer: error Slot current not
found 1303930564.664838: amidxtaped: changer: ERRORerror Slot
current not found 1303930564.664856: amidxtaped: critical (fatal):
loadlabel_slot: assertion `rc 1 || device_name != NULL' failed
amidxtaped: loadlabel_slot: assertion `rc 1 || device_name != NULL'
failed /usr/local/amanda/lib/libamanda-2.6.1p2.so[0x2b935a2b84e2]
/lib64/libglib-2.0.so.0(g_logv+0x26f)[0x32df634d5f]
/lib64/libglib-2.0.so.0(g_log+0x83)[0x32df634f33]
/usr/local/amanda/lib/librestore-2.6.1p2.so(loadlabel_slot+0x3f5)[0x2
b93 59c54b25]
/usr/local/amanda/lib/libamserver-2.6.1p2.so(changer_find+0x1b8)[0x2b
93 59e61f58]
/usr/local/amanda/lib/librestore-2.6.1p2.so(search_tapes+0x413)[0x2b9
35 9c570f3]
/usr/local/amanda/libexec/amidxtaped(main+0xbd3)[0x403213]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x32db61d994]
/usr/local/amanda/libexec/amidxtaped[0x4020a9]
In amanda.conf I define this:
tapedev chg-disk:/amandatapes/newbktapes
tapetype vtape
define tapetype vtape {
length 500 mbytes
}
500 megs How many of these virtual tapes do you allow it to use
per run? That is runtapes in the amanda.conf.
I am a home usr, using a commodity 1 terrabyte drive for the vtapes,
and my tapetype is set for about 30Gb. I am backing up this machine,
and pieces of the one out in the shop that runs my cnc milling
machine, on a 5 day cycle, so each days runs vary from 12Gb to 25Gb.
500 megs I outgrew by 1998. ;-)
This is just a test and I'm backing up /boot on a single system. Since
this is currently a test I didn't want
