Just an update.
The issue was resolved by modifying all of DLEs in disklist from /export/./abc
to /export/abc which means I removed '.' from all DLEs.
Now I can recover anyfile/directory using amrecover. Hope this is helpful for
people using '.' inside their DLEs.
Thanks
Well, I have added one more partition in disklist file - /etc . This sure
does not have '.' like /export/./local/
I have started to think that either tar/gtar or amrecove, one of that does not
work well with a . in the specified DLE. It may also be version on solaris
atleast.
I am going
Hi,
I have been backing up using amanda for about 1 month and I agree that I should
have checked amrestore earlier. Now that I am trying to restore
files/directories using amrestore, there is always this error :
Not found in archive
tar: Exiting with failure status due to previous errors
If I do grep manually from terminal, I see that file is available.
/opt/csw/bin/gzip -dc
/opt/csw/etc/amanda/weeklyfull/index/amclient.domain/_export_._local/2011011117_0.gz
| grep gcc-3.2-sol8-sparc-local
/local/gcc-3.2-sol8-sparc-local
Am 16.09.10 19:52 schrieb(en) Dustin J. Mitchell:
On Thu, Sep 16, 2010 at 12:13 PM, Albrecht Dreß albrecht.dr...@arcor.de wrote:
Does anyone know about the reason (and maybe a workaround) for this issue, or
is this something for Fedora support? I don't have a Fedora box, but of course
this
that the file is
Not found in archive.
Below are a few examples which illustrate this issue (/opt/bin/setar is the fedora app,
tar the standard GNU tar).
For a short file name, it works just fine:
--8
adr...@myserver:~$ /opt/bin
On Thu, Sep 16, 2010 at 12:13 PM, Albrecht Dreß albrecht.dr...@arcor.de wrote:
Does anyone know about the reason (and maybe a workaround) for this issue,
or is this something for Fedora support? I don't have a Fedora box, but of
course this might also be caused by either the Ubuntu libs and/or
On Tue, Jul 13, 2010 at 04:14:17PM -0500, Dustin J. Mitchell wrote:
Hmm, 14 parts and 14 Error writing to fd 5 messages. From my memory
and a brief look at the 2.6.1 sources (I couldn't find a version in
the thread, but this looks like 2.6.1 to me), that wouldn't have come
from Amanda itself,
Hi Dustin,
In amidxtaped I get the following:
1278951470.354229: amidxtaped: search_a_tape: desired_tape=0x7a0450
label=HASNAPSHOT-05
1278951470.354237: amidxtaped: tape: numfiles = 14
1278951470.354242: amidxtaped: tape: files[0] = 1
1278951470.354247: amidxtaped: tape: files[1] = 2
Hmm, 14 parts and 14 Error writing to fd 5 messages. From my memory
and a brief look at the 2.6.1 sources (I couldn't find a version in
the thread, but this looks like 2.6.1 to me), that wouldn't have come
from Amanda itself, but from something Amanda ran - perhaps the
decompression binary? You
OK, So i've tried again without the custom-compress option, now when it
gets to the 5th tape when trying to recover I just get
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
Extractor child exited with status 2
Whats the best way forward here? Should I be using a
On Mon, Jul 12, 2010 at 11:45 AM, Mark Adams m...@campbell-lange.net wrote:
OK, So i've tried again without the custom-compress option, now when it
gets to the 5th tape when trying to recover I just get
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
Extractor child
On Wed, Jul 7, 2010 at 10:41 AM, Mark Adams m...@campbell-lange.net wrote:
client_custom_compress /usr/bin/pigz
I've heard about pigz in use several times now, and in no case was it
successful. I don't know exactly what the problem is, but history
suggests that things will work fine for you
Hi Dustin,
I'd tried it not using pigz with the original errors. Thats when I added
NO-UNQUOTE to see if it helped, I'll run again with pigz but I believe
the problem is elsewhere.
On Wed, Jul 07, 2010 at 10:46:32AM -0500, Dustin J. Mitchell wrote:
On Wed, Jul 7, 2010 at 10:41 AM, Mark Adams
Hi Dustin,
backed up using sudo -u backup amdump namehere
Trying to recover using amrecover. Config for dump is as follows;
-
define dumptype clientbackup_archive {
comment CLIENTBACKUP_ARCHIVE
program GNUTAR
property NO-UNQUOTE yes
compress client custom
Hi Dustin,
Doesn't look like it's worked. Now I'm getting the following (before the
normal Not found in archive message comes up
tar: Skipping to next header
tar: Archive contains `b\371^h\r%\247\0 \006\212\214' where numeric off_t value
expected
tar: Archive contains `\211\023\034cQ\r\004\252
On Tue, Jul 6, 2010 at 8:37 AM, Mark Adams m...@campbell-lange.net wrote:
Anything else I can try? This is really killing me!
It doesn't look like that was a tar file. How was it backed up, and
how are you restoring?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
Great thanks. I'll try this - is this something most people set on as
part of a normal config?
On Wed, Jun 30, 2010 at 12:52:38PM -0500, Dustin J. Mitchell wrote:
On Wed, Jun 30, 2010 at 12:52 PM, Dustin J. Mitchell dus...@zmanda.com
wrote:
property NO-QUOTING yes
Sorry, that's
On Thu, Jul 1, 2010 at 3:57 AM, Mark Adams m...@campbell-lange.net wrote:
Great thanks. I'll try this - is this something most people set on as
part of a normal config?
It's relatively new, so no, not yet, but if it proves to have lots of
upsides and no significant downsides, then I'm sure it
to retrieve from a 2nd tape. I then
went on to test using normal gzip and retrieved from a 2nd tape without
issue.
However, I've now run a set with 7 tapes, and am having trouble
retrieving from them. I'm getting the Not found in archive message
even though the files show in the index
, and not being able to retrieve from a 2nd tape. I then
went on to test using normal gzip and retrieved from a 2nd tape without
issue.
However, I've now run a set with 7 tapes, and am having trouble
retrieving from them. I'm getting the Not found in archive message
even though
How do I enable it?
Regards,
Mark
On 30 Jun 2010, at 17:39, Dustin J. Mitchell dus...@zmanda.com wrote:
On Wed, Jun 30, 2010 at 10:51 AM, Mark Adams m...@campbell-lange.net wrote:
Is this possibly my problem Dustin?
NO-UNQUOTE
If NO (the default), gnutar doesn't get the --no-unquote
On Wed, Jun 30, 2010 at 12:39 PM, Mark Adams m...@campbell-lange.net wrote:
How do I enable it?
Assuming you have a new enough version, add
property NO-QUOTING yes
to your dumptype.
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Wed, Jun 30, 2010 at 12:52 PM, Dustin J. Mitchell dus...@zmanda.com wrote:
property NO-QUOTING yes
Sorry, that's
property NO-UNQUOTE yes
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Wed, Jun 30, 2010 at 10:51 AM, Mark Adams m...@campbell-lange.net wrote:
Is this possibly my problem Dustin?
NO-UNQUOTE
If NO (the default), gnutar doesn't get the --no-unquote option
and the diskname can't have some characters, eg. '\'. If YES, then the
--no-unquote option is given to
Am 30.06.2010 19:52, schrieb Dustin J. Mitchell:
On Wed, Jun 30, 2010 at 12:52 PM, Dustin J. Mitchell dus...@zmanda.com
wrote:
property NO-QUOTING yes
Sorry, that's
property NO-UNQUOTE yes
Non-IT-people might say QUOTE yes --- ;-) ?
S
On Wed, Jun 30, 2010 at 5:53 PM, Stefan G. Weichinger s...@amanda.org wrote:
Non-IT-people might say QUOTE yes --- ;-) ?
Yes, we IT people do love our N-negatives, since we can just look at
the rightmost bit of N to determine its interpretation.
The name is based on the underlying gnu-tar
using normal gzip and retrieved from a 2nd tape without
issue.
However, I've now run a set with 7 tapes, and am having trouble
retrieving from them. I'm getting the Not found in archive message
even though the files show in the index.
This makes me think that maybe, after all
retrieving from them. I'm getting the Not found in archive message
even though the files show in the index.
This makes me think that maybe, after all, it was just my poor
configuration and not pigz that was causing the issues! Can anyone shed
any light on this or advise on how I can figure out why
.
However, I've now run a set with 7 tapes, and am having trouble
retrieving from them. I'm getting the Not found in archive message
even though the files show in the index.
This makes me think that maybe, after all, it was just my poor
configuration and not pigz that was causing the issues! Can
30 matches
Mail list logo
