"John R. Jackson" wrote:
> >***A TAPE ERROR OCCURRED: [[writing filemark: Input/output error]].
>
> First, Amanda is doing nothing more than report to you what the OS
> told it. So there really was an I/O error of some type someplace.
> It's unlikely Amanda could cause this (except possibly by t
I want to (once a month) do a backup of all disks. My tapes are not
large enough to fit the whole thing, so I need to spread it across 3
tapes or so. I was thinking of setting up a 1-day dumpcycle with 3
runspercycle and just do all three dumps on a saturday. I don't think
this is the best way
At 2002-01-25T19:16:22Z, "Jeremy Wadsack" <[EMAIL PROTECTED]> writes:
> We switch from tape- to hdd-based backup because hard drives are MUCH
> cheaper than tapes these days. I need to figure out the 2GB limit on the
> drives before I completely restart the system (separate problem.)
Ehhh? The
>What was it exactly that the complaint was regarding dump?
Please, please, please, I'm **begging** all you nice folks on this list.
Don't start this thread up again :-) :-) :-).
This topic comes up here every once in a while. I won't go back into it
(although I might try writing up something f
>Is there any way to re-do this backup onto a good tape or am I hosed?
Amanda normally uses the same level as it did on the previous run unless
it thinks there will be enough savings to warrant moving to the next
level. It's not unusual on a very static file system, for instance,
to do all level
>... when I test using
>amrecover the directory /mnt/share/ is empty. No Photos, no Work.
>What am I doing wrong?
What was your working directory when you started amrecover? Amrecover
restores files into your current working directory, not back into the
original location. It even tries to warn
> On Friday, amdump wrote my dump images to a tape successfully, but a
> subsequent amverify showed that the tape is defective. Now, my dumps have
> been removed from the holding disk, but I don't think the images on the
> tape are usable.
>
> Is there any way to re-do this backup onto a good ta
Hi,
here's a patch for Amanda 2.4.2p2 to ignore xfsdump's occasionally
output on busy filesystems "WARNING: failed to get bulkstat information
for inode ..." and "WARNING: failed to get valid bulkstat information
for inode ...".
--- amanda-2.4.2p2-20011020.orig/client-src/sendbackup-dump.c Sat
Hi all,
I'm backing only 2 directories contained on a partition mounted
at /mnt/share using GNUTAR. Here's my disklist entry:
...
linuxman /mnt/share/Photos user
linuxman /mnt/share/Work user
...
amcheck runs fine, as does amdump. However, when I test using
amrecover the directory /mnt/shar