Sigfried and Roy wrote:
i've been successfully backing up our data to a hard drive for over a
year but i need to upgrade the harddrive to a large size and was
thinking i might purchase a couple of external firwire drives, my
thinking being i could copy the config and logs over to the hard drives
This morning, I cam back from holiday, and had to see that there was no
successful backup since some days ... :-(
amstatus shows me, that almost all hosts have been backed up, but some
still have dumping to tape running for over 26 hours, although there
is no running amanda-process or anything
The following (just scripted, with commentary added) is a little long
and rather un-good.
samar 9# script
Script started, file is typescript
Position us at the start of the next volume. This volume has been
relabeled after setting the block size on the tape (last week).
samar 1#
I'm new to amanda but I've been administering UNIX servers for a while.
Dump is for dumping whole filesystems not directories. Tar is more
versatile. I believe in the amanda.conf you can specify DUMP or GNUTAR as
the dump mechanism. If you used GNUTAR you'll be able to dump only
directories.
On Mon, Jan 10, 2005 at 11:48:42AM -0500, Brian Cuttler wrote:
The following (just scripted, with commentary added) is a little long
and rather un-good.
...
Probing the drive I find a block size of 32768 again.
samar 25# mt -f /dev/sdlt2 setblksz 131072
samar 26#
Jon,
On Mon, Jan 10, 2005 at 04:19:45PM -0500, Jon LaBadie wrote:
Something that didn't error during the write but did
during the read ?
This is not too surprising to me.
A tape with a blocksize of 132k will accept a write of 32k and
simply pad it to the required size. No errors.
Hello,
I am new to Amanda and tape drives for that matter. I have set up
a Amanda server and for now have it just backing up itself. All works
well for the backup part. However when I try to restore I get this
message..
tar: ./2005-01-07_17-00-57/ibdata01.ibz: implausibly old time stamp
On Mon, Jan 10, 2005 at 02:47:43PM -0700, Jason Davis wrote:
tar: ./2005-01-07_17-00-57/ibdata01.ibz: implausibly old time stamp
1969-12-31 17:00:00
For some reason, tar thinks the file's timestamp is 0, or else
the timestamp recorded in the tarball is in fact 0. (1969-12-31
17:00:00 is the
