Re: Restoring files from amanda in a script
Hi,
Thank you for all the replies. They are a good food for the mind.
On Tue, Mar 06, 2018 at 09:10:48PM +, Jean-Louis Martineau wrote:
> You can't restore in a unique tree of files.
> I do not understand why you want to do that.
Let-me explain better. I have a big tree of files on OpenAFS, a
network filesystem, that is backup up by amanda. I need to copy this
tree to another place. I could use rsync, but I think this rsync will
take several days on a moving target.
My "clever idea" was to use the backups of amanda to restore the files
in the target. The backups I want forms a subset of all the clients
and DLEs in the amanda server. This means some thing like 6 clients
and 61 DLEs from 800. So is a good case for a script to recover this
61 DLEs.
>
> To do it:
> - patch amgtar to remove the -G flag ("-xpGvf" to "-xpvf"), otherwise
> extracting a DLE will remove what was extracted from another DLE, but file
> erase before the backup will not be erased
> - run 'amadmin CONF find' to get the list of all dumps [HOST DISK DATE LEVEL]
> you want to restore
> - run 'amfetchdump CONF --extract --directory /tmp/restore [HOST DISK DATE
> LEVEL]*',putting all [HOST DISK DATE LEVEL] on the same command line.
>
> Jean-Louis
>
> From: owner-amanda-us...@amanda.org on behalf
> of Jose M Calhariz
> Sent: March 6, 2018 3:28 PM
> To: amanda-users@amanda.org
> Subject: Restoring files from amanda in a script
>
> Hi,
>
> In short I want to restore from a specific date, all the data from
> multiples DLEs and multiples servers into a unique tree of files in
> the amanda server. This is too much tedious to do using the
> interactive amrecover. This is Complex enough to use a script with
> amrestore or amfetchdump to restore all the files I want. My first
> approach is not working well. So I would like to hear the experiences
> from the list for similar problems. I am interested in hints before I
> deep dive into the RTFM.
>
> Kind regards
> Jose M Calhariz
>
Kind regards
Jose M Calhariz
--
--
Quem não se comunica se estrumbica
--Chacrinha
Re: Restoring files from amanda in a script
Charles Curley wrote: > I have not had this problem. I wonder if you can use expect to > control an amrecover session. Along these lines you could use here documents: https://en.wikipedia.org/wiki/Here_document then modify them using editing macros. Steve -- Steven J. BackusComputer Systems Manager University of Utah E-Mail: steven.bac...@utah.edu Genetic EpidemiologyAlternate: bac...@math.utah.edu 391 Chipeta Way -- Suite D Office: 801.587.9308 Salt Lake City, UT 84108-1266 http://www.math.utah.edu/~backus
Re: Restoring files from amanda in a script
> On Mar 6, 2018, at 2:28 PM, Jose M Calhariz > wrote: > > Hi, > > In short I want to restore from a specific date, all the data from > multiples DLEs and multiples servers into a unique tree of files in > the amanda server. This is too much tedious to do using the > interactive amrecover. This is Complex enough to use a script with > amrestore or amfetchdump to restore all the files I want. My first > approach is not working well. So I would like to hear the experiences > from the list for similar problems. I am interested in hints before I > deep dive into the RTFM. > > Kind regards > Jose M Calhariz > If all the data is on one tape (or virtual tape area) you can ignore amanda commands and just use unzip, tar, dump, dd, etc on the actual backup files. Actually, several tapes or areas will still work this way. You are not limited to amanda commands. Deb Baddorf
Re: Restoring files from amanda in a script
You can't restore in a unique tree of files.
I do not understand why you want to do that.
To do it:
- patch amgtar to remove the -G flag ("-xpGvf" to "-xpvf"), otherwise
extracting a DLE will remove what was extracted from another DLE, but file
erase before the backup will not be erased
- run 'amadmin CONF find' to get the list of all dumps [HOST DISK DATE LEVEL]
you want to restore
- run 'amfetchdump CONF --extract --directory /tmp/restore [HOST DISK DATE
LEVEL]*',putting all [HOST DISK DATE LEVEL] on the same command line.
Jean-Louis
From: owner-amanda-us...@amanda.org on behalf
of Jose M Calhariz
Sent: March 6, 2018 3:28 PM
To: amanda-users@amanda.org
Subject: Restoring files from amanda in a script
Hi,
In short I want to restore from a specific date, all the data from
multiples DLEs and multiples servers into a unique tree of files in
the amanda server. This is too much tedious to do using the
interactive amrecover. This is Complex enough to use a script with
amrestore or amfetchdump to restore all the files I want. My first
approach is not working well. So I would like to hear the experiences
from the list for similar problems. I am interested in hints before I
deep dive into the RTFM.
Kind regards
Jose M Calhariz
--
--
Quem não se comunica se estrumbica
--Chacrinha
This message is the property of CARBONITE, INC. and may contain confidential or
privileged information.
If this message has been delivered to you by mistake, then do not copy or
deliver this message to anyone. Instead, destroy it and notify me by reply
e-mail
Re: Restoring files from amanda in a script
On Tue, 6 Mar 2018 20:28:09 + Jose M Calhariz wrote: > In short I want to restore from a specific date, all the data from > multiples DLEs and multiples servers into a unique tree of files in > the amanda server. This is too much tedious to do using the > interactive amrecover. This is Complex enough to use a script with > amrestore or amfetchdump to restore all the files I want. My first > approach is not working well. So I would like to hear the experiences > from the list for similar problems. I am interested in hints before I > deep dive into the RTFM. I have not had this problem. I wonder if you can use expect to control an amrecover session. apt show expect -- A great civilization is not conquered from without until it has destroyed itself within. The essential causes of Rome's decline lay in her people, her morals, her class struggle, her failing trade, her bureaucratic despotism, her stifling taxes, her consuming wars. -- Will and Ariel Durant, III The Story of Civilization (1944) epilogue
Restoring files from amanda in a script
Hi, In short I want to restore from a specific date, all the data from multiples DLEs and multiples servers into a unique tree of files in the amanda server. This is too much tedious to do using the interactive amrecover. This is Complex enough to use a script with amrestore or amfetchdump to restore all the files I want. My first approach is not working well. So I would like to hear the experiences from the list for similar problems. I am interested in hints before I deep dive into the RTFM. Kind regards Jose M Calhariz -- -- Quem não se comunica se estrumbica --Chacrinha
Restoring ZFS datasets with amfetchdump and feedback on S3 conf
Hi there,
I’m setting up a backup server running Amanda 3.3.6 on Ubuntu 16.04. My main
idea is to use the amzfs-sendrecv plugin. The dump part works, but I have a
couple of questions about the restore procedures. If anyone could give me some
advice that would be great.
I’m still having a hard time in figuring out the interplay between ZFS
snapshots and Amanda. As far as I can tell, Amanda create a temporary ZFS
snapshot, and send the delta between that and the previous one the backup. Then
it proceeds to swap / rename the snapshot for the next run. When a full backup
is needed a it sends the snapshots without the `-i` flag. Assuming my
understanding is correct, I still don’t know how to:
- execute a full restore a ZFS dataset, i.e. the dataset is gone. In
particular, I’d like to use amfetchdump so that I can pipe the stream back with
`zfs recv`
- execute a partial restore, i.e. a point in time recovery with an existing ZFS
dataset. Now, I realize that you could solve this particular use case just with
ZFS, assuming you have a usable ZFS snapshot, but since I’m just getting
started with Amanda, I’d like to know how to solve it with this tool, as well.
The configuration shown below is what I come up with by looking at the wiki
pages. I’d be really grateful if someone could give me feedback on this. Does
anybody see anything wrong or that can be improved?
My conf:
> infofile "/var/lib/amanda/state/curinfo"
> indexdir "/var/lib/amanda/state/index"
> dumpuser "backup"
> mailto “<…>"
>
> define changer s3 {
> tapedev
> "chg-multi:s3:<…>/slot-bb2e601e63b3408bb6a865e442a28366-{1,2,3,4,5,6,7,8,9,10,11,12,13,14,15}"
> changerfile "/var/lib/amanda/state/s3-statefile"
> device-property "NB_THREADS_BACKUP""8"
> device-property "NB_THREADS_RECOVERY" "8"
> device_property "S3_ACCESS_KEY”“<…>"
> device_property "S3_SECRET_KEY”“<…>"
> device_property "S3_BUCKET_LOCATION" "eu-west-1"
> device_property "S3_SSL" "YES"
> device_property "BLOCK_SIZE" "10 megabytes"
> }
>
> tpchanger "s3"
> tapetype S3
>
> define tapetype S3 {
> comment "S3 Bucket"
> length 10240 gigabytes
> }
>
> org "zfs-dataset"
> logdir "/var/log/zfs-dataset"
>
> define application-tool zfs-dataset-app {
>comment "amzfs-sendrecv"
>plugin "amzfs-sendrecv"
>property "ZFS-PATH" "/sbin/zfs"
>property "PFEXEC-PATH" "/usr/bin/sudo"
>property "PFEXEC""YES"
> }
>
> define dumptype zfs-dataset-dump {
> program "APPLICATION"
> application "zfs-dataset-app"
> auth"ssh"
> ssh_keys"/var/backups/.ssh/id_rsa”
> }
--
Giorgio Valoti
No data found on restoring from backups taken from Windows host - Seeking help
Hi, While restoring backups taken from Windows host, receiving following error 'part 1/UNKNOWN ' and there is no data: [amandabackup@pciambkup restore]$ amfetchdump DailySet21 pcivmm1.itrnetwork.com "C:/Scripts" 20170119010002 1 volume(s) needed for restoration The following volumes are needed: DailySet21-08 Press enter when ready Reading label 'DailySet21-08' filenum 1 split dumpfile: date 20170119010002 host pcivmm1.itrnetwork.com disk "C:/Scripts" part 1/UNKNOWN lev 1 comp N program pkzip 1 kb [amandabackup@pciambkup restore]$ Can someone help to identify cause & resolving this issue? There is only one entry in the disklist file: pcivmm1.itrnetwork.com C:/Scripts zwc-compress CONFIDENTIAL NOTICE: All information, data and attachments contained in this message are confidential and are the property of the sender. If you are not the intended recipient and have received this email in error delete it immediately and destroy all copies. Any redistribution, communication or actions taken on information contained in this message is strictly prohibited.
Re: restoring from vtapes on client machine
Ah ha! At first it gave a warning for each of my virtual tapes, there are 80 of them. So then I used rsync to replicate /var/log/amanda/DailySet1/ from the real backup server to the backup backup server. At that point, "amadmin DailySet1 find" showed a list of backups. And now amrecover works on the second server. I am a little uncertain as to how to pprocede now though. Maybe I could move the log directory to the NFS share as well. Is that what you'd recommend? On 11/02/2016 02:08 PM, Jean-Louis Martineau wrote: John, Then it is the tapelist or the log..0 files that are not correct. What 'amadmin DailySet1 find' returns? It should list all dumps available. Jean-Louis On 02/11/16 03:04 PM, John G Heim wrote: Oops, I mislead you. There is an error message displayed. It is the classic no dumps available before this date. I am blind and I just didn't hear it. I am still as puzzled as ever though. I've cut/pasted a screen cap of my amrecover session. I'll paste in the amindexd log as well. I see that amindexd runs as user backup. I checked the user backup has access to the index files. Recall that in an earlier message, I mentioned that I moved them to the same NFS share that the vtapes are on. I made sure the user backup has the same uid and gid on both of the machines onwhich I am trying this. I am fairly sure the user backup has access to the index files. In my amanda.conf, it says: indexdir "/nfs.drive/amanda/DailySet1/index" Doing an "ls -l" of /nfs.drive/amanda/DailySet1/index, shows that the files in there are owned by user backup and user backup can read/write the files. I even ungzipped one of the index files just to make sure. root@turing:/etc/amanda/DailySet1# amrecover DailySet1 -o auth=local -s localhost AMRECOVER Version 3.3.6. Contacting server on localhost ... 220 turing AMANDA index server (3.3.6) ready. Setting restore date to today (2016-11-02) 200 Working date set to 2016-11-02. 200 Config set to DailySet1. 200 Dump host set to turing. Use the setdisk command to choose dump disk to recover amrecover> sethost alpha 200 Dump host set to alpha. amrecover> setdisk /etc 200 Disk set to /etc. 500 No dumps available on or before date "2016-11-02" No index records for disk for specified date If date correct, notify system administrator amrecover> --- log --- Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: pid 20291 ruid 34 euid 34 version 3.3.6: start at Wed Nov 2 14:01:10 2016 Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: version 3.3.6 Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: < 220 turing AMANDA index server (3.3.6) ready. Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: > FEATURES 9efefbff3f Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: < 200 FEATURES 9efefbff3f Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: > DATE 2016-11-02 Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: < 200 Working date set to 2016-11-02. Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: > SCNF DailySet1 Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: pid 20291 ruid 34 euid 34 version 3.3.6: rename at Wed Nov 2 14:01:10 2016 Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: < 200 Config set to DailySet1. Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: > HOST turing Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: < 200 Dump host set to turing. Wed Nov 2 14:01:38 2016: thd-0x55d0b8434400: amindexd: > HOST alpha Wed Nov 2 14:01:38 2016: thd-0x55d0b8434400: amindexd: < 200 Dump host set to alpha. Wed Nov 2 14:01:45 2016: thd-0x55d0b8434400: amindexd: > DISK /etc Wed Nov 2 14:01:45 2016: thd-0x55d0b8434400: amindexd: no recovery limit found; allowing access Wed Nov 2 14:01:45 2016: thd-0x55d0b8434400: amindexd: < 200 Disk set to /etc. Wed Nov 2 14:01:45 2016: thd-0x55d0b8434400: amindexd: > OISD / Wed Nov 2 14:01:45 2016: thd-0x55d0b8434400: amindexd: < 500 No dumps available on or before date "2016-11-02" Wed Nov 2 14:01:45 2016: thd-0x55d0b8434400: amindexd: > DLE Wed Nov 2 14:01:45 2016: thd-0x55d0b8434400: amindexd: < 200 "\n GNUTAR\n /etc\n BSDTCP\n FAST\n YES\n YES\n AMANDA\n\n" On 11/01/2016 09:29 AM, Jean-Louis Martineau wrote: Any error message in the amindexd debug file? It looks like the amindexd process can't read the index files. Jean-Louis On 01/11/16 10:26 AM, John G Heim wrote: I tried both "localhost backup" and "localhost root" in the amandahosts file. No difference. It is odd -- everything seems to work. I can connect to the localhost, issue sethost and setdisk commands. In fact, if I give an invalid host or disk name, I get an error message. But the ls command just shows no backups. It just gives an empty list. I feel I am tantilizingly close to making this work. On 10/31/2016 03:00 PM, Debra S Baddorf wrote: Is this related to the .amandahosts file on the server, which n
Re: restoring from vtapes on client machine
Oops, I mislead you. There is an error message displayed. It is the classic no dumps available before this date. I am blind and I just didn't hear it. I am still as puzzled as ever though. I've cut/pasted a screen cap of my amrecover session. I'll paste in the amindexd log as well. I see that amindexd runs as user backup. I checked the user backup has access to the index files. Recall that in an earlier message, I mentioned that I moved them to the same NFS share that the vtapes are on. I made sure the user backup has the same uid and gid on both of the machines onwhich I am trying this. I am fairly sure the user backup has access to the index files. In my amanda.conf, it says: indexdir "/nfs.drive/amanda/DailySet1/index" Doing an "ls -l" of /nfs.drive/amanda/DailySet1/index, shows that the files in there are owned by user backup and user backup can read/write the files. I even ungzipped one of the index files just to make sure. root@turing:/etc/amanda/DailySet1# amrecover DailySet1 -o auth=local -s localhost AMRECOVER Version 3.3.6. Contacting server on localhost ... 220 turing AMANDA index server (3.3.6) ready. Setting restore date to today (2016-11-02) 200 Working date set to 2016-11-02. 200 Config set to DailySet1. 200 Dump host set to turing. Use the setdisk command to choose dump disk to recover amrecover> sethost alpha 200 Dump host set to alpha. amrecover> setdisk /etc 200 Disk set to /etc. 500 No dumps available on or before date "2016-11-02" No index records for disk for specified date If date correct, notify system administrator amrecover> --- log --- Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: pid 20291 ruid 34 euid 34 version 3.3.6: start at Wed Nov 2 14:01:10 2016 Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: version 3.3.6 Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: < 220 turing AMANDA index server (3.3.6) ready. Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: > FEATURES 9efefbff3f Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: < 200 FEATURES 9efefbff3f Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: > DATE 2016-11-02 Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: < 200 Working date set to 2016-11-02. Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: > SCNF DailySet1 Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: pid 20291 ruid 34 euid 34 version 3.3.6: rename at Wed Nov 2 14:01:10 2016 Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: < 200 Config set to DailySet1. Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: > HOST turing Wed Nov 2 14:01:10 2016: thd-0x55d0b8434400: amindexd: < 200 Dump host set to turing. Wed Nov 2 14:01:38 2016: thd-0x55d0b8434400: amindexd: > HOST alpha Wed Nov 2 14:01:38 2016: thd-0x55d0b8434400: amindexd: < 200 Dump host set to alpha. Wed Nov 2 14:01:45 2016: thd-0x55d0b8434400: amindexd: > DISK /etc Wed Nov 2 14:01:45 2016: thd-0x55d0b8434400: amindexd: no recovery limit found; allowing access Wed Nov 2 14:01:45 2016: thd-0x55d0b8434400: amindexd: < 200 Disk set to /etc. Wed Nov 2 14:01:45 2016: thd-0x55d0b8434400: amindexd: > OISD / Wed Nov 2 14:01:45 2016: thd-0x55d0b8434400: amindexd: < 500 No dumps available on or before date "2016-11-02" Wed Nov 2 14:01:45 2016: thd-0x55d0b8434400: amindexd: > DLE Wed Nov 2 14:01:45 2016: thd-0x55d0b8434400: amindexd: < 200 "\n GNUTAR\n /etc\n BSDTCP\n FAST\n YES\n YES\n AMANDA\n\n" On 11/01/2016 09:29 AM, Jean-Louis Martineau wrote: Any error message in the amindexd debug file? It looks like the amindexd process can't read the index files. Jean-Louis On 01/11/16 10:26 AM, John G Heim wrote: I tried both "localhost backup" and "localhost root" in the amandahosts file. No difference. It is odd -- everything seems to work. I can connect to the localhost, issue sethost and setdisk commands. In fact, if I give an invalid host or disk name, I get an error message. But the ls command just shows no backups. It just gives an empty list. I feel I am tantilizingly close to making this work. On 10/31/2016 03:00 PM, Debra S Baddorf wrote: Is this related to the .amandahosts file on the server, which needs to have a line for each client, allowing it to access the index-process and maybe the tape-process?I have entries like this: node.FQDN root amindexd amidxtaped I’m not certain that both of those are still needed, but there was at one time a reason I put them there. Deb Baddorf On Oct 31, 2016, at 12:35 PM, John G Heim wrote: Well, that got me a lot closer. I gave user backup read permission to /etc/amanda/DailySet1/amanda.conf on the "backup" backup server. Now when I run amrecover, I can do a sethost and a setdisk. But after doing so, an ls gives me an empty list. No error message. It's just that there are no files listed. On the real backup server, where the backups are actually being made, I do get a
Re: restoring from vtapes on client machine
I tried both "localhost backup" and "localhost root" in the amandahosts file. No difference. It is odd -- everything seems to work. I can connect to the localhost, issue sethost and setdisk commands. In fact, if I give an invalid host or disk name, I get an error message. But the ls command just shows no backups. It just gives an empty list. I feel I am tantilizingly close to making this work. On 10/31/2016 03:00 PM, Debra S Baddorf wrote: Is this related to the .amandahosts file on the server, which needs to have a line for each client, allowing it to access the index-process and maybe the tape-process?I have entries like this: node.FQDN root amindexd amidxtaped I’m not certain that both of those are still needed, but there was at one time a reason I put them there. Deb Baddorf On Oct 31, 2016, at 12:35 PM, John G Heim wrote: Well, that got me a lot closer. I gave user backup read permission to /etc/amanda/DailySet1/amanda.conf on the "backup" backup server. Now when I run amrecover, I can do a sethost and a setdisk. But after doing so, an ls gives me an empty list. No error message. It's just that there are no files listed. On the real backup server, where the backups are actually being made, I do get a list of files, just as normal. I checked the permissions on the index and info files. They look right. Actually, I moved the location of the indexdir and infofile to be on the same remote nfs share as the virtual tapes themselves. So when I run amrecover on the backup backup server, it is reading the same files as it is when I run it on the real backup server. I think moving those files to the remote nfs server was a good thing, not just for this use but also, now amanda's index and info files are in another building. I would still like to be able to use amrecover on two different hosts in my buildijng though. On 10/28/2016 10:52 AM, Jean-Louis Martineau wrote: It is the amindexd process that report the error. Look at its debug file. It is run as your amanda user, did it have permission to read /etc/amanda/DailySet1/amanda.conf. Jean-Louis On 28/10/16 11:08 AM, John G Heim wrote: I am using the ubuntu amanda-server and amanda-client packages (3.3.6) on ubuntu server 16.04 to backup to virtual tapes on an NFS mounted file system. Everything is great on the backup server. I can run amrecover locally and recover files. But I thought I'd try mounting the NFS share on a client machine to see if I could recover files that way. I thought if the backup server ever goes down, I might still be able to recover files on the client machine. So I installed amanda-server on the client machine and copied the contents of /etc/amanda/DailySet1/ to the client. Then I ran: # amrecover DailySet1 -o auth=local -s localhost That gives me the error message, ""501 Could not read config file for DailySet1!". I amd doing this as root. Root does have permission to open/read /etc/amanda/DailySet1/amanda.conf. -- -- John G. Heim; jh...@math.wisc.edu; sip://jh...@sip.linphone.org -- -- John G. Heim; jh...@math.wisc.edu; sip://jh...@sip.linphone.org
Re: restoring from vtapes on client machine
Is this related to the .amandahosts file on the server, which needs to have a line for each client, allowing it to access the index-process and maybe the tape-process?I have entries like this: node.FQDN root amindexd amidxtaped I’m not certain that both of those are still needed, but there was at one time a reason I put them there. Deb Baddorf > On Oct 31, 2016, at 12:35 PM, John G Heim wrote: > > Well, that got me a lot closer. I gave user backup read permission to > /etc/amanda/DailySet1/amanda.conf on the "backup" backup server. Now when I > run amrecover, I can do a sethost and a setdisk. But after doing so, an ls > gives me an empty list. No error message. It's just that there are no files > listed. On the real backup server, where the backups are actually being made, > I do get a list of files, just as normal. I checked the permissions on the > index and info files. They look right. > > > Actually, I moved the location of the indexdir and infofile to be on the same > remote nfs share as the virtual tapes themselves. So when I run amrecover on > the backup backup server, it is reading the same files as it is when I run it > on the real backup server. I think moving those files to the remote nfs > server was a good thing, not just for this use but also, now amanda's index > and info files are in another building. I would still like to be able to use > amrecover on two different hosts in my buildijng though. > > > > > > > > On 10/28/2016 10:52 AM, Jean-Louis Martineau wrote: >> It is the amindexd process that report the error. >> Look at its debug file. >> It is run as your amanda user, did it have permission to read >> /etc/amanda/DailySet1/amanda.conf. >> >> Jean-Louis >> >> On 28/10/16 11:08 AM, John G Heim wrote: >>> I am using the ubuntu amanda-server and amanda-client packages (3.3.6) on >>> ubuntu server 16.04 to backup to virtual tapes on an NFS mounted file >>> system. Everything is great on the backup server. I can run amrecover >>> locally and recover files. But I thought I'd try mounting the NFS share on >>> a client machine to see if I could recover files that way. I thought if the >>> backup server ever goes down, I might still be able to recover files on the >>> client machine. >>> >>> >>> So I installed amanda-server on the client machine and copied the contents >>> of /etc/amanda/DailySet1/ to the client. Then I ran: >>> >>> >>> # amrecover DailySet1 -o auth=local -s localhost >>> >>> That gives me the error message, ""501 Could not read config file for >>> DailySet1!". I amd doing this as root. Root does have permission to >>> open/read /etc/amanda/DailySet1/amanda.conf. >>> >>> >>> >>> >>> >> > > -- > -- > John G. Heim; jh...@math.wisc.edu; sip://jh...@sip.linphone.org >
Re: restoring from vtapes on client machine
Well, that got me a lot closer. I gave user backup read permission to /etc/amanda/DailySet1/amanda.conf on the "backup" backup server. Now when I run amrecover, I can do a sethost and a setdisk. But after doing so, an ls gives me an empty list. No error message. It's just that there are no files listed. On the real backup server, where the backups are actually being made, I do get a list of files, just as normal. I checked the permissions on the index and info files. They look right. Actually, I moved the location of the indexdir and infofile to be on the same remote nfs share as the virtual tapes themselves. So when I run amrecover on the backup backup server, it is reading the same files as it is when I run it on the real backup server. I think moving those files to the remote nfs server was a good thing, not just for this use but also, now amanda's index and info files are in another building. I would still like to be able to use amrecover on two different hosts in my buildijng though. On 10/28/2016 10:52 AM, Jean-Louis Martineau wrote: It is the amindexd process that report the error. Look at its debug file. It is run as your amanda user, did it have permission to read /etc/amanda/DailySet1/amanda.conf. Jean-Louis On 28/10/16 11:08 AM, John G Heim wrote: I am using the ubuntu amanda-server and amanda-client packages (3.3.6) on ubuntu server 16.04 to backup to virtual tapes on an NFS mounted file system. Everything is great on the backup server. I can run amrecover locally and recover files. But I thought I'd try mounting the NFS share on a client machine to see if I could recover files that way. I thought if the backup server ever goes down, I might still be able to recover files on the client machine. So I installed amanda-server on the client machine and copied the contents of /etc/amanda/DailySet1/ to the client. Then I ran: # amrecover DailySet1 -o auth=local -s localhost That gives me the error message, ""501 Could not read config file for DailySet1!". I amd doing this as root. Root does have permission to open/read /etc/amanda/DailySet1/amanda.conf. -- -- John G. Heim; jh...@math.wisc.edu; sip://jh...@sip.linphone.org
restoring from vtapes on client machine
I am using the ubuntu amanda-server and amanda-client packages (3.3.6) on ubuntu server 16.04 to backup to virtual tapes on an NFS mounted file system. Everything is great on the backup server. I can run amrecover locally and recover files. But I thought I'd try mounting the NFS share on a client machine to see if I could recover files that way. I thought if the backup server ever goes down, I might still be able to recover files on the client machine. So I installed amanda-server on the client machine and copied the contents of /etc/amanda/DailySet1/ to the client. Then I ran: # amrecover DailySet1 -o auth=local -s localhost That gives me the error message, ""501 Could not read config file for DailySet1!". I amd doing this as root. Root does have permission to open/read /etc/amanda/DailySet1/amanda.conf. -- -- John G. Heim; jh...@math.wisc.edu; sip://jh...@sip.linphone.org
RE: restoring (various scenarios) and backing up amanda config
OK managed to test a small restore using mt+dd Still need to explore more... figure out implication of part_size in this situation - Issuing this:amadmin MY CONFIG find I see Warning: no log files found for tape MYTAPE written 2015-11-27 17:00:13 I can see the logs in /amanda/state/log/oldlog These are set in my config infofile "/amanda/state/curinfo"# database DIRECTORY logdir "/amanda/state/log"# log directory indexdir "/amanda/state/index" # index directory Not quite sure why they've ended up in old log? Presumably this is expected? Can I rectify this situation so I can test amfetchdump (by copying logs into /amanda/state/log/)? David David Simpson - Computing Support Officer IBME - Institute of Biomedical Engineering Old Road Campus Research Building Oxford, OX3 7DQ Tel: 01865 617697 ext: 17697 From: David Simpson Sent: 30 November 2015 11:03 To: Amanda Users Subject: restoring (various scenarios) and backing up amanda config So what I decided to do was kick the archiving off. With separate configs and on a per-host basis - a disklist for each host/config. Allocating enough tape but no more (by looking a numbers generated from du). I came up with a low number for runtapes and tapecycle. This is a full level 0 too. I've done the first host on two tapes. I then removed the tapes, flicked the tab to write-protect ON and set no-reuse within Amanda. I will need to test more restore situations... I'm confident about AMRECOVER... but I want to test the everything has gone up in smoke (inc Amanda server) situation further. I've got LEOM off, but I am using a part_size of 200GB with a changer/loader that amanda understands. *On the backup server I was thinking of taking a copy of /etc/amanda, /var/lib/amanda and /var/log/amanda (is this everything?) and putting it somewhere safe**. I was wondering if this could be sensibly scripted within cron? Could simply [on successfully dump] automatically tar and copy the config to another server? **I assume this could this be transplanted to a new backup server? (If I have the contents of all 3 of those directories). I.e. install new server with Centos, install Amanda RPM... copy those files into relevant dirs. For AMRECOVER I need Amanda information present (Config+logs)... mentioned above For AMFETCHDUMP Assuming above* is safe... It sounds like it will handle the part_size automatically... I would just specify the hostname+DLE and restore the full DLE somewhere on Amanda server then copy it (scp, rsync etc) to other server. For AMRESTORE - man page suggests it cannot handle split dumps...! (or does it mean multi tape? ... can it assemble multi parts from 1 tape?)... bit confused about its capability For non-Amanda OS Tools only I've managed to test with a small part ok... I need to test assembling parts Thanks David David Simpson - Computing Support Officer IBME - Institute of Biomedical Engineering Old Road Campus Research Building Oxford, OX3 7DQ Tel: 01865 617697 ext: 17697
restoring (various scenarios) and backing up amanda config
So what I decided to do was kick the archiving off. With separate configs and on a per-host basis - a disklist for each host/config. Allocating enough tape but no more (by looking a numbers generated from du). I came up with a low number for runtapes and tapecycle. This is a full level 0 too. I've done the first host on two tapes. I then removed the tapes, flicked the tab to write-protect ON and set no-reuse within Amanda. I will need to test more restore situations... I'm confident about AMRECOVER... but I want to test the everything has gone up in smoke (inc Amanda server) situation further. I've got LEOM off, but I am using a part_size of 200GB with a changer/loader that amanda understands. *On the backup server I was thinking of taking a copy of /etc/amanda, /var/lib/amanda and /var/log/amanda (is this everything?) and putting it somewhere safe**. I was wondering if this could be sensibly scripted within cron? Could simply [on successfully dump] automatically tar and copy the config to another server? **I assume this could this be transplanted to a new backup server? (If I have the contents of all 3 of those directories). I.e. install new server with Centos, install Amanda RPM... copy those files into relevant dirs. For AMRECOVER I need Amanda information present (Config+logs)... mentioned above For AMFETCHDUMP Assuming above* is safe... It sounds like it will handle the part_size automatically... I would just specify the hostname+DLE and restore the full DLE somewhere on Amanda server then copy it (scp, rsync etc) to other server. For AMRESTORE - man page suggests it cannot handle split dumps...! (or does it mean multi tape? ... can it assemble multi parts from 1 tape?)... bit confused about its capability For non-Amanda OS Tools only I've managed to test with a small part ok... I need to test assembling parts Thanks David David Simpson - Computing Support Officer IBME - Institute of Biomedical Engineering Old Road Campus Research Building Oxford, OX3 7DQ Tel: 01865 617697 ext: 17697
Re: problem with restoring dump gzipped on client-side
We used this, as a temporary fix. This is a file named GZIP.NULL.KLUDGE It worked when we tested it, in what I think are the circumstances you describe. The comments in it describe how to use it — but feel free to ask, if they aren’t clear. gzip.null.kludge: #!/bin/bash # # null gzip command to fake out amanda when restoring an old dump # from an old amanda server where the server gunzips before sending # and then the client also tries to gunzip the data... which fails # # to use: # cp this-file /usr/bin/gzip.null (if not already in place) # mv /usr/bin/gzip /usr/bin/gzip.real # mv /usr/bin/gzip.null /usr/bin/gzip # amrecover ... # mv /usr/bin/gzip /usr/bin/gzip.null # mv /usr/bin/gzip.real /usr/bin/gzip # /bin/cat My “make it not happen” fix was to tell all backups to do the compression on the server. Jean-Louis was telling us that it shouldn’t be needed any more. I’ve never removed it, so I don’t know. I don’t want to chance it! Deb Baddorf Fermilab On Apr 17, 2015, at 4:16 AM, Michael Schmitz wrote: > > Finally I managed to do a test with our old Amanda v2.5.2 > installation. It really worked fine with this version (using > passwordlesss SSH) although it really took a lot of time, but that's > fine. Therefore I will have to check what's been changed, that will > take some time. > >>>>>> "Michael" == Michael Schmitz writes: > >Michael> Ok, I can of course do what you suggested to do a >Michael> complete restore. That's fine for now, but will there be >Michael> a real fix for this problem? > >Michael> Our old backup server is still somewhere waiting for a >Michael> new "job", and I will re-check whether the problem is >Michael> really "new".
RE: problem with restoring dump gzipped on client-side
Finally I managed to do a test with our old Amanda v2.5.2 installation. It really worked fine with this version (using passwordlesss SSH) although it really took a lot of time, but that's fine. Therefore I will have to check what's been changed, that will take some time. > "Michael" == Michael Schmitz writes: Michael> Ok, I can of course do what you suggested to do a Michael> complete restore. That's fine for now, but will there be Michael> a real fix for this problem? Michael> Our old backup server is still somewhere waiting for a Michael> new "job", and I will re-check whether the problem is Michael> really "new".
RE: problem with restoring dump gzipped on client-side
Ok, I can of course do what you suggested to do a complete restore. That's
fine for now, but will there be a real fix for this problem?
Our old backup server is still somewhere waiting for a new "job", and I will
re-check whether the problem is really "new".
-Original Message-
From: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org]
On Behalf Of Jean-Louis Martineau
Sent: Montag, 30. März 2015 19:38
To: Debra S Baddorf; Michael Schmitz
Cc: AMANDA users
Subject: Re: problem with restoring dump gzipped on client-side
The problem here is the answer you entered to "set owner/mode for '.'?"
is never sent to the dump process, and dump is just waiting for the answer.
The problem is not related to compression.
Some older amrecover version had problem restoring client compressed backup,
but it is fixed in newer release.
Jean-Louis
On 03/30/2015 01:25 PM, Debra S Baddorf wrote:
> On Mar 30, 2015, at 11:33 AM, Jean-Louis Martineau
wrote:
>
>> On 03/30/2015 04:05 AM, Michael Schmitz wrote:
>>> Hi all,
>>>
>>> I've been using Amanda v2.5 for years an switched to v3.3.6 on
>>> freshly installed FC21 server and all clients (SLES11) a few days
>>> ago. My configuration contains the definition
>>>
>>> define dumptype my-dump {
>>>
>>> global
>>> auth "ssh"
>>> ssh_keys "/var/lib/amanda/.ssh/id_rsa"
>>>
>>> program "DUMP"
>>> index
>>>
>>> priority high
>>>
>>> compress client fast
>>> }
>>>
>>> and disklist entry like
>>>
>>> foo.bar.com /home1 my-dump
>>>
>>> Backing up works like a charm, but now I tried to restore a directory
from foo.bar.com:/home1 locally on my server:
>>>
>>> # amrecover -C daily
>>>
>>> AMRECOVER Version 3.3.6. Contacting server on 10.2.19.3 ...
>>> 220 amanda AMANDA index server (3.3.6) ready.
>>>
>>> ...
>>>
>>> amrecover> sethost foo.bar.com
>>>
>>> amrecover> setdate 2015-03-20
>>>
>>> amrecover> setdisk /home1
>>>
>>> amrecover> add ako
>>>
>>> amrecover> lcd /tmp/amanda
>>>
>>> amrecover> extract
>>>
>>> Extracting files using tape drive changer on host 10.2.19.3.
>>> The following tapes are needed: daily-23
>>> daily-2
>>>
>>> Extracting files using tape drive changer on host 10.2.19.3.
>>> Load tape daily-23 now
>>> Continue [?/Y/n/s/d]? y
>>> Restoring files into directory /tmp/amanda All existing files in
>>> /tmp/amanda can be deleted Continue [?/Y/n]? y
>>>
>>> set owner/mode for '.'? [yn] y
>>>
>>> And this is where my trouble begins! Some files have been successfully
restored, but my response "y" is not processed. I see some zombie processes
in the process table. Pressing Ctrl-C terminates the entire restore. I don't
really care too much about the permissions, but "amrecover" didn't pick the
second tape!
>>>
>> Redo the restore with amrecover, but skip (s) the level 0 backup and
extract only the level 1 backup.
>>
>> Kill the dump process instead of amrecover when it ask to set owner/mode.
>>
>> Jean-Louis
> i.e. This is how to proceed from NOW, in order to get that second tape.
(As I understand it?)
> It isnt how to fix the original problem, or how not to have a problem
for the NEXT recover that you do.
>
> And actually if the original backup was on two tapes, the above still
doesnt fix it, Jean-Louis.
>
>
> Ive seen that problem too. I think it is related to whether the
host or the client had done
> the original compression. I have all my compression done on the
server just because of this issue.
> I havent check lately as to WHETHER the problem has gone away; I
just always compress on the
> server, because the problem cropped up when I first went to which ever
version caused it. Per your
> experiences, apparently the problem is still there
.
>
> Deb Baddorf
> Fermilab
>
>
>>> First I tried with my password-less SSH setup, which worked fine in the
past, later I switched to "bsdtcp", but this doesn't make any difference.
>>>
>>> What's the problem and - even more important - what can I do?
>>>
>>> Best regards,
>>>
>>> Michael.
>>>
>
Re: problem with restoring dump gzipped on client-side
The problem here is the answer you entered to "set owner/mode for '.'?"
is never sent to the dump process, and dump is just waiting for the answer.
The problem is not related to compression.
Some older amrecover version had problem restoring client compressed
backup, but it is fixed in newer release.
Jean-Louis
On 03/30/2015 01:25 PM, Debra S Baddorf wrote:
On Mar 30, 2015, at 11:33 AM, Jean-Louis Martineau wrote:
On 03/30/2015 04:05 AM, Michael Schmitz wrote:
Hi all,
I've been using Amanda v2.5 for years an switched to v3.3.6 on freshly
installed FC21 server and all clients (SLES11) a few days ago. My configuration
contains the definition
define dumptype my-dump {
global
auth "ssh"
ssh_keys "/var/lib/amanda/.ssh/id_rsa"
program "DUMP"
index
priority high
compress client fast
}
and disklist entry like
foo.bar.com /home1 my-dump
Backing up works like a charm, but now I tried to restore a directory from
foo.bar.com:/home1 locally on my server:
# amrecover -C daily
AMRECOVER Version 3.3.6. Contacting server on 10.2.19.3 ...
220 amanda AMANDA index server (3.3.6) ready.
...
amrecover> sethost foo.bar.com
amrecover> setdate 2015-03-20
amrecover> setdisk /home1
amrecover> add ako
amrecover> lcd /tmp/amanda
amrecover> extract
Extracting files using tape drive changer on host 10.2.19.3.
The following tapes are needed: daily-23
daily-2
Extracting files using tape drive changer on host 10.2.19.3.
Load tape daily-23 now
Continue [?/Y/n/s/d]? y
Restoring files into directory /tmp/amanda
All existing files in /tmp/amanda can be deleted
Continue [?/Y/n]? y
set owner/mode for '.'? [yn] y
And this is where my trouble begins! Some files have been successfully restored, but my response
"y" is not processed. I see some zombie processes in the process table. Pressing Ctrl-C
terminates the entire restore. I don't really care too much about the permissions, but
"amrecover" didn't pick the second tape!
Redo the restore with amrecover, but skip (s) the level 0 backup and extract
only the level 1 backup.
Kill the dump process instead of amrecover when it ask to set owner/mode.
Jean-Louis
i.e. This is how to proceed from NOW, in order to get that second tape.
(As I understand it?)
It isn’t how to fix the original problem, or how not to have a problem for the
NEXT recover that you do.
And actually — if the original backup was on two tapes, the above still
doesn’t fix it, Jean-Louis.
I’ve seen that problem too. I think it is related to whether the host or
the client had done
the original compression. I have all my compression done on the server
just because of this issue.
I haven’t check lately as to WHETHER the problem has gone away; I just
always compress on the
server, because the problem cropped up when I first went to which ever version
caused it. Per your
experiences, apparently the problem is still there …….
Deb Baddorf
Fermilab
First I tried with my password-less SSH setup, which worked fine in the past, later I
switched to "bsdtcp", but this doesn't make any difference.
What's the problem and - even more important - what can I do?
Best regards,
Michael.
Re: problem with restoring dump gzipped on client-side
On Mar 30, 2015, at 11:33 AM, Jean-Louis Martineau wrote:
> On 03/30/2015 04:05 AM, Michael Schmitz wrote:
>>
>> Hi all,
>>
>> I've been using Amanda v2.5 for years an switched to v3.3.6 on freshly
>> installed FC21 server and all clients (SLES11) a few days ago. My
>> configuration contains the definition
>>
>> define dumptype my-dump {
>>
>>global
>>auth "ssh"
>>ssh_keys "/var/lib/amanda/.ssh/id_rsa"
>>
>>program "DUMP"
>>index
>>
>>priority high
>>
>>compress client fast
>> }
>>
>> and disklist entry like
>>
>> foo.bar.com /home1 my-dump
>>
>> Backing up works like a charm, but now I tried to restore a directory from
>> foo.bar.com:/home1 locally on my server:
>>
>> # amrecover -C daily
>>
>> AMRECOVER Version 3.3.6. Contacting server on 10.2.19.3 ...
>> 220 amanda AMANDA index server (3.3.6) ready.
>>
>> ...
>>
>> amrecover> sethost foo.bar.com
>>
>> amrecover> setdate 2015-03-20
>>
>> amrecover> setdisk /home1
>>
>> amrecover> add ako
>>
>> amrecover> lcd /tmp/amanda
>>
>> amrecover> extract
>>
>> Extracting files using tape drive changer on host 10.2.19.3.
>> The following tapes are needed: daily-23
>>daily-2
>>
>> Extracting files using tape drive changer on host 10.2.19.3.
>> Load tape daily-23 now
>> Continue [?/Y/n/s/d]? y
>> Restoring files into directory /tmp/amanda
>> All existing files in /tmp/amanda can be deleted
>> Continue [?/Y/n]? y
>>
>> set owner/mode for '.'? [yn] y
>>
>> And this is where my trouble begins! Some files have been successfully
>> restored, but my response "y" is not processed. I see some zombie processes
>> in the process table. Pressing Ctrl-C terminates the entire restore. I don't
>> really care too much about the permissions, but "amrecover" didn't pick the
>> second tape!
>>
>
> Redo the restore with amrecover, but skip (s) the level 0 backup and extract
> only the level 1 backup.
>
> Kill the dump process instead of amrecover when it ask to set owner/mode.
>
> Jean-Louis
i.e. This is how to proceed from NOW, in order to get that second tape.
(As I understand it?)
It isn’t how to fix the original problem, or how not to have a problem for the
NEXT recover that you do.
And actually — if the original backup was on two tapes, the above still
doesn’t fix it, Jean-Louis.
I’ve seen that problem too. I think it is related to whether the host or
the client had done
the original compression. I have all my compression done on the server
just because of this issue.
I haven’t check lately as to WHETHER the problem has gone away; I just
always compress on the
server, because the problem cropped up when I first went to which ever version
caused it. Per your
experiences, apparently the problem is still there …….
Deb Baddorf
Fermilab
>>
>> First I tried with my password-less SSH setup, which worked fine in the
>> past, later I switched to "bsdtcp", but this doesn't make any difference.
>>
>> What's the problem and - even more important - what can I do?
>>
>> Best regards,
>>
>> Michael.
>>
>
Re: problem with restoring dump gzipped on client-side
On 03/30/2015 04:05 AM, Michael Schmitz wrote:
Hi all,
I've been using Amanda v2.5 for years an switched to v3.3.6 on freshly
installed FC21 server and all clients (SLES11) a few days ago. My
configuration contains the definition
define dumptype my-dump {
global
auth "ssh"
ssh_keys "/var/lib/amanda/.ssh/id_rsa"
program "DUMP"
index
priority high
compress client fast
}
and disklist entry like
foo.bar.com /home1 my-dump
Backing up works like a charm, but now I tried to restore a directory
from foo.bar.com:/home1 locally on my server:
# amrecover -C daily
AMRECOVER Version 3.3.6. Contacting server on 10.2.19.3 ...
220 amanda AMANDA index server (3.3.6) ready.
...
amrecover> sethost foo.bar.com
amrecover> setdate 2015-03-20
amrecover> setdisk /home1
amrecover> add ako
amrecover> lcd /tmp/amanda
amrecover> extract
Extracting files using tape drive changer on host 10.2.19.3.
The following tapes are needed: daily-23
daily-2
Extracting files using tape drive changer on host 10.2.19.3.
Load tape daily-23 now
Continue [?/Y/n/s/d]? y
Restoring files into directory /tmp/amanda
All existing files in /tmp/amanda can be deleted
Continue [?/Y/n]? y
set owner/mode for '.'? [yn] y
And this is where my trouble begins! Some files have been successfully
restored, but my response "y" is not processed. I see some zombie
processes in the process table. Pressing Ctrl-C terminates the entire
restore. I don't really care too much about the permissions, but
"amrecover" didn't pick the second tape!
Redo the restore with amrecover, but skip (s) the level 0 backup and
extract only the level 1 backup.
Kill the dump process instead of amrecover when it ask to set owner/mode.
Jean-Louis
First I tried with my password-less SSH setup, which worked fine in
the past, later I switched to "bsdtcp", but this doesn't make any
difference.
What's the problem and - even more important - what can I do?
Best regards,
Michael.
problem with restoring dump gzipped on client-side
Hi all,
I've been using Amanda v2.5 for years an switched to v3.3.6 on freshly
installed FC21 server and all clients (SLES11) a few days ago. My
configuration contains the definition
define dumptype my-dump {
global
auth "ssh"
ssh_keys "/var/lib/amanda/.ssh/id_rsa"
program "DUMP"
index
priority high
compress client fast
}
and disklist entry like
foo.bar.com /home1 my-dump
Backing up works like a charm, but now I tried to restore a directory from
foo.bar.com:/home1 locally on my server:
# amrecover -C daily
AMRECOVER Version 3.3.6. Contacting server on 10.2.19.3 ...
220 amanda AMANDA index server (3.3.6) ready.
...
amrecover> sethost foo.bar.com
amrecover> setdate 2015-03-20
amrecover> setdisk /home1
amrecover> add ako
amrecover> lcd /tmp/amanda
amrecover> extract
Extracting files using tape drive changer on host 10.2.19.3.
The following tapes are needed: daily-23
daily-2
Extracting files using tape drive changer on host 10.2.19.3.
Load tape daily-23 now
Continue [?/Y/n/s/d]? y
Restoring files into directory /tmp/amanda
All existing files in /tmp/amanda can be deleted
Continue [?/Y/n]? y
set owner/mode for '.'? [yn] y
And this is where my trouble begins! Some files have been successfully
restored, but my response "y" is not processed. I see some zombie processes
in the process table. Pressing Ctrl-C terminates the entire restore. I don't
really care too much about the permissions, but "amrecover" didn't pick the
second tape!
First I tried with my password-less SSH setup, which worked fine in the
past, later I switched to "bsdtcp", but this doesn't make any difference.
What's the problem and - even more important - what can I do?
Best regards,
Michael.
Re: restoring encrypted backups: amrecover vs amrestore
I’m pretty sure I tested an amrecover (not a whole amrestore) with my setup, where the server does the encryption. And it worked, I mean. Or I wouldn’t have continued. I might only have tested an amrecover ON the server though, and not on the client. Mine are all connected, so I guess I figured I could recover onto the server & transport later (more likely, it just didn’t occur to me to test from a client). Or maybe I did …. Let us know how your test works. Deb Baddorf On Mar 13, 2015, at 3:46 PM, Oscar Ricardo Silva wrote: > The idea behind client encryption is to treat each server/sysadmin as an > independent operator and with encryption done by the client the contents of > the tapes (or in our case, vtapes) wouldn't necessarily be accessible to the > amanda server operator. > > Ultimately, server encryption gets us a little closer. We're already > transmitting the backups over ssh so that gets us some privacy over the wire. > I'll switch over one of my test systems to "server encryption" and see how > that works. > > Thank you for the reply and the "bump" > > > > Oscar > > > On 03/13/2015 03:33 PM, Debra S Baddorf wrote: >> Since you’ve gotten no answers yet (I know very little):might this be >> related to whether the client or the server >> is the one doing the unpacking of the dump, and in turn, which one of >> those also did the encrypting? >> >> I do some encrypting on one small set of nodes, but the server does the >> encrypting. I’m merely making sure the tapes >> are encrypted so they can be stored remotely. Any reason why you have >> the client itself doing the encryption? >> I suppose it is more private that way ….. specially if the data is going >> over the network and might be seen there. >> >> This is by way of starting a discussion, and also “bump”. >> >> Deb Baddorf >> Fermilab >> >> >> On Mar 12, 2015, at 5:21 PM, Oscar Ricardo Silva wrote: >> >>> I've been testing encrypted storage of backups but am confused as to how to >>> restore files. In my setup, I run the backup server with other sysadmins >>> running the individual servers being backed up and ideally I'd like for >>> these sysadmins to restore files from the client systems without bothering >>> me ... I mean "without involving me" ... >>> >>> >>> I've had no luck restoring files using amrecover (one server encrypted with >>> amcrypt-ossl and another with amcrypt-ossl-asym) so I decided to review the >>> man page and saw: >>> >>> >>> *** >>> Note >>> The Default values are those set at compile-time. Use amrestore to recover >>> client-encrypted or client-custom-compressed tapes. >>> *** >>> >>> >>> >>> Does this mean that for the sysadmin of a client to restore files from an >>> encrypted backup, they can only use amrestore and not amrecover? amrestore >>> suggests (and I might be wrong) that the individual running it know a lot >>> about how the backups are stored. >>> >>> >>> The backups *SEEM* to run OK and using amrecover I can even browse the >>> files that were backed up. >>> >>> >>> I've reviewed the amanda HOWTOs and FAQ but while they describe the setup >>> for encrypted storage of backups, I don't believe there are examples on >>> restoring files. >>> >>> >>> >>> >>> Oscar >>
Re: restoring encrypted backups: amrecover vs amrestore
The idea behind client encryption is to treat each server/sysadmin as an independent operator and with encryption done by the client the contents of the tapes (or in our case, vtapes) wouldn't necessarily be accessible to the amanda server operator. Ultimately, server encryption gets us a little closer. We're already transmitting the backups over ssh so that gets us some privacy over the wire. I'll switch over one of my test systems to "server encryption" and see how that works. Thank you for the reply and the "bump" Oscar On 03/13/2015 03:33 PM, Debra S Baddorf wrote: Since you’ve gotten no answers yet (I know very little):might this be related to whether the client or the server is the one doing the unpacking of the dump, and in turn, which one of those also did the encrypting? I do some encrypting on one small set of nodes, but the server does the encrypting. I’m merely making sure the tapes are encrypted so they can be stored remotely. Any reason why you have the client itself doing the encryption? I suppose it is more private that way ….. specially if the data is going over the network and might be seen there. This is by way of starting a discussion, and also “bump”. Deb Baddorf Fermilab On Mar 12, 2015, at 5:21 PM, Oscar Ricardo Silva wrote: I've been testing encrypted storage of backups but am confused as to how to restore files. In my setup, I run the backup server with other sysadmins running the individual servers being backed up and ideally I'd like for these sysadmins to restore files from the client systems without bothering me ... I mean "without involving me" ... I've had no luck restoring files using amrecover (one server encrypted with amcrypt-ossl and another with amcrypt-ossl-asym) so I decided to review the man page and saw: *** Note The Default values are those set at compile-time. Use amrestore to recover client-encrypted or client-custom-compressed tapes. *** Does this mean that for the sysadmin of a client to restore files from an encrypted backup, they can only use amrestore and not amrecover? amrestore suggests (and I might be wrong) that the individual running it know a lot about how the backups are stored. The backups *SEEM* to run OK and using amrecover I can even browse the files that were backed up. I've reviewed the amanda HOWTOs and FAQ but while they describe the setup for encrypted storage of backups, I don't believe there are examples on restoring files. Oscar
Re: restoring encrypted backups: amrecover vs amrestore
Since you’ve gotten no answers yet (I know very little):might this be related to whether the client or the server is the one doing the unpacking of the dump, and in turn, which one of those also did the encrypting? I do some encrypting on one small set of nodes, but the server does the encrypting. I’m merely making sure the tapes are encrypted so they can be stored remotely. Any reason why you have the client itself doing the encryption? I suppose it is more private that way ….. specially if the data is going over the network and might be seen there. This is by way of starting a discussion, and also “bump”. Deb Baddorf Fermilab On Mar 12, 2015, at 5:21 PM, Oscar Ricardo Silva wrote: > I've been testing encrypted storage of backups but am confused as to how to > restore files. In my setup, I run the backup server with other sysadmins > running the individual servers being backed up and ideally I'd like for these > sysadmins to restore files from the client systems without bothering me ... I > mean "without involving me" ... > > > I've had no luck restoring files using amrecover (one server encrypted with > amcrypt-ossl and another with amcrypt-ossl-asym) so I decided to review the > man page and saw: > > > *** > Note > The Default values are those set at compile-time. Use amrestore to recover > client-encrypted or client-custom-compressed tapes. > *** > > > > Does this mean that for the sysadmin of a client to restore files from an > encrypted backup, they can only use amrestore and not amrecover? amrestore > suggests (and I might be wrong) that the individual running it know a lot > about how the backups are stored. > > > The backups *SEEM* to run OK and using amrecover I can even browse the files > that were backed up. > > > I've reviewed the amanda HOWTOs and FAQ but while they describe the setup for > encrypted storage of backups, I don't believe there are examples on restoring > files. > > > > > Oscar
restoring encrypted backups: amrecover vs amrestore
I've been testing encrypted storage of backups but am confused as to how to restore files. In my setup, I run the backup server with other sysadmins running the individual servers being backed up and ideally I'd like for these sysadmins to restore files from the client systems without bothering me ... I mean "without involving me" ... I've had no luck restoring files using amrecover (one server encrypted with amcrypt-ossl and another with amcrypt-ossl-asym) so I decided to review the man page and saw: *** Note The Default values are those set at compile-time. Use amrestore to recover client-encrypted or client-custom-compressed tapes. *** Does this mean that for the sysadmin of a client to restore files from an encrypted backup, they can only use amrestore and not amrecover? amrestore suggests (and I might be wrong) that the individual running it know a lot about how the backups are stored. The backups *SEEM* to run OK and using amrecover I can even browse the files that were backed up. I've reviewed the amanda HOWTOs and FAQ but while they describe the setup for encrypted storage of backups, I don't believe there are examples on restoring files. Oscar
Re: Restoring/indexing
On Sun, Sep 12, 2010 at 10:10 AM, Dustin J. Mitchell wrote: > On Fri, Sep 10, 2010 at 3:02 PM, Jon Brown wrote: >> Is there a way to have amrecover restore from multiple DLE's at the same >> time? >> Ideally by providing an input file that would specify the >> hosts/volumes/directories that I would like to have restored. > > Not that I can think of. You could script amfetchdump for this > purpose, though.. > >> What is the best way to recover an index of a tape when spanning tapes? >> e.g. the index has been lost, using tape spanning and I only want to see >> what is on the tape. > > We need a utility that will scan a tape and rebuild the catalog from > it (I imagine it would be called amrecatalog). But such a thing does > not exist at this point. > > Dustin > > -- > Open Source Storage Engineer > http://www.zmanda.com > > I recall a script called 'amcattape' or something like that. I think it was a third-party thing, and I don't remember where I got it, but possibly the amanda wiki. I haven't looked at it in years, but it would read a tape and output a description of the contents, with all DLEs. It didn't create a proper index, but was useful in a couple of emergencies. -- -- Jeffrey Anderson | jdander...@lbl.gov Lawrence Berkeley National Laboratory | Office: 50A-5104E | Mailstop 50A-5101 Phone: 510 486-4208 | Fax: 510 486-4204
Re: Restoring/indexing
On Fri, Sep 10, 2010 at 3:02 PM, Jon Brown wrote: > Is there a way to have amrecover restore from multiple DLE's at the same > time? > Ideally by providing an input file that would specify the > hosts/volumes/directories that I would like to have restored. Not that I can think of. You could script amfetchdump for this purpose, though.. > What is the best way to recover an index of a tape when spanning tapes? > e.g. the index has been lost, using tape spanning and I only want to see > what is on the tape. We need a utility that will scan a tape and rebuild the catalog from it (I imagine it would be called amrecatalog). But such a thing does not exist at this point. Dustin -- Open Source Storage Engineer http://www.zmanda.com
Restoring/indexing
Hi, couple of questions hopefully I can get clarified, Is there a way to have amrecover restore from multiple DLE's at the same time? Ideally by providing an input file that would specify the hosts/volumes/directories that I would like to have restored. What is the best way to recover an index of a tape when spanning tapes? e.g. the index has been lost, using tape spanning and I only want to see what is on the tape. Thanks! JB
Re: restoring without amanda
On Monday 22 March 2010, Dustin J. Mitchell wrote: >On Mon, Mar 22, 2010 at 7:29 AM, Chris Hoogendyk > > wrote: >> I've also tried just reading the Amanda tapes directly. It works even if >> it is a little tedious. In my case the sequence of commands involves >> ufsrestore, but that too is documented on the tape itself in the first >> record. > >I've been thinking about an "amrecatalog" utility for a while now. It >would be similar to amrestore, but would output a useable trace log >file giving the location and header metadata for all files on the >tape. This would be helpful during a bare-metal recovery with highly >split DLEs, since you could use amfetchdump to reassemble the files >once amrecatalog had generated logs for the tape. > >This would be a Perl script much like amrestore. It could also be >implemented as an option to amrestore (maybe 'amrestore --recatalog'), >which is already in Perl. There's probably still a window to get this >into 3.1 if anyone wants to give it a try! > >Dustin This is one place where GenesAmandaHelper is quite redundant. I not only have a copy of both the configs AND the indices as of the end of the amanda run on my vtapes, I use amanda style housekeeping in that scratchpad directory I generate them in, in that directory tree also, so I wind up with 3 copies of all that, 100% uptodate. One on the tape, one in the GenesAmandaHelper subdir, and the ones amanda actually looks for. [r...@coyote f12]# ls /GenesAmandaHelper-0.6/config-bak/ configuration.tar.Dailys-1 configuration.tar.Dailys-26 dd.report.Dailys-15 dd.report.Dailys-4 indices.tar.Dailys-20 configuration.tar.Dailys-10 configuration.tar.Dailys-27 dd.report.Dailys-16 dd.report.Dailys-5 indices.tar.Dailys-21 configuration.tar.Dailys-11 configuration.tar.Dailys-28 dd.report.Dailys-17 dd.report.Dailys-6 indices.tar.Dailys-22 configuration.tar.Dailys-12 configuration.tar.Dailys-29 dd.report.Dailys-18 dd.report.Dailys-7 indices.tar.Dailys-23 configuration.tar.Dailys-13 configuration.tar.Dailys-3 dd.report.Dailys-19 dd.report.Dailys-8 indices.tar.Dailys-24 configuration.tar.Dailys-14 configuration.tar.Dailys-30 dd.report.Dailys-2 dd.report.Dailys-9 indices.tar.Dailys-25 configuration.tar.Dailys-15 configuration.tar.Dailys-4 dd.report.Dailys-20 indices.tar.Dailys-1 indices.tar.Dailys-26 configuration.tar.Dailys-16 configuration.tar.Dailys-5 dd.report.Dailys-21 indices.tar.Dailys-10 indices.tar.Dailys-27 configuration.tar.Dailys-17 configuration.tar.Dailys-6 dd.report.Dailys-22 indices.tar.Dailys-11 indices.tar.Dailys-28 configuration.tar.Dailys-18 configuration.tar.Dailys-7 dd.report.Dailys-23 indices.tar.Dailys-12 indices.tar.Dailys-29 configuration.tar.Dailys-19 configuration.tar.Dailys-8 dd.report.Dailys-24 indices.tar.Dailys-13 indices.tar.Dailys-3 configuration.tar.Dailys-2 configuration.tar.Dailys-9 dd.report.Dailys-25 indices.tar.Dailys-14 indices.tar.Dailys-30 configuration.tar.Dailys-20 dd.report.Dailys-1 dd.report.Dailys-26 indices.tar.Dailys-15 indices.tar.Dailys-4 configuration.tar.Dailys-21 dd.report.Dailys-10 dd.report.Dailys-27 indices.tar.Dailys-16 indices.tar.Dailys-5 configuration.tar.Dailys-22 dd.report.Dailys-11 dd.report.Dailys-28 indices.tar.Dailys-17 indices.tar.Dailys-6 configuration.tar.Dailys-23 dd.report.Dailys-12 dd.report.Dailys-29 indices.tar.Dailys-18 indices.tar.Dailys-7 configuration.tar.Dailys-24 dd.report.Dailys-13 dd.report.Dailys-3 indices.tar.Dailys-19 indices.tar.Dailys-8 configuration.tar.Dailys-25 dd.report.Dailys-14 dd.report.Dailys-30 indices.tar.Dailys-2 indices.tar.Dailys-9 As the (v)tapes are reused the old files are deleted and new ones constructed. The file dd.report.Dailys-xx is used by my script to track the use counts of the tapes. That is the first entry, then a list of the contents packed into the other two files follows. Handy to read as it tells you where to put everything too. So I have several ways of restoring in the event this cat runs out of lives. ;) -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) I consider the day misspent that I am not either charged with a crime, or arrested for one. -- "Ratsy" Tourbillon
Re: restoring without amanda
On Monday 22 March 2010, Chris Hoogendyk wrote: >Gene Heskett wrote: >> On Sunday 21 March 2010, Steve Wray wrote: >>> Hi there >>> >>> I'm preparing some documentation on our backup/restore process. >>> >>> Some time ago I linked to amanda documentation on how to extract from >>> tapes without using any amanda tools or indexes. >>> >>> This link was: >>> >>> http://www.amanda.org/docs/using.html#restoring_without_amanda >>> >>> and is now broken. >>> >>> This isn't quite what I'm after as it uses amrestore: >>> >>> http://wiki.zmanda.com/index.php/How_To:Recover_Lost_Amanda_Configuratio >>>n >>> >>> >>> Can anyone point me at the current correct link please? >>> >>> Thanks! >> >> cd to /tmp, then dd the first block of the tape to std out. You will see >> a command line that will recover that file to /tmp. Repeat till out of >> tape. I keep the amanda printouts, so I know which tape has the last >> level0 backup of the amanda stuff, and pull that out first. It will >> probably be 3 or 4 tapes to get it all, but once you've pulled the >> config, then get the indexes & put both back where they go. Next get the >> directory you built amanda in, probably /home and copy that back. cd to >> /home/amanda (if amanda is the user that built and installed it, and do >> another install as root. >> >> That ought to get you enough to run amrecover at which point load it up >> with the full monty and stand by to give it the tapes it asks for. > >Or, you can be a bit more preemptive. > >I have a script that runs after the Amanda backup is done and copies all >the Amanda home directory to another server. This includes all the >configuration and indexes. You can do this with just about any mechanism >you're comfortable with -- cpio, tar, scp, rsync, ... whatever. Each of >my Amanda servers sends everything over to another Amanda server. Sort >of a round robin. I use a script with a combination of find and cpio to >achieve a sequence of full and incremental backups that are kept for a > week. > >Without something like the above, you end up being a backup behind on >things like the indexes. Backups of the Amanda home directory that are >on tape can't include the latest changes to the Amanda indexes made as >backups that go on that tape are being collected. > >I've also tried just reading the Amanda tapes directly. It works even if >it is a little tedious. In my case the sequence of commands involves >ufsrestore, but that too is documented on the tape itself in the first >record. > Exactly why I wrote GenesAmandaHelper, Chris. So we're both on the same wavelength there. So we both have last nights indexes saved and usable. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) It's union rules. There's nothing we can do about it. Sorry.
Re: restoring without amanda
Chris Hoogendyk schrieb: > > > Gene Heskett wrote: >> On Sunday 21 March 2010, Steve Wray wrote: > Or, you can be a bit more preemptive. > > I have a script that runs after the Amanda backup is done and copies all > the Amanda home directory to another server. This includes all the > configuration and indexes. You can do this with just about any mechanism > you're comfortable with -- cpio, tar, scp, rsync, ... whatever. Each of > my Amanda servers sends everything over to another Amanda server. Sort > of a round robin. I use a script with a combination of find and cpio to > achieve a sequence of full and incremental backups that are kept for a > week. Yes, that is something I do on our systems too, but only locally. In most cases we're using something like an MD1000 with virtual tapes, so in case the the server providing the OS goes down, we still have the parts of /etc/amanda and /var/lib/amanda on that external storage. We only have to set up a new server and rsync the "local_backup" data back from the storage. For very important systems I have a dedicated backupserver just for the amanda-stuff of the important servers. It already did save my day once :) /Michael -- Michael Müskens Rule #18: It's better to seek forgiveness than ask permission. signature.asc Description: OpenPGP digital signature
Re: restoring without amanda
On Mon, Mar 22, 2010 at 7:29 AM, Chris Hoogendyk wrote: > I've also tried just reading the Amanda tapes directly. It works even if it > is a little tedious. In my case the sequence of commands involves > ufsrestore, but that too is documented on the tape itself in the first > record. I've been thinking about an "amrecatalog" utility for a while now. It would be similar to amrestore, but would output a useable trace log file giving the location and header metadata for all files on the tape. This would be helpful during a bare-metal recovery with highly split DLEs, since you could use amfetchdump to reassemble the files once amrecatalog had generated logs for the tape. This would be a Perl script much like amrestore. It could also be implemented as an option to amrestore (maybe 'amrestore --recatalog'), which is already in Perl. There's probably still a window to get this into 3.1 if anyone wants to give it a try! Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: restoring without amanda
Gene Heskett wrote: On Sunday 21 March 2010, Steve Wray wrote: Hi there I'm preparing some documentation on our backup/restore process. Some time ago I linked to amanda documentation on how to extract from tapes without using any amanda tools or indexes. This link was: http://www.amanda.org/docs/using.html#restoring_without_amanda and is now broken. This isn't quite what I'm after as it uses amrestore: http://wiki.zmanda.com/index.php/How_To:Recover_Lost_Amanda_Configuration Can anyone point me at the current correct link please? Thanks! cd to /tmp, then dd the first block of the tape to std out. You will see a command line that will recover that file to /tmp. Repeat till out of tape. I keep the amanda printouts, so I know which tape has the last level0 backup of the amanda stuff, and pull that out first. It will probably be 3 or 4 tapes to get it all, but once you've pulled the config, then get the indexes & put both back where they go. Next get the directory you built amanda in, probably /home and copy that back. cd to /home/amanda (if amanda is the user that built and installed it, and do another install as root. That ought to get you enough to run amrecover at which point load it up with the full monty and stand by to give it the tapes it asks for. Or, you can be a bit more preemptive. I have a script that runs after the Amanda backup is done and copies all the Amanda home directory to another server. This includes all the configuration and indexes. You can do this with just about any mechanism you're comfortable with -- cpio, tar, scp, rsync, ... whatever. Each of my Amanda servers sends everything over to another Amanda server. Sort of a round robin. I use a script with a combination of find and cpio to achieve a sequence of full and incremental backups that are kept for a week. Without something like the above, you end up being a backup behind on things like the indexes. Backups of the Amanda home directory that are on tape can't include the latest changes to the Amanda indexes made as backups that go on that tape are being collected. I've also tried just reading the Amanda tapes directly. It works even if it is a little tedious. In my case the sequence of commands involves ufsrestore, but that too is documented on the tape itself in the first record. -- --- Chris Hoogendyk - O__ Systems Administrator c/ /'_ --- Biology & Geology Departments (*) \(*) -- 140 Morrill Science Center ~~ - University of Massachusetts, Amherst --- Erdös 4
Re: restoring without amanda
On Sunday 21 March 2010, Steve Wray wrote: >Hi there > >I'm preparing some documentation on our backup/restore process. > >Some time ago I linked to amanda documentation on how to extract from tapes >without using any amanda tools or indexes. > >This link was: > >http://www.amanda.org/docs/using.html#restoring_without_amanda > >and is now broken. > >This isn't quite what I'm after as it uses amrestore: > >http://wiki.zmanda.com/index.php/How_To:Recover_Lost_Amanda_Configuration > > >Can anyone point me at the current correct link please? > >Thanks! > cd to /tmp, then dd the first block of the tape to std out. You will see a command line that will recover that file to /tmp. Repeat till out of tape. I keep the amanda printouts, so I know which tape has the last level0 backup of the amanda stuff, and pull that out first. It will probably be 3 or 4 tapes to get it all, but once you've pulled the config, then get the indexes & put both back where they go. Next get the directory you built amanda in, probably /home and copy that back. cd to /home/amanda (if amanda is the user that built and installed it, and do another install as root. That ought to get you enough to run amrecover at which point load it up with the full monty and stand by to give it the tapes it asks for. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) "It's ten o'clock... Do you know where your AI programs are?" -- Peter Oakley
Re: restoring without amanda
Steve Wray schrieb: > > Some time ago I linked to amanda documentation on how to extract from > tapes without using any amanda tools or indexes. > > This link was: > > http://www.amanda.org/docs/using.html#restoring_without_amanda > > and is now broken. > > This isn't quite what I'm after as it uses amrestore: > > http://wiki.zmanda.com/index.php/How_To:Recover_Lost_Amanda_Configuration I figure that's what your looking for: http://wiki.zmanda.com/index.php/Restoring_files Actually you have the way to restore with in every Amandadump: To restore, position tape at start of file and run: dd if= bs=32k skip=1 | /bin/gzip -dc | /bin/tar -xpGf - ... Michael -- Michael Müskens Rule #18: It's better to seek forgiveness than ask permission. signature.asc Description: OpenPGP digital signature
restoring without amanda
Hi there I'm preparing some documentation on our backup/restore process. Some time ago I linked to amanda documentation on how to extract from tapes without using any amanda tools or indexes. This link was: http://www.amanda.org/docs/using.html#restoring_without_amanda and is now broken. This isn't quite what I'm after as it uses amrestore: http://wiki.zmanda.com/index.php/How_To:Recover_Lost_Amanda_Configuration Can anyone point me at the current correct link please? Thanks! -- Please remember that an email is just like a postcard; it is not confidential nor private nor secure and can be read by many other people than the intended recipient. A postcard can be read by anyone at the mail sorting office and expecting what is written on it to be private and secret is not realistic. Please hold no higher expectation of email. If you need to send confidential information in an email you need to use encryption. PGP is Pretty good for this.
Re: [Amanda-users] ZRM error restoring file
On Thu, May 7, 2009 at 10:23 AM, ga jimenez55 wrote: > I have amanda serven in a SPARC solaris 10. when i going to do restore my > file i have this error >From your subject and the content of your post, it looks like you're using ZRM. This is amanda-us...@amanda.org. Please post to the correct forum. Dustin Other amanda-users denizens: sorry for the noise -- backupcentral seems to to provide a way to reply to the sender only. -- Open Source Storage Engineer http://www.zmanda.com
[Amanda-users] ZRM error restoring file
I have amanda serven in a SPARC solaris 10. when i going to do restore my file i have this error Use of uninitialized value in concatenation (.) or string at /opt/zmanda/amanda/bin/amfetchandresolve line 3352. DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 at /opt/zmanda/amanda/bin/amfetchandresolve line 3602. Use of uninitialized value in concatenation (.) or string at /opt/zmanda/amanda/bin/amfetchandresolve line 3356. Use of uninitialized value in concatenation (.) or string at /opt/zmanda/amanda/bin/amfetchandresolve line 3356. DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'and restore=true) and conf_dle_id=' at line 1 at /opt/zmanda/amanda/perl/lib/5.8.8/sun4-solaris-thread-multi-64/Logging.pm line 197. ERROR: Error selecting index files list from index_details ERROR: Files Not Selected for Restore Error restoring the selected files +-- |This was sent by tavog...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
[Amanda-users] Restoring amanda tapes without amanda
I did use the name of my virtual tape its a file on directory, it works, get back all from my backup without using amanda restore command, becouse did not have index # dd if=1.desktop.__tijuanaserver_www.0 bs=32k skip=1 | tar -zxvf - thanks for your post it help me to get this done. +-- |This was sent by amest...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: [Amanda-users] Restoring amanda tapes without amanda
On 2008-11-27 22:49, rory_f wrote: As amanda uses tar, you surely can restore a tape (or a portion of a tape, perhaps just a dle?) using the command line 'tar' command, right ? Is it just the same as a normal extract ? tar -xvf /dev/nst0 ? Or do you have to do other things to ensure this works properly. Nothing is wrong with my amanda configuration, but It's something i want to document for my own reference :) For a lot of different scenario's, including how to restore without amanda software: http://wiki.zmanda.com/index.php/Restoring_files -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
[Amanda-users] Restoring amanda tapes without amanda
sf karel wrote: > On Nov 27, 2008, at 4:49 PM, rory_f wrote: > > > > > > As amanda uses tar, you surely can restore a tape (or a portion of > > a tape, perhaps just a dle?) using the command line 'tar' command, > > right ? > > > > no, amanda doesn't always use tar. See the latter part of the AMANDA > chapter from "Backup and Recovery" for the commands to use "mt" and > "dd" to extract files from the tapes and then use tar from the > command line if that is how the backup was made. > > http://wiki.zmanda.com/index.php/Amanda_chapter_in_Backup_and_Recovery i always do my runs with gnutar and i always observe tar processes on my machines when taping is going on so im sure my backups use tar. thanks for the link +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +--
Re: [Amanda-users] Restoring amanda tapes without amanda
On Nov 27, 2008, at 4:49 PM, rory_f wrote: As amanda uses tar, you surely can restore a tape (or a portion of a tape, perhaps just a dle?) using the command line 'tar' command, right ? no, amanda doesn't always use tar. See the latter part of the AMANDA chapter from "Backup and Recovery" for the commands to use "mt" and "dd" to extract files from the tapes and then use tar from the command line if that is how the backup was made. http://wiki.zmanda.com/index.php/Amanda_chapter_in_Backup_and_Recovery
[Amanda-users] Restoring amanda tapes without amanda
As amanda uses tar, you surely can restore a tape (or a portion of a tape, perhaps just a dle?) using the command line 'tar' command, right ? Is it just the same as a normal extract ? tar -xvf /dev/nst0 ? Or do you have to do other things to ensure this works properly. Nothing is wrong with my amanda configuration, but It's something i want to document for my own reference :) Rory +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +--
Re: Problem Restoring Files
Steven Backus wrote: amrecover: time 392.438: security_close(handle=0x8c40330, driver=0xd4b120 (BSD)) amrecover: time 408.626: security_stream_close(0x8c48fa8) amrecover: time 408.627: Can't read file header amrecover: time 408.627: pid 6276 finish time Fri May 16 08:55:28 2008 amrecover: time 408.627: security_stream_close(0x8c40f70 It failed to restore the full, it only restored the incremental level 1 and 2. Did you see a failed message in the amrecover session? Can you post the corresponding amandad.*.debug and amidxtaped.*.debug files from the server. Jean-Louis
Re: Problem Restoring Files
> Looks like it restored only the level 1, not the full. It is a known > bug, it is fixed in latest 2.5.2p1 snapshot from > http://www.zmanda.com/community-builds.php/amanda-2.5.2p1-20071101.tar.gz I'll try this and post the logs if it doesn't work. Thanks, Steve -- Steven J. BackusComputer Specialist University of Utah E-Mail: [EMAIL PROTECTED] Genetic EpidemiologyAlternate: [EMAIL PROTECTED] 391 Chipeta Way -- Suite D150 Office: 801.587.9308 Salt Lake City, UT 84108-1266 http://www.math.utah.edu/~backus
Re: Problem Restoring Files
Steven Backus wrote: I'm having a problem restoring on my 2.5.2p1 system. The indexes show all the data is there: amrecover> sethost ambiance 501 Host ambiance is not in your disklist. Trying host ambiance.med.utah.edu ... 200 Dump host set to ambiance.med.utah.edu. amrecover> listdisk 200- List of disk for host ambiance.med.utah.edu 201- / 201- sdc1 201- sdb5 200 List of disk for host ambiance.med.utah.edu amrecover> setdisk sdc1 200 Disk set to sdc1. amrecover> cd /9gb/jv/mcsim/prost/ICPCG_CIDR /9gb/jv/mcsim/prost/ICPCG_CIDR amrecover> ls 2008-05-09 noLDanal/ 2008-05-09 Summary/ 2008-05-09 . 2008-05-05 tmp.pl~ 2008-05-05 tmp.pl 2008-05-05 summclinx 2008-05-05 runProstSet2 2008-05-05 runProstSet1 2008-05-05 runMela_SNP_summary 2008-05-05 runICPCG_CIDR.summary 2008-05-05 runICPCG_CIDR.best~ 2008-05-05 runICPCG_CIDR.best 2008-05-05 runGWMelaSNP 2008-05-05 run.merlin2labout~ 2008-05-05 run.merlin2labout 2008-05-05 run.mcsimPrep2~ 2008-05-05 run.mcsimPrep2 2008-05-05 out.log 2008-05-05 icpcg_cidr.noLD.hets But only the directory structure is restored when I extract: % cd /9gb/jv/mcsim/prost/ICPCG_CIDR % ls Files/ LDanal/ Rcode/ Summary/ noLDanal/ None of the files are restored. I'm using tar 1.15.1, just let me know if you need more information. As always, the complete debug files and the complete amrecover session. The 'amadmin ... find ambiance sdc1' output. Looks like it restored only the level 1, not the full. It is a known bug, it is fixed in latest 2.5.2p1 snapshot from http://www.zmanda.com/community-builds.php/amanda-2.5.2p1-20071101.tar.gz Jean-Louis
Problem Restoring Files
I'm having a problem restoring on my 2.5.2p1 system. The indexes show all the data is there: amrecover> sethost ambiance 501 Host ambiance is not in your disklist. Trying host ambiance.med.utah.edu ... 200 Dump host set to ambiance.med.utah.edu. amrecover> listdisk 200- List of disk for host ambiance.med.utah.edu 201- / 201- sdc1 201- sdb5 200 List of disk for host ambiance.med.utah.edu amrecover> setdisk sdc1 200 Disk set to sdc1. amrecover> cd /9gb/jv/mcsim/prost/ICPCG_CIDR /9gb/jv/mcsim/prost/ICPCG_CIDR amrecover> ls 2008-05-09 noLDanal/ 2008-05-09 Summary/ 2008-05-09 . 2008-05-05 tmp.pl~ 2008-05-05 tmp.pl 2008-05-05 summclinx 2008-05-05 runProstSet2 2008-05-05 runProstSet1 2008-05-05 runMela_SNP_summary 2008-05-05 runICPCG_CIDR.summary 2008-05-05 runICPCG_CIDR.best~ 2008-05-05 runICPCG_CIDR.best 2008-05-05 runGWMelaSNP 2008-05-05 run.merlin2labout~ 2008-05-05 run.merlin2labout 2008-05-05 run.mcsimPrep2~ 2008-05-05 run.mcsimPrep2 2008-05-05 out.log 2008-05-05 icpcg_cidr.noLD.hets But only the directory structure is restored when I extract: % cd /9gb/jv/mcsim/prost/ICPCG_CIDR % ls Files/ LDanal/ Rcode/ Summary/ noLDanal/ None of the files are restored. I'm using tar 1.15.1, just let me know if you need more information. Thanks, Steve -- Steven J. BackusComputer Specialist University of Utah E-Mail: [EMAIL PROTECTED] Genetic EpidemiologyAlternate: [EMAIL PROTECTED] 391 Chipeta Way -- Suite D150 Office: 801.587.9308 Salt Lake City, UT 84108-1266 http://www.math.utah.edu/~backus
Re: Restoring info from Windows
Mario Silva Borrego schrieb: > any thoughts ? Sure > amrecover: warning: using /dev/null as the tape device will not work Choose your correct tape-device (the one you use as "tapedev" in your amanda.conf) at the step > Extracting files using tape drive /dev/null on host amanda.nmcourts.com. > Load tape ws2003sms01-Backups-9 now > Continue [?/Y/n/s/t]? via "t" or by adding the option "-d tape-device" to amrecover. "man amrecover" also helps, but don't tell anyone, we keep those infos secret ;-) > warning: restore program for /usr/bin/smbclient not available. > amrecover couldn't exec: No such file or directory > problem executing restore this is another story ... try upper suggestions first and let us know. Stefan
Restoring info from Windows
Hi guys: I want you to ask about how to restore information from a Windows Client. I am getting this error message when I am trying to restore directly from windows side: This is my amrecover session: amrecover> sethost amanda.nmcourts.com 200 Dump host set to amanda.nmcourts.com. amrecover> setdisk //ws2003sms01/Backup$ 200 Disk set to //ws2003sms01/Backup$. amrecover> lcd /tmp amrecover> add websenserptr Added dir /websenserptr/ at date 2008-01-29-20-00-01 amrecover> extract amrecover: warning: using /dev/null as the tape device will not work Extracting files using tape drive /dev/null on host amanda.nmcourts.com. The following tapes are needed: ws2003sms01-Backups-9 Restoring files into directory /tmp Continue [?/Y/n]? Y Extracting files using tape drive /dev/null on host amanda.nmcourts.com. Load tape ws2003sms01-Backups-9 now Continue [?/Y/n/s/t]? Y warning: restore program for /usr/bin/smbclient not available. amrecover couldn't exec: No such file or directory problem executing restore any thoughts ? -- Mario Silva Borrego Systems Administrator Supreme Court of New Mexico Judicial Information Division 2905 Rodeo Park Dr. East, Bldg. #5 Santa Fe, NM 87505 Phone: (505) 476-6959 / Mobil: (505) 660-1026 Fax:(505) 476-6952 Website: http://www.nmcourts.gov mailto: [EMAIL PROTECTED] LEGAL DISCLAIMER: The content of this data transmission is not considered as an offer, proposal, understanding, or agreement unless it is confirmed in a document signed by a legal representative of Supreme Court of the State of New Mexico or the Judicial Information Division. The content of this data transmission is confidential and it is intended to be delivered only to the addresses, therefore, it shall not be distributed and/or disclosed through any mean without the original sender's previous authorization. If you are not the addressee you are forbidden to use it, either totally or partially, for any purpose. AVISO LEGAL: El contenido de este mensaje de datos no se considera oferta, propuesta o acuerdo, sino hasta que sea confirmado en documento por escrito que contenga la firma autógrafa del apoderado legal de La Suprema Corte del Estado de Nuevo Mexico o de la Division de Informatica del Estado. El contenido de este mensaje de datos es confidencial y se entiende dirigido y para uso exclusivo del destinatario, por lo que no podrá distribuirse y/o difundirse por ningún medio sin la previa autorización del emisor original. Si usted no es el destinatario, se le prohíbe su utilización total o parcial para cualquier fin. begin:vcard fn:Mario Silva Borrego n:Silva Borrego;Mario org:Supreme Court of New Mexico;Judicial Information Division adr:;;2905 Rodeo Park Dr. East, Bldg. #5;Santa Fe;NM;87505;USA email;internet:[EMAIL PROTECTED] title:Systems Administrator tel;work:(505) 476-6959 tel;fax:(505) 476-6952 tel;cell:(505) 660-1026 x-mozilla-html:TRUE url:http://www.nmcourts.gov version:2.1 end:vcard
Re: Restoring from a holding disk?
On 9/7/07, Chris Hoogendyk <[EMAIL PROTECTED]> wrote: > Why get tangled up trying to second guess Amanda? Amanda knows what's on > tape and what's on holding disk and how to put it together. In my > experience, I can simply do > > $ amrecover daily > > and specify a host, etc. and it will recover it. I've purposely tested > this on stuff that was left in the holding disk. It seems that the only > time you should have to piece things together "manually" is if the > amanda server itself is down and you have nothing set up for the > situation and no other recourse but to start using dd, concatenating > pieces, gunzipping them, untarring them, etc. And those steps are > actually spelled out in the file header when it goes on tape. > > Am I mistaken or missing something here? I've had bad luck with amrecover in the past; it seemed fairly unreliable the last time I tried it (Amanda 2.4.4p3 on RHEL 4), and so I've avoided it since. I really ought to give it another try, though. Thank you for the encouragement to do so. Josh Kelley
Re: Restoring from a holding disk?
On 9/7/07, Jean-Louis Martineau <[EMAIL PROTECTED]> wrote: > You must remove the first 32k bytes of each files > > for i in `ls -1 alva._home.4*`; do dd if=$i bs=32k skip=1 >> wholedump.0; done > > and run tar directly on wholedump.0, may need to be uncompressed. That worked. Thank you for your help. Josh Kelley
Re: Restoring from a holding disk?
amrecover Then you set the hostname, which might be in your disklist file: sethost www.dell.com Then you set the DLE you want to work: setdisk /usr then you've done ! you can navigate in all the structure and just typing "add directory>" you will restore information after you type extract if you want I can send you a full restore session of my amanda server. mario once you are in the amrecover session, you can type help and you'll see is pretty easy to understand what you need to do, this way work pretty fine for me and I can restore the information so fast. mario Chris Hoogendyk wrote: Josh Kelley wrote: I checked the wiki and Google and couldn't find an answer. How do I restore from files on a holding disk if the dump has been split across multiple chunks on the holding disk? I have the following files: alva._home.4alva._home.4.2 alva._home.4.4 alva._home.4.1 alva._home.4.3 alva._home.4.5 I can restore from alva._home.4 using amrestore as normal: amrestore -p alva._home.4 | tar xvf - But that's obviously only part of the backup. If I try to concatenate all of the files together, as the wiki suggests when using amrestore to restore from a tape: for i in `ls -1 alva._home.4*`; do dd if=$i >> wholedump.0; done then run amrestore on wholedump.0, amrestore successfully processes the data corresponding to alva._home.4 then gives the following errors: tar: Skipping to next header gzip: stdin: invalid compressed data--crc error gzip: stdin: invalid compressed data--length error What's the correct procedure for restoring from holding disk files in this case? Why get tangled up trying to second guess Amanda? Amanda knows what's on tape and what's on holding disk and how to put it together. In my experience, I can simply do $ amrecover daily and specify a host, etc. and it will recover it. I've purposely tested this on stuff that was left in the holding disk. It seems that the only time you should have to piece things together "manually" is if the amanda server itself is down and you have nothing set up for the situation and no other recourse but to start using dd, concatenating pieces, gunzipping them, untarring them, etc. And those steps are actually spelled out in the file header when it goes on tape. Am I mistaken or missing something here? --- Chris Hoogendyk - O__ Systems Administrator c/ /'_ --- Biology & Geology Departments (*) \(*) -- 140 Morrill Science Center ~~ - University of Massachusetts, Amherst <[EMAIL PROTECTED]> --- Erdös 4 -- Mario Silva Systems Administrator Supreme Court of New Mexico Judicial Information Division 2905 Rodeo Park Dr. East, Bldg. #5 Santa Fe, NM 87505 Phone: (505) 476-6959 / Mobil: (505) 660-1026 Fax:(505) 476-6952 Website: http://www.nmcourts.gov mailto: [EMAIL PROTECTED] LEGAL DISCLAIMER: The content of this data transmission is not considered as an offer, proposal, understanding, or agreement unless it is confirmed in a document signed by a legal representative of Supreme Court of the State of New Mexico or the Judicial Information Division. The content of this data transmission is confidential and it is intended to be delivered only to the addresses, therefore, it shall not be distributed and/or disclosed through any mean without the original sender's previous authorization. If you are not the addressee you are forbidden to use it, either totally or partially, for any purpose. AVISO LEGAL: El contenido de este mensaje de datos no se considera oferta, propuesta o acuerdo, sino hasta que sea confirmado en documento por escrito que contenga la firma autógrafa del apoderado legal de La Suprema Corte del Estado de Nuevo Mexico o de la Division de Informatica del Estado. El contenido de este mensaje de datos es confidencial y se entiende dirigido y para uso exclusivo del destinatario, por lo que no podrá distribuirse y/o difundirse por ningún medio sin la previa autorización del emisor original. Si usted no es el destinatario, se le prohíbe su utilización total o parcial para cualquier fin. begin:vcard fn:Mario Silva n:Silva;Mario org:Supreme Court of New Mexico;Judicial Information Division adr:;;2905 Rodeo Park Dr. East, Bldg. #5;Santa Fe;NM;87505;USA email;internet:[EMAIL PROTECTED] title:Systems Administrator tel;work:(505) 476-6959 tel;fax:(505) 476-6952 tel;cell:(505) 660-1026 x-mozilla-html:TRUE url:http://www.nmcourts.gov version:2.1 end:vcard
Re: Restoring from a holding disk?
Josh Kelley wrote: > I checked the wiki and Google and couldn't find an answer. How do I > restore from files on a holding disk if the dump has been split across > multiple chunks on the holding disk? > > I have the following files: > alva._home.4alva._home.4.2 alva._home.4.4 > alva._home.4.1 alva._home.4.3 alva._home.4.5 > > I can restore from alva._home.4 using amrestore as normal: > > amrestore -p alva._home.4 | tar xvf - > > But that's obviously only part of the backup. > > If I try to concatenate all of the files together, as the wiki > suggests when using amrestore to restore from a tape: > > for i in `ls -1 alva._home.4*`; do dd if=$i >> wholedump.0; done > > then run amrestore on wholedump.0, amrestore successfully processes > the data corresponding to alva._home.4 then gives the following > errors: > > tar: Skipping to next header > gzip: stdin: invalid compressed data--crc error > gzip: stdin: invalid compressed data--length error > > What's the correct procedure for restoring from holding disk files in this > case? Why get tangled up trying to second guess Amanda? Amanda knows what's on tape and what's on holding disk and how to put it together. In my experience, I can simply do $ amrecover daily and specify a host, etc. and it will recover it. I've purposely tested this on stuff that was left in the holding disk. It seems that the only time you should have to piece things together "manually" is if the amanda server itself is down and you have nothing set up for the situation and no other recourse but to start using dd, concatenating pieces, gunzipping them, untarring them, etc. And those steps are actually spelled out in the file header when it goes on tape. Am I mistaken or missing something here? --- Chris Hoogendyk - O__ Systems Administrator c/ /'_ --- Biology & Geology Departments (*) \(*) -- 140 Morrill Science Center ~~ - University of Massachusetts, Amherst <[EMAIL PROTECTED]> --- Erdös 4
Re: Restoring from a holding disk?
I preffer to use the amrecover, which is interactive and if amanda needs to look for chunks, amrecover will do it for you automaticly. mario Josh Kelley wrote: I checked the wiki and Google and couldn't find an answer. How do I restore from files on a holding disk if the dump has been split across multiple chunks on the holding disk? I have the following files: alva._home.4alva._home.4.2 alva._home.4.4 alva._home.4.1 alva._home.4.3 alva._home.4.5 I can restore from alva._home.4 using amrestore as normal: amrestore -p alva._home.4 | tar xvf - But that's obviously only part of the backup. If I try to concatenate all of the files together, as the wiki suggests when using amrestore to restore from a tape: for i in `ls -1 alva._home.4*`; do dd if=$i >> wholedump.0; done then run amrestore on wholedump.0, amrestore successfully processes the data corresponding to alva._home.4 then gives the following errors: tar: Skipping to next header gzip: stdin: invalid compressed data--crc error gzip: stdin: invalid compressed data--length error What's the correct procedure for restoring from holding disk files in this case? Thank you. Josh Kelley -- Mario Silva Systems Administrator Supreme Court of New Mexico Judicial Information Division 2905 Rodeo Park Dr. East, Bldg. #5 Santa Fe, NM 87505 Phone: (505) 476-6959 / Mobil: (505) 660-1026 Fax:(505) 476-6952 Website: http://www.nmcourts.gov mailto: [EMAIL PROTECTED] LEGAL DISCLAIMER: The content of this data transmission is not considered as an offer, proposal, understanding, or agreement unless it is confirmed in a document signed by a legal representative of Supreme Court of the State of New Mexico or the Judicial Information Division. The content of this data transmission is confidential and it is intended to be delivered only to the addresses, therefore, it shall not be distributed and/or disclosed through any mean without the original sender's previous authorization. If you are not the addressee you are forbidden to use it, either totally or partially, for any purpose. AVISO LEGAL: El contenido de este mensaje de datos no se considera oferta, propuesta o acuerdo, sino hasta que sea confirmado en documento por escrito que contenga la firma autógrafa del apoderado legal de La Suprema Corte del Estado de Nuevo Mexico o de la Division de Informatica del Estado. El contenido de este mensaje de datos es confidencial y se entiende dirigido y para uso exclusivo del destinatario, por lo que no podrá distribuirse y/o difundirse por ningún medio sin la previa autorización del emisor original. Si usted no es el destinatario, se le prohíbe su utilización total o parcial para cualquier fin. begin:vcard fn:Mario Silva n:Silva;Mario org:Supreme Court of New Mexico;Judicial Information Division adr:;;2905 Rodeo Park Dr. East, Bldg. #5;Santa Fe;NM;87505;USA email;internet:[EMAIL PROTECTED] title:Systems Administrator tel;work:(505) 476-6959 tel;fax:(505) 476-6952 tel;cell:(505) 660-1026 x-mozilla-html:TRUE url:http://www.nmcourts.gov version:2.1 end:vcard
Re: Restoring from a holding disk?
On 9/7/07, Josh Kelley <[EMAIL PROTECTED]> wrote: > I checked the wiki and Google and couldn't find an answer. How do I > restore from files on a holding disk if the dump has been split across > multiple chunks on the holding disk? > I can restore from alva._home.4 using amrestore as normal: > > amrestore -p alva._home.4 | tar xvf - > > But that's obviously only part of the backup. That should extract the whole backup -- are you sure it hasn't? Look at the first block of that first file. It should contain CONT_FILENAME=... Is that filename correctly pointing to the next file? Dustin -- Storage Software Engineer http://www.zmanda.com
Re: Restoring from a holding disk?
Josh Kelley wrote: I checked the wiki and Google and couldn't find an answer. How do I restore from files on a holding disk if the dump has been split across multiple chunks on the holding disk? I have the following files: alva._home.4alva._home.4.2 alva._home.4.4 alva._home.4.1 alva._home.4.3 alva._home.4.5 I can restore from alva._home.4 using amrestore as normal: amrestore -p alva._home.4 | tar xvf - It should works, try 'amrestore alva._home.4' and feed the resulting file to tar. But that's obviously only part of the backup. If I try to concatenate all of the files together, as the wiki suggests when using amrestore to restore from a tape: for i in `ls -1 alva._home.4*`; do dd if=$i >> wholedump.0; done You must remove the first 32k bytes of each files for i in `ls -1 alva._home.4*`; do dd if=$i bs=32k skip=1 >> wholedump.0; done and run tar directly on wholedump.0, may need to be uncompressed. then run amrestore on wholedump.0, amrestore successfully processes the data corresponding to alva._home.4 then gives the following errors: tar: Skipping to next header gzip: stdin: invalid compressed data--crc error gzip: stdin: invalid compressed data--length error What's the correct procedure for restoring from holding disk files in this case? Thank you. Josh Kelley
Restoring from a holding disk?
I checked the wiki and Google and couldn't find an answer. How do I restore from files on a holding disk if the dump has been split across multiple chunks on the holding disk? I have the following files: alva._home.4alva._home.4.2 alva._home.4.4 alva._home.4.1 alva._home.4.3 alva._home.4.5 I can restore from alva._home.4 using amrestore as normal: amrestore -p alva._home.4 | tar xvf - But that's obviously only part of the backup. If I try to concatenate all of the files together, as the wiki suggests when using amrestore to restore from a tape: for i in `ls -1 alva._home.4*`; do dd if=$i >> wholedump.0; done then run amrestore on wholedump.0, amrestore successfully processes the data corresponding to alva._home.4 then gives the following errors: tar: Skipping to next header gzip: stdin: invalid compressed data--crc error gzip: stdin: invalid compressed data--length error What's the correct procedure for restoring from holding disk files in this case? Thank you. Josh Kelley
Re: Restoring from virtual tapes
Um, never mind...I was able to use amrestore with no problems, and for what I was doing, it was probably better than amrecover anyway. On Mon, 23 Jul 2007 [EMAIL PROTECTED] wrote: > > OMG, I had those two commented out, because at one time, the amanda server > was a client only. It's now the server, and it's been backing up fine > with just amandad in there. I just uncommented restarted inetd, but now I > get the following: > > AMRECOVER Version 2.5.0p2. Contacting server on ns1.pil.net ... > 220 ns1 AMANDA index server (2.5.0p2) ready. > 200 Access OK > Setting restore date to today (2007-07-23) > 200 Working date set to 2007-07-23. > 501 Index directory /var/adm/amanda/colos/index does not exist > > I assume this is because amandixd never ran on that config. The question > now is, can this FS be restored, and if nos, how? > > Thanks! > > On Mon, 23 Jul 2007, Jean-Louis Martineau wrote: > > > > > What is your xinetd configure on ns1.pil.net for the amandaidx and > > amidxtaped services? > > > > Jean-Louis > > > > > > [EMAIL PROTECTED] wrote: > > > I've restored amanda file systems in the past from tape using amrestore. > > > However, I switched from tapes to vtapes several months ago and am trying > > > to restore a file system. > > > > > > According to the FAQs and posts I saw searching various archives, one > > > wants to use amrecover intead of amrestore for vtapes. > > > > > > Trying to run as user amanda, I am told it has to be run as root. When I > > > run it as root, I get this error: > > > > > > su-2.05b# amrecover -C colos > > > AMRECOVER Version 2.5.0p2. Contacting server on ns1.pil.net ... > > > amrecover: cannot connect to server.mydomain.net: Connection refused > > > > > > I then add the user root to ~amanda/.amandahosts, but it doesn't make a > > > difference: > > > > > > (Partial) cat ~amanda/.amandahosts > > > > > > localhost.mydomain.net amanda > > > server.mydomain.net amanda > > > server.mydomain.net root > > > localhost.mydomain.net root > > > > > > I also tried adding to this config's amanda.conf the following: > > > > > > amrecover_changer "file:/path/to/tapedev" > > > > > > And it didn't help. What am I missing? > > > > > > TIA, > > > > > > James Smallacombe PlantageNet, Inc. CEO and Janitor > > > [EMAIL PROTECTED] > > > http://3.am > > > = > > > > > > > > > > > > > > > > > > > > > James Smallacombe PlantageNet, Inc. CEO and Janitor > [EMAIL PROTECTED] > http://3.am > = > > James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Re: Restoring from virtual tapes
On Mon, Jul 23, 2007 at 11:19:54AM -0400, [EMAIL PROTECTED] wrote: > > I've restored amanda file systems in the past from tape using amrestore. > However, I switched from tapes to vtapes several months ago and am trying > to restore a file system. > > According to the FAQs and posts I saw searching various archives, one > wants to use amrecover intead of amrestore for vtapes. > Misconception. Either amrestore or amrecover can be used with real or virtual tapes. Typically amrecover is used for an interactive recovery session where a limited number of specific files or directories will be recovered. amrestore is more suited to entire DLE restoration. The docs you were reading were probably focused on a common reason for switching to vtapes, or using vtapes and real tapes in combination. Real tapes are often used for offsite/archive storage. Vtapes, with their high performance, random access, are often the choice for "I just deleted a file" type recovery. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Restoring from virtual tapes
What's in the amrecover.*.debug file? Any amandad.*.debug file on ns1.pil.net? What is your xinetd configure on ns1.pil.net for the amandaidx and amidxtaped services? Check your system log for firewall Jean-Louis [EMAIL PROTECTED] wrote: I've restored amanda file systems in the past from tape using amrestore. However, I switched from tapes to vtapes several months ago and am trying to restore a file system. According to the FAQs and posts I saw searching various archives, one wants to use amrecover intead of amrestore for vtapes. Trying to run as user amanda, I am told it has to be run as root. When I run it as root, I get this error: su-2.05b# amrecover -C colos AMRECOVER Version 2.5.0p2. Contacting server on ns1.pil.net ... amrecover: cannot connect to server.mydomain.net: Connection refused I then add the user root to ~amanda/.amandahosts, but it doesn't make a difference: (Partial) cat ~amanda/.amandahosts localhost.mydomain.net amanda server.mydomain.net amanda server.mydomain.net root localhost.mydomain.net root I also tried adding to this config's amanda.conf the following: amrecover_changer "file:/path/to/tapedev" And it didn't help. What am I missing? TIA, James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Restoring from virtual tapes
I've restored amanda file systems in the past from tape using amrestore. However, I switched from tapes to vtapes several months ago and am trying to restore a file system. According to the FAQs and posts I saw searching various archives, one wants to use amrecover intead of amrestore for vtapes. Trying to run as user amanda, I am told it has to be run as root. When I run it as root, I get this error: su-2.05b# amrecover -C colos AMRECOVER Version 2.5.0p2. Contacting server on ns1.pil.net ... amrecover: cannot connect to server.mydomain.net: Connection refused I then add the user root to ~amanda/.amandahosts, but it doesn't make a difference: (Partial) cat ~amanda/.amandahosts localhost.mydomain.net amanda server.mydomain.net amanda server.mydomain.net root localhost.mydomain.net root I also tried adding to this config's amanda.conf the following: amrecover_changer "file:/path/to/tapedev" And it didn't help. What am I missing? TIA, James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Re: amanda-20070530 amrecover problem with restoring from older amanda version.
Robert,
Did you configure with --with-maxtapeblocksize? What is the value?
What is your blocksize setting in the tapetype?
Did the tape labeled D5 was written with the same blocksize?
Can you try the attached patch.
Jean-Louis
McGraw, Robert P. wrote:
Jean-Louis,
Here is the amidxtaped that you requested.
amidxtaped: short file header block: 32768 bytes
Not an amanda tape
diff -u -r --show-c-function --new-file --exclude-from=/home/martinea/src.orig/amanda.diff --ignore-matching-lines='$Id:' amanda-2.5.2/restore-src/restore.c amanda-2.5.2.restore/restore-src/restore.c
--- amanda-2.5.2/restore-src/restore.c 2007-05-04 07:39:06.0 -0400
+++ amanda-2.5.2.restore/restore-src/restore.c 2007-06-06 10:31:55.0 -0400
@@ -647,7 +647,7 @@ read_file_header(
fprintf(stderr, "%s: error reading file header: %s\n",
get_pname(), strerror(errno));
file->type = F_UNKNOWN;
-} else if((size_t)bytes_read < blocksize) {
+} else if((size_t)bytes_read < DISK_BLOCK_BYTES) {
if(bytes_read == 0) {
fprintf(stderr, "%s: missing file header block\n", get_pname());
} else {
Re: amanda-20070530 amrecover problem with restoring from older amanda version.
What's in the amidxtaped.*.debug on the server? Jean-Louis McGraw, Robert P. wrote: My configuration: build: VERSION="Amanda-2.5.2-20070530" BUILT_DATE="Thu May 31 09:14:26 EDT 2007" BUILT_MACH="SunOS zorn.math.purdue.edu 5.10 Generic_118833-03 sun4u sparc SUNW,Sun-Fire-280R" CC="/pkgs/gcc-3.4.3/bin/gcc" CONFIGURE_COMMAND="'./configure' 'CC=/pkgs/gcc-3.4.3/bin/gcc' 'MT=/opt/csw/bin/mt' 'MTF=-f' 'MTX=/opt/csw/sbin/mtx' 'PERL=/opt/csw/bin/perl' '--prefix=/local/Amanda/amanda-2.5.2-20070530' '--with-user=amanda' '--with-group=operator' '--with-gnutar=/opt/csw/bin/gtar' '--with-gnutar-listdir=/var/amanda/gnutar-lists' '--with-includes=/opt/csw/include' '--with-libraries=/opt/csw/lib' '--with-index-server=zorn' '--with-smbclient=/pkgs/samba/bin/smbclient' '--with-tape-device=/dev/rmt/1bn' '--with-changer-device=/dev/changer/1' '--with-maxtapeblocksize=2048'" paths: bindir="/local/Amanda/amanda-2.5.2-20070530/bin" sbindir="/local/Amanda/amanda-2.5.2-20070530/sbin" libexecdir="/local/Amanda/amanda-2.5.2-20070530/libexec" mandir="/local/Amanda/amanda-2.5.2-20070530/man" AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" CONFIG_DIR="/local/Amanda/amanda-2.5.2-20070530/etc/amanda" DEV_PREFIX="/dev/dsk/" RDEV_PREFIX="/dev/rdsk/" DUMP="/usr/sbin/ufsdump" RESTORE="/usr/sbin/ufsrestore" VDUMP=UNDEF VRESTORE=UNDEF XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF SAMBA_CLIENT="/pkgs/samba/bin/smbclient" GNUTAR="/opt/csw/bin/gtar" COMPRESS_PATH="/bin/gzip" UNCOMPRESS_PATH="/bin/gzip" LPRCMD="/local/bin/lpr" MAILER="/usr/ucb/Mail" listed_incr_dir="/var/amanda/gnutar-lists" defs: DEFAULT_SERVER="zorn" DEFAULT_CONFIG="DailySet1" DEFAULT_TAPE_SERVER="zorn" DEFAULT_TAPE_DEVICE="/dev/rmt/1bn" NEED_STRSTR HAVE_SYSVSHM LOCKING=**NONE** SETPGRP_VOID DEBUG_CODE AMANDA_DEBUG_DAYS=4 BSD_SECURITY RSH_SECURITY USE_AMANDAHOSTS CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" I tested amrecover on a file that was backed up with amanda-20070530 and had no problem. Today I tried to do a amrecover on a file the was backed up with amanda-2.5.1p2 and get the following: Extracting files using tape drive /dev/rmt/1bn on host zorn. Load tape D5 now Continue [?/Y/n/s/t]? y Not an amanda tape Looking for tape D5... Not an amanda tape Load tape D5 now Continue [?/Y/n/t]? y Not an amanda tape Not an amanda tape Looking for tape D5... ^[[ANot an amanda tape Load tape D5 now Continue [?/Y/n/t]? y Continue [?/Y/n/t]? Not an amanda tape Not an amanda tape Looking for tape D5... Not an amanda tape Load tape D5 now Continue [?/Y/n/t]? n The following is from amrecover.20070601151822.debug: amidxtaped_streams[0].fd = 810a0 amrecover: time 353.630: security_streaminit(stream=8bf88, driver=ff2d8f6c (BSD)) amrecover: time 353.635: connect_port: Try port 0: Available - amrecover: time 353.635: connected to 128.210.3.177.50856 amrecover: time 353.635: our side is 0.0.0.0.50860 amrecover: time 353.635: try_socksize: send buffer size is 65536 amrecover: time 353.635: try_socksize: receive buffer size is 65536 amidxtaped_streams[1].fd = 8bf88 amrecover: time 353.635: security_close(handle=7d2f8, driver=ff2d8f6c (BSD)) amrecover: time 581.477: security_stream_close(8bf88) amrecover: time 581.478: Can't read file header amrecover: time 581.479: pid 2521 finish time Fri Jun 1 15:28:03 2007 amrecover: time 581.484: security_stream_close(810a0) amrecover: time 822.433: security_stream_close(732d8) amrecover: time 822.434: pid 1863 finish time Fri Jun 1 15:32:04 2007 which seems to fit “Not an amanda tape” message from the amrecover script. I do not remember seeing anything about this any of the amanda-users forum but could have over looked. Robert _ Robert P. McGraw, Jr. Manager, Computer System EMAIL: [EMAIL PROTECTED] Purdue University ROOM: MATH-807 Department of Mathematics PHONE: (765) 494-6055 150 N. University Street FAX: (419) 821-0540 West Lafayette, IN 47907-2067
amanda-20070530 amrecover problem with restoring from older amanda version.
My configuration: build: VERSION="Amanda-2.5.2-20070530" BUILT_DATE="Thu May 31 09:14:26 EDT 2007" BUILT_MACH="SunOS zorn.math.purdue.edu 5.10 Generic_118833-03 sun4u sparc SUNW,Sun-Fire-280R" CC="/pkgs/gcc-3.4.3/bin/gcc" CONFIGURE_COMMAND="'./configure' 'CC=/pkgs/gcc-3.4.3/bin/gcc' 'MT=/opt/csw/bin/mt' 'MTF=-f' 'MTX=/opt/csw/sbin/mtx' 'PERL=/opt/csw/bin/perl' '--prefix=/local/Amanda/amanda-2.5.2-20070530' '--with-user=amanda' '--with-group=operator' '--with-gnutar=/opt/csw/bin/gtar' '--with-gnutar-listdir=/var/amanda/gnutar-lists' '--with-includes=/opt/csw/include' '--with-libraries=/opt/csw/lib' '--with-index-server=zorn' '--with-smbclient=/pkgs/samba/bin/smbclient' '--with-tape-device=/dev/rmt/1bn' '--with-changer-device=/dev/changer/1' '--with-maxtapeblocksize=2048'" paths: bindir="/local/Amanda/amanda-2.5.2-20070530/bin" sbindir="/local/Amanda/amanda-2.5.2-20070530/sbin" libexecdir="/local/Amanda/amanda-2.5.2-20070530/libexec" mandir="/local/Amanda/amanda-2.5.2-20070530/man" AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" CONFIG_DIR="/local/Amanda/amanda-2.5.2-20070530/etc/amanda" DEV_PREFIX="/dev/dsk/" RDEV_PREFIX="/dev/rdsk/" DUMP="/usr/sbin/ufsdump" RESTORE="/usr/sbin/ufsrestore" VDUMP=UNDEF VRESTORE=UNDEF XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF SAMBA_CLIENT="/pkgs/samba/bin/smbclient" GNUTAR="/opt/csw/bin/gtar" COMPRESS_PATH="/bin/gzip" UNCOMPRESS_PATH="/bin/gzip" LPRCMD="/local/bin/lpr" MAILER="/usr/ucb/Mail" listed_incr_dir="/var/amanda/gnutar-lists" defs: DEFAULT_SERVER="zorn" DEFAULT_CONFIG="DailySet1" DEFAULT_TAPE_SERVER="zorn" DEFAULT_TAPE_DEVICE="/dev/rmt/1bn" NEED_STRSTR HAVE_SYSVSHM LOCKING=**NONE** SETPGRP_VOID DEBUG_CODE AMANDA_DEBUG_DAYS=4 BSD_SECURITY RSH_SECURITY USE_AMANDAHOSTS CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" I tested amrecover on a file that was backed up with amanda-20070530 and had no problem. Today I tried to do a amrecover on a file the was backed up with amanda-2.5.1p2 and get the following: Extracting files using tape drive /dev/rmt/1bn on host zorn. Load tape D5 now Continue [?/Y/n/s/t]? y Not an amanda tape Looking for tape D5... Not an amanda tape Load tape D5 now Continue [?/Y/n/t]? y Not an amanda tape Not an amanda tape Looking for tape D5... ^[[ANot an amanda tape Load tape D5 now Continue [?/Y/n/t]? y Continue [?/Y/n/t]? Not an amanda tape Not an amanda tape Looking for tape D5... Not an amanda tape Load tape D5 now Continue [?/Y/n/t]? n The following is from amrecover.20070601151822.debug: amidxtaped_streams[0].fd = 810a0 amrecover: time 353.630: security_streaminit(stream=8bf88, driver=ff2d8f6c (BSD)) amrecover: time 353.635: connect_port: Try port 0: Available - amrecover: time 353.635: connected to 128.210.3.177.50856 amrecover: time 353.635: our side is 0.0.0.0.50860 amrecover: time 353.635: try_socksize: send buffer size is 65536 amrecover: time 353.635: try_socksize: receive buffer size is 65536 amidxtaped_streams[1].fd = 8bf88 amrecover: time 353.635: security_close(handle=7d2f8, driver=ff2d8f6c (BSD)) amrecover: time 581.477: security_stream_close(8bf88) amrecover: time 581.478: Can't read file header amrecover: time 581.479: pid 2521 finish time Fri Jun 1 15:28:03 2007 amrecover: time 581.484: security_stream_close(810a0) amrecover: time 822.433: security_stream_close(732d8) amrecover: time 822.434: pid 1863 finish time Fri Jun 1 15:32:04 2007 which seems to fit "Not an amanda tape" message from the amrecover script. I do not remember seeing anything about this any of the amanda-users forum but could have over looked. Robert _ Robert P. McGraw, Jr. Manager, Computer System EMAIL: [EMAIL PROTECTED] Purdue University ROOM: MATH-807 Department of MathematicsPHONE: (765) 494-6055 150 N. University Street FAX: (419) 821-0540 West Lafayette, IN 47907-2067 smime.p7s Description: S/MIME cryptographic signature
Re: restoring from DVDs
Ross Vandegrift wrote: > On Sun, Aug 06, 2006 at 03:13:39PM +0100, Laurence Darby wrote: > > This is besides the point, but that wont work, and I'm not sure if > > you completely understand the situation. I *DON'T* want data to be > > recovered from the drive, and because I'm returning it under > > warranty, I want the data on it to be destroyed. > > Aha! I did misunderstand. > > You shouldn't worry about this - the manufacturers are bound by > process requirements that prevent them from recovering data on RMAed > drives. That's nice to know. I'm slowly realizing I'm not the first to have this problem... I had a look at thier (Maxtor's) website but found conflicting answers: "Failed drive teardown and rebuild involves automated re-process which also includes Zero fill pattern, and write verify." ok, but then: "As a returning defective drive, if the drive is not in a functional state capable of a low-level format, the drive is disassembled and the platters (where the data is stored) are recycled. Once a platter is removed from the spindle of a hard drive, the data is no longer readable by any means." What do they mean by recycled? Doesn't the next sentence (which I don't believe) contradict any notion of recycling? Anyway, I'll try phoning them tommorow to ask about it. Laurence
Re: restoring from DVDs
On Sunday 06 August 2006 13:14, Jon LaBadie wrote: >On Sun, Aug 06, 2006 at 03:14:40PM +0100, Laurence Darby wrote: >> Ross Vandegrift wrote: >> > On Sun, Aug 06, 2006 at 09:41:39AM +0200, Geert Uytterhoeven wrote: >> > > > I've had quite good luck doing poor man's data recovery. Boot >> > > > the >> >> This is besides the point, but that wont work, and I'm not sure if you >> completely understand the situation. I *DON'T* want data to be >> recovered from the drive, and because I'm returning it under warranty, >> I want the data on it to be destroyed. > >I wonder about returning it under warranty. >If the data has sufficient sensitivity, it might be easiest >to eat the cost of a new replacement drive. The net-cost >would be reduced by the time spent trying to destroy the data. > >If you do retain it, are there mechanical shredders that would >chew up a disk drive? Yeah, I know there are, just are they >easily and cost effective to consider. Well, now, theres always that handy-dandy 4 lb blacksmiths maul. Doesn't everyone have one of those? ISTR I have 2, one for each hand if I really need to work something over. Unforch, my ambi-dexterity in former years seems to have gone away over the last 10 or so. :-) -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: restoring from DVDs
Jon LaBadie wrote: > > I wonder about returning it under warranty. > If the data has sufficient sensitivity, it might be easiest > to eat the cost of a new replacement drive. The net-cost > would be reduced by the time spent trying to destroy the data. > I'm trying to get the warranty replacement purely out of the principle of it :) I've reviewed the stuff I've restored, and there's nothing critical, and I always made a point of removing my credit card details from places like Dabs.com and paypal that hold on to them. > If you do retain it, are there mechanical shredders that would > chew up a disk drive? Yeah, I know there are, just are they > easily and cost effective to consider. > If I was going to forfeit the cost (or it didn't have a warranty), I'd have no hesitation in taking it apart and destroying it completely myself :) The strong magnets in them are always useful. Anyway, it's taken me a while to fully recover, I hadn't backed up /usr/lib which had a bunch of dependencies I had to redownload. I was not sure if I was still affected by the problem I mentioned a while ago, where some data was missing from the backup. All the DVD's, execpt the first of each dump, seemed to be missing 32KiB missing from the end, and tar was giving the message: "tar: skipping to next header" >From that I expected one corrupt file per DVD, but it turned out only one file in total was corrupt, which didn't happen to be an important one. I really should investigate that, but its kind of low priority at the moment, maybe will do the next time I backup, which should be soon. Laurence
Re: restoring from DVDs
On Sun, Aug 06, 2006 at 03:14:40PM +0100, Laurence Darby wrote: > Ross Vandegrift wrote: > > > On Sun, Aug 06, 2006 at 09:41:39AM +0200, Geert Uytterhoeven wrote: > > > > > I've had quite good luck doing poor man's data recovery. Boot the > > This is besides the point, but that wont work, and I'm not sure if you > completely understand the situation. I *DON'T* want data to be > recovered from the drive, and because I'm returning it under warranty, I > want the data on it to be destroyed. > I wonder about returning it under warranty. If the data has sufficient sensitivity, it might be easiest to eat the cost of a new replacement drive. The net-cost would be reduced by the time spent trying to destroy the data. If you do retain it, are there mechanical shredders that would chew up a disk drive? Yeah, I know there are, just are they easily and cost effective to consider. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: restoring from DVDs
On Sun, Aug 06, 2006 at 03:13:39PM +0100, Laurence Darby wrote: > This is besides the point, but that wont work, and I'm not sure if you > completely understand the situation. I *DON'T* want data to be > recovered from the drive, and because I'm returning it under warranty, I > want the data on it to be destroyed. Aha! I did misunderstand. You shouldn't worry about this - the manufacturers are bound by process requirements that prevent them from recovering data on RMAed drives. My employer is going through the process of becoming certified for various government/banking/etc security processes. Part of it is verifying that sensitive data is not recoverable. According to our compliance manager, sending a drive to RMA places data security liability on the RMA facility as soon as they acceept the package. You'd be able to sue for damages if you did have plaintext passwords that they leaked. This still leaves a hole while the disk is in transit, but you can only do so much... -- Ross Vandegrift [EMAIL PROTECTED] "The good Christian should beware of mathematicians, and all those who make empty prophecies. The danger already exists that the mathematicians have made a covenant with the devil to darken the spirit and to confine man in the bonds of Hell." --St. Augustine, De Genesi ad Litteram, Book II, xviii, 37
Re: restoring from DVDs
Ross Vandegrift wrote:
> On Sun, Aug 06, 2006 at 09:41:39AM +0200, Geert Uytterhoeven wrote:
> > > I've had quite good luck doing poor man's data recovery. Boot the
> > > machine into Knoppix or like ilk and use dd_rescue to copy the disk to
> > > an image file or another disk. dd_rescue is smart about skipping
> > > areas of the disk it cannot read instead of giving up. It can take a
> > > long time, but I've recovered quite a bit of data with that sucker.
> >
> > But this simple methods won't work, as the disk used to be part of a RAID0
> > setup, and thus contains only half of the data. Then it depends on the
> > stripe
> > size: the larger it is, the more likely you can find useful pieces of data
> > (e.g. a complete password or credit card number).
>
> Well, no reason you couldn't apply this principle to the RAID0 data.
> Suppose your disks are /dev/sda1 and /dev/sdb1, sdb has failed:
>
> # dd_rescue /dev/sdb1 some_file_or_device
This is besides the point, but that wont work, and I'm not sure if you
completely understand the situation. I *DON'T* want data to be
recovered from the drive, and because I'm returning it under warranty, I
want the data on it to be destroyed.
I can't erase it, because if anything accesses the drive, it makes loud
grumbling noises and vibrates, then the whole computer locks up seconds
later, with the following in dmesg:
ata2: status=0x51 { DriveReady SeekComplete Error }
ata2: error=0x40 { UncorrectableError }
end_request: I/O error, dev sdb, sector 18944
Buffer I/O error on device sdb, logical block 2368
I'm quite sure the only way to recover from it is to transplant the
platter into an identical good drive, assumming it isn't physically
scratched. Then I think gnu `strings' can be used on the raw device,
and get at the stripe sized text fragments. There is 0.5 probability
that my passwords are there in plain text, which is what I'm now worried
about. I've already extracted the backups to the good drive, so I can't
check that to see what's not on the dead drive.
If I'm feeling lucky, when I get the new drive, I could try the
transplant operation, carefully reset the warrantly violation detection
stickers, and send the clean platter back in the dead drive. It's an
"Advance" RMA, where they send me the new drive first so I can use
approved packaging for the return.
Or I could just hope whoever finds it whereever dead drives go, isn't
curious enough to see if anything is on it, and use encrypted loopback
devices from now on...
Laurence
Re: restoring from DVDs
On Sun, Aug 06, 2006 at 09:41:39AM +0200, Geert Uytterhoeven wrote: > > I've had quite good luck doing poor man's data recovery. Boot the > > machine into Knoppix or like ilk and use dd_rescue to copy the disk to > > an image file or another disk. dd_rescue is smart about skipping > > areas of the disk it cannot read instead of giving up. It can take a > > long time, but I've recovered quite a bit of data with that sucker. > > But this simple methods won't work, as the disk used to be part of a RAID0 > setup, and thus contains only half of the data. Then it depends on the stripe > size: the larger it is, the more likely you can find useful pieces of data > (e.g. a complete password or credit card number). Well, no reason you couldn't apply this principle to the RAID0 data. Suppose your disks are /dev/sda1 and /dev/sdb1, sdb has failed: # dd_rescue /dev/sdb1 some_file_or_device (wait a long time) (if you're using a file # losetup /dev/loop/0 some_file) # mdadm --assemble /dev/md0 /dev/sda1 /dev/whatever If the superblock of the second disk is intact, mdadm should be able to assemble the array with no problems. Of course you'll run into files with corrupt data, as you know one half of the stuff is damaged. If you're unlucky, the filesystem data was damaged and you'll have either lost everything or will need to run fsck... -- Ross Vandegrift [EMAIL PROTECTED] "The good Christian should beware of mathematicians, and all those who make empty prophecies. The danger already exists that the mathematicians have made a covenant with the devil to darken the spirit and to confine man in the bonds of Hell." --St. Augustine, De Genesi ad Litteram, Book II, xviii, 37
Re: restoring from DVDs
On Sat, 5 Aug 2006, Ross Vandegrift wrote:
> On Sat, Aug 05, 2006 at 12:29:43AM +0100, Laurence Darby wrote:
> > BTW, it was actually one disk of nice and fast RAID 0 (so I'm
> > restoring to the one good disk). Does anybody know if data recovery from
> > it would be possible? I hope *not*, since I'm sending it back under
> > waranty, and I can't erase it cos its dead, although it sounded like
> > the platter might be all scratched up...
>
> As always, it depends on what you want to pay. If you have the money
> to burn, just about anything besdies physical platter
> destruction/degaussing can be recovered. I read an article not that
> long ago about recovering a hard disk that had been burned in a fire.
>
> I've had quite good luck doing poor man's data recovery. Boot the
> machine into Knoppix or like ilk and use dd_rescue to copy the disk to
> an image file or another disk. dd_rescue is smart about skipping
> areas of the disk it cannot read instead of giving up. It can take a
> long time, but I've recovered quite a bit of data with that sucker.
But this simple methods won't work, as the disk used to be part of a RAID0
setup, and thus contains only half of the data. Then it depends on the stripe
size: the larger it is, the more likely you can find useful pieces of data
(e.g. a complete password or credit card number).
That's the advantage (for the manufacturer) of drive warranty policies: people
who care a lot about the security of their data will never return a drive under
warranty, but just buy a new one instead...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Re: restoring from DVDs
On Sat, Aug 05, 2006 at 12:29:43AM +0100, Laurence Darby wrote: > BTW, it was actually one disk of nice and fast RAID 0 (so I'm > restoring to the one good disk). Does anybody know if data recovery from > it would be possible? I hope *not*, since I'm sending it back under > waranty, and I can't erase it cos its dead, although it sounded like > the platter might be all scratched up... As always, it depends on what you want to pay. If you have the money to burn, just about anything besdies physical platter destruction/degaussing can be recovered. I read an article not that long ago about recovering a hard disk that had been burned in a fire. I've had quite good luck doing poor man's data recovery. Boot the machine into Knoppix or like ilk and use dd_rescue to copy the disk to an image file or another disk. dd_rescue is smart about skipping areas of the disk it cannot read instead of giving up. It can take a long time, but I've recovered quite a bit of data with that sucker. Good luck! -- Ross Vandegrift [EMAIL PROTECTED] "The good Christian should beware of mathematicians, and all those who make empty prophecies. The danger already exists that the mathematicians have made a covenant with the devil to darken the spirit and to confine man in the bonds of Hell." --St. Augustine, De Genesi ad Litteram, Book II, xviii, 37
restoring from DVDs
Hi All, So one of my disks crashed before I had time to test all the DVD's I backed up to can be read, so I'm currently testing that now... :-/ Haven't had any read errors yet, but I'm keeping my fingers crossed :) BTW, it was actually one disk of nice and fast RAID 0 (so I'm restoring to the one good disk). Does anybody know if data recovery from it would be possible? I hope *not*, since I'm sending it back under waranty, and I can't erase it cos its dead, although it sounded like the platter might be all scratched up... Cheers, Laurence
SOLVED! (WAS: RE: Need help restoring: -p doesn't seem to work)
For the archives, turns out the problem was not with "-p" in 'amrestore -p /dev/nsa0 freebee aacd0s1f | restore -ivf -' but rather with the hostname and diskname being specified. Turns out that if I specified any of them the error would occur (even though I've verified that they were all syntactically correct). I found this out by simply trying: 'amrestore -p /dev/nsa0 | restore -ivf -' And it worked--sort of. I was dropped into interactive mode of restore. However, I noticed that it was for the /var volume which corresponded to disk aacd0s1e, which was the first on the tape, which corresponds to what I think is called "fileno 0" in amanda. I knew that "fileno" started with 0 and not 1, so I guessed that aacd0s1f was fileno #2, and I tried this command: 'amrestore -f 2 -p /dev/nsa0 | restore -ivf -' Lo and behold I was put in interactive restore mode of dump with the /usr partition available to restore. Just what I wanted! I was able to "add" and "extract" the files I needed to restore from this point. I don't know why specifying the hostname and diskname causes errors, but it does--for me at least. Specifying the fileno instead gets the job done. Thanks to everyone who responded! --Sean Noonan > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Sean Noonan > Sent: Wednesday, July 26, 2006 10:23 AM > To: amanda-users@amanda.org > Cc: 'Paul Haldane'; 'Joshua Baker-LePain' > Subject: RE: Need help restoring: -p doesn't seem to work > > > > >> What does "mt stat" say before you run amrestore? Is the tape > > positioned > > > > > > > > "mt start" gives an error. "start" doesn't seem to be a valid command > > for > >^ > > > > Erm, start != stat. > > > > -- > > Joshua Baker-LePain > > Department of Biomedical Engineering > > Duke University > > Doh! Long night, high resolution, small typeface. Sorry about that! > > Here's what I get: > > freebee# mt -f /dev/nsa0 stat > Mode Density Blocksize bpi Compression > Current: 0x42 variable 0disabled > -available modes- > 0:0x42 variable 00x1 > 1:0x42 variable 00x1 > 2:0x42 variable 00x1 > 3:0x42 variable 00x1 > - > Current Driver State: at rest. > - > File Number: 0 Record Number: 0Residual Count 0 > freebee# > > Thanks! > > --Sean Noonan >
RE: Need help restoring: -p doesn't seem to work
> >> What does "mt stat" say before you run amrestore? Is the tape > positioned > > > > > "mt start" gives an error. "start" doesn't seem to be a valid command > for >^ > > Erm, start != stat. > > -- > Joshua Baker-LePain > Department of Biomedical Engineering > Duke University Doh! Long night, high resolution, small typeface. Sorry about that! Here's what I get: freebee# mt -f /dev/nsa0 stat Mode Density Blocksize bpi Compression Current: 0x42 variable 0disabled -available modes- 0:0x42 variable 00x1 1:0x42 variable 00x1 2:0x42 variable 00x1 3:0x42 variable 00x1 - Current Driver State: at rest. - File Number: 0 Record Number: 0Residual Count 0 freebee# Thanks! --Sean Noonan
Re: Need help restoring: -p doesn't seem to work
Sean Noonan wrote: freebee# amrestore -p /dev/nsa0 freebee aacd0s1f | gzip -d | restore - ivf - Verify tape and initialize maps amrestore: missing file header block amrestore: 2: skipping freebee.aacd0s1e.20060721.0 amrestore: 10: reached end of information gzip: stdin: unexpected end of file End-of-tape encountered Tape is not a dump tape freebee# - What did amverify said about that tape? Amverify ran without errors. Specifically: freebee# su -m operator -c 'amverify Get1Free' No tape changer... Tape device is /dev/nsa0... Verify summary to [EMAIL PROTECTED] Defects file is /tmp/amanda/amverify.37453/defects amverify Get1Free Wed Jul 26 08:11:49 PDT 2006 Using device /dev/nsa0 Waiting for device to go ready... Rewinding... Processing label... Volume Get1FreeDailyLTO2-17, Date 20060721 Rewinding... Checked freebee.aacd0s1e.20060721.0 Checked freebee.aacd0s1a.20060721.0 Checked freebee.aacd0s1f.20060721.0 Checked freebee.aacd0s1g.20060721.0 End-of-Information detected. Rewinding... freebee# - Are you sure you have a backup for aacd0s1f on that tape? Yes. At least the above amverify output indicates so. Also, remember that I can (if I had the disk space) do a amrestore if I don't try to use "-p" and do an interactive session. So yes, aacd0s1f is on that tape. And it's a level 0 dump. - Can you restore to a disk and then see what type of file you get from the restore? That would allow you to make faster test with gunzip, restore or whatever without reading the tape again and again. I'm sorry but I'm not sure what you mean by this--I'm not the sharpest knife in the drawer. I don't have the disk space to restore the entire file, otherwise I wouldn't need to pipe the output of amrestore and I wouldn't have a problem in the first place. However, your idea has me thinking about trying to use mount_smbfs to a NAS device. Maybe that'll work and give me the temporary necessary disk space I need to restore. have you tried using amrecover? If "index" is on in the dumptype during amdump, the amanda index server will give the listing of the files in aacd0s1f and you can choose what files to extract. I have also tested "amrestore -p", it's working fine for me. -- Thank you! Kevin Till Amanda documentation: http://wiki.zmanda.com Amanda forums:http://forums.zmanda.com
RE: Need help restoring: -p doesn't seem to work
> > freebee# amrestore -p /dev/nsa0 freebee aacd0s1f | gzip -d | restore - > ivf - > > Verify tape and initialize maps > > amrestore: missing file header block > > amrestore: 2: skipping freebee.aacd0s1e.20060721.0 > > amrestore: 10: reached end of information > > > > gzip: stdin: unexpected end of file > > End-of-tape encountered > > Tape is not a dump tape > > freebee# > > - What did amverify said about that tape? Amverify ran without errors. Specifically: freebee# su -m operator -c 'amverify Get1Free' No tape changer... Tape device is /dev/nsa0... Verify summary to [EMAIL PROTECTED] Defects file is /tmp/amanda/amverify.37453/defects amverify Get1Free Wed Jul 26 08:11:49 PDT 2006 Using device /dev/nsa0 Waiting for device to go ready... Rewinding... Processing label... Volume Get1FreeDailyLTO2-17, Date 20060721 Rewinding... Checked freebee.aacd0s1e.20060721.0 Checked freebee.aacd0s1a.20060721.0 Checked freebee.aacd0s1f.20060721.0 Checked freebee.aacd0s1g.20060721.0 End-of-Information detected. Rewinding... freebee# > - Are you sure you have a backup for aacd0s1f on that tape? Yes. At least the above amverify output indicates so. Also, remember that I can (if I had the disk space) do a amrestore if I don't try to use "-p" and do an interactive session. So yes, aacd0s1f is on that tape. And it's a level 0 dump. > - Can you restore to a disk and then see what type of file you get > from the restore? That would allow you to make faster test with > gunzip, restore or whatever without reading the tape again and > again. I'm sorry but I'm not sure what you mean by this--I'm not the sharpest knife in the drawer. I don't have the disk space to restore the entire file, otherwise I wouldn't need to pipe the output of amrestore and I wouldn't have a problem in the first place. However, your idea has me thinking about trying to use mount_smbfs to a NAS device. Maybe that'll work and give me the temporary necessary disk space I need to restore. > Bests, > > Olivier Thanks for your assistance, --Sean Noonan
Re: Need help restoring: -p doesn't seem to work
On Wed, Jul 26, 2006 at 08:24:19AM -0700, Sean Noonan wrote: > > > > > > That looks like amrestore isn't finding the dump file on the tape and is > > running off the end of tape. > > > > I'm puzzled by the "missing file header block". That implies that the > > tape isn't positioned at the start of a tape file when you run amrestore. > > What does "mt stat" say before you run amrestore? Is the tape positioned > > at the very start of the tape file you want (or at least somewhere before > > there)? > > "mt start" gives an error. "start" doesn't seem to be a valid command for I think that was supposed to be "status". -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: Need help restoring: -p doesn't seem to work
On Wed, 26 Jul 2006 at 8:24am, Sean Noonan wrote What does "mt stat" say before you run amrestore? Is the tape positioned "mt start" gives an error. "start" doesn't seem to be a valid command for ^ Erm, start != stat. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
RE: Need help restoring: -p doesn't seem to work
> > That looks like amrestore isn't finding the dump file on the tape and is > running off the end of tape. > > I'm puzzled by the "missing file header block". That implies that the > tape isn't positioned at the start of a tape file when you run amrestore. > What does "mt stat" say before you run amrestore? Is the tape positioned > at the very start of the tape file you want (or at least somewhere before > there)? "mt start" gives an error. "start" doesn't seem to be a valid command for me implementation of mt. "mt rewind", however, was used before the attempted restore. I'm quite sure the tape was successfully rewound beforehand. > > Is that all the output you get from amrestore? Does it really skip from > 2: to 10:? Unfortunately, yes, that was the entire output from amrestore. > > Paul > Thanks. Any other ideas on how to proceed/troubleshoot? --Sean Noonan
Re: Need help restoring: -p doesn't seem to work
On Wed, Jul 26, 2006 at 09:35:13AM +0700, Olivier Nicole wrote: > > freebee# amrestore -p /dev/nsa0 freebee aacd0s1f | gzip -d | restore -ivf - > > Verify tape and initialize maps > > amrestore: missing file header block > > amrestore: 2: skipping freebee.aacd0s1e.20060721.0 > > amrestore: 10: reached end of information > > > > gzip: stdin: unexpected end of file > > End-of-tape encountered > > Tape is not a dump tape > > freebee# > > - What did amverify said about that tape? > > - Are you sure you have a backup for aacd0s1f on that tape? > > - Can you restore to a disk and then see what type of file you get > from the restore? That would allow you to make faster test with > gunzip, restore or whatever without reading the tape again and > again. I was about to suggest a similar strategy. The original OP said they could not restore the entire DLE due to space limitations. However for just testing if anything is coming off the tape, and what type of data, you need not restore the entier image (though that would be better of course). You could pipe it into dd to cut off after a couple of good size chunk (even up to 1GB if room is available, several 10s of MB if not), or even just watch it restore for a while and interupt with Ctrl-C. Then use the file command to see what type of data, if any, was extracted. Unzip it if necessary with gunzip < x > y (leaves original untouched) and test the result. If it is a dump file, try a restore with the "toc" options to see if that piece seems valid. What Oliver and I are driving at, is check whether the amrestore part of your command is getting what you expect. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Need help restoring: -p doesn't seem to work
> freebee# amrestore -p /dev/nsa0 freebee aacd0s1f | gzip -d | restore -ivf - > Verify tape and initialize maps > amrestore: missing file header block > amrestore: 2: skipping freebee.aacd0s1e.20060721.0 > amrestore: 10: reached end of information > > gzip: stdin: unexpected end of file > End-of-tape encountered > Tape is not a dump tape > freebee# - What did amverify said about that tape? - Are you sure you have a backup for aacd0s1f on that tape? - Can you restore to a disk and then see what type of file you get from the restore? That would allow you to make faster test with gunzip, restore or whatever without reading the tape again and again. Bests, olivier
RE: Need help restoring: -p doesn't seem to work
> -Original Message- > From: Sean Noonan > Sent: 25 July 2006 22:45 > > > > > > Use the -h option of amrestore to confirm if it was compressed, > > probably with gzip. > > > > If that is the case you will have to put a gzip -d command in > > the pipeline between amrestore and restore. My understanding is that amrestore automatically does any uncompression necessary so the explicit gzip -d isn't needed. > Thanks for the reply. I'm quite sure it was gzip compressed, > the amanda > config files specifies "compress client fast" for this > volume. Still no love, though. Here's what I got: > > freebee# amrestore -p /dev/nsa0 freebee aacd0s1f | gzip -d | restore -ivf - > Verify tape and initialize maps > amrestore: missing file header block > amrestore: 2: skipping freebee.aacd0s1e.20060721.0 > amrestore: 10: reached end of information > > gzip: stdin: unexpected end of file > End-of-tape encountered > Tape is not a dump tape That looks like amrestore isn't finding the dump file on the tape and is running off the end of tape. I'm puzzled by the "missing file header block". That implies that the tape isn't positioned at the start of a tape file when you run amrestore. What does "mt stat" say before you run amrestore? Is the tape positioned at the very start of the tape file you want (or at least somewhere before there)? Is that all the output you get from amrestore? Does it really skip from 2: to 10:? Paul
RE: Need help restoring: -p doesn't seem to work
> > > > Suggestions anyone? > > Use the -h option of amrestore to confirm if it was compressed, > probably with gzip. > > If that is the case you will have to put a gzip -d command in > the pipeline between amrestore and restore. > > -- > Jon H. LaBadie [EMAIL PROTECTED] > JG Computing > 4455 Province Line Road(609) 252-0159 > Princeton, NJ 08540-4322 (609) 683-7220 (fax) Hi Jon, Thanks for the reply. I'm quite sure it was gzip compressed, the amanda config files specifies "compress client fast" for this volume. Still no love, though. Here's what I got: freebee# amrestore -p /dev/nsa0 freebee aacd0s1f | gzip -d | restore -ivf - Verify tape and initialize maps amrestore: missing file header block amrestore: 2: skipping freebee.aacd0s1e.20060721.0 amrestore: 10: reached end of information gzip: stdin: unexpected end of file End-of-tape encountered Tape is not a dump tape freebee# Any other/more ideas? --Sean Noonan
Re: Need help restoring: -p doesn't seem to work
On Tue, Jul 25, 2006 at 12:15:55PM -0700, Sean Noonan wrote: > Hello, > > Hoping someone can help me with the magical incarnation to restore files. > Box is running FreeBSD 5.4-STABLE. Amanda is v2.5.0p2,1 installed from the > ports collection. Server name is freebee. Disk name is aacd0s1f. Tape > device is /dev/nsa0 (which is a LTO-2 drive). > > When I try to attempt an interactive restore this is what I get: > > freebee# amrestore -p /dev/nsa0 freebee aacd0s1f | restore -ivf - > amrestore: missing file header block > amrestore: 2: skipping freebee.aacd0s1e.20060721.0 > amrestore: 10: reached end of information > Verify tape and initialize maps > End-of-tape encountered > Tape is not a dump tape > freebee# > > However, if I leave off the "-p" I seem to be able to successfully restore, > e.g., files are created in the current directory with names similar to > "freebee.aacd0s1e.20060721.0", etc. The problem is I don't have a volume > with enough free space left on it to restore the entire > freebee.aacd0s1f.20060721.0 file. > > Suggestions anyone? Use the -h option of amrestore to confirm if it was compressed, probably with gzip. If that is the case you will have to put a gzip -d command in the pipeline between amrestore and restore. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Need help restoring: -p doesn't seem to work
Hello, Hoping someone can help me with the magical incarnation to restore files. Box is running FreeBSD 5.4-STABLE. Amanda is v2.5.0p2,1 installed from the ports collection. Server name is freebee. Disk name is aacd0s1f. Tape device is /dev/nsa0 (which is a LTO-2 drive). When I try to attempt an interactive restore this is what I get: freebee# amrestore -p /dev/nsa0 freebee aacd0s1f | restore -ivf - amrestore: missing file header block amrestore: 2: skipping freebee.aacd0s1e.20060721.0 amrestore: 10: reached end of information Verify tape and initialize maps End-of-tape encountered Tape is not a dump tape freebee# However, if I leave off the "-p" I seem to be able to successfully restore, e.g., files are created in the current directory with names similar to "freebee.aacd0s1e.20060721.0", etc. The problem is I don't have a volume with enough free space left on it to restore the entire freebee.aacd0s1f.20060721.0 file. Suggestions anyone? TIA, --Sean Noonan
Re: Restoring from tape when Amanda server failed - conclusion and open questions
On Fri, Jul 21, 2006 at 06:22:38AM -0700, gil naveh wrote:
> Thanks much for the support. Eventually I was able to restore some of the
> missing files but I still have some open questions.
> 1) I was able to restore the files on the Server where Amanda
> server was initially installed. However, I could not restore the tape from a
> different server (ServerB) with similar operating system (Solaris 9). The
> mystery about the restore process was that I successfully run the
> commands(on serverB):
>
> a. mt -f /dev/rmt/0cn rewind
>
> b. mt -f /dev/rmt/0cn fsf 1
> But when I run the command:
>
> dd if=/dev/rmt/0cn bs=32k skip=1
> It gave me the following error message:
> read: Invalid argument
> 0+0 records in
> 0+0 records out
> Does anybody know why?
> 2) When I restored the data using the command:
>
> dd if=/dev/rmt/0cn bs=32k skip=1 | gzip -d | /usr/sbin/ufsrestore -ivf -
> I was only able to restore files that were saved - level 0 on that
> particular tape; Yet I also restored a folder on Amanda that folder was
> lastly restored on run level-1.
> But need to restore certain files from that folder without restoring
> the whole folder is this possible using the ufsrestore tool? In the past I
> was able to do so with the amrestore utility.
>
> Thanks,
> gil
> gil naveh <[EMAIL PROTECTED]> wrote: Thanks Jon,
> Regarding your comments/questions:
> 1) You keep using a blocksize of 64k for dd, why? Amanda normally uses 32k
> I tried both for 32K and 64k (part of try and error trial I did to recover
> the data) - anyway thanks, now I am confident that amanda uses 32k.
>
> 2)Have you read the docs refered to above for how to recover?
> I read those documents many times - I hate asking questions before doing
> my research - but when I tried to follow the instructions the recover
> failed!
>
> 3)Following an mt rewind, the first thing a dd should see is
> the tape label header file. Your output is certainly NOT
> an amanda tape label. Are you certain this is a valid
> amanda tape? Or you showed the sequence of commands accurately?
> I am 100% sure, it is an Amanda tape label - I only backed up those tapes
> with Amanda and restore the data from them using amrestore!
> Ignore my previous comment regarding reading file from /tmp/data - I just
> realized that I read those files from the HD instead from the tape.
>
> 4)Solaris has a fine file(1) command. What does "file /tmp/data"
> tell you about what dd pulled from the tape? - ignore my privious comment
> regarding reading file from /tmp/data - I just realized that I read those
> files from the HD instead from the tape.
>
> At this stage I just can't recover files from the tape! When running dd I
> keep getting the message:
> read: Invalid argument
> 0+0 records in
> 0+0 records out
>
>
> Thx,
> gil
>
> Jon LaBadie <[EMAIL PROTECTED]> wrote: On Wed, Jul 19, 2006 at 02:07:42PM
> -0700, gil naveh wrote:
> > Thanks for all the help, but I have a problem to restore the files.
> > When I type:
> > root@ # dd if=/dev/rmt/0n ibs=64k | ufsrestore if -
> > I recieve the following error message:
> > read: Invalid argument
> > 0+0 records in
> > 0+0 records out
> > Volume is not in dump format
> >
> > But as far as I know it should be in a dump format!!! because in the
> > Amanda.conf I defined the backup as:
> >
> > define dumptype daily {
> > global
> > # program "DUMP" # the default
> > # record yes # the default
> > comment "daily"
> > compress client fast
> > priority high
> > # dumpcycle 5# should be obtained from dumpcycle above
> > index yes
> > }
> >
> >
> > I also tried the following:
> > % mt -f /dev/rmt/0n rewind
> > % dd if=/dev/rmt/0n of=/tmp/data bs=64k count=2
> > % od -c /tmp/data | head
> >
> > And received the following output:
> > 000 \0 002 P 022 \0 \f \0 001 . \0 \0 \0 \0 003 242 Q
> > 020 \0 \f \0 002 . . \0 \0 \0 002 P 023 001 350 \0 006
> > 040 n e w bc k \0 \0 \0 \f \0 003b c k \0
> > 060 \0 \0 \0 \0 001 320 \0 006n e w b
Re: Restoring from tape when Amanda server failed - conclusion and open questions
Thanks much for the support. Eventually I was able to restore some of the missing files but I still have some open questions. 1) I was able to restore the files on the Server where Amanda server was initially installed. However, I could not restore the tape from a different server (ServerB) with similar operating system (Solaris 9). The mystery about the restore process was that I successfully run the commands(on serverB): a. mt -f /dev/rmt/0cn rewind b. mt -f /dev/rmt/0cn fsf 1 But when I run the command: dd if=/dev/rmt/0cn bs=32k skip=1 It gave me the following error message: read: Invalid argument 0+0 records in 0+0 records out Does anybody know why?
2) When I restored the data using the command: dd if=/dev/rmt/0cn bs=32k skip=1 | gzip -d | /usr/sbin/ufsrestore -ivf - I was only able to restore files that were saved - level 0 on that particular tape; Yet I also restored a folder on Amanda that folder was lastly restored on run level-1. But need to restore certain files from that folder without restoring the whole folder is this possible using the ufsrestore tool? In the past I was able to do so
with the amrestore utility. Thanks, gilgil naveh <[EMAIL PROTECTED]> wrote: Thanks Jon, Regarding your comments/questions: 1) You keep using a blocksize of 64k for dd, why? Amanda normally uses 32k I tried both for 32K and 64k (part of try and error trial I did to recover the data) - anyway thanks, now I am confident that amanda uses 32k.2)Have you read the docs refered to above for how to recover? I read those documents many times - I hate asking questions before doing my research - but when I tried to follow the instructions the recover failed!
3)Following an mt rewind, the first thing a dd should see is the tape label header file. Your output is certainly NOT an amanda tape label. Are you certain this is a valid amanda tape? Or you showed the sequence of commands accurately? I am 100% sure, it is an Amanda tape label - I only backed up those tapes with Amanda and restore the data from them using amrestore! Ignore my previous comment regarding reading file from /tmp/data - I just realized that I read those files from the HD instead from the tape.4)Solaris has a fine file(1) command. What does "file /tmp/data" tell you about what dd pulled from the tape? - ignore my privious comment regarding reading file from /tmp/data - I just realized that I read those files from the HD instead from the tape.At this stage I just can't recover files from the tape! When running dd I keep getting the message: read: Invalid argument 0+0 records
in 0+0 records outThx, gilJon LaBadie <[EMAIL PROTECTED]> wrote: On Wed, Jul 19, 2006 at 02:07:42PM -0700, gil naveh wrote:> Thanks for all the help, but I have a problem to restore the files.> When I type:> root@ # dd if=/dev/rmt/0n ibs=64k | ufsrestore if -> I recieve the following error message:> read: Invalid argument> 0+0 records in> 0+0 records out> Volume is not in dump format> > But as far as I know it should be in a dump format!!! because in the Amanda.conf I defined the backup as:>> define dumptype daily {> global> # program "DUMP" # the default> # record yes # the default> comment
"daily"> compress client fast> priority high> # dumpcycle 5# should be obtained from dumpcycle above> index yes> }> > > I also tried the following:> % mt -f /dev/rmt/0n rewind > % dd if=/dev/rmt/0n of=/tmp/data bs=64k count=2> % od -c /tmp/data | head> > And received the following output:> 000 \0 002 P 022 \0 \f \0 001 . \0 \0 \0 \0 003 242 Q> 020 \0 \f \0 002 . . \0 \0 \0 002 P 023 001 350 \0 006> 040 n e w bc k \0 \0 \0 \f \0 003b c k \0> 060 \0 \0 \0 \0 001 320 \0 006n e w b c k \0 \0> 100 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0> *> 0001000> > Can one deduct the dump format from the above
output?> > Many thanks,> gil> Paul Bijnens wrote: > On 2006-07-19 17:35, gil naveh wrote:> > Thanks for the help.> > I am familiar with the Amrestore command.> > Then you understand that you can replace "amrestore" with a> "mt" and "dd".> > ...> The docs in http://www.amanda.org/docs/restore.html> are a little more expanded, giving more examples in:> > http://wiki.zmanda.com/index.php/Restoring_files>Grr
Re: Restoring from tape when Amanda server failed
Thanks Jon, Regarding your comments/questions: 1) You keep using a blocksize of 64k for dd, why? Amanda normally uses 32k I tried both for 32K and 64k (part of try and error trial I did to recover the data) - anyway thanks, now I am confident that amanda uses 32k.2)Have you read the docs refered to above for how to recover? I read those documents many times - I hate asking questions before doing my research - but when I tried to follow the instructions the recover failed! 3)Following an mt rewind, the first thing a dd should see is the tape label header file. Your output is certainly NOT an amanda tape label. Are you certain this is a valid amanda tape? Or you showed the sequence of commands accurately? I am 100% sure, it is an Amanda tape label - I only backed up those tapes with Amanda and restore the data from them using amrestore! Ignore my previous comment regarding
reading file from /tmp/data - I just realized that I read those files from the HD instead from the tape.4)Solaris has a fine file(1) command. What does "file /tmp/data" tell you about what dd pulled from the tape? - ignore my privious comment regarding reading file from /tmp/data - I just realized that I read those files from the HD instead from the tape.At this stage I just can't recover files from the tape! When running dd I keep getting the message: read: Invalid argument 0+0 records in 0+0 records outThx, gilJon LaBadie <[EMAIL PROTECTED]> wrote: On Wed, Jul 19, 2006 at 02:07:42PM -0700, gil naveh wrote:> Thanks for all the help, but I have a problem to restore the files.> When I type:> root@ # dd if=/dev/rmt/0n
ibs=64k | ufsrestore if -> I recieve the following error message:> read: Invalid argument> 0+0 records in> 0+0 records out> Volume is not in dump format> > But as far as I know it should be in a dump format!!! because in the Amanda.conf I defined the backup as:>> define dumptype daily {> global> # program "DUMP" # the default> # record yes # the default> comment "daily"> compress client fast> priority high> # dumpcycle 5# should be obtained from dumpcycle above> index yes> }> > > I also tried the following:> % mt -f /dev/rmt/0n rewind > % dd if=/dev/rmt/0n of=/tmp/data bs=64k count=2> % od -c /tmp/data | head> > And received the following
output:> 000 \0 002 P 022 \0 \f \0 001 . \0 \0 \0 \0 003 242 Q> 020 \0 \f \0 002 . . \0 \0 \0 002 P 023 001 350 \0 006> 040 n e w bc k \0 \0 \0 \f \0 003b c k \0> 060 \0 \0 \0 \0 001 320 \0 006n e w b c k \0 \0> 100 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0> *> 0001000> > Can one deduct the dump format from the above output?> > Many thanks,> gil> Paul Bijnens wrote: > On 2006-07-19 17:35, gil naveh wrote:> > Thanks for the help.> > I am familiar with the Amrestore command.> > Then you understand that you can replace "amrestore" with a> "mt" and "dd".> > ...> The docs in http://www.amanda.org/docs/restore.html> are a little
more expanded, giving more examples in:> > http://wiki.zmanda.com/index.php/Restoring_files>Grrr, I hate top posting.So hard to add inline and followingAnyway, several points.We don't know it should be a ufsdump, your dumptype includesglobal that we don't see and otherwise does not define PROGRAM.You keep using a blocksize of 64k for dd, why? Amanda normallyuses 32k.Have you read the docs refered to above for how to recover?Your dumptype says compress, presumably with gzip. I see nounzipping in your attempted recoverycommentary.Following an mt rewind, the first thing a dd should see isthe tape label header file. Your output is certainly NOTan amanda tape label. Are you certain this is a validamanda tape? Or you showed the sequence of commands accurately?Solaris has a fine file(1) command. What does "file /tmp/data"tell you about what dd pulled
from the tape?-- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Restoring from tape when Amanda server failed
Pavel,Below if the output from the running the following commands: root@ # mt -f /dev/rmt/0n rewind root@ # mt -f /dev/rmt/0n fsf 1 root@ # dd if=/dev/rmt/0n bs=32k count=1 read: Invalid argument 0+0 records in 0+0 records outThanks, GilPavel Pragin <[EMAIL PROTECTED]> wrote: Hello,Can you please run this and post the output:-bash-3.00$ ammt -f /dev/rmt/0n rewind-bash-3.00$ ammt -f /dev/rmt/0n fsf 1-bash-3.00$ amdd if=/dev/rmt/0n bs=32k count=1Pavelgil naveh wrote:> Thanks> but I tried to strip the header as well and it gave me teh same error > message!>> */Matt Hyclak /* wrote:>> On Wed, Jul 19, 2006 at 02:07:42PM -0700, gil naveh enlightened us:> > Thanks for all the help, but I have a problem to restore the files.> > When I type:> > root@ # dd if=/dev/rmt/0n ibs=64k | ufsrestore if -> > I recieve the following error message:> > read: Invalid argument> > 0+0 records in> > 0+0 records out> > Volume is not in dump format> >> > But as far as I know it should be in a dump format!!! because> in the> > Amanda.conf I defined the backup as:> >>> You forgot to strip off the amanda header at the beginning of the> file.> Usually this is>> dd if=/dev/tape bs=32k skip=1>> -- > Matt Hyclak> Department of Mathematics> Department of Social Work> Ohio University> (740) 593-1263>>
Re: Restoring from tape when Amanda server failed
On Wed, 19 Jul 2006 at 2:07pm, gil naveh wrote Thanks for all the help, but I have a problem to restore the files. When I type: root@ # dd if=/dev/rmt/0n ibs=64k | ufsrestore if - Where did you get 64k from? Why aren't you following the directions you've been pointed at multiple times? Try this: mt rewind mt fsf 1 (this gets you past the amanda tape label) dd if=/dev/rmt/0n of=restored.image bs=32k skip=1 (this will get you the first backup image) Then run 'file restored.image', which will tell you what type of file that restore image is. Given your dumptype, the image will likely be gzipped. So then you'd have to do: zcat restored.image > restored.image.unzipped Obviously, that's assuming your zcat understands gzipped files. You should then be able to run ufsrestore on restored.image.unzipped. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Restoring from tape when Amanda server failed
Gil, You wheren't by any chance using SW compression ? You may have said earlier but I missed it if you did, if so you will need to lengthen the pipe a little bit... # dd | gunzip | ufsrestore On Wed, Jul 19, 2006 at 04:20:25PM -0700, Pavel Pragin wrote: > Hello, > Can you please run this and post the output: > -bash-3.00$ ammt -f /dev/rmt/0n rewind > -bash-3.00$ ammt -f /dev/rmt/0n fsf 1 > -bash-3.00$ amdd if=/dev/rmt/0n bs=32k count=1 > Pavel > > gil naveh wrote: > > >Thanks > >but I tried to strip the header as well and it gave me teh same error > >message! > > > >*/Matt Hyclak <[EMAIL PROTECTED]>/* wrote: > > > >On Wed, Jul 19, 2006 at 02:07:42PM -0700, gil naveh enlightened us: > >> Thanks for all the help, but I have a problem to restore the files. > >> When I type: > >> root@ # dd if=/dev/rmt/0n ibs=64k | ufsrestore if - > >> I recieve the following error message: > >> read: Invalid argument > >> 0+0 records in > >> 0+0 records out > >> Volume is not in dump format > >> > >> But as far as I know it should be in a dump format!!! ? because > >in the > >> Amanda.conf I defined the backup as: > >> > > > >You forgot to strip off the amanda header at the beginning of the > >file. > >Usually this is > > > >dd if=/dev/tape bs=32k skip=1 > > > >-- > >Matt Hyclak > >Department of Mathematics > >Department of Social Work > >Ohio University > >(740) 593-1263 > > > > > --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: Restoring from tape when Amanda server failed
Forgot one comment. After mt rewind, you have to mt fsf #, where # is a tape file number, to get to the start of the #'th dump on the tape. Then if you had followed the suggested reading, that tapefile contains a file header that must be skipped. It does no good to do a skip=1 to the first tape file, that is not a dump file. It is the tape label file. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Restoring from tape when Amanda server failed
On Wed, Jul 19, 2006 at 02:07:42PM -0700, gil naveh wrote:
> Thanks for all the help, but I have a problem to restore the files.
> When I type:
> root@ # dd if=/dev/rmt/0n ibs=64k | ufsrestore if -
> I recieve the following error message:
> read: Invalid argument
> 0+0 records in
> 0+0 records out
> Volume is not in dump format
>
> But as far as I know it should be in a dump format!!! because in the
> Amanda.conf I defined the backup as:
>
> define dumptype daily {
> global
> # program "DUMP" # the default
> # record yes # the default
> comment "daily"
> compress client fast
> priority high
> # dumpcycle 5# should be obtained from dumpcycle above
> index yes
> }
>
>
> I also tried the following:
> % mt -f /dev/rmt/0n rewind
> % dd if=/dev/rmt/0n of=/tmp/data bs=64k count=2
> % od -c /tmp/data | head
>
> And received the following output:
> 000 \0 002 P 022 \0 \f \0 001 . \0 \0 \0 \0 003 242 Q
> 020 \0 \f \0 002 . . \0 \0 \0 002 P 023 001 350 \0 006
> 040 n e w bc k \0 \0 \0 \f \0 003b c k \0
> 060 \0 \0 \0 \0 001 320 \0 006n e w b c k \0 \0
> 100 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
> *
> 0001000
>
> Can one deduct the dump format from the above output?
>
> Many thanks,
> gil
> Paul Bijnens <[EMAIL PROTECTED]> wrote:
> On 2006-07-19 17:35, gil naveh wrote:
> > Thanks for the help.
> > I am familiar with the Amrestore command.
>
> Then you understand that you can replace "amrestore" with a
> "mt" and "dd".
>
>
...
> The docs in http://www.amanda.org/docs/restore.html
> are a little more expanded, giving more examples in:
>
> http://wiki.zmanda.com/index.php/Restoring_files
>
Grrr, I hate top posting.
So hard to add inline and following
Anyway, several points.
We don't know it should be a ufsdump, your dumptype includes
global that we don't see and otherwise does not define PROGRAM.
You keep using a blocksize of 64k for dd, why? Amanda normally
uses 32k.
Have you read the docs refered to above for how to recover?
Your dumptype says compress, presumably with gzip. I see no
unzipping in your attempted recovery
commentary.
Following an mt rewind, the first thing a dd should see is
the tape label header file. Your output is certainly NOT
an amanda tape label. Are you certain this is a valid
amanda tape? Or you showed the sequence of commands accurately?
Solaris has a fine file(1) command. What does "file /tmp/data"
tell you about what dd pulled from the tape?
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Restoring from tape when Amanda server failed
Hello, Can you please run this and post the output: -bash-3.00$ ammt -f /dev/rmt/0n rewind -bash-3.00$ ammt -f /dev/rmt/0n fsf 1 -bash-3.00$ amdd if=/dev/rmt/0n bs=32k count=1 Pavel gil naveh wrote: Thanks but I tried to strip the header as well and it gave me teh same error message! */Matt Hyclak <[EMAIL PROTECTED]>/* wrote: On Wed, Jul 19, 2006 at 02:07:42PM -0700, gil naveh enlightened us: > Thanks for all the help, but I have a problem to restore the files. > When I type: > root@ # dd if=/dev/rmt/0n ibs=64k | ufsrestore if - > I recieve the following error message: > read: Invalid argument > 0+0 records in > 0+0 records out > Volume is not in dump format > > But as far as I know it should be in a dump format!!! – because in the > Amanda.conf I defined the backup as: > You forgot to strip off the amanda header at the beginning of the file. Usually this is dd if=/dev/tape bs=32k skip=1 -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Re: Restoring from tape when Amanda server failed
On Wednesday 19 July 2006 17:07, gil naveh wrote:
>Thanks for all the help, but I have a problem to restore the
> files. When I type:
> root@ # dd if=/dev/rmt/0n ibs=64k | ufsrestore if -
> I recieve the following error message:
> read: Invalid argument
> 0+0 records in
> 0+0 records out
> Volume is not in dump format
>
> But as far as I know it should be in a dump format!!! because in
> the Amanda.conf I defined the backup as:
>
> define dumptype daily {
> global
> # program "DUMP" # the default
> # record yes # the default
> comment "daily"
> compress client fast
> priority high
> # dumpcycle 5# should be obtained from dumpcycle
> above index yes
> }
>
>
> I also tried the following:
> % mt -f /dev/rmt/0n rewind
> % dd if=/dev/rmt/0n of=/tmp/data bs=64k count=2
> % od -c /tmp/data | head
>
> And received the following output:
> 000 \0 002 P 022 \0 \f \0 001 . \0 \0 \0 \0 003 242
> Q 020 \0 \f \0 002 . . \0 \0 \0 002 P 023 001 350
> \0 006 040 n e w bc k \0 \0 \0 \f \0 003b
> c k \0 060 \0 \0 \0 \0 001 320 \0 006n e w b
> c k \0 \0 100 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
> \0 \0 \0 \0 \0 *
> 0001000
>
One thing I can categoricly state is that that is not an amanda tape
header.
It should resemble this for the above command line:
[EMAIL PROTECTED] amanda]# od -c scratch1 | head
000 A M A N D A : T A P E S T A R
020 T D A T E 2 0 0 3 0 5 2 6
040 T A P E D a i l y S e t 1 - 0
060 2 \n \f \n \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
100 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
*
010
> Can one deduct the dump format from the above output?
>
> Many thanks,
> gil
>Paul Bijnens <[EMAIL PROTECTED]> wrote:
>
>On 2006-07-19 17:35, gil naveh wrote:
>> Thanks for the help.
>> I am familiar with the Amrestore command.
>
>Then you understand that you can replace "amrestore" with a
>"mt" and "dd".
>
>> But the problem I am facing is that the Amanda server which also
>> holds other applications crushed. So I have to restore data from
>> another server - I have Solaris 9 and and or Solaris 10 servers that
>> I can connect to the tape drive...
>> I also saved the configuration files of the amanda server.
>> Is there a way to directly connect to the tape drive and use unix
>> commands to restore data from it?
>> Or any other suggestions...
>
>mt -f /dev/rmt/0n fsf 34
>dd bs=32k if=/dev/rmt/0n skip=1 of=/some/where
>
>dd to to stdout, in a pipe with netcat:
> ... | nc -w 1 client 1234
>
>And on the client you have already this command listening:
>
>nc -l -p 1234 | gtar -zxpGvf -
>
>The docs in http://www.amanda.org/docs/restore.html
>are a little more expanded, giving more examples in:
>
>http://wiki.zmanda.com/index.php/Restoring_files
>
>Easiest is to first restore the amanda command "amrestore"
>That one does not need any config file at all.
--
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules. I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: Restoring from tape when Amanda server failed
gil naveh wrote: Thanks but I tried to strip the header as well and it gave me teh same error message! If it's compressed, it need to be uncompressed first. Do something like: dd if=/dev/tape bs=32k skip=1 |gzip -dc | ufsrestore if - */Matt Hyclak <[EMAIL PROTECTED]>/* wrote: On Wed, Jul 19, 2006 at 02:07:42PM -0700, gil naveh enlightened us: > Thanks for all the help, but I have a problem to restore the files. > When I type: > root@ # dd if=/dev/rmt/0n ibs=64k | ufsrestore if - > I recieve the following error message: > read: Invalid argument > 0+0 records in > 0+0 records out > Volume is not in dump format > > But as far as I know it should be in a dump format!!! – because in the > Amanda.conf I defined the backup as: > You forgot to strip off the amanda header at the beginning of the file. Usually this is dd if=/dev/tape bs=32k skip=1 -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263 -- Thank you! Kevin Till Amanda documentation: http://wiki.zmanda.com Amanda forums:http://forums.zmanda.com
