Trying to recover a file via amrecover. I set the host and disk. I add
the file in question. I confirm the tape is in the drive. I tell it to
extract.
I get:
Got no header and data from server, check in amidxtaped.*.debug and
amandad.*.debug files on server
Any help? I have no idea where to
On 04/26/2012 11:43 AM, Greg Copeland wrote:
Trying to recover a file via amrecover. I set the host and disk. I add
the file in question. I confirm the tape is in the drive. I tell it to
extract.
I get:
Got no header and data from server, check in amidxtaped.*.debug and
amandad.*.debug files
On 4/26/12 11:43 AM, Greg Copeland wrote:
Trying to recover a file via amrecover. I set the host and disk. I add the file in question. I
confirm the tape is in the drive. I tell it to extract.
I get:
Got no header and data from server, check in amidxtaped.*.debug and
amandad.*.debug files
On Thu, 2012-04-26 at 09:54 -0600, Steven Backus wrote:
Thanks to Steven Backus and Jean-Louis for the win. This excerpt was
sent to me by Steven and did fix my issue.
I manually applied it to the perl module from my source build directory
and then simply copied it into production. Of course, I
On Thu, 2012-04-26 at 12:12 -0400, Chris Hoogendyk wrote:
The debug files should be in /tmp/amanda/server/ with the date-time stamp in
the place of the *.
Of course, if you commented out debugging, you can always uncomment it and
then run amrecover again
to get the debug files.
Greetings;
Conditions still the same, but last night I was again forced to use dd to
extract a directory from a backup vtape file, amrecover again complaining it
cannot find the Daily-18 vtape. And if you ask it to rescan, there seems to
be a lock on chg-disk and it cannot access chg-disk to
On Fri, Nov 21, 2008 at 12:24 PM, Gene Heskett [EMAIL PROTECTED] wrote:
Extracting files using tape drive chg-disk on host coyote.
Load tape Dailys-13 now
Continue [?/Y/n/s/d]?
Volume labeled 'Dailys-13' not found.
Load tape Dailys-13 now
Continue [?/Y/n/d]?
Is amanda_changer set to
On Friday 21 November 2008, Dustin J. Mitchell wrote:
On Fri, Nov 21, 2008 at 12:24 PM, Gene Heskett [EMAIL PROTECTED]
wrote:
Extracting files using tape drive chg-disk on host coyote.
Load tape Dailys-13 now
Continue [?/Y/n/s/d]?
Volume labeled 'Dailys-13' not found.
Load tape Dailys-13 now
On Fri, Nov 21, 2008 at 1:30 PM, Gene Heskett [EMAIL PROTECTED] wrote:
Not an 'amanda_changer' in my old amanda.conf, remember this thing can darned
near be exempt from child labor laws. I do have:
Sorry, I meant 'amrecover_changer'. I'd have to look at the logs to
see what happened, then.
On Friday 21 November 2008, Dustin J. Mitchell wrote:
On Fri, Nov 21, 2008 at 1:30 PM, Gene Heskett [EMAIL PROTECTED]
wrote:
Not an 'amanda_changer' in my old amanda.conf, remember this thing can
darned near be exempt from child labor laws. I do have:
Sorry, I meant 'amrecover_changer'. I'd
On Friday 21 November 2008, Dustin J. Mitchell wrote:
On Fri, Nov 21, 2008 at 1:30 PM, Gene Heskett [EMAIL PROTECTED] wrote:
Not an 'amanda_changer' in my old amanda.conf, remember this thing can
darned near be exempt from child labor laws. I do have:
Sorry, I meant 'amrecover_changer'. I'd
On Fri March 28 2003 23:32, Gene Heskett wrote:
On Fri March 28 2003 12:46, Mike Simpson wrote:
Hi --
Any tips or tricks or other thoughts? Is this the Linux
dump/restore problem I've seen talked about on the mailing
list? I don't understand how the gzip file could be corrupted
by a problem
Hi Mike,
Thanks for your good description of the problem.
You found a bug in a the way the taper read a file from holding disk
if blocksize 32k.
There is two posible workaround (untested).
1. Set your chunksize to '32k + n * blocksize' where n is an integer.
2. Set file-pad to false.
Setting
On Sat March 29 2003 12:04, Jean-Louis Martineau wrote:
Hi Mike,
Thanks for your good description of the problem.
You found a bug in a the way the taper read a file from holding
disk if blocksize 32k.
There is two posible workaround (untested).
1. Set your chunksize to '32k + n * blocksize'
Hi --
Any tips or tricks or other thoughts? Is this the Linux dump/restore
problem I've seen talked about on the mailing list? I don't
understand how the gzip file could be corrupted by a problem internal
to the dump/restore cycle.
Answering my own question after a week of testing ... I
On Fri March 28 2003 12:46, Mike Simpson wrote:
Hi --
Any tips or tricks or other thoughts? Is this the Linux
dump/restore problem I've seen talked about on the mailing list?
I don't understand how the gzip file could be corrupted by a
problem internal to the dump/restore cycle.
Answering
Hi --
Running Amanda 2.4.4 servers and clients, using a RedHat 7.3 tape
host, backing up using DUMP method (dump/restore) ext2 filesystems on
a RedHat 7.2 client host:
I tried to do an amrecover on the /home filesystem (~8 GB), which
recovered all of the directories (as expected) and about
Hello, I was wondering if anyone had ran into any troubles with amrecover
before. I can backup files fine but when I try to run amrecover, then it says
that amanda access is not allowed. It seems like if amanda wasn't allowed
then
I wouldn't be able to backup the files on the server.
[root@tapeserver /root]# amrecover -C Normal
AMRECOVER Version 2.4.2p1. Contacting server on name_server ...
220 tapeserver AMANDA index server (2.4.2p1) ready.
500 Access not allowed: [access as amanda not allowed from root@tapeserver]
amandahostsauth failed
[root@tapeserver /root]#
In
Okay, I see. amrecover is trying to put the files back to baboquivari, the
NT machine that crashed. What I was trying to do was restore the specified
files to a local drive on navajo (my amanda server) because baboquivari
isn't going to be coming back, and there were just a couple of files that
20 matches
Mail list logo
