Re: Backup and recovery CD
On Tue, Feb 25, 2003 at 05:26:23PM -0500, Matt Hyclak wrote: > On Tue, Feb 25, 2003 at 09:32:54PM +0100, Martin Schwarz enlightened us: > > One of my colleagues has built a bootable rescue CD based on the Knoppix > > Gnu/Linux distribution (see www.knoppix.net if you don't know Knoppix). > > His CD includes an amanda client besides our usual tools and goodies. I > > Any chance we might be able to download said CD anywhere? I've not played > with Knoppix, so I don't know how easy it is to add software to the disk... Sorry, it's not available for download atm. But I hear it wasn't that hard to customize the Knoppix CD. It's based on Debian, so the Debian package management tools should work for adding stuff to it and removeing unneeded things. Perhaps amanda client was even already included in the latest version of the original Knoppix distribution, not sure... There are some infos on customizing/remastering Knoppix CDs at http://www.knoppix.net/docs/index.php/KnoppixCustomizations Knoppix Lite ftp://ftp.es.debian.org/pub/miniKnoppix looks like a nice starting point for an amanda rescue CD. Hth, Martin -- [EMAIL PROTECTED] toplink-plannet GmbH Network Operations EngineerSchönfeldstraße 8 Tel +49 [0] 721 6636-0 D-76131 Karlsruhe Fax +49 [0] 721 6636-199 http://www.toplink-plannet.de/
Re: Backup and recovery CD
On Tue, Feb 25, 2003 at 12:29:17PM -0500, Kevin M. Myer wrote: > A number of commercial backup vendors ship bootable CDs with a copy of their > backup application installed. You can use these CDs to restore a system that > was totally toasted, due to massive disk failure, being hacked, etc. I'm > wondering if anyone has ever developed something similar for AMANDA. One of my colleagues has built a bootable rescue CD based on the Knoppix Gnu/Linux distribution (see www.knoppix.net if you don't know Knoppix). His CD includes an amanda client besides our usual tools and goodies. I have just recently used this CD to clone two of our machines, testing the disaster recovery in case of a complate hard disk failure. Steps are: - booting from the rescue CD - setting up networking and starting sshd to be able to work comfortably from my workstation ;-) - partitioning the hard disk, setting up swap, creating file systems - mounting the root partition somewhere like /mnt/target - recovering the root partition using amrecover via the network - mounting the remaining partitions into the recovered root partition's mount points - recovering the remaining partitions - setting up tmp on the target partition (since /tmp is normally excluded from our backups), giving it the correct permissions - chrooting into /mnt/target and making the system bootable (quite easy with grub) - rebooting and testing the system. Works great if the new machine is identical to the old one. In my case, I ran into a (small) problem because the clone machines were only Pentium I while the original machine's kernel was built for Pentium II and higher. However, since Knoppix (and thus my colleagues's rescue CD) are based on Debian, "apt-get install"-ing an appropriate kernel wasn't very hard :-) The most tedious part of this procedure was changing the tapes (only a single DLT drive here). I should really take a look at the file: driver some time... Bye, Martin -- [EMAIL PROTECTED] toplink-plannet GmbH Network Operations EngineerSchönfeldstraße 8 Tel +49 [0] 721 6636-0 D-76131 Karlsruhe Fax +49 [0] 721 6636-199 http://www.toplink-plannet.de/
Re: Force level 0 on certain days?
On Fri, Feb 07, 2003 at 09:47:55AM -0500, wab wrote: > I'm wondering if it's possible to Force a level 0 of a certain > filesystem on a certain day, say, Friday. Use "amadmin CONFIG force HOST DISK" to force a level 0 at the next run, use cron to automate the job for the weekday you want. Bye, Martin -- [EMAIL PROTECTED] toplink-plannet GmbH Network Operations EngineerSchönfeldstraße 8 Tel +49 [0] 721 6636-0 D-76131 Karlsruhe Fax +49 [0] 721 6636-199 http://www.toplink-plannet.de/
Re: strange dump message
Hello Eric, On Wed, Feb 05, 2003 at 09:01:10AM -0500, Eric Sproul wrote: > ? /dev/sda1: EXT2 directory corrupted while converting directory #41021 [...] > I tried looking for an explanation for the "EXT2 directory corrupted" > dump message, but all I could find was basically "we don't know what it > is, just fsck it and move on". That isn't good enough for me. ;) > Whatever it is, it doesn't seem to be causing grief to the server's > normal operation, but it is preventing me from getting a backup. > > Has anyone else run across this problem? How did you solve it? I have seen the same error message a few times (on Debian 3.0, too, but I don't think that matters). AFAIK (someone please correct me if I'm wrong!) this "error" is the result of dumping an active (mounted) filesystem on which files are being changed during the dump run. fsck checks I have run afterwards (on the umounted fs) have shown no errors. The incident still is very annoying since "the ENTIRE dump is aborted" leaving me without a backup for this DLE. My solution was to switch from dump to gnutar. I still get messages files that have changed during the read operation etc. but these do not cause the whole DLE to fail. Bye, Martin -- [EMAIL PROTECTED] toplink-plannet GmbH Network Operations EngineerSchönfeldstraße 8 Tel +49 [0] 721 6636-0 D-76131 Karlsruhe Fax +49 [0] 721 6636-199 http://www.toplink-plannet.de/
Re: Amflush failing silently
Hi Christoph, On Wed, Feb 05, 2003 at 10:14:35AM +0100, Christoph Scheeder wrote: > Problem if i tell amflush only to flush run named "C:", for example, > amflush does nothing, terminating without sending an e-mail. are your literally typing "C:" including the colon? Try to use just the letter, see if that helps. Bye, Martin. -- [EMAIL PROTECTED] toplink-plannet GmbH Network Operations EngineerSchönfeldstraße 8 Tel +49 [0] 721 6636-0 D-76131 Karlsruhe Fax +49 [0] 721 6636-199 http://www.toplink-plannet.de/
Re: Amcheck not emailing
On Tue, Oct 22, 2002 at 12:20:15PM -0400, Thom Paine wrote: > On Tue, 2002-10-22 at 12:03, Martin Schwarz wrote: > > "Nothing is printed, but mail is sent if any errors are detected." > > (amcheck manpage) > > Oh, well then. I thought it would email with an okay similar to the > amcheck DailySet1. You can get that beheviour if you want: just leave out the -m flag and pipe amcheck's output to mail. Or let cron send you mail about the output of the cron job. But why be bothered by another email when everything is fine? ;-) Greetings, Martin.
Re: Amcheck not emailing
On Tue, Oct 22, 2002 at 11:49:31AM -0400, Thom Paine wrote: > For some reason amanda is not sending out the mail report from amcheck > -m DailySet1. I get the report after the backup has run. IMO you are experiencing perfectly normal behaviour: - amcheck -m doesn't find any errors, thus is keeping quiet. You will only get mail from amcheck -m if it has encountered some errors: "Nothing is printed, but mail is sent if any errors are detected." (amcheck manpage) - amdump runs the backup and sends out its usual report about the run. Kind regards, Martin.
Re: Planner note inconsistent with stats & summary
On Tue, Oct 22, 2002 at 10:04:41AM -0300, Doug Meredith wrote: > I have seen this a couple of times now. In the notes section of the report, > planner claims "Incremental of filet:/platoon/v1.1 bumped to level 2.". > According to the dump summary, a level 0 was done for this directory. The > statistics section shows two level 0 and six level 1 dumps. Has anyone seen > this before? Yes, occurs here sometimes as well: planner announces a level 2 backup for a disk list entry, but a level 0 (full) dump is done instead. If I understand amanda correctly, planner WOULD bump this disk list entry's level to 2 (instead of staying at level 1, since the bump threshold has been reached), but the DLE is due for a full (level 0) dump, so this is what really gets done. (Anybody please correct me if I'm wrong.) A little confusing perhaps, but otherwise normal behaviour. Greetings, Martin.
Re: a quick question
On Fri, Oct 04, 2002 at 10:54:16AM -0400, c white wrote: > i've been running amanda for over a year now and every time i get a > report it tells me that the esitmated time for the job is 3 minutes, > when it actually take almost 1.5 hours, why is this? that's the time it took amanda to collect the size estimates from each client, not an estimate on the overall run time. 3 minutes sounds normal to me. Greetings, Martin.
Re: turn off hardware compression
On Fri, Oct 04, 2002 at 02:08:07PM +0200, Per olof Ljungmark wrote: > > >take the correct tape device, usually /dev/nrmt0l on Compaq/T64. This > >device does no compression, while the others (/dev/nrmt0[hc..]) use more > >or less of hardware compression. > > Are there any knowledgeable people around here using FreeBSD? What is the > non-compressed tape device called? I have no in-depth experience with FreeBSD, but I have not heard of a distinction on compression in the device file. Perhaps this is mixed up with the distinction of the rewinding/non-rewinding device? We have a FreeBSD 4.1-RELEASE machine here (that will soon be replaced) which is using hardware compression (we'll change that, of course) on a DLT drive by calling the following wrapper script from cron: #!/bin/sh /usr/bin/mt comp on $HOME/sbin/amdump ToplinkDaily /usr/bin/mt rewoffl tapedev used is the normal non-rewinding scsi tape: tapedev "/dev/nrsa0" Hope this helps, Martin.
Re: no bandwidth
Hello Gene, On Tue, Oct 01, 2002 at 11:28:54AM -0400, Gene Heskett wrote: > On Tuesday 01 October 2002 10:53, Martin Schwarz wrote: > > I have set netusage to 12800 KBytes/sec, the theoretical maximum > > of a 100MBit/s ethernet, since I want amanda to use all the > > bandwith she can and needs. > > I believe thats an erronious value Martin. The com protocol over > ethernet is still basicly a seriel channel albeit a duplex one if > the cards are new enough all the way through. Being a seriel > protocol, there is still a start and stop bit for each byte, making > each byte actually occupy 10 bit times in the 100mbit data stream, > so that would mean the net is maxed out at 10,000 KBytes/Sec, or 10 that's why I wrote "theoretical maximum" ;-) I admit my theory is heavily simplified here, that's right, but ... > megabytes. And I've leave some room for other traffic by backing > that off about 2 megabytes a second to 80,000kbps just to be a nice > hog about it at the bandwidth trough. > > OTOH, thats just my $0.02, whatever works _is_ whatever works. If > nothing else needs any bandwidth while amanda is running, then grab > it all. ... I just want to make sure, that amanda will try to use the bandwidth she needs. And if something else needs bandwidth at the same time, the total bandwidth will be divided up between them. IMO the netusage parameter is most useful if you want to _guarantee_ a certain free bandwidth for other traffic on the net (time-critical applications like Voice-over-IP come to mind) by forcing amanda to _always_ stay below the netusage limit. However (if I understand the docs correctly), amanda will honor this limit no matter if there _is_ any other traffic, so most of the time you might end up leaving bandwidth unused. Greetings, Martin
Re: no bandwidth
On Tue, Oct 01, 2002 at 10:11:48AM -0400, [EMAIL PROTECTED] wrote: > I have an amanda run that I have been watching over the last couple of > days with amstatus. I am receiving a "no bandwitdh" message for three of > my four dumpers. I have the netusage option in my amanda.conf file > commented out. Is this what is going on? Does amanda have a compile time > default that I am maxing out? What is a good number for this? I archive > between 5 and 80Gs a day depending on the level of the backup. According to the amanda manpage, the default value for netusage is 300 Kbps, which IMO is far too low for today's LAN technologies. I have set netusage to 12800 KBytes/sec, the theoretical maximum of a 100MBit/s ethernet, since I want amanda to use all the bandwith she can and needs. Greetings, Martin
Re: Autoloader SLR100: Tapetype definition in amanda.conf ?
On Tue, Oct 01, 2002 at 01:05:07PM +0200, GERHARD Daniel wrote: > I'm installing Amanda on Debian 3.0, with an Autoloader SLR100 from > Tandberg Data. > I want to define the Tapetype, but I haven't any information about the > filemark and the speed of this band. > Has anyone information, please? sorry, no Tandberg drive here. But you can run the tapetype(1) program to find out this data yourself, if you can't find it on the Amanda FAQ-O-Matic (http://www.amanda.org/cgi-bin/fom?): | $ whatis tapetype | tapetype (1) - test a tape in a tape drive and generate an Amanda tapetype |entry | $ /usr/sbin/tapetype -h | usage: tapetype -h [-e estsize] [-f tapedev] [-t typename] | -hdisplay this message | -e estsizeestimated tape size (default: 1g == 1024m) | -f tapedevtape device name (default: $TAPE) | -t typename tapetype name (default: unknown-tapetype) | | Note: disable hardware compression when running this program. Be warned however that tapetype might run quite a long time. Hope this helps, Martin.
Re: comments about amanda packages requested
On Fri, Sep 27, 2002 at 07:40:06AM -0500, Jim Summers wrote:
> I have lost the original post on this. But how will options such as
> --with-udp-ports, etc... be done in a pre-built? Could be important for
> firewallers. I guess a certian range could be specified and documented.
At least in the Debian package no port range is given at all, i.e. any
random UDP port must be allowed which made my firewall admin (once more)
grumble about the "unusual" network protocol amanda uses ("even worse
than ftp"). But since both source and destination IPs are well-known and
fixed, the security implications can probably be accepted.
Below is the build information from the Debian package, as gets recorded
in the amdump.n log file:
build: VERSION="Amanda-2.4.2p2"
BUILT_DATE="Tue Apr 2 21:24:21 UTC 2002"
BUILT_MACH="Linux cyberhq 2.4.18pre2 #1 SMP Tue Jan 8 18:13:43 PST 2002 i686
unknown"
CC="gcc"
paths: bindir="/usr/sbin" sbindir="/usr/sbin"
libexecdir="/usr/lib/amanda" mandir="/usr/share/man"
AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda"
CONFIG_DIR="/etc/amanda" DEV_PREFIX="/dev/"
RDEV_PREFIX="/dev/r" DUMP="/sbin/dump"
RESTORE="/sbin/restore" SAMBA_CLIENT="/usr/bin/smbclient"
GNUTAR="/bin/tar" COMPRESS_PATH="/bin/gzip"
UNCOMPRESS_PATH="/bin/gzip" MAILER="/usr/bin/Mail"
listed_incr_dir="/var/lib/amanda/gnutar-lists"
defs: DEFAULT_SERVER="localhost" DEFAULT_CONFIG="DailySet1"
DEFAULT_TAPE_SERVER="localhost"
DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM
LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS
CLIENT_LOGIN="backup" FORCE_USERID HAVE_GZIP
COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
Greetings,
Martin.
Re: comments about amanda packages requested
Hello Jon, On Thu, Sep 26, 2002 at 11:04:23AM -0400, Jon LaBadie wrote: > I have the ear of the site maintainer and think I can influence > what goes into the amanda package. But I need some suggestions. just a quick idea: You might want to take a look at the amanda packages in Debian. IMO the package maintainer has done a nice job there. Perhaps you can get some ideas from them... http://packages.debian.org/cgi-bin/search_packages.pl ?keywords=amanda&searchon=names&subword=1&version=all&release=all (URL should go in one line, of course) Greetings, Martin.
Re: WangDAT 3400DX DDS2-120m tapetype
On Wed, Sep 25, 2002 at 02:35:54AM -0400, Gene Heskett wrote:
> assumption on my part is wrong. When and if you re-run tapetype
> again, leave out or change the -e option and see if that effects
> the filemark value returned. But it will take longer to run
> without the -e option IIRC.
As suggested, I have re-run tapetype on the drive, leaving out the -e
[estimate] argument:
--
$ time sudo -u backup tapetype -f /dev/tape -t DDS2-120m-no-estimate \
&& echo Ok.
wrote 120009 32Kb blocks in 367 files in 12166 seconds (short write)
wrote 119968 32Kb blocks in 736 files in 13385 seconds (short write)
define tapetype DDS2-120m-no-estimate {
comment "just produced by tapetype program"
length 3751 mbytes
filemark 3 kbytes
speed 301 kps
}
real428m24.768s
user0m2.700s
sys 4m15.500s
Ok.
$
--
Both the length and speed values are somewhat lower than before, but the
most significant difference is in the filemark value, which looks much
more reasonable now.
Greetings,
Martin.
Re: WangDAT 3400DX DDS2-120m tapetype
Hello Gene, On Wed, Sep 25, 2002 at 02:35:54AM -0400, Gene Heskett wrote: > The drive can do about 350-375 on hot rod machines, so its possible > the p133 is beginning to effect it somewhat. I certainly wouldn't AFAIR the machine had been quite busy otherwise at the time of that tapetype run. The backup last night (my first on this setup without hardware compression) achieved an average tape write rate of 344.6 KByte/s which is ok IMO. The drive is connected to an old Adaptec 1542 controller (ISA) which might as well slow things down... > want to run the compression on that machine as I'd think that a > dumptype spec of "compress server best" would be downright painfull > to watch, if you could manage to stay awake. :-) Besides, compress There's only one client backed up besides the server itself, and this is a moderately fast machine that does its own compress-best. However, I had once tried a "compress-best" on the server's own paritions and it took about 5 times longer than the usual. Now I'm back to compress-fast and happy with it. Greetings, Martin.
WangDAT 3400DX DDS2-120m tapetype (was: Re: [amanda 2.4.2p2] tar exclude list not working)
On Sun, Sep 22, 2002 at 10:44:35AM +0200, Martin Schwarz wrote:
> On Sat, Sep 21, 2002 at 04:00:31PM -0400, Gene Heskett wrote:
> > The above looks as if you have the drives compression turned on,
>
> I have, although I should know better about this - having read the list
> for a while. Somehow I never thought about my own setup when reading
> about the cons of hardware compression... will switch it off.
Hardware compression is now switched off (both with the drive's internal
dip switch and the mt utility option), and I have rerun tapetype after
making sure the tape's internal information on this was cleared
(following Gene's instructions - thanks!). The results are as follows
(this is a WangDAT 3400DX SCSI DAT drive with a DDS2 120m tape):
martin@lissy:~$ sudo -u backup tapetype -h
usage: tapetype -h [-e estsize] [-f tapedev] [-t typename]
-hdisplay this message
-e estsizeestimated tape size (default: 1g == 1024m)
-f tapedevtape device name (default: $TAPE)
-t typename tapetype name (default: unknown-tapetype)
Note: disable hardware compression when running this program.
martin@lissy:~$ time sudo -u backup tapetype -e 4g -t DDS2-120m && echo
done.
wrote 121830 32Kb blocks in 93 files in 11355 seconds (short write)
wrote 111350 32Kb blocks in 170 files in 11570 seconds (short write)
define tapetype DDS2-120m {
comment "just produced by tapetype program"
length 4202 mbytes
filemark 4355 kbytes
speed 325 kps
}
real384m37.786s
user0m1.980s
sys 4m6.670s
done.
martin@lissy:~$
I'm not sure if this is correct.
- The length value looks good. How was that influenced by the estimate
of 4GByte I gave with the -e option? I had left out this option the
last time I ran tapetype.
- The filemark seems to be unusually high. Can this be correct? Does
this mean I'm wasting over 4 MBytes between two files on tape? Is this
something that can be changed or is it a property of the drive?
- The speed is not that high, but might well be correct. The machine the
tape drive is connected to is a lowly Pentium-133...
I will try to rerun the tapetype utility on another tape and see if the
results are similar.
Thanks for your time and your comments!
Martin.
Re: [amanda-users] Some Basic questions about rewinding/non-rewinding tape drives
Hello Vlad, On Mon, Sep 23, 2002 at 06:23:22PM +0200, Vlad Popa wrote: > How could I access the tapedrive with amanda which is a rewinding device, not > a non-rewinding ? In my setup (a Debian 3.0 i386 system as yours), I use tapedev "/dev/nst0" > Could it be that /dev/nst0 would be physically the same device (e.g. my > travan tape ) as /dev/st0 without the rewinding option ? That's correct. The manpage for st (the SCSI tape driver) shows: /dev/st* : the auto-rewind SCSI tape devices /dev/nst* : the non-rewind SCSI tape devices Perhaps you will also find the mt (magentic tape) manpage helpful. The mt tool allows you to manually operate your tape device. Greetings, Martin.
Re: [amanda 2.4.2p2] tar exclude list not working
Hello Gene, On Sat, Sep 21, 2002 at 04:00:31PM -0400, Gene Heskett wrote: > The above looks as if you have the drives compression turned on, I have, although I should know better about this - having read the list for a while. Somehow I never thought about my own setup when reading about the cons of hardware compression... will switch it off. > Back up the list here maybe 2 days, and read the procedure I posted > for someone else that will fix this. But I forgot to have him That's Message-Id: <[EMAIL PROTECTED]> - I will look into it, thanks! Greetings, Martin.
Re: [amanda 2.4.2p2] tar exclude list not working
Hi Christoph, On Sat, Sep 21, 2002 at 06:32:03PM +0200, Christoph Scheeder wrote: > your exclude-list syntax is not correct [...] > > [/etc/amanda/exclude.gtar] > > /disk-c1/martin/mac > > this should read > > ./mac > > it is relative to the root stated in your disklist-entry. ah, so absolute paths are not possible here? Using an absolute path for the exclude-list file in the dumptype definition as I did, would then lead to the exclusion af ANY directory named "mac" on ANY filesystem that uses this dumptype? Not what I wanted... The solution seems to use a _relative_ definition of the exclude-list file as well: [amanda.conf] exclude-list ".amanda-exclude.gtar" and [/disk-c1/martin/.amanda-exclude.gtar] ./mac I'll try this and see if it works. Many thanks for your help, Martin
Re: amanda reports and some questions
Hello Neil, On Sat, Sep 21, 2002 at 07:38:01AM -0500, Neil wrote: > Gene Heskett writes: > > 3) mt -f /dev/sra0 datcompression off > > I "man mt" but didn't find similar option as above. there are different implementations of the mt utlitiy. On my Debian 3.0 system I find: - GNU mt version 2.4.2 from the cpio package: "... This package also includes rmt, the remote tape server, and GNU mt, a tape drive control program. The mt program is essential for magnetic tape drive users. Debian's version of GNU mt supports SCSI tape drives." and - mt-st v. 0.7, package mt-st: "Linux SCSI tape driver aware magnetic tape control (aka. mt) Mt-st contains a version of "mt" that is aware of Linux's SCSI tape driver. Mt-st is able to set some esoteric control flags like tape partitions. Mt-st diverts (replaces) the GNU version of mt, in the cpio package. It also comes with stinit, a program to be run at boot time to set up tape defaults." The GNU mt manpage mentions the datcompression operation, while mt-st knows about compression and defcompression (default compression state). Greetings, Martin
[amanda 2.4.2p2] tar exclude list not working
Hello fellow amanda users,
I have been using amanda for some time, successfully backing up whole
filsystems with dump. Now I'm trying to back up only parts of one
(large) filesystem using gnutar and the exclude-list feature. The
relevant config snippets are as follows (machine lissy is server and
client in one, config name is "lissyDaily1"):
[/etc/amanda/lissyDaily1/disklist]
lissy /disk-c1/martin comp-user-tar
[/etc/amanda/lissyDaily1/amanda.conf]
...
define dumptype comp-user-tar {
program "GNUTAR"
comment "partitions dumped with tar"
options compress-fast, index
exclude list "/etc/amanda/exclude.gtar"
priority medium
}
[/etc/amanda/exclude.gtar]
/disk-c1/martin/mac
The results are not as I had expected. amanda seems to ignore the
exclude list and tries to backup the whole filesystem below
"/disk-c1/martin". Since this includes the rather large subdirectory
"/disk-c1/martin/mac", the backup doesn't fit on the tape and fails:
[lissyDaily1 AMANDA MAIL REPORT FOR September 21, 2002]
FAILURE AND STRANGE DUMP SUMMARY:
lissy /disk-c1/martin lev 1 FAILED [dump larger than tape,
skipping incremental]
The /var/log/amanda/lissyDaily1/amdump.1 log file show the estimated
backup size as:
got result for host lissy disk /disk-c1/martin: 0 -> 23243790K, 1 ->
23093150K, -1 -> -1K
which is (give or take a few KB) the size of the whole /disk-c1/martin
hierarchy INCLUDING the /disk-c1/martin/mac subdirectory:
$ du -sk /disk-c1/martin /disk-c1/martin/mac
23298740/disk-c1/martin
23133416/disk-c1/martin/mac
$
So, /disk-c1/martin EXCLUDING /disk-c1/martin/mac should be only
165324KB or about 160MBytes which would fit perfectly on the tape.
Some more information on my system:
- Debian GNU/Linux 3.0 on i386, using the distribiution binary packages
(amanda-client 2.4.2p2-4, amanda-common 2.4.2p2-4, amanda-server
2.4.2p2-4)
- single DDS2 SCSI tape drive (/dev/nst0), configured like this:
define tapetype DDS2-120m {
comment "WangTek DAT tape drive (DDS2)"
length 3265 mbytes
filemark 100 kbytes
speed 300 kbytes
}
I have searched the mailing list archives and FAQ-O-Matic but still
haven't got a clue about this. I will happily give more information on
the setup if needed. Any help is very welcome!
Many thanks in advance!
Martin.
[I am subscribed to amanda-users, so no need to Cc: to my address -
thanks!]
