Creating a snapshot of a multi-volume database requires careful coordination to ensure data consistency across all volumes. The best practice in this scenario involves using a Consistency Group in conjunction with a Scheduler:
* Consistency Group: This is a collection of volumes that are treated as a single entity for snapshot purposes. When a snapshot is taken of a Consistency Group, it captures a point-in-time image of all volumes in the group simultaneously.This ensures that the snapshot reflects a consistent state across all volumes, which is crucial for databases that span multiple volumes1.
* Scheduler: The Scheduler is used to automate the snapshot process. By setting up a schedule, the systems administrator can ensure that the snapshot is taken at exactly 1:00 AM without manual intervention.The Scheduler will trigger the snapshot process at the specified time, using the settings defined for the Consistency Group1.
* Presenting to a Backup Server: Once the snapshot is created, it can be presented to a backup server.This server will see the snapshot as if it were the actual data, allowing for backup operations to be performed without impacting the production environment1.
* Snapshot Restore and Snapshot Set (OA): While these are components of snapshot operations, they do not provide the same level of coordination and automation as a Consistency Group with a Scheduler.
* Snapshot Set and the Scheduler (OB): A Snapshot Set is a collection of snapshots, but without the use of a Consistency Group, there is no guarantee that the snapshots will be consistent across all volumes.
* Consistency Group and Snapshot Refresh (OD): Snapshot Refresh is a process of updating a snapshot with changes from the source volumes. While useful in certain scenarios, it is not the initial step for creating and presenting snapshots to a backup server.