Veritas Storage Foundation 5.0 for Oracle RAC Configuration Guide Extracts for HP Serviceguard Storage Management Suite, Second Edition, May 2008

Using Storage Checkpoints and Storage Rollback
Using Storage Checkpoints and Storage Rollback for Backup and Restore
Chapter 4
44
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.
NOTE 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
dbed_update.
Mountable Storage Checkpoints can be used for a wide range of application solutions,
including backup, investigations into data integrity, staging upgrades or database
modifications, and data replication solutions.
If you mount a Storage Checkpoint as read-write, the command does 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 of 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 the Veritas Storage
Foundation for Oracle Administrator's Guide available on the SG SMS media and at:
http://www.docs.hp.com