On Tue, 12 Dec 2000, John R. Jackson wrote:
> >... I have have been using amstatus to monitor the
> >dump, and it seems that the dump gets to about 140%, then goes back to 0%.
>
> I notice it's well over 2 (or 4) GBytes in size. It's my understanding
> Linux does not support files > 2 GBytes. What do you have chunksize set
> to in amanda.conf? I'd suggest something along the lines of 1000 MBytes.
Yes, I have my chunksize set to 1000 MB.
I am a little confused by this issue. I understand that Linux has a 2 gig
file limit, but I am not sure how this might affect the amanda backups.
Does this mean that I should make sure that I should ensure that the
directories I back up should be under 2 gig? I thought that the tape did
not have a file size limit, so it would happily eat up what was given to
it by amanda. When restoring, I though that it would just pull the files
it needed from the tape and back to the client, and as long as no
individual file was larger than 2 gig there would not be a problem. Am I
off the mark here?
By the way, my backup appears to be working perfectly tonight (it's the
third night it's been run). I added some exclusions so I wasn't
backing up any *really* large directories. Tomorrow I will test
restoring...
> >Is there a way to stop 'amdump' nicely, so it will stop trying to dump
> >from 'queg' and send me it's nice email report? ...
>
> Not really a nice way. If you poke around at the process tree and find
> the dumper doing the work (you can also look through the amdump file and
> map back dumperNN that got the {PORT|FILE}-DUMP command to the begging
> of the file where the PID's are listed), just kill it. That will either
> get it to give up or it will try that dump one more time and you can
> kill off that dumper.
worked a treat, thanks :)
matt
