# Requirements and Considerations for SafeMode

Review the following requirements and considerations for SafeMode:

From firmware version 5.3.7 and later, Pure Storage has introduced an option called SafeMode snapshots. Commvault supports SafeMode snapshots. However, starting from version 5.6.16 to 6.3.3, array-wide safe mode is not supported. Additionally, it’s important not to enable safe mode configuration on Commvault created protection groups.

From firmware version 6.3.4 and later, SafeMode is supported. The following will be considered for Commvault created protection groups:

- When there is a target removal (change in the source array to target array mapping at the copy level), a new protection group will be created.

- When the Commvault-created protection group is ratcheted externally or array-wide SafeMode is enabled, if a volume is removed from subclient content, the next backup creates a new protection group when the snapshot configuration Behavior of SafeMode protection groups if subclient content is removed is set to Create a new protection group.

  For database workloads that protect separate data volumes and log volumes, Create a new protection group creates dedicated protection groups for data volumes and log volumes. These protection groups are reused for future backup operations.

- When the Commvault created protection group is ratcheted externally or array-wide SafeMode is enabled, if a volume is removed from subclient content, the next backup uses the existing protection group if the snapshot configuration Behavior of SafeMode protection groups if subclient content is removed is set to Use existing protection group.

  For database workloads that protect separate data volumes and log volumes, if you use Use existing protection group, volumes that were previously added to the protection group cannot be removed because of the immutable nature of SafeMode snapshots. As a result, additional snapshots can be created on one of the protection groups even when those snapshots are not required.

- Snapshots are indexed, retained, and aged correctly for both options.

- All volumes in the protection group will be snapped even though they are not part of the snapshot backup.

×

Loading...