Protection Group Requirements (Both Workflows)

Oracle
Audience
Public
Technology Integrations
Oracle
Source Type
Documentation

  • The Protection Group must contain every Everpure FlashArray volume that backs this database's ASM disk groups.

  • Never snapshot individual volumes separately — doing so creates write-order inconsistency risk.

  • Pre-stage Protection Group membership before the maintenance window.

  • Every ASM disk in each protected database disk group must map to a volume in the same Protection Group.

  • Do not add the Grid Infrastructure clusterware volumes (OCR / voting — GRID, CRS, or +OCR) to this Protection Group. The clusterware disk group is not part of the database snapshot and is rebuilt or restored through normal Grid Infrastructure procedures.

  • A Protection Group cannot span multiple arrays. If the database spans arrays, use one Protection Group per array and the application-consistent workflow.

Snapshot Naming Convention

Use a consistent format that encodes environment, database, snapshot type, UTC timestamp, and change ticket: 

<environment>-<db_unique_name>-<snapshot_type>-<timestamp>-<change_id>
 # Example
prod-ORCL-appcons-20260316-153000Z-CHG12345