[Amanda-users] Bare metal restore problem

Jean-Louis Martineau wrote: What program do you use to do the backup? dump or tar? Jean-Louis khalil_noura wrote: Hi all, I am trying to do a bare metal restore. After I partionsed the disk and restored the client to holding. I rebooted to rescue mode created a

Snapshots, redundant ?

Here is a fun thought question. Assuming that we are running daily snapshots for the purposes of easing file restores and providing recovery for users that accidently remove files they still need (or corrupt spreadsheets or whatever they do)... daily snapshots on a rolling basis. /usr1 has

hard coded limit REP_TIMEOUT of 6hrs in amandad-src/amandad.c

Hi, I was hitting this hard coded limit a couple years ago running 2.5.2-20070523 and over the last month it started to show up again on a client having a lot of big DLEs (20 or so for a total of 11TB). Client is running 2.6.0p2 and server is at 2.6.1p1. Back then Jean-Louis provided me with a

Re: Backup issues with OpenBSD 4.5 machines

You get the error in the index pipe instead of the data path. The backup is correct but your index is empty. That's why you get a STRANGE result instead of a failure. Can you post a sendbackup.*.debug for a dle that failed? Jean-Louis Michael Burk wrote: Hello, I applied the patches to the

Re: Backup issues with OpenBSD 4.5 machines

Here are the two sendbackup.*.debug files for the / fs. First: 1251693102.343436: sendbackup: pid 29087 ruid 150 euid 150 version 2.6.2alpha: start at Sun Aug 30 22:31:42 2009 1251693102.345326: sendbackup: Version 2.6.2alpha 1251693102.379331: sendbackup: pid 29087 ruid 150 euid 150 version

Re: Backup issues with OpenBSD 4.5 machines

Do you have the patch I sent to stan on this system? The patch check before and after the write if the pipe is in O_NONBLOCK or not and give an error if it is. I'm totally lost since it is in blocking mode and you get EAGAIN, which is impossible Jean-louis Michael Burk wrote: Here

Re: Backup issues with OpenBSD 4.5 machines

Hi Jean-Louis, I thought I had applied the patches on this machine also, but it turns out I didn't (sorry about that). I applied the patches and ran a new dump. This time all 4 file systems succeeded, though /usr got the same strange message as on the other machine: 1251752282.483677:

Re: Backup issues with OpenBSD 4.5 machines

amanda doesn't do fcntl on these file descriptor. But my patch do: fcntl(fd, F_GETFL, 0) to check if it have O_NONBLOCK set, the patch doesn't change it. Can you try the attached patch, it do the same trick for the index file descriptor (remove previous patch before applying). Jean-Louis

Re: very slow dumper (42.7KB/s)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tom Robinson wrote: Hi, I'm running amanda (2.6.0p2-1) but have an older client running 2.4.2p2-1. On that client the full backup of a 4GB disk takes a very long time: DUMP SUMMARY: DUMPER

Re: very slow dumper (42.7KB/s)

Try looking on the client while the backup is running. Could be any of a lot of things. Network problems (check for errors on the NIC and the switch port), lack of CPU to run the compression, disk I/O contention, huge numbers of files (either in aggregate or in a single directory), or possibly

Re: very slow dumper (42.7KB/s)

Frank Smith wrote: Tom Robinson wrote: Hi, I'm running amanda (2.6.0p2-1) but have an older client running 2.4.2p2-1. On that client the full backup of a 4GB disk takes a very long time: DUMP SUMMARY: DUMPER STATS

Re: very slow dumper (42.7KB/s)

On Mon, Aug 31, 2009 at 11:51 PM, Tom Robinsontom.robin...@motec.com.au wrote: While the disk is reaching saturation (and recovering quickly) I'm thinking that the all the retransmissions would be slowing things down more. I don't see any errors on the client interface but there are four on