>... But if something gets changed
>at 3am and you want to backup the current data instead of the 3am
>data, how do you ensure that it gets backed up early enough in the
>run so that the data doesn't change during the backup and cause errors?
The only thing I can think of is to run an external script just before
amdump that copies the current data to a holding area and then have
Amanda back that up. This is similar to the recommended approach for
dealing with databases.
There is no way to guarantee Amanda will get something done before a
certain time other than knowing historically how long it takes to do a
run and starting the whole thing soon enough to be done by that time.
Even then you don't know for sure because one of the clients might
misbehave for some reason and go really, really slow, throwing the whole
thing off.
>Frank
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
