What we do is flip the database into hot backup mode, which allows
us to make a consistent backup of the live database files. This is combined
with the snapshot capability of the NetApp so that we don't have to stay in
hot backup mode for more than a minute or so. Together, this procedure
Hm. Are you saying that Amanda can do a block-level incremental
backup? I had assumed that the main database files would have to be backed
up on every run, since they get written to thousands of times a day.
If it is feasible to incorporate everything into a daily rotation,
then I
The problem with the offsite is that I want it to include everything
from both the daily and the weekly database backups. So the disklist is a
composite of the other two jobs. If we tried to include the Oracle data
files under the regular daily rotation, they would get backed up every day
I've got a situation where that sort of thing might be handy. My
Amanda server covers an Oracle database (snapshotted on a NetApp) and
numerous individual servers.
For Oracle, a weekly full backup means grabbing the Oracle datafiles
and redologs, and a daily incremental means bac
