Snapshots provide a fast and space-efficient way to protect Oracle databases. When using snapshots with Oracle databases, there are important considerations to ensure a successful database recovery.
- All Oracle database LUNs must be protected as a set. Enable the Apply write-order consistency to protect all volume group members attribute to ensure that the LUNs reside in the same volume group. This attribute ensures that the snapshot applies at a single point in time to the member volumes of a write-order consistent volume group.
- Snapshots do not replace Oracle RMAN for regular database backups. However, they offer additional protection to the database and allow offloading RMAN processing to an alternate host.
- Snapshots can be created or deleted manually or automatically based on a schedule that is defined by a PowerStore protection policy.
- Special consideration of using BEGIN and END backup may be necessary before and after a snap is taken of pre 12c Oracle databases. For further information, see Oracle documentation.
PowerStore has three data recovery mechanisms that behave differently depending on the usage scenario.
- Thin clone: A thin clone takes an existing snapshot from a parent volume and creates a child volume from that point in time.
- Refresh: Using the refresh operation, snapshot data can replace existing data in the volume. The existing data is removed, and snapshot data from the new source is copied to it in place.
- Restore: The restore operation replaces the contents of a parent storage resource with data from an associated snapshot. Restoring resets the data in the parent storage resource to the point in time the snapshot was taken.