Re: amrestore and split dumps

* Jean-Louis Martineau [20160426 14:11]: > You can't do that with amrestore. > > Use amfetchdump to do that. OK! I'm aware of amfetchdump. I was asking because I'm preparing an archive to be shipped offsite for some people that don't have the archive's logs and Amanda installed, for that matter

Re: amrestore blocksize

Stefan, The -b argument of amrestore is not working in 3.2.1 The attached patch was commited a long time ago to fix it. Jean-Louis On 12/03/2012 10:01 AM, Stefan Gustafsson wrote: Hi, We have an running amanda environment (Amanda-3.2.1) based on Ubuntu 11.10 backing up some XEN hosts. Last

Re: amrestore, retriving ufsdump, bad filesystem block size

Work-around --- Looking in google I didn't see anything amanda specific but did find articles talking about the zfs file system. The client DLE is UFS, the work area I restored to is ZFS. I copied one of the smaller dmp files over to /tmp which is UFS and was able to read it fine. I am

Re: amrestore bug with split dumps (and workaround)

On Wed, Feb 24, 2010 at 6:40 PM, Christopher wrote: > Was it always that way?  I haven't used amrestore since amfetchdump came > out. Yes. Or, if not, it was a bug :) > I'll spend some time tracking down exactly what is not being stripped > out.  Maybe stderr is being included?  My C programing

Re: amrestore bug with split dumps (and workaround)

Hello... On Wed, 2010-02-24 at 17:33 -0600, Dustin J. Mitchell wrote: > On Wed, Feb 24, 2010 at 5:08 PM, Christopher > wrote: > > amfetchdump does not seem to have this problem, but you cannot run > > amfetchdump while amdump is running (which would be a cool feature ;) > > We're working on tha

Re: amrestore bug with split dumps (and workaround)

On Wed, Feb 24, 2010 at 5:08 PM, Christopher wrote: > amfetchdump does not seem to have this problem, but you cannot run > amfetchdump while amdump is running (which would be a cool feature ;) We're working on that. In fact, I think it should be doable in 3.1. I'll make a note to test it before

Re: amrestore and tape rewinding

On Wednesday 27 May 2009, Darin Perusich wrote: >Gene Heskett wrote: >> On Tuesday 26 May 2009, Darin Perusich wrote: >>> Dustin J. Mitchell wrote: On Tue, May 26, 2009 at 2:56 PM, Darin Perusich wrote: > Why does 'amrestore' always rewind the tape when I go to restore > som

Re: amrestore and tape rewinding

Gene Heskett wrote: > On Tuesday 26 May 2009, Darin Perusich wrote: >> Dustin J. Mitchell wrote: >>> On Tue, May 26, 2009 at 2:56 PM, Darin Perusich >>> >>> wrote: Why does 'amrestore' always rewind the tape when I go to restore something? This is something I just started seeing after

Re: amrestore and tape rewinding

On Tue, May 26, 2009 at 2:56 PM, Darin Perusich wrote: > Why does 'amrestore' always rewind the tape when I go to restore > something? This is something I just started seeing after upgrading to > 2.6.x, it wasn't happening with previous versions, 2.5.2. The man page > says I can use '-f #' to fast

Re: amrestore and tape rewinding

On Tuesday 26 May 2009, Darin Perusich wrote: >Dustin J. Mitchell wrote: >> On Tue, May 26, 2009 at 2:56 PM, Darin Perusich >> >> wrote: >>> Why does 'amrestore' always rewind the tape when I go to restore >>> something? This is something I just started seeing after upgrading to >>> 2.6.x, it wasn

Re: amrestore and tape rewinding

On Tue, May 26, 2009 at 4:32 PM, Darin Perusich wrote: > Being able to specify with an argument, -n or whatever, to not rewind > the tape would be convenient, a time saver, and make for more efficient > recovery I would think. One option may be to add a "no-rewind" property to the tape device. I'

Re: amrestore and tape rewinding

Dustin J. Mitchell wrote: > On Tue, May 26, 2009 at 2:56 PM, Darin Perusich > wrote: >> Why does 'amrestore' always rewind the tape when I go to restore >> something? This is something I just started seeing after upgrading to >> 2.6.x, it wasn't happening with previous versions, 2.5.2. The man pa

Re: amrestore and multiple tapes

Used amfetchdump and after 3hours of restore 10M files, it just throwed a amfetchdump: 3006: restoring split dumpfile: date 20090424 host hostname disk /fileset part 2992/UNKNOWN lev 0 comp .gz program /bin/tar amfetchdump: missing file header block could not fsf /dev/nst0: Input/output error

