
Processing Before and After the Frozen Image
18 NetBackup ServerFree Agent System Administrator’s Guide
Note If additional disk drives are available and virtual volumes have already been
configured with the VERITAS Volume Manager 3.1 or later, choose a mirror frozen
image method.
Processing Before and After the Frozen Image
NetBackup performs several vital functions prior to creating a frozen image, as outlined
below and in the following text. Without this pre-processing, the integrity of the frozen
image cannot be guaranteed and the backup data may be of no value.
NetBackup Processing Before and After Creating the Frozen Image
Getting the Dust to Settle: Quiescing the System
Before a useful frozen image can be created, the target data must be transactionally
consistent or complete. A transaction is a single data action, such as updating a patient’s
record in a medical database, or creating a record for a new patient. Such a transaction is
composed of multiple I/O requests (search, copy, send, write, and so forth). Until the
transaction’s I/O requests are complete, the data is inconsistent and may be unsuitable for
backup.
1. Backup process requests database quiesce.
2. Database application quiesces (must wait for transactions
to complete).
3. Lock and flush the file system.
4. Create the frozen image.
5. Unlock the file system.
6. Release (unquiesce) the application.
7. Back up the frozen image.
8. Remove the frozen image.
Steps 1, 2, and 6 apply
only to databases, such
as those requiring
NetBackup for Oracle
ServerFree Agent.
Komentáře k této Příručce