- Notes, cautions, and warnings
- Preface
- PowerProtect Data Manager for Storage Arrays Overview
- Managing Assets and Protection
- About asset sources, assets, and storage
- Enable the storage array asset source
- Add a storage array
- Edit a storage array asset source
- Delete a storage array asset source
- Protection policies for block volume protection
- Supported protection policy purposes
- Supported protection policy objectives
- Replication triggers
- Roadmap for planning a protection policy
- Before you add a protection policy for block volume protection
- Add a protection policy for block volume protection
- Change the password of the new target storage user (PowerStore block volume type policy only)
- Create a manual snapshot
- Protection rules
- Restoring block volume data
- Restore a block volume using Instant Access
- Troubleshooting
- Glossary
PowerProtect Data Manager 19.16 Storage Array User Guide
Protection policy best practices
Before you create a protection policy, note the following best practices:
- The maximum number of remote systems that you can connect to a PowerStore storage array differs between different PowerStore models. It is recommended that you reuse the storage units created in other protection policies for block volume protection. The PowerStore documentation provides more information.
- In the Protection Policies window, you can export protection policy data by using the Export All functionality.
Understanding backup terminology and managing backup frequency
When scheduling backups in a protection policy, be aware of the following:
- Different protection-policy types can use different terminology to describe available backup levels. This terminology can differ not only between protection-policy types, but also from traditional terminology.
- To avoid high CPU usage that can lead to failure issues, do not schedule backups more often than recommended.
To understand the different backup levels to manage backup frequencies, see the following table.
| Protection-policy types | Available backup levels | Description | Equivalent traditional terminology | Recommended minimum backup interval |
|---|---|---|---|---|
| Block Volume | Synthetic Full | Backs up only the blocks that have changed since the last synthetic-full or full backup, and then performs an operation to merge those changes with the last synthetic-full or full backup in order to produce a full backup in storage. Only the changed blocks are copied over the network, but the result is still a full backup in storage. | An incremental backup is performed, followed by a merge operation that produces a full backup in storage. | 6 hours |
| Snapshot | Saves the state of the volume or volume group and all files and data within it at a particular point in time. Snapshots provide a method of recovery for data that has been corrupted or accidentally deleted. You can use snapshots to restore the volume or volume group to a previous state. | 15 minutes |
You can increase the backup frequency of a protection policy by scheduling more synthetic-full backups with different retention times to meet your requirements.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\