Re: amrestore and multiple tapes

It neither works, then you must use dd! For each file on tape position the tape on the file dd if=/dev/nst0 of=file.[number] bs=32k skip=1 concatenate all file.[number] files. 'amadmin [config] find hostname /fileset' list all files on tape you need. You can also try to upgrade the server t

Re: amrestore and multiple tapes

On Wed, May 6, 2009 at 5:35 AM, Franck GANACHAUD wrote: > I've been trying to use amrestore but the backup is around 250Go splitted > over 5 tapes and I'm not successful so far. amrestore is restoring the > fileset using 10M size files. First, you should be using a much larger split size than 10M

Re: amrestore and multiple tapes

It is easier to restore a splitted dump with amfetchdump. It will write a 250Go file. There is no way to automatically rebuild index from tape. Jean-Louis Franck GANACHAUD wrote: Hello, Server and client are 2.5.1p1 on debian etch I've been trying to use amrestore but the backup is around 2

Re: amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

On Sun, Mar 01, 2009 at 07:28:32PM -0700, John Hein wrote: > Charles Curley wrote at 18:54 -0700 on Mar 1, 2009: > > On Sun, Mar 01, 2009 at 05:49:20PM -0700, John Hein wrote: > > > man amrecover (see -s & -t). I don't know if there is a run-time > > > configuration option for these (I didn't

Re: amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

Charles Curley wrote at 18:54 -0700 on Mar 1, 2009: > On Sun, Mar 01, 2009 at 05:49:20PM -0700, John Hein wrote: > > man amrecover (see -s & -t). I don't know if there is a run-time > > configuration option for these (I didn't see one after a quick read > > of the man pages) - if so, -o would

Re: amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

On Sun, Mar 01, 2009 at 05:49:20PM -0700, John Hein wrote: > Charles Curley wrote at 16:53 -0700 on Mar 1, 2009: > > On Sun, Mar 01, 2009 at 02:18:27PM -0700, Charles Curley wrote: > > > On Sun, Mar 01, 2009 at 12:50:50PM -0700, John Hein wrote: > > > > Do you know how your stock ubuntu build o

Re: amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

John Hein wrote at 17:49 -0700 on Mar 1, 2009: > man amrecover (see -s & -t). I don't know if there is a run-time > configuration option for these (I didn't see one after a quick read > of the man pages) - if so, -o would be of no help. ^^^ s/so/not/

Re: amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

Charles Curley wrote at 16:53 -0700 on Mar 1, 2009: > On Sun, Mar 01, 2009 at 02:18:27PM -0700, Charles Curley wrote: > > On Sun, Mar 01, 2009 at 12:50:50PM -0700, John Hein wrote: > > > Do you know how your stock ubuntu build of amanda was configured (the > > > args to configure)? > > > >

Re: amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

On Sun, Mar 01, 2009 at 02:18:27PM -0700, Charles Curley wrote: > On Sun, Mar 01, 2009 at 12:50:50PM -0700, John Hein wrote: > > > > > Do you know how your stock ubuntu build of amanda was configured (the > > args to configure)? > > > > I just noticed that the request came from 'localhost' which

Re: amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

On Sun, Mar 01, 2009 at 12:50:50PM -0700, John Hein wrote: > > Do you know how your stock ubuntu build of amanda was configured (the > args to configure)? > > I just noticed that the request came from 'localhost' which does > not match your .amandahosts entry. Short of pulling in the source pac

Re: amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

Charles Curley wrote at 11:48 -0700 on Mar 1, 2009: > On Sun, Mar 01, 2009 at 10:11:38AM -0700, John Hein wrote: > > Charles Curley wrote at 08:29 -0700 on Mar 1, 2009: > > > r...@dragon:/home/ccurley/projects/ror# amrecover -C > > /etc/amanda/DailySet1 > > > AMRECOVER Version 2.5.2p1. Co

Re: amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

On Sun, Mar 01, 2009 at 10:11:38AM -0700, John Hein wrote: > Charles Curley wrote at 08:29 -0700 on Mar 1, 2009: > > r...@dragon:/home/ccurley/projects/ror# amrecover -C /etc/amanda/DailySet1 > > AMRECOVER Version 2.5.2p1. Contacting server on localhost ... > > NAK: user root from localhost is

Re: amrestore: NAK: user root from localhost is not allowed to execute the service amindexd

Charles Curley wrote at 08:29 -0700 on Mar 1, 2009: > r...@dragon:/home/ccurley/projects/ror# amrecover -C /etc/amanda/DailySet1 > AMRECOVER Version 2.5.2p1. Contacting server on localhost ... > NAK: user root from localhost is not allowed to execute the service > amindexd: Please add "aminde

Re: amrestore

Krahn, Anderson wrote: After creating a amada-client.conf in /etc/Amanda.. I get the following error /opt/amanda/server/sbin/amrecover Full AMRECOVER Version 2.5.2p1. Contacting server on prdapp16-qa-master ... NAK: amindexd: invalid service, add 'amindexd' as argument to amandad #cat /

RE: amrestore

After creating a amada-client.conf in /etc/Amanda.. I get the following error /opt/amanda/server/sbin/amrecover Full AMRECOVER Version 2.5.2p1. Contacting server on prdapp16-qa-master ... NAK: amindexd: invalid service, add 'amindexd' as argument to amandad #cat /etc/amanda/amanda-client.c

Re: amrestore and tape changers: has it changed since 2.4.4p3?

On 9/13/07, Francis Galiegue <[EMAIL PROTECTED]> wrote: > One question though: is it really the role of amrecover to drive the tape > changer? Isn't that done on the server side? What if I decide to upgrade the > server to the latest 2.5.x but leave clients with 2.4.x? Yes, that's correct -- I was

Re: amrestore and tape changers: has it changed since 2.4.4p3?

Le jeudi 13 septembre 2007, vous avez écrit : [...] > > That's still the case with amrestore, which is considered the > "bare-metal" recovery tool of the three currently available. In the > copy of 2.4.4p1 I have available, amfetchdump does not exist, but that > tool is able to use a changer to f

Re: amrestore does not work "NAK: amindexd: invalid service"

Hi, first i will use amoldrecover for recover ;-) why didn´t i remember this before... Thats not solving the problem, but it is a work arround. This afternoon i will leave to vacation. Will work on this at a later time. Thanks for help. bye B² Bjoern B schrieb: Hi, Jean-Louis Martineau s

Re: amrestore does not work "NAK: amindexd: invalid service"

Hi, Jean-Louis Martineau schrieb: Can you upgrade to 2.5.2p1? would not to be my preferred way. I like my aptitude get update thing. But i will look if there is a real reason for not upgrading. When i upgrade i will use the configure options for the 2.5.1.p1 Debian package or what should i t

Re: amrestore does not work "NAK: amindexd: invalid service"

Can you upgrade to 2.5.2p1? Jean-Louis Bjoern B wrote: Hi, Jean-Louis Martineau schrieb: The only way to get this error is if amandad doesn't get "amindexd" as argument. But it is listed in the server_args of /etc/xinetd.d/amanda You should recheck that file, verify that it doesn't have char

Re: amrestore does not work "NAK: amindexd: invalid service"

Hi, Jean-Louis Martineau schrieb: Frank Smith wrote: amandad: time 0.000: amindexd: invalid service amandad: time 0.000: sending NAK pkt: < ERROR amindexd: invalid service My interpretation of this error is that it couldn't find the service named amindexd. Is this something new in 2

Re: amrestore does not work "NAK: amindexd: invalid service"

Hi, Jean-Louis Martineau schrieb: The only way to get this error is if amandad doesn't get "amindexd" as argument. But it is listed in the server_args of /etc/xinetd.d/amanda You should recheck that file, verify that it doesn't have character you don't see. I have retyped the server_args in

Re: amrestore does not work "NAK: amindexd: invalid service"

Frank Smith wrote: amandad: time 0.000: amindexd: invalid service amandad: time 0.000: sending NAK pkt: < ERROR amindexd: invalid service My interpretation of this error is that it couldn't find the service named amindexd. Is this something new in 2.5, as in 2.4 it was named amandaidx

Re: amrestore does not work "NAK: amindexd: invalid service"

The only way to get this error is if amandad doesn't get "amindexd" as argument. But it is listed in the server_args of /etc/xinetd.d/amanda You should recheck that file, verify that it doesn't have character you don't see. Verify that you doesn't have an amandad process already running. Jean-

Re: amrestore does not work "NAK: amindexd: invalid service"

Bjoern B wrote: > Hi, > > you are right i mean amrecover. sorry > > Jean-Louis Martineau schrieb: >> Your config looks good, are you sure you restarted xinetd? > > I did a /etc/init.d/xinetd restart > > To be sure, i have done a server restart and tested it again. > Same message. > >> amrecove

Re: amrestore does not work "NAK: amindexd: invalid service"

Hi, you are right i mean amrecover. sorry Jean-Louis Martineau schrieb: Your config looks good, are you sure you restarted xinetd? I did a /etc/init.d/xinetd restart To be sure, i have done a server restart and tested it again. Same message. amrecover in 2.4.* will use the amandaidx and a

Re: amrestore does not work "NAK: amindexd: invalid service"

amrestore doesn't use the network and can't fail with "NAK: amindexd: invalid service". amrestore and amrecover are two distinct commands, don't say amrestore when you talk about amrecover, it's really confusing. Your config looks good, are you sure you restarted xinetd? amrecover in 2.4.* wil

Re: Amrestore

On Saturday 05 May 2007 09:13, Donofrio, Lewis wrote: > Do I still have to use another tty to change tapes with amanda 2.5.x? Amrestore only supports one tape at a time, so you can change tapes with the same TTY. Amrecover and amfetchdump know how to use the changer now, so you don't need anoth

Re: amrestore help

I'd love to, but see my message below. I get an error when I try to run amrecover. Is there a way to get past this error? Guy Dallaire wrote: amrecover is easier to use 2007/4/27, Steven Settlemyre <[EMAIL PROTECTED] >: actually, i found how to put the desired

Re: amrestore help

actually, i found how to put the desired tape into the active slot of the changer. But when i do "amrestore /dev/nst0 lollipop /files1" I get this: amrestore: missing file header block amrestore: 2: skipping zoo._.20070419.1.1 amrestore: missing file header block amrestore: 6: skipping marl

Re: amrestore with disk with spaces in name

Downloaded an compiled amanda-2.5.1p3-20070420 Fixed the problem. Thanks, Michael On 26/04/07, Jean-Louis Martineau <[EMAIL PROTECTED]> wrote: Michael, This bug is already fix in the latest 2.5.1p3 snapshot. You can download it from http://www.zmanda.com/community-builds.php The snapshot have

Re: amrestore with disk with spaces in name

Michael, This bug is already fix in the latest 2.5.1p3 snapshot. You can download it from http://www.zmanda.com/community-builds.php The snapshot have many bugs fixed since the release of 2.5.1p3. Jean-Louis Michael Keightley wrote: I am trying to use amrecover with with directory names in th

Re: amrestore with disk with spaces in name

Tried this already: amrecover> setdisk "/opt/test\ directory" 501 Disk myhost:"\"/opt/test\\ directory\"" is not in your disklist. Michael On 26/04/07, Stefan G. Weichinger <[EMAIL PROTECTED]> wrote: Michael Keightley schrieb: > I am trying to use amrecover with with directory names in the dis

Re: amrestore with disk with spaces in name

Michael Keightley schrieb: > Any idea how to fix this? Problem is lots of Windows folders that we want > to add to the disklist contain spaces. Additional thought: Read "man amanda", section DISKLIST FILE. You could use disknames without spaces, like in amclient mydiskname "/opt/test director

Re: amrestore with disk with spaces in name

Michael Keightley schrieb: > I am trying to use amrecover with with directory names in the disklist > file which > contain spaces. Having no joy, e.g. with a test setup: > > % cat disklist > myhost "/opt/test directory"comp-user-tar > > % amrecover testset > AMRECOVER V

Re: amrestore with tar empty directories at mountpoints

Jon LaBadie wrote: On Sun, Sep 24, 2006 at 02:23:56PM -0400, Nick Brockner wrote: Hi All. I am new to amanda, and maybe I just don't understand how it works, but here is my problem: I have a remote machine that I back up over my network. The backups and everything go fine. I am doing a

Re: amrestore with tar empty directories at mountpoints

On Sun, Sep 24, 2006 at 02:23:56PM -0400, Nick Brockner wrote: > Hi All. > > I am new to amanda, and maybe I just don't understand how it works, but > here is my problem: > > I have a remote machine that I back up over my network. The backups and > everything go fine. I am doing a disaster re

Re: AMRESTORE

Never mind I found the -C option and that worked fine. Thanks for any replies. James Wilson wrote: I am trying to do a test restore from amanda and I get this error " Could not read config file /etc/amanda/DailySet1/amanda.conf!" I don't have a DailySet1 directory. Where do I change the path f

Re: amrestore: missing file header block

Iulian Topliceanu wrote: Iulian Topliceanu wrote: Hi, When trying to [EMAIL PROTECTED] recover]# amrestore /dev/nst0 baal /data/data0/conf amrestore: missing file header block amrestore: 2: skipping pbx2._etc.20060503.1 amrestore: missing file header block amrestore: 5: skipping pbx1._etc

Re: amrestore: missing file header block

> Iulian Topliceanu wrote: > >>Hi, >> >>When trying to >> >>[EMAIL PROTECTED] recover]# amrestore /dev/nst0 baal /data/data0/conf >>amrestore: missing file header block >>amrestore: 2: skipping pbx2._etc.20060503.1 >>amrestore: missing file header block >>amrestore: 5: skipping pbx1._etc.200605

Re: amrestore: missing file header block

Iulian Topliceanu wrote: Hi, When trying to [EMAIL PROTECTED] recover]# amrestore /dev/nst0 baal /data/data0/conf amrestore: missing file header block amrestore: 2: skipping pbx2._etc.20060503.1 amrestore: missing file header block amrestore: 5: skipping pbx1._etc.20060503.1 amrestore: mis

Re: amrestore: error reading file header: Device or resource busy

Cameron Matheson wrote: Extracting files using tape drive /dev/nst1 on host localhost. Load tape DailySet1037 now Continue [?/Y/n/s/t]? y tar: ./var/cache/man/index.db: invalid sparse archive member tar: Skipping to next header tar: Archive contains obsolescent base-64 headers tar: ./var/cache/ma

Re: amrestore: error reading file header: Device or resource busy

Just a quick follow-up: On Wed, May 10, 2006 at 03:17:16PM -0600, Cameron Matheson wrote: > Device or resource busy? I haven't seen it do this before. I'm > assuming it means my tape-drive? I'm not sure why it would be busy, but > does anyone know what I could to do fix this? I tried running '

Re: amrestore/dump failing

David Gitman wrote: I'm receiving a "restore: Tape is not a dump tape" message when trying to restore a amrestore file via restore. I'm running the amrestore or restore command incorrectly? $ amrestore /dev/rst0 host1 amrestore: 1: restoring host1._.20060116.1 amrestore: 3: restoring host

Re: amrestore/dump failing

David Gitman schrieb: $ restore -i -v -b 2 -f host1._.20060116.1 Verify tape and initialize maps restore: Tape is not a dump tape Did you use program "GNUTAR" inside of your dumptype? If yes, then you have to use tar to restore the data also. Stefan

Re: amrestore: could not stat disklist:/var2/amandadumps/tape02

Kevin, This is the content of 1.myhost.mynetwork.com._etc_amanda.0 AMANDA: FILE 20060109 myhost.mynetwork.com /etc/amanda lev 0 comp .gz program /bin/tar To restore, position tape at start of file and run: dd if= bs=32k skip=1 | /usr/bin/gzip -dc | bin/tar -f... - Just like what you e

Re: amrestore: could not stat disklist:/var2/amandadumps/tape02

did the amdump run successfully? 1) go to backup-dir/data 2) look for the file 1.myhost.mynetwork.com._etc_amanda.0 3) what does the header of the above file say? it should be something similar to AMANDA: FILE 20060105 myhost.mynetwork.com /etc/amanda/ lev 0 comp .gz program /bin/amgtar

Re: amrestore: could not stat disklist:/var2/amandadumps/tape02

Hi Kevin, I did run multiple daily dumps in a day but it was okay before I changed amgtar permission etc. I'll run once a day and see if there is any changes after 5 days of full dumps. Following is the latest amtrmidx: /tmp/amanda/amtrmidx.20060109170452.debug amtrmidx: debug 1 pid 8319 ruid 3

Re: amrestore: could not stat disklist:/var2/amandadumps/tape02

Ong Loeng Seng wrote: Hi Kevin, Hi Ong Loeng, I have done quite a bit of amrecover testing on 2.4.5 and I know it works very well. In /tmp/amanda directory, find the latest amindexd*.debug see if there is any error after the line amindexd: uncompress command: /usr/bin/gzip -dc .. -

Re: amrestore: could not stat disklist:/var2/amandadumps/tape02

On Sun, Jan 08, 2006 at 09:54:51AM +1100, Ong Loeng Seng wrote: > Hi Kevin, > > It does say that it can contact the index server. > This is the output when I run "amrecover -C DailySet1" > > AMRECOVER Version 2.4.5p1. Contacting server on myhost.mynetwork.com ... > 220 myhost AMANDA index server

Re: amrestore: could not stat disklist:/var2/amandadumps/tape02

