>160 Mb, not that much huh, and it gives me the answer in just 1.5 second or
>so..
>And I'm not quite sure that the duration of 1.5 second is okay... Is the
>command used to make an
>inventory of the data to backup?
GNU tar is very clever about noticing it is writing to /dev/null and
essentially does nothing. Try the command again but pipe the output
like this:
gtar ... --file - | cat > /dev/null
>Would it help if I should exclude these files?
You mean the sockets? You don't need to. The latest version of Amanda
ignores those messages.
>Or can I only exclude directories? Is there an example exclude.gtar file?
>I've been unlucky in finding one up to now.
Exclude lists are a black art. One of the Amanda users is writing a
document on how to do them, but it's not ready yet.
There are some examples in "the chapter":
http://www.backupcentral.com/amanda.html
You might also look at:
ftp://gandalf.cc.purdue.edu/pub/amanda/gtartest-exclude
>I don't know if I can simulate a backup without using the backup tapes (thus
>not increasing the tapenumber and amount of backups made). If I know that,
>it would help me, so I can simulate and test...
Only one Amanda thing can go on at a time. That's why you could not
run amcheck while amdump was running.
When nothing is running, you can test by creating a configuration just
like the one you have and making a few changes:
* Set tapedev to /dev/null and comment out any tape changer entries.
This will throw the images away.
* Set the "record" dumptype option to "no" so your tests do not
affect the sequence of real backups.
Make sure you keep the log files (logfile), database area (infofile),
index files (indexdir) and tapelist (same directory as amanda.conf or
"tapelist" in amanda.conf) separate between the two configurations.
>Thanks again for additional help.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
