Re: restoring a particular file
Hi Hery! On 25 Oct 01 at 11:00 you wrote: > For example, let's say my configuration name is "Testconf" > My cartridges are labeled TestConf01, TestConf02, ... > Can anyone tell me the options I have to give amrestore (or amrecover?) > if I want to restore a file called /etc/test.txt which has been backep > up from host "seine" from filesystem "/etc"? assuming you want to restore the file on "seine" and your backup server is called "tapeserver" seine# cd /tmp seine# amrecover -C Testconf -s tapeserver -t tapeserver -d \ /dev/nsa0 (I don't know if *all* the switches are really required, but specifying them doesn't hurt) amrecover> sethost seine amrecover> setdisk /etc amrecover> add test.txt amrecover> extract After that you'll have a file /tmp/etc/test.txt, which you can copy over the original file. If you wanted the restored file to overwrite existing file immediately, you would start amrecover in /etc directory instead of /tmp. This is all assuming that /etc is separate partition, as you specified. HTH. -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * This message transmitted on 100% recycled electrons.
ide tape drives
Hi all, I was wondering if anyone has used ide tr5 tape drives successfully with amanda, and if so, what I should be giving amanda access to. ie. for a scsi drive, i'd set: /dev/nst0 and /dev/st0 What's the ide equivalent? (/dev/ht0)? Any success / disaster stories? I'll be using the 10G model. Thanks, Chris Herrmann Far Edge Technology p. 02 99553640 f. 02 99547994 m. 0403 393309 http://www.faredge.com.au
Re: ~/.netscape and ~/nsmail
On Mon, 29 Oct 2001, Alan Pham wrote: >Hi, > >Can anyone confirm that Amanda does not backing up the following directories: > > ~/.netscape > ~/nsmail > >of user home directories? Is this the default configuration? This is not the default configuration. You may, however, specify an exclude file to gnutar. See the relevant documentation for more detailed information. BTW, it's a bad idea to exclude ~/.netscape and ~/nsmail. You'll lose your mail and bookmarks. I always exclude ~/.netscape/cache though. -- "Never put off until tomorrow what you can do today. There might be a law against it by that time." -- /usr/games/fortune, 07/30/2001 Brandon D. Valentine
FreeBSD Gmake and port not secure
Hi, I am at a loss for these two problems. If anyone has had experiences like this and found solutions, please let me know. The first is an Amanda 2.4.2p2 client on a FreeBSD 4.3 machine. When I try to 'make clean'an install I get workbench-01# make clean *** Error code 1 Stop in /usr/amanda-2.4.2p2. workbench-01# When I tried the make install the first time there was the same error message at the end, but it compiled, and ran when I tried it. I even did a backup of the client that worked fine without error message. I searched the FAQ-O-Matic and it mentioned that gmake is necessary on a FreeBSD machine. I have tried installing gmake, but the make clean (and gmake clean) still produce the error code 1. Is there another way? The client works and gets backed up fine, or at least it would if the 2nd error wasn't around, but that error code bugs me. If I ever need to make clean, I can't. Are there other things I can take a look at? The other problem is with the server, a RH Linux 7.1. On Friday I had the back ups working. It saw all the clients and was working fine. Today (Monday) the server began with error messages about the clients timing out. Looking into it I found that the clients were referencing ports other than the ones specified, thereby getting the "port not secure" error. I feel like it's the server because all of the clients respond to an odd port range. I set the udpportrange to be <1024, but it seems like the range is 10070-10079. When I set the ipchains to accept this range, with amcheck I got the "port not secure" on the server side, as well as on the client amdebug. I am the only person with access to the server, and I don't believe we've been cracked, so something changed through a misconfiguration of mine. It was working on Friday, and I'm certain I saved the configuration files as they were. My only thought it that it may have had something to do with closing the terminal window connections I had to the server. But that feels like I'm reaching for an explanation. Has anyone else had this specific problem with the port not secure come up when it was once thought to be solved? For that matter, does anyone have any suggestions on things to try to get rid of the error? The methods I used on Friday to fix it aren't working on Monday. I have checked the owner of amanda files, and re-compiled with the same arguments used on Friday. I have restarted the xinetd, and verified the ipchains to let everything through.I've looked for what's different and found nothing. Thanks in advance. -- Lalo Castro CNS McHenry Library UC Santa Cruz
~/.netscape and ~/nsmail
Hi, Can anyone confirm that Amanda does not backing up the following directories: ~/.netscape ~/nsmail of user home directories? Is this the default configuration? Thanks! --alan
No Subject
Craig, Are all of you networking daemons running (mountd, statd, lockd, automountd). And no errors on your rc.3 scripts on startup (nfs.server, nfs.client or autofs. Regards, Sean
Re: selfcheck request timed out. Host down? error
> I am having a problem backing up one of my UNIX boxes with Amanda. When I > run AmCheck I get the error: > > WARNING: bill: selfcheck request timed out. Host down? > Client check: 7 hosts checked in 29.678 seconds, 1 problem found. > > As you can see the check runs successfully on 6 hosts but times out on 1. > The host is not down as I can ping and rlogin in to it without any problem. > It does also have the appropriate entries in the /etc/services and > /etc/inetd.conf What's in /tmp/amanda/*debug on this machine?
Re: indexes
On Tue Oct 23, 2001 at 11:48:19PM +0200, Bernhard R. Erdmann wrote: > > I've got amanda serwer 2.4.2p2 on freebsd 4.4rc5 and amanda client > > on linux RH7.0 and freebsd 3.4 release. > > There isn't a lot of data to backup, only 2 GB from every host. > > Backup is done every night, starting from cron. > > Streamer is 40/80GB Tandberg DLT1, I've only one tape. > > Go buy some more tapes - if writing to this single tape fails you will > be lost with no backup Ok that's right, but in amanda documentation, there was written that one backup (6GB) on one tape (80GB) is a waste of space, thats why amanda support multiple backup on one tape. > > > In my opinion amanda should write next backup on tape just after the > > previous, so on one tape 80 GB there is a lot of place for lets say > > 4 backups. > > But when I run amrecover and type setdate ---21 (today is 23 ) > > amrecover says: > > 200 Working date set to 2001-10-21. > > No index records for cwd on new date > > Setting cwd to mount point > > > > But in directory /usr/local/amanda/DailySet1/index/"hostname"/"partition" > > ther is a lot of files like: 20011023_2.gz 20011022_2.gz 20011021_2.gz > > all in mode 600. > > So why amrecover says that there is no indexes, > > and I can't recover from few days earlier? > > Did you type "sethost " and "setdisk " in > amrecover? Yes I did. When I type history in amrecover, output is: 200- Dump history for config "DailySet1" host "ekoraid" disk "/export" 201- 2001-10-25 0 DailySet123 5 200 Dump history for config "DailySet1" host "ekoraid" disk "/export" Backup is done every day since last two weeks, so something is wrong. "ekoraid" is amanda client. Maybe this is client not server problem?
Re: Linux dump failure
> Does anyone know what the following error means: > > /-- otis /home lev 1 FAILED [/sbin/dump returned 3] > sendbackup: start [otis:/home level 1] > sendbackup: info BACKUP=/sbin/dump > sendbackup: info RECOVER_CMD=/sbin/restore -f... - > sendbackup: info end > | DUMP: Date of this level 1 dump: Thu Oct 25 22:06:24 2001 > | DUMP: Date of last level 0 dump: Sat Oct 6 03:03:08 2001 > | DUMP: Dumping /dev/sda6 (/home) to standard output > | DUMP: Label: none > | DUMP: mapping (Pass I) [regular files] > | DUMP: mapping (Pass II) [directories] > | DUMP: estimated 6405 tape blocks. > | DUMP: Volume 1 started at: Thu Oct 25 22:06:25 2001 > | DUMP: dumping (Pass III) [directories] > ? /dev/sda6: EXT2 directory corrupted while converting directory #31015 > ? > ? DUMP: error reading command pipe: Connection reset by peer > ? DUMP: error reading command pipe: Connection reset by peer > sendbackup: error [/sbin/dump returned 3] > \ > > Other filesystems on the same host work fine. Thanks, mount -o ro,remount /home e2fsck /dev/sda6 e2fsck -f /dev/sda6
No Subject
unsubscribe _ Si no encuentras lo que buscas... ¿a qué estás esperando para entrar en www.wanadoo.es? Con nuestro nuevo motor de búsqueda conseguirás más rápido resultados de actualidad, personalizados y renovados diariamente.
[Fwd: Re: TapeTypes]
hi
i just do it
define tapetype unknown-tapetype {
comment "just produced by tapetype program"
length 34566 mbytes
filemark 27 kbytes
speed 1439 kps
}
this for the HP 40/80 DLT
c5141f tape
have fun
Patrick
Chris Heiser wrote:
> Anyone have a tapetype for 40/80GB DLT1 Tapes? Tapetype will definitely
> take too long to run on this drive
>
> --Chris
>
>
>
--
__( /
| | /
\ | This message is transmitted by | \
\ | 100 % recycled electrons |___\
/ |__(
/__)
RESULTS MISSING
Hi, As of yesterday my AMANDA backups stopped running, and simply send me a mail report listings all my hosts with "RESULTS MISSING". I've reviewed sendsize.debug on each of the hosts and it looks like everything was working normal. I'm using the fully qualified hostname for the machine local to AMANDA. What other reasons are there for AMANDA to give up and report "RESULTS MISSING" for _EVERY_ host? I'm running Amanda version 2.4.1p1 on each host. Thank You, Rob
Re: indexes
> I've got amanda serwer 2.4.2p2 on freebsd 4.4rc5 and amanda client > on linux RH7.0 and freebsd 3.4 release. > There isn't a lot of data to backup, only 2 GB from every host. > Backup is done every night, starting from cron. > Streamer is 40/80GB Tandberg DLT1, I've only one tape. Go buy some more tapes - if writing to this single tape fails you will be lost with no backup > In my opinion amanda should write next backup on tape just after the > previous, so on one tape 80 GB there is a lot of place for lets say > 4 backups. > But when I run amrecover and type setdate ---21 (today is 23 ) > amrecover says: > 200 Working date set to 2001-10-21. > No index records for cwd on new date > Setting cwd to mount point > > But in directory /usr/local/amanda/DailySet1/index/"hostname"/"partition" > ther is a lot of files like: 20011023_2.gz 20011022_2.gz 20011021_2.gz > all in mode 600. > So why amrecover says that there is no indexes, > and I can't recover from few days earlier? Did you type "sethost " and "setdisk " in amrecover?
Re: tapetype question
> I have a Sony SDX-500C and tapetype reported the following:
>
> define tapetype SDX-500C {
> comment "just produced by tapetype program"
> length 21709 mbytes
> filemark 773 kbytes
> speed 3660 kbytes
> }
>
> From the above output tapetype believes that this tape will only hold 21
> Gigs. The tape is an AIT-1 25/50G tape. Is it ok for me to up the
> length? Why does tapetype report at least 4 gigs less then the native
> capacity of the tape.
I guess you enabled hardware compression.
Re: exclude list question
[...]
> Which is what I expect to see, but if I attempt to use a directory that
> begins with a dot "." it does not work:
>
> For example new dump type:
>
> define dumptype test {
> program "GNUTAR"
> comment "test"
> priority medium
> exclude list ".amexclude/exclude"
> }
>
> Produces the following on the client:
>
> 5763 ?R 0:00 /bin/tar --create --directory /usr
> --listed-incremental /var/lib/amanda/gnutar-lists/hostname.sda5_0.new
> --sparse --one-file-system --ignore-failed-read --totals --file /dev/null
> .
>
> Any ideas?
Don't use a path starting with dot.
testing
Re: amanda/gnutar croaks/corrupts big .Z compressed file
On Monday 29 October 2001 01:04 am, shan wrote: > Do you know if the backup you had problems with was an incremental? > exclude patterns? etc? I believe it was a straight tar with gzip. I know that I wasn't doing anything incremental. I didn't have any excludes, but I did have a long list of includes, as I was only grabbing certain things in the directory to span 2 cd's. I'm going to try again, probably tomorrow when I get a chance. Perhaps (knock on wood) it is just a happy coincidence, or brought on by cosmic rays.
SCSI Tape Issues
Hi All, I was wondering if someone can shed some light on the following problem I'm having with my HP SCSI DAT 40x6e. I'm using amanda-2.4.2-ps on FreeBSD 4.3. The problem is this : Almost seemingly randomly I get the following error in /var/log/messages when writing to the tape device : Oct 25 16:28:26 hercules /kernel: (sa0:ahc2:0:5:0): camisr(sa0:ahc2:0:5:0): tape is now fr ozen- use an OFFLINE, REWIND or MTEOM command to clear this state. At the above point all writing stops. As a 'mt status' shows I'm not using compression and I've set the device to use variable block sizes. # mt status Mode Density Blocksize bpi Compression Current: 0x26:DDS-4 variable 97000disabled -available modes- 0:0x26:DDS-4 variable 97000DCLZ 1:0x26:DDS-4 variable 97000DCLZ 2:0x26:DDS-4 variable 97000DCLZ 3:0x26:DDS-4 variable 97000DCLZ - Current Driver State: at rest. - File Number: 8 Record Number: 0Residual Count -32768 There are also two SCSI controllers in the machine. One onboard the motherboard and a PCI controller. Both are Adaptecs. The external backup device is connected to the PCI controller and is the only device on it. Any ideas? This is driving me mad ... Thanks, -byron