Hi Kevin, It does say that it can contact the index server. This is the output when I run "amrecover -C DailySet1" AMRECOVER Version 2.4.5p1. Contacting server on myhost.mynetwork.com ... 220 myhost AMANDA index server (2.4.5) ready. 200 Access OK Setting restore date to today (2006-01-08) 200 Wo

Re: amrestore: could not stat disklist:/var2/amandadumps/tape02

did amrecover connect to the right index server? Do you see something similar to the following? AMRECOVER Version 2.4.5p1. Contacting server on ... ... 220 boston AMANDA index server (2.4.5p1) ready. 200 Access OK Ong Loeng Seng wrote: Hi Paul, I understand now. Thanks. However, I 've got

Re: amrestore: could not stat disklist:/var2/amandadumps/tape02

Hi Paul, I understand now. Thanks. However, I 've got another problem : when I run amrecover -C "DailySet1" ... Setting restore date to today (2006-01-05) 200 Working date set to 2006-01-05. Scanning /var/tmp... 200 Config set to DailySet1. 200 Dump host set to myhost.mynetwork.com. Trying disk

Re: amrestore: could not stat disklist:/var2/amandadumps/tape02

Ong Loeng Seng wrote: amrecover> settape myhost.mynetwork.com:amanda.conf:/var2/amandadumps/tape02 Using tape "amanda.conf:/var2/amandadumps/tape02" from server myhost.mynetwork.com. What is this??? Is that the name of your tape device??? When you are using the "FILE" driver, the name is: my

Re: amrestore from virtual tape

On Tue, Jul 19, 2005 at 12:26:16PM -0400, Jon LaBadie wrote: > > Ah, reading the man page and RTFMing the documentation helps a bit - I > Oh my gosh, now there is an idea, RTM ;)) My point exactly. ;) > > That, of course, would be a viable alternative to extracting the > > archives using amrestor

Re: amrestore from virtual tape

On Tue, Jul 19, 2005 at 05:53:00PM +0200, Michael Weiser wrote: > On Mon, Jul 18, 2005 at 04:01:25PM -0400, Jon LaBadie wrote: > > > > > The amrestore command is getting the file in uncompressed format > > > > even if it was compressed. If you want to transfer the compressed > > > > form I think

Re: amrestore from virtual tape

On Mon, Jul 18, 2005 at 04:01:25PM -0400, Jon LaBadie wrote: > > > The amrestore command is getting the file in uncompressed format > > > even if it was compressed. If you want to transfer the compressed > > > form I think you could add the -r option. > > I think it's -c actually and the manpage

Re: amrestore from virtual tape

On Sat, Jul 16, 2005 at 03:19:23PM -0400, Jon LaBadie wrote: > > > amrestore -p diskdir/slot30/2.machine._.3 | \ > > > ssh machine "cat - >~/restore/machine._.2.tar" > > Does anybody know if the above is the right way to restore complete > > archives from virtual tapes? > Don't have a rea

Re: amrestore from virtual tape

On Mon, Jul 18, 2005 at 07:50:12PM +0200, Michael Weiser wrote: > On Sat, Jul 16, 2005 at 03:19:23PM -0400, Jon LaBadie wrote: > > > The amrestore command is getting the file in uncompressed format > > even if it was compressed. If you want to transfer the compressed > > form I think you could ad

Re: amrestore from virtual tape

On Fri, Jul 15, 2005 at 09:07:02PM +0200, Michael Weiser wrote: > On Wed, Jul 13, 2005 at 07:22:10AM +0200, Michael Weiser wrote: > > > But I actually want to restore the archives not individual files. Can I > > do that with amrecover? > > > I found that I can do something like this though: > >

Re: amrestore from virtual tape

On Wed, Jul 13, 2005 at 07:22:10AM +0200, Michael Weiser wrote: > But I actually want to restore the archives not individual files. Can I > do that with amrecover? > I found that I can do something like this though: > amrestore -p diskdir/slot30/2.machine._.3 | \ > ssh machine "cat -

Re: amrestore from virtual tape

On Tue, Jul 12, 2005 at 10:15:14PM +0200, Geert Uytterhoeven wrote: > > I've set up a very nice backup to disk and everything works like a > > charm. I've just got one problem: How do I run an amrestore of one of > > the virtual tapes? Or can I just copy the files out of the tape > > directory? Ho

Re: amrestore from virtual tape

