amrestore + tar not working.

2003-10-09 Thread Byarlay, Wayne A.
Hi. I just want to extract * from a tar'ed tape archive to '.' (current
directory on the backup server). I've done it before and it worked OK.
Maybe I wrote something down wrong from before.

 /usr/sbin/amrestore -p /dev/nst0 servername pathname | tar xvf -

All I get for any server/filesystem is:

tar: /whatever/whatever: Cannot open: No such file or directory
tar: /whatever/whatever2: Cannot open: No such file or directory
.
.
tar: Error exit delayed from previous errors

Am I doing something wrong?

wab



RE: amrestore + tar not working.

2003-10-09 Thread Yeates, Stephen [Heanet]
Hi Wayne,
I'm new to this group but in my experience you need to 
specify the directory name to extract for tar

So if you want everything relative to server pathname you would specify

/usr/sbin/amrestore -p /dev/nst0 servername pathname | tar xvf - ./

or if you know the directory name

/usr/sbin/amrestore -p /dev/nst0 servername pathname | tar xvf - ./foo

This will extract files into your current working directory you can test it
with 

/usr/sbin/amrestore -p /dev/nst0 servername pathname | tar tvf - ./foo

HTH!

Does anyone know how to get around [parse of reply message failed]
when backing up a solaris 2.6 client to amanda server?

Any help would be appreciated more details of setup if needed but I'm
heading away
for the evening so will get back tommorrow.

regards,

Stephen 

 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Byarlay, Wayne A.
Sent: 09 October 2003 16:56
To: [EMAIL PROTECTED]
Subject: amrestore + tar not working.


Hi. I just want to extract * from a tar'ed tape archive to '.' (current
directory on the backup server). I've done it before and it worked OK.
Maybe I wrote something down wrong from before.

 /usr/sbin/amrestore -p /dev/nst0 servername pathname | tar xvf -

All I get for any server/filesystem is:

tar: /whatever/whatever: Cannot open: No such file or directory
tar: /whatever/whatever2: Cannot open: No such file or directory
.
.
tar: Error exit delayed from previous errors

Am I doing something wrong?

wab

application/ms-tnef

RE: amrestore + tar not working.

2003-10-09 Thread donald . ritchey
Just an observation:

1.  Tar will happily extract the entire contents of the archive 
if you don't specify files or sets of files to extract.  So:
tar xvf -
says extract all files from archive that is in standard input.

2.  Check to see if your user ID has permission to extract the files
into the current directory.  If you are running the tar as the 'amanda' 
user ID, you may not be able to write the extracted files into the 
current directory.  If the parent directories could not be created,
the messages you are seeing are what could be expected in that case.

Don

Donald L. (Don) Ritchey
E-mail:  [EMAIL PROTECTED]


-Original Message-
From: Yeates, Stephen [Heanet] [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2003 11:40 AM
To: 'Byarlay, Wayne A.'; '[EMAIL PROTECTED]'
Subject: RE: amrestore + tar not working.


Hi Wayne,
I'm new to this group but in my experience you need to 
specify the directory name to extract for tar

So if you want everything relative to server pathname you would specify

/usr/sbin/amrestore -p /dev/nst0 servername pathname | tar xvf - ./

or if you know the directory name

/usr/sbin/amrestore -p /dev/nst0 servername pathname | tar xvf - ./foo

This will extract files into your current working directory you can test it
with 

/usr/sbin/amrestore -p /dev/nst0 servername pathname | tar tvf - ./foo

HTH!

Does anyone know how to get around [parse of reply message failed]
when backing up a solaris 2.6 client to amanda server?

Any help would be appreciated more details of setup if needed but I'm
heading away
for the evening so will get back tommorrow.

regards,

Stephen 

 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Byarlay, Wayne A.
Sent: 09 October 2003 16:56
To: [EMAIL PROTECTED]
Subject: amrestore + tar not working.


Hi. I just want to extract * from a tar'ed tape archive to '.' (current
directory on the backup server). I've done it before and it worked OK.
Maybe I wrote something down wrong from before.

 /usr/sbin/amrestore -p /dev/nst0 servername pathname | tar xvf -

All I get for any server/filesystem is:

tar: /whatever/whatever: Cannot open: No such file or directory
tar: /whatever/whatever2: Cannot open: No such file or directory
.
.
tar: Error exit delayed from previous errors

Am I doing something wrong?

wab




This e-mail and any of its attachments may contain Exelon Corporation
proprietary information, which is privileged, confidential, or subject 
to copyright belonging to the Exelon Corporation family of Companies. 
This e-mail is intended solely for the use of the individual or entity 
to which it is addressed.  If you are not the intended recipient of this 
e-mail, you are hereby notified that any dissemination, distribution, 
copying, or action taken in relation to the contents of and attachments 
to this e-mail is strictly prohibited and may be unlawful.  If you have 
received this e-mail in error, please notify the sender immediately and 
permanently delete the original and any copy of this e-mail and any 
printout. Thank You.




RE: amrestore + tar not working.

2003-10-09 Thread Byarlay, Wayne A.
Hmm. Well, I looked closer (by piping through more) at the output more;
and there's some permission denied's that I'm not especially too
worried about. Also, the /dev was not ignored when backing up root on
the client; so naturally I expect Cannot mknod; operation not
permitted is probably because it can't copy /dev/floppy, for instance,
to an amanda archive!

For the most part, I've got this stuff figured out... thanks all for
your help! I'm sure I'll be back with more newbie-type questions,
probably pertaining to client configuration.

wab.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Thursday, October 09, 2003 12:45 PM
To: [EMAIL PROTECTED]
Subject: RE: amrestore + tar not working.


What does the full output stream look like?

Tar issues that error message when it fails at part of the extract,
but not fatally.  For example, a directory might already exist with
read-only permissions and tar cannot overwrite it, but everything 
else in the extract goes OK.  Look at the complete stream and see 
if you can find out the original complaint from tar.

Don

Donald L. (Don) Ritchey
E-mail:  [EMAIL PROTECTED]


-Original Message-
From: Byarlay, Wayne A. [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2003 12:35 PM
To: [EMAIL PROTECTED]
Subject: RE: amrestore + tar not working.


AHA! It was a permissions thing, as far as the actual extraction.

However, it appears as though I'm not out of the woods yet... the
untarring process only get yea far before bombing out with the 2nd
error:

tar: Error exit delayed from previous errors

Maybe I need a different tar? or some large-archive specification? I
know I've successfully restored much larger archives... but it's been a
while.

Thanks for your help!!

wab

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Thursday, October 09, 2003 11:54 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: amrestore + tar not working.


Just an observation:

1.  Tar will happily extract the entire contents of the archive 
if you don't specify files or sets of files to extract.  So:
tar xvf -
says extract all files from archive that is in standard input.

2.  Check to see if your user ID has permission to extract the files
into the current directory.  If you are running the tar as the 'amanda' 
user ID, you may not be able to write the extracted files into the 
current directory.  If the parent directories could not be created,
the messages you are seeing are what could be expected in that case.

Don

Donald L. (Don) Ritchey
E-mail:  [EMAIL PROTECTED]


-Original Message-
From: Yeates, Stephen [Heanet] [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2003 11:40 AM
To: 'Byarlay, Wayne A.'; '[EMAIL PROTECTED]'
Subject: RE: amrestore + tar not working.


Hi Wayne,
I'm new to this group but in my experience you need to 
specify the directory name to extract for tar

So if you want everything relative to server pathname you would
specify

/usr/sbin/amrestore -p /dev/nst0 servername pathname | tar xvf - ./

or if you know the directory name

/usr/sbin/amrestore -p /dev/nst0 servername pathname | tar xvf -
./foo

This will extract files into your current working directory you can test
it
with 

/usr/sbin/amrestore -p /dev/nst0 servername pathname | tar tvf -
./foo

HTH!

Does anyone know how to get around [parse of reply message failed]
when backing up a solaris 2.6 client to amanda server?

Any help would be appreciated more details of setup if needed but I'm
heading away
for the evening so will get back tommorrow.

regards,

Stephen 

 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Byarlay, Wayne A.
Sent: 09 October 2003 16:56
To: [EMAIL PROTECTED]
Subject: amrestore + tar not working.


Hi. I just want to extract * from a tar'ed tape archive to '.' (current
directory on the backup server). I've done it before and it worked OK.
Maybe I wrote something down wrong from before.

 /usr/sbin/amrestore -p /dev/nst0 servername pathname | tar xvf -

All I get for any server/filesystem is:

tar: /whatever/whatever: Cannot open: No such file or directory
tar: /whatever/whatever2: Cannot open: No such file or directory
.
.
tar: Error exit delayed from previous errors

Am I doing something wrong?

wab




This e-mail and any of its attachments may contain Exelon Corporation
proprietary information, which is privileged, confidential, or subject 
to copyright belonging to the Exelon Corporation family of Companies. 
This e-mail is intended solely for the use of the individual or entity 
to which it is addressed.  If you are not the intended recipient of this

e-mail, you are hereby notified that any dissemination, distribution, 
copying, or action taken in relation to the contents of and attachments 
to this e-mail is strictly prohibited and may