On Fri, Jan 07, 2005 at 02:01:26PM -0500, Eric Siegerman wrote:
On Fri, Jan 07, 2005 at 11:17:21AM -0500, Brian Cuttler wrote:
samar 170# dd of=/dev/sdlt2 obs=32k if=./scratch
64+0 records in
1+0 records out
bs block size, obs outpub BS, (there is an IBS also, which I
am afraid of developing
On Fri, Jan 07, 2005 at 01:20:42PM -0500, Brian Cuttler wrote:
samar 170# dd of=/dev/sdlt2 obs=32k if=./scratch
64+0 records in
1+0 records out
bs block size, obs outpub BS, (there is an IBS also, which I
am afraid of developing should this not resolve soon)
Yup, this makes sense. Since
samar 5# /usr/local/sbin/amrestore -r /dev/sdlt2
amrestore: 0: skipping start of tape: date 20050107 label SAMAR05
amrestore: 1: restoring samar._usr5_amanda.20050107.1
amrestore: read error: I/O error
samar 6# mt -f /dev/sdlt2 rewind
samar 7# mt -f /dev/sdlt2 fsf 1
samar 8# dd if=/dev/sdlt2
On Fri, Jan 07, 2005 at 03:40:12PM -0500, Brian Cuttler wrote:
samar 24# mt -f /dev/sdlt2 blksize
Recommended tape I/O size: 131072 bytes (256 512-byte blocks)
Minimum block size: 4 byte(s)
Maximum block size: 16777212 bytes
Current block size: Variable
I am using /dev/sdlt2 link
On Friday 07 January 2005 15:40, Brian Cuttler wrote:
samar 5# /usr/local/sbin/amrestore -r /dev/sdlt2
amrestore: 0: skipping start of tape: date 20050107 label SAMAR05
amrestore: 1: restoring samar._usr5_amanda.20050107.1
amrestore: read error: I/O error
samar 6# mt -f /dev/sdlt2 rewind
On Fri, Jan 07, 2005 at 03:40:12PM -0500, Brian Cuttler wrote:
samar 5# /usr/local/sbin/amrestore -r /dev/sdlt2
amrestore: 0: skipping start of tape: date 20050107 label SAMAR05
amrestore: 1: restoring samar._usr5_amanda.20050107.1
amrestore: read error: I/O error
[likewise with dd bs=32k
chunk on disk was broken into the
amanda header followed by the collected chuncks. Makes sense if
you think about it.
New information--
The amdump run I started yesterday completed in record time. 51 hours
of dump time and only 33 hours of elapse time.
I tried to amrestore several dumps from
of elapse time.
I tried to amrestore several dumps from the tape to disk, oddly
the restores of the DUMP DLE both failed, the restore of the TAR
DLE sort of worked, I can... I'm an idiot.
I was able to take the DLE restored from tape and # tar -tf the
tar ball but was unable to restore it with # tar
# /usr/local/sbin/amrestore /dev/sdlt2 samar /usr5/dtaylor
amrestore: 0: skipping start of tape: date 20041227 label SAMAR23
amrestore: 1: skipping samar._usr1.20041227.1
amrestore: 2: skipping samar._usr5_lalor.20041227.1
amrestore: 3: skipping samar._usr5_amanda.20041227.0
amrestore: 4
errors. Or where not until I
## tried to test the file restore process.
##
## I am able to see the DLEs on tape but I'm unable to retried any
## data, either from the dump or the tar partitions.
##
## samar 144# mt -f /dev/sdlt2 rewind
## samar 145# /usr/local/sbin/amrestore /dev/sdlt2 samar
## samar 145# /usr/local/sbin/amrestore /dev/sdlt2 samar
/usr5/dtaylor ## amrestore: 0: skipping start of tape: date
20041227 label SAMAR23 ## amrestore: 1: skipping
samar._usr1.20041227.1
## amrestore: 2: skipping samar._usr5_lalor.20041227.1
## amrestore: 3: skipping samar._usr5_amanda
restore process.
I am able to see the DLEs on tape but I'm unable to retried any data,
either from the dump or the tar partitions.
samar 144# mt -f /dev/sdlt2 rewind
samar 145# /usr/local/sbin/amrestore /dev/sdlt2 samar /usr5/dtaylor
amrestore: 0: skipping start of tape: date 20041227 label SAMAR23
but there are no apparent errors. Or where not until I
tried to test the file restore process.
I am able to see the DLEs on tape but I'm unable to retried any
data, either from the dump or the tar partitions.
samar 144# mt -f /dev/sdlt2 rewind
samar 145# /usr/local/sbin/amrestore /dev/sdlt2 samar /usr5
How do i retrieve multiple backup images from the tape to the Hard disk
using amrestore, I have used
amrestore /dev/nst0 inventory.mumbai.redhat.com oscar.mumbai.redhat.com
but doesnot seem to work
Any help
--
Regards,
Kaushal Shriyan
Technical Engineer
Red Hat India Pvt. Ltd.
Tel : +91
OK, I've got another problem.
Figured out how to position the fake tape; thanks to Paul for help.
Now, when I'm restoring stuff via the following command:
/usr/sbin/amrestore -p file:/data1/amanda/tape4 servername usr | tar
-xvf -
Eventually, it looks as though it's right in the middle
Byarlay, Wayne A. wrote:
Now, when I'm restoring stuff via the following command:
/usr/sbin/amrestore -p file:/data1/amanda/tape4 servername usr | tar
-xvf -
usr should probably be /usr, unless you specifically
used a syntax in disklist like:
servername usr /usr {
comp-usr-tar
I'm trying to restore some files, but everything seems to crash.
I tried with three different methods :
amrecover, amrestore and by hand (dd + restore), but everything crashes.
[EMAIL PROTECTED] # amrestore -p /dev/nsa0.1 verdon.acc.fr /dev/amrd0s2f
|restore -ivf -
Verify tape and initialize maps
On Mon, 24 May 2004 at 4:20pm, Nicolas Ecarnot wrote
amrestore: 8: restoring verdon.acc.fr._dev_amrd0s2f.20040518.1
Tape is not a dump tape
Error 32 (Broken pipe) offset 32768+32768, wrote 0
amrestore: pipe reader has quit in middle of file.
Have you any idea ?
Are you sure the archive
(being the level 0 dump) and Dagtape-02 after
that?
I thought I did, so I inserted Dagtape-04, booted the machine to be
restored off a Knoppix CD, made the partition to which I wanted to restore
pristine (love that word!), cd'ed into it and ran:
amrestore -p /dev/nst0 xxx / | restore rf
Hello Hans,
As quoted from Hans van Zijst [EMAIL PROTECTED]:
I tried a bare metal recovery yesterday,
Why didn't you just use amrecover? It prompts you to insert the right
tapes in the tape server as needed, without you having to figure it out
yourself.
Kind regards,
--
-- Gertjan van
Hi Gertjan,
Two reasons. First, UNIX Backup and recovery (O'Reilly) says:
amrecover should not be used to do full system recovery with vendor restore
tools [...] Full system recovery with vendor restore should be done with
amrestore.
Makes sense. And the second reason is that I want to build
Hans van Zijst wrote:
I tried a bare metal recovery yesterday, but without the success I had hoped
for. I restored the latest level 0 dump and then tried to restore the
incremental dump over it. First step worked like a charm, but as soon as I
restored the incremental tape, I got the error:
Paul,
Every machine here runs Amanda 2.4.4p2. I'm sure the tapes that amadmin
lists, are the correct ones: Dagtape-04 was made last thursday and on
fridays I make a full dump, using another configuration. This monday and
tuesday I went on with Dagelijks.
I got exactly the same message
Hans van Zijst wrote:
Restore can get confused when doing incremental restores from dumps that
were made on active file systems.
Of course I make backups of active file systems. If this really is the
problem, I can't imagine I'm the only one who ran into it. Or am I just the
only one who's
Hi Paul,
Funny that you mention tar. The reason why I chose dump is that dump was
supposed to handle open files better than tar. Plus, I don't like the idea
of atime being updated because of a backup.
Anyway, I couldn't find anything about this in the changelogs of
dump/restore between my
Hans van Zijst wrote:
Funny that you mention tar. The reason why I chose dump is that dump was
supposed to handle open files better than tar. Plus, I don't like the idea
of atime being updated because of a backup.
Tar and dump handle open files just as bad. Or maybe tar is a little
better in
), and then amanda does this for you.
I'm running amanda-2.4.4p2. I've added the parameters in my amanda.conf
but nothing happens exept the 'amrestore /dev/nst0 ^iulian$ ^/$ 20040317'
does not work anymore.
[EMAIL PROTECTED] root]# amrestore /dev/nst0 ^iulian$ ^/$ 20040317
amrestore: WARNING: not at start
Iulian Topliceanu wrote:
[EMAIL PROTECTED] root]# mt fsf
[EMAIL PROTECTED] root]#
fsf is fast-skip-forward, and expects a number for how many files.
So nothing happens. I should I manualy rewind a tape? I guess not by using
my finger.
Type with your fingers:
mt -f /dev/nst0 rewind
The
The next new tape already labelled is: DailySet1-0.
DailySet1-0 DailySet1-1 DailySet1-2 etc.
Regards,
Iulian Topliceanu
Hi,
I get the following error while running amrestore after amdump and amflush
are doing their jobs without any errors:
I'm running amrecover from the amanda-server machine to avoid possible
filters:
[EMAIL PROTECTED] amanda]# amrecover -s 192.168.154.21 -t 192.168.154.21 -d
/dev/nst0
Iulian Topliceanu wrote:
argv[0] = amrestore
argv[1] = -p
argv[2] = -h
argv[3] = /dev/nst0
argv[4] = ^iulian$
argv[5] = ^/$
argv[6] = 20040317
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore: 0: reached end of information
Your tape was not rewound. Either
On Fri, 12 Mar 2004 at 11:08am, Gerhard den Hollander wrote
* Joshua Baker-LePain [EMAIL PROTECTED] (Thu, Mar 11, 2004 at 04:29:57PM -0500)
Anyways, it looks to be hardware, and not amanda or kernel related. So,
thanks all, and sorry for the noise. Is it Friday yet?
It is now.
Yeah,
I'm reading some somewhat large (14-18GB) images off of AIT3 tapes, and
it's taking *forever*. Some crude calculations show it coming off the
tape at around 80 KB/s, whereas it was written out at 11701.6 KB/s. The
tapes were written in variable block size mode. What's the best way to
read
. What's the best way to
read these images more quickly?
Are you piping the amrestore output, say to uncompress and extract
files? Maybe the extraction process is too slow, and causes the tape to
have to stop and reposition while the pipe is emptying out. I wonder if
you could put a bigger buffer
On Thu, 11 Mar 2004 at 2:21pm, Jonathan Dill wrote
I would try amrestore -c to just dump the image off the tape, and then
do the uncompress and extraction separately, but you will need enough
disk space to do it. Worst case, you could try amrestore -r and use
dd bs=32k skip=1 if=dump-file
--On Thursday, March 11, 2004 2:30 PM -0500 Joshua Baker-LePain
[EMAIL PROTECTED] wrote:
[snip]
Maybe I should try dd with bs=16M? But will that pad the output file
with an unacceptable-to-tar chunk at the end since the tapefile is
unlikely to be an exact multiple of 16M?
In my experience,
with
Exabyte 820 Eagle drives. It was a pain, and there were loads of
errors, but I got most of the data off the tapes.
--jonathan
Joshua Baker-LePain wrote:
On Thu, 11 Mar 2004 at 2:21pm, Jonathan Dill wrote
I would try amrestore -c to just dump the image off the tape, and then
do
On Thu, 11 Mar 2004 at 8:34pm, Gerhard den Hollander wrote
I am assuming the disk you are writing to, the machine the tape drive is
attached to and the machine on which the amrestore is running are all the
same ?
Yep.
If not, your network might be the bottleneck.
I was originally doing
On Thu, 11 Mar 2004 at 2:52pm, Jonathan Dill wrote
Hmm. Check also mt status to make sure the drive thinks that the
blocksize is 0 if not change it with mt blksize. The files will be
perfectly fine with bs=16M. gzip and/or tar will probably give a warning
bitching about the nulls at the
Have you taken a look around in /proc/scsi? /proc/scsi/scsi should give
you some basic information, and the subdir for your driver should give
more details, such as what transfer rate the drive is negotatiated at,
for example /proc/scsi/aic7xxx/0 for an Adaptec 2940 series. Perhaps
there was
On Thu, Mar 11, 2004 at 03:29:23PM -0500, Joshua Baker-LePain wrote:
But 4M works. ?? And to add insult to injury, that's going at about
70K/s.
What about our old oft occuring observations on scsi devices,
Writing through that cable uses different wires than reading.
--
Jon H.
chain). 'amrestore -r' chugged right along at what
looked to be full speed for the tape drive.
The drives are the same model (SDX-700C), although I only recently added
the second (slow) one, so it has less usage and a newer firmware revision.
I cleaned the slow drive once, and that made
HI,
WE have changed the hostname of a computer which was called linux and
now it is called backup-server on Suse Enterprise 8. WE changed all the
required .amandahosts, /etc/HOSTNAME, /etc/hosts; then rebooted the
system. The amdump works ok, but amrestore gives me the following error
the
system. The amdump works ok, but amrestore gives me the following error.
This is urgent.
help will be much appreciated
thanks
What error are you getting?
Frank
--
Frank Smith [EMAIL PROTECTED]
Sr. Systems Administrator
I'm hoping someone can clear something up for me. Does amrestore
uncompress an image as it restores it? The reason I ask is that I had
an image on an amanda tape that was supposedly compressed via gzip. The
amanda mail report indicated that the original KB was about 5.1Gb, and
Out-KB
On Wed, Jan 21, 2004 at 03:06:30PM -0500, Aaron Smith wrote:
I'm hoping someone can clear something up for me. Does amrestore
uncompress an image as it restores it?
The amrestore(8) man page says it does.
Amrestore normally writes output files in a format understood by
restore or tar
DOH! Never mindI read the man page for amrecover...hehe
Yeah, yeah, I knowRTFM.
On Wed, 2004-01-21 at 15:06, Aaron Smith wrote:
I'm hoping someone can clear something up for me. Does amrestore
uncompress an image as it restores it? The reason I ask is that I had
an image
Paul Bijnens wrote:
One important point is that you need to REWIND the tape before starting
amrestore, or you need to MANUALLY position the tape to the beginning
of your backup image using commands like 'mt ... fsf 123'.
If using amanda 2.4.4 or later you may add -f 123 to rewind and
skip
On Fri, 9 Jan 2004 at 12:55pm, Martin wrote
I've been trying to do a manual restore as well, just in case an
amrecover/amrestore is not possible. Paul, you say that it is possible to
skip over backup images by using the fsf parameter. That's true, but is
there any way of determining WHERE
Martin wrote:
Paul Bijnens wrote:
One important point is that you need to REWIND the tape before starting
amrestore, or you need to MANUALLY position the tape to the beginning
of your backup image using commands like 'mt ... fsf 123'.
If using amanda 2.4.4 or later you may add -f 123 to rewind
On Fri, 2004-01-09 at 07:23, Joshua Baker-LePain wrote:
You can run 'amtoc' after each night's backups, and store the results on
another machine. That gives you the order.
This is an awesome idea. This is why I follow this list. I probably
never would given amtoc a second thought otherwise.
Martin wrote:
Paul Bijnens wrote:
One important point is that you need to REWIND the tape before starting
amrestore, or you need to MANUALLY position the tape to the beginning
of your backup image using commands like 'mt ... fsf 123'.
If using amanda 2.4.4 or later you may add -f 123 to rewind
How do I use amrestore properly, although I've looked at the documentation
and various sites, I seem to have peculiar things happen when I attempt a
restore.
My server with tape drive is 'admin01' and my client to backup is
'webserver04'.
Should I be using:
amrestore -p /dev/nst0 webserver04
Using just:
amrestore /dev/nst0 webserver04
Everything seems to complete with no visible errors.
How do I make sure that 'webserver04' /dev/sda3 (the partition I backed up)
has now been restored?!
Dean
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf
Dean Pullen wrote:
Using just:
amrestore /dev/nst0 webserver04
Everything seems to complete with no visible errors.
How do I make sure that 'webserver04' /dev/sda3 (the partition I backed up)
has now been restored?!
First read the man page, and look at the examples in it.
amrestore itself does
PROTECTED]
Sent: 07 January 2004 15:52
To: Dean Pullen
Cc: [EMAIL PROTECTED]
Subject: Re: Using amrestore
Dean Pullen wrote:
Using just:
amrestore /dev/nst0 webserver04
Everything seems to complete with no visible errors.
How do I make sure that 'webserver04' /dev/sda3 (the partition I
is obviously what I'm retrieving from the tape drive.
So what do I do with this file?
-Original Message-
From: Paul Bijnens [mailto:[EMAIL PROTECTED]
Sent: 07 January 2004 15:52
To: Dean Pullen
Cc: [EMAIL PROTECTED]
Subject: Re: Using amrestore
Dean Pullen wrote:
Using just:
amrestore
PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 07 January 2004 10:37
To: Dean Pullen
Cc: 'Paul Bijnens'; [EMAIL PROTECTED]
Subject: Re: Using amrestore
If it is a dump file you could type
restore -f webserver04._dev_sda3.20040107.0 -xwhatever directory you would
like to extract
Dean Pullen wrote
the backup every time, as opposed
to a specific directory. How would I do this?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 07 January 2004 10:37
To: Dean Pullen
Cc: 'Paul Bijnens'; [EMAIL PROTECTED]
Subject: Re: Using amrestore
If it is a dump file you
: 20031210
amidxtaped: time 0.000: Ready to execv amrestore with:
path = /usr/sbin/amrestore
argv[0] = amrestore
argv[1] = -h
argv[2] = -p
argv[3] = file:/file1
argv[4] = ^hccweb$
argv[5] = ^/etc$
argv[6] = 20031210
amrestore: could not stat file:/file1
amidxtaped
On Mon, Dec 29, 2003 at 04:03:23PM -0600, Josh Welch wrote:
tapedev file:/backup/ # the no-rewind tape device to be used
I've never used the file driver in production, only played with it
a little, but I think this needs to be a file, not a directory. Perhaps
someone else can clarify
Frank Smith wrote:
--On Friday, December 12, 2003 12:38:26 -0500 jessica blackburn [EMAIL PROTECTED] wrote:
Here is my amanda.conf file:
...
tpchanger chg-multi # the tape-changer glue script
tapedev file:/backup/ # the no-rewind tape device to be used
I've never used the file driver in
: time 0.000: 20031210
amidxtaped: time 0.000: Ready to execv amrestore with:
path = /usr/sbin/amrestore
argv[0] = amrestore
argv[1] = -h
argv[2] = -p
argv[3] = file:/file1
argv[4] = ^hccweb$
argv[5] = ^/etc$
argv[6] = 20031210
amrestore: could not stat file:/file1
amidxtaped
to execv amrestore with:
path = /usr/sbin/amrestore
argv[0] = amrestore
argv[1] = -h
argv[2] = -p
argv[3] = file:/file1
argv[4] = ^hccweb$
argv[5] = ^/etc$
argv[6] = 20031210
amrestore: could not stat file:/file1
amidxtaped: time 0.004: amrestore terminated normally with status: 2
: time 0.000: -h
amidxtaped: time 0.000: -p
amidxtaped: time 0.000: file:/file1
amidxtaped: time 0.000: ^hccweb$
amidxtaped: time 0.000: ^/etc$
amidxtaped: time 0.000: 20031210
amidxtaped: time 0.000: Ready to execv amrestore with:
path = /usr/sbin/amrestore
argv[0] = amrestore
argv[1] = -h
$
amidxtaped: time 0.000: 20031210
amidxtaped: time 0.000: Ready to execv amrestore with:
path = /usr/sbin/amrestore
argv[0] = amrestore
argv[1] = -h
argv[2] = -p
argv[3] = file:/file1
argv[4] = ^hccweb$
argv[5] = ^/etc$
argv[6] = 20031210
amrestore: could not stat file:/file1
amidxtaped
able to backup fine.
I restore with the following
amrestore -p /dev/nst0 machinename /u05/archive | tar xvfp -
When i restore however i get the following
my files first get restored and then i get
amrestore: 2: reached end of information
is this something to be concerned about do you
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
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
) 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
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
Hi all,
I'm trying to do a remote recovery of a Solaris server, I have booted to
single user mode and create a newfs.
when I use:
rsh -n -l user server /usr/local/sbin/amrestore -p /dev/rmt/0bn server
name / | ufsrestore rvbfd 2 - for the level 0
the restore works fine.
I then load
On Thu, Aug 21, 2003 at 03:28:24PM +0100, Keith Foster wrote:
[Solaris restore]
Dump date: Tue Aug 19 18:09:34 2003
Dumped from: Mon May 19 05:32:04 2003
Level 1 dump of / on server:/dev/md/dsk/d0
[...]
Incremental volume too high
I don't understand where it gets the Dumped from date,
On Thu, Aug 21, 2003 at 03:28:24PM +0100, Keith Foster wrote:
I'm trying to do a remote recovery of a Solaris server, I have booted to
rsh -n -l user server /usr/local/sbin/amrestore -p /dev/rmt/0bn server
name / | ufsrestore rvbfd 2 - for the level 0
I then load the incremental tape
On Fri, Jul 25, 2003 at 02:29:46PM +0200, Andreas Ntaflos wrote:
Anyone have an idea? The logs (amdump.*, log.date.*) don't give much
more information apart from telling me that the `dump to drive failed'
and it `will try again'. Not of much help. Any pointers where I should
have a look?
Look
is an array mounted on /d on mobilkom.
When trying to use amrestore on such a `tape' (file:/dump/normal02 for
example) I get an error like this:
[EMAIL PROTECTED] root]# amrestore -p file:/dump/normal02 mobilkom md0 |
restore -ivb 2 -f -
amrestore: WARNING: not at start of tape, file numbers
Amanda version - various
Sorry, searched the amanda_users searchable archived but didn't
see anything on this.
We see messages like amrestore: gzip, restore ok, trailing garbage ingored
and have always assumed it resulted from DD writing trailing garbage at
the end of the last (fixed length
Now that I know the date they want to see the database from, I've tried
(twice) to amrestore the files in a safe location, but with no joy.
After setting the host/disk/path/date to restore, I get the following
from amrestore:
---
amrecover extract
Extracting files using tape drive /dev/nst0
I've just finished setting up amanda here, and am making sure I know how to
do full-volume restores with amrestore before disaster strikes and I
_NEED_ to know. That said, I'm running into a problem: I have a level 0
dump of a filesystem from one server, and am trying to restore
--On Monday, June 23, 2003 16:46:28 -0400 Jon Sippel [EMAIL PROTECTED] wrote:
I've just finished setting up amanda here, and am making sure I know how to
do full-volume restores with amrestore before disaster strikes and I
_NEED_ to know. That said, I'm running into a problem: I have
On Monday 23 June 2003 16:46, Jon Sippel wrote:
I've just finished setting up amanda here, and am making sure I know
how to do full-volume restores with amrestore before disaster
strikes and I _NEED_ to know. That said, I'm running into a
problem: I have a level 0 dump of a filesystem from
On Monday 23 June 2003 17:42, Frank Smith wrote:
--On Monday, June 23, 2003 16:46:28 -0400 Jon Sippel
[EMAIL PROTECTED] wrote:
I've just finished setting up amanda here, and am making sure I
know how to do full-volume restores with amrestore before
disaster strikes and I _NEED_ to know
On Thursday 20 March 2003 01:31 am, Madhvi Gokool wrote:
[EMAIL PROTECTED] restoredir]$ amrestore /dev/st0 osama /
It looks like you're using the auto-rewinding tape device. If you try
'/dev/nst0', it might work better for you.
This is my second try posting this... I hope I am not screwing
something up...
Hi, thanks for the great program. I am having a problem with
amrestore/amrecover. When amdump goes off, everything is fine, and
the report says everything is fine. When I try amrestore though, I
get:
[EMAIL
PROTECTED] restoredir]$ amrestore /dev/st0 osama /
1.. amrestore: 0: skipping start of tape: date 20030318 label DailySet15
2.. amrestore: 1: skipping osama.hda5.20030318.0
3.. amrestore: 2: skipping osama.hda1.20030318.0
4.. amrestore: 3: restoring osama._.20030318.0
5.. amrestore
On Mon, 17 Mar 2003, Jon LaBadie wrote:
On Mon, Mar 17, 2003 at 10:26:14AM +0530, T. Bhaskar Reddy wrote:
Hi there,
I am using amanda 2.4.4. Using amanda i have dumped a directory on
localhost. While i am trying restore it displays the following message
amrestore: 0: restoring
Hi there,
I am using amanda 2.4.4. Using amanda i have dumped a directory on
localhost. While i am trying restore it displays the following message
amrestore: 0: restoring localhost._home_amanda_QA.20030315.0
the commanda i executed is
/usr/local/sbin/amrestore 1.localhost
On Mon, Mar 17, 2003 at 10:26:14AM +0530, T. Bhaskar Reddy wrote:
Hi there,
I am using amanda 2.4.4. Using amanda i have dumped a directory on
localhost. While i am trying restore it displays the following message
amrestore: 0: restoring localhost._home_amanda_QA.20030315.0
Hi,
when I run the command amrestore -p /dev/rmt/1n scuba /boot | tar -pxv on
the tape server itself,
I manage to restore the files however the files are restored in a new
directory structure. A number of new directories are created and also the
files loose permissions.
any idea how this can
liam pace wrote:
Hi,
when I run the command amrestore -p /dev/rmt/1n scuba /boot | tar -pxv on
the tape server itself,
I manage to restore the files however the files are restored in a new
directory structure. A number of new directories are created and also the
files loose permissions.
any idea
Since I'm having trouble with my tool of choice (amrecover) today (see my
previous mails on this(, I'm trying to simply get a backup set off of a
Amanda tape using amrestore (which I have never used before).
I see the set I want going by in amverify, and amrestore. In amrestore it's
listed
On Sat, 25 Jan 2003, John R. Jackson wrote:
Sorry it took so long to get back to you.
I was able to reproduce (and even fix :-) the problem. Give the
following patch a try.
Hi John.
This patch works great. Thanks for your time/efforts.
--david
... I'm trying to simply get a backup set off of a
Amanda tape using amrestore (which I have never used before).
You have used it (via amrecover), you just didn't know it :-).
I see the set I want going by in amverify, and amrestore. In amrestore it's
listed as set 35 (phse7
Here's what I get when I run the patched 2.4.3 version:
# /amanda/sbin/amrestore /dev/rmt0.1 shrike /home
amrestore: could not stat /dev/rmt0.1: A memory address is not in the
address space for the process.
Sorry it took so long to get back to you.
I was able to reproduce (and even fix
You try to recover from the device PSI_ASM_DailySet130,
amrestore expect a device name, not a label.
Use the settape command in amrecover (eg. settape /dev/nst0)
Jean-Louis
On Wed, Jan 22, 2003 at 09:26:57AM -0500, [EMAIL PROTECTED] wrote:
Hello there,
I've managed to get a tapeless backup
: PSI_ASM_DailySet130
amidxtaped: time 0.001: ^pc3690$
amidxtaped: time 0.001: ^/home$
amidxtaped: time 0.002: 20030120
amidxtaped: time 0.002: Ready to execv amrestore with:
path = /usr/local/sbin/amrestore
argv[0] = amrestore
argv[1] = -h
argv[2] = -p
argv[3] = PSI_ASM_DailySet130
argv[4] = ^pc3690$
argv[5
Hi again.
Quick summary of the thread:
Replaced the tape drive in backup server. After that, got problems with
amrestore:
The backup ran for the first time tonight. The output that amdump sent
me after the backup looked entirely normal, and also I could restore
some files from the tape
Hi,
AFAIK you'll have to rewind the tape explicitly between amdump and
amverify, as neither
amdump nor amverify do that for you.
Christoph
Toomas Aas schrieb:
Hi again.
Quick summary of the thread:
Replaced the tape drive in backup server. After that, got problems with
amrestore
Hi!
Christoph Scheeder wrote:
AFAIK you'll have to rewind the tape explicitly between amdump and
amverify, as neither
amdump nor amverify do that for you.
Christoph
I tried running mt rewind and then amverify from command line.
Still the same errors...
--
Toomas Aas | [EMAIL PROTECTED] |
Toomas Aas wrote:
Hi again.
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore: 0: reached end of information
** No header
0+0 in
0+0 out
Whenever (very seldomly)I get the not at start of tape error, I ran
the vtblc program that lists the contents
201 - 300 of 435 matches
Mail list logo