On Tue, 12 Jul 2005, Michael Weiser wrote: > I've set up a very nice backup to disk and everything works like a > charm. I've just got one problem: How do I run an amrestore of one of > the virtual tapes? Or can I just copy the files out of the tape > directory? How do I handle the usual 2GB chunki

Re: amrestore: how this works?

ÐÑÐÑÐÑÐÐ, 05-ÐÐÑ-2005 10:13 ÐÐ ÑÐÐÐ: > ÐÑÐÐÐ, 04-ÐÐÑ-2005 15:20 ÐÐ ÑÐÐÐ: > > ÐÐÑÐÑÐ ÐÐÑ wrote: > > > And that the parameter means itself "name-of-tape-device"? > > > It is somehow designated in amanda.conf? > > > If it is parameter "tapedev" at me it is designated as > > > " "file:/

Re: amrestore: how this works?

ÐÑÐÐÐ, 04-ÐÐÑ-2005 15:20 ÐÐ ÑÐÐÐ: > ÐÐÑÐÑÐ ÐÐÑ wrote: > > And that the parameter means itself "name-of-tape-device"? > > It is somehow designated in amanda.conf? > > If it is parameter "tapedev" at me it is designated as > > " "file:/amandatapes/daily" " and when I do > > amrecover dail

Re: amrestore problem:: URGENT!!!

ÐÑÐÑÐÑÐÐ, 05-ÐÐÑ-2005 01:19, Stefan G. Weichinger ÐÐ ÑÐÐÐ: > Hi, AndrÃs, > > on Montag, 04. April 2005 at 23:01 you wrote to amanda-users: > > AFAD> Now I have a problem restoring. I tried to use amrestore but it > AFAD> returns this to me > > AFAD> #amrecover > AFAD> AMRECOVER Version 2.4.4p4

Re: amrestore problem:: URGENT!!!

Hi, Andrés, on Montag, 04. April 2005 at 23:01 you wrote to amanda-users: AFAD> Now I have a problem restoring. I tried to use amrestore but it AFAD> returns this to me AFAD> #amrecover AFAD> AMRECOVER Version 2.4.4p4. Contacting server on localhost ... AFAD> amrecover: cannot connect to localho

Re: amrestore: how this works?

ÐÐÑÐÑÐ ÐÐÑ wrote: Hi all! Sorry, i am speak a little english and i'm a beginner in amanda. I have a question. I have some files for which I have made amdump. Then I have removed these files, and now I wish them to restore. How to me it to make by means of amanda? For example, the server refe

RE: Amrestore error

>I'm not sure whats happening at the 92 megabyte mark, but I would make >an observation re the block size you are using. To me, that seems >rather large. To do a checksum over a 4 megabyte block might >possibly be running into a math problem because much of that code is >legacy, and probably

Re: Amrestore error

On Sunday 20 February 2005 12:13, Spicer, Kevin (MBLEA it) wrote: >Hello, > >I'm having a strange problem with amrestore. I get an I/O error in > the middle of a restore and amrestore exits, but st0 device remains > busy and only a reboot can clear it. There is an error on the > console as follow

Re: amrestore problem, headers ok but no data

On Friday 21 January 2005 11:37, Brian Cuttler wrote: >Stefan, > >On Wed, Jan 19, 2005 at 10:48:54PM +0100, Stefan G. Weichinger wrote: >> BC> Major imporvement though still below the acceptable threshold. >> >> BC> Definitely looking like it was never an amanda issue, this >> looks to BC> be an un

Re: amrestore problem, headers ok but no data

Stefan, On Wed, Jan 19, 2005 at 10:48:54PM +0100, Stefan G. Weichinger wrote: > BC> Major imporvement though still below the acceptable threshold. > > BC> Definitely looking like it was never an amanda issue, this looks to > BC> be an underlying architecture problem. > > I hope that you spot the

Re: amrestore problem, headers ok but no data

Hi, Brian, on Mittwoch, 19. Jänner 2005 at 22:02 you wrote to amanda-users: BC> Major imporvement though still below the acceptable threshold. BC> Definitely looking like it was never an amanda issue, this looks to BC> be an underlying architecture problem. I hope that you spot the issue soon,

Re: amrestore problem, headers ok but no data

Info update only. Ok we've shutdown the Origin 300 and swapped the scsi daisy-chain around a little. At this point the SDLT in the shoebox was able to restore a large tar file without causing a SCSI reset and hanging the system. I then set the blocksize on the SDLT in the jukebox and relable

Re: amrestore problem, headers ok but no data

