Veritas Storage Foundation 5.1 SP1: Storage and Availability Management for Oracle (5900-1504, April 2011)

You can set a quota to limit how much space a file system will give to all storage
checkpoints, to prevent the checkpoints from consuming all free space.
See the command dbed_ckptquota for more information.
Storage Rollback restores a database, a tablespace, or datafiles on the primary
file systems to the point-in-time image created during a Storage Checkpoint.
Storage Rollback is accomplished by copying the "before" images from the
appropriate Storage Checkpoint back to the primary file system. As with Storage
Checkpoints, Storage Rollback restores at the block level, rather than at the file
level. Storage Rollback is executed using the dbed_ckptrollback command.
Whenever you change the structure of the database (for example, by adding or
deleting datafiles, converting PFILE to SPFILE, or converting SPFILE to PFILE),
you must run the dbed_update command.
For example:
$ /opt/VRTS/bin/dbed_update -S $ORACLE_SID -H $ORACLE_HOME
Mountable Storage Checkpoints can be used for a wide range of application
solutions including the following:
■ Backups
■ Investigations into data integrity
■ Staging upgrades
■ Database modifications
■ Data replication solutions
If you mount a Storage Checkpoint as read-write, the command will not allow you
to roll back to this Storage Checkpoint. This ensures that any Storage Checkpoint
data that has been modified incorrectly cannot be a source of any database
corruption. When a Storage Checkpoint is mounted as read-write, the
dbed_ckptmount command creates a "shadow" Storage Checkpoint and mounts
this "shadow" Storage Checkpoint as read-write. This allows the database to still
be rolled back to the original Storage Checkpoint.
For more information on mountable Storage Checkpoints:
See “Mounting Storage Checkpoints using dbed_ckptmount” on page 218.
197Using Database Storage Checkpoints and Storage Rollback
Using Storage Checkpoints and Storage Rollback for backup and restore