I tried to create a config for test use only. In general the test
config has a single filesystem and dumptype definition copied over
from the production config, and then modified for testing. It had a
cycle of one tape and I was using it to text the syntax for "exlude
list", because I was finding it impossible to exclude
directories. (I'm using 2.4.2 on Redhat-6.2 on both Sparc and Intel
platforms.)
All, I'm trying to figure out at the moment is the correct test config
and what I need to do to reset everything so I can run my DailySet in
production after running the test. It seems that there are certain
files which can't be separated out in the configuration
file. Specifically, the lists for the tar files and others. Also, all
the debugging information in /tmp gets overwritten so there is no way
for me to tell why a test worked but the production failed.
For me the ideal would be a test-mode where I could rerun repeatedly
with the same tape, remove the switch and then it would be production,
though I realize this may not be feasable with the amanda design
philosophy. Still there must be a standard way to test. How do I
create a test amanda.config that won't impact, any files used by the
production amand.config?
--
Josh Kuperman
[EMAIL PROTECTED]