On Wednesday 12 January 2005 14:55, Gene Heskett wrote: >On Wednesday 12 January 2005 12:04, Jon LaBadie wrote: >>On Wed, Jan 12, 2005 at 11:18:00AM -0500, Eric Siegerman wrote: >>> On Tuesday 11 January 2005 16:40, Jon LaBadie wrote: >>> >Also, I think that if both types of devices exist on the sa

Re: amrestore problem, headers ok but no data

On Wednesday 12 January 2005 12:04, Jon LaBadie wrote: >On Wed, Jan 12, 2005 at 11:18:00AM -0500, Eric Siegerman wrote: >> On Tuesday 11 January 2005 16:40, Jon LaBadie wrote: >> >Also, I think that if both types of devices exist on the same >> > bus, the lower performance one determines the perfor

Re: amrestore problem, headers ok but no data

Google says: voltage standing wave ratio > > > To many folks forget that a a scsi bus is indeed > > > an rf transmission line, subject to the usual rules about vswr. > > > > >From the context it's pretty clear what "vswr" means, but what > > does it stand for? > > > > > Wondered too, as I'm po

Re: amrestore problem, headers ok but no data

On Wed, Jan 12, 2005 at 11:18:00AM -0500, Eric Siegerman wrote: > On Tuesday 11 January 2005 16:40, Jon LaBadie wrote: > >Also, I think that if both types of devices exist on the same bus, > >the lower performance one determines the performance of the entire > >bus. > > In theory, this is *not* th

Re: amrestore problem, headers ok but no data

On Tuesday 11 January 2005 16:40, Jon LaBadie wrote: >Also, I think that if both types of devices exist on the same bus, >the lower performance one determines the performance of the entire >bus. In theory, this is *not* the case. One of the (many) selling points of SCSI over IDE is supposed to be

Re: amrestore problem, headers ok but no data

On Tuesday 11 January 2005 16:40, Jon LaBadie wrote: >On Tue, Jan 11, 2005 at 03:40:47PM -0500, Brian Cuttler wrote: >> Amanda user list, >> >> I've spoken to Harry at Condre systems and he confirmed what we >> where seeing. The jukebox robot is a narrow bus so that are two >> changes we need to ma

Re: amrestore problem, headers ok but no data

Jon, Recommended buying an additional scsi card more than once to the system's owners, haven't made the case yet (maybe now). I would really have liked the raid array on a separate bus from the tape drives. I have to trust that the proper cabeling to terminate the additional lines is present in

Re: amrestore problem, headers ok but no data

On Tue, Jan 11, 2005 at 03:40:47PM -0500, Brian Cuttler wrote: > > Amanda user list, > > I've spoken to Harry at Condre systems and he confirmed what we > where seeing. The jukebox robot is a narrow bus so that are two > changes we need to make. > > 1) We want to move the jukebox/SDLT to be the

Re: amrestore problem, headers ok but no data

Amanda user list, I've spoken to Harry at Condre systems and he confirmed what we where seeing. The jukebox robot is a narrow bus so that are two changes we need to make. 1) We want to move the jukebox/SDLT to be the last device on the daisy chain. 2) We want to terminate the jukebox-robot,

Re: amrestore problem, headers ok but no data

On Tue, Jan 11, 2005 at 09:11:31AM +0100, Stefan G. Weichinger wrote: > The minimum blocksize value > is 32 KBytes. The maximum blocksize value is 32 > KBytes. The man pages have configure variables, which are expanded during "make". Presumably the

Re: amrestore problem, headers ok but no data

Hi, Jon, on Montag, 10. Jänner 2005 at 22:19 you wrote to amanda-users: JL> In recent versions, amanda can work with blocksizes other than 32k. JL> I forget if it is a configure option needed during the build or JL> a parameter that can be set in amanda.conf. I've never used it. The parameter b

Re: amrestore problem, headers ok but no data

Jon, On Mon, Jan 10, 2005 at 04:19:45PM -0500, Jon LaBadie wrote: > > Something that didn't error during the write but did > > during the read ? > > > > This is not too surprising to me. > > A tape with a blocksize of 132k will accept a write of 32k and > simply pad it to the required size. N

Re: amrestore problem, headers ok but no data

On Mon, Jan 10, 2005 at 11:48:42AM -0500, Brian Cuttler wrote: > > The following (just scripted, with commentary added) is a little long > and rather un-good. > ... > > Probing the drive I find a block size of 32768 again. > > samar 25# mt -f /dev/sdlt2 setblksz 131072 > > samar 26# /usr/local

  1   2   3   >