- Notes, cautions, and warnings
- Introduction
- Revision history
- Initial configuration and setup
- Performing common tasks
- Displaying system information at a glance
- Managing block storage
- Protection domains
- Fault sets
- Storage data servers
- Storage pools
- Acceleration pools
- Devices
- Volumes
- NVMe targets
- Hosts
- Managing file storage
- Overview of configuring NAS servers
- About file system storage
- File protection
- Create a protection policy
- Create snapshot rules
- Create a snapshot
- Assign a protection policy to a file system
- Unassign a protection policy
- Modify a protection policy
- Delete a protection policy
- Modify a snapshot rule
- Delete a snapshot rule
- Refresh a file system using snapshot
- Restore a file system from a snapshot
- Protecting a block storage environment
- Snapshots
- Create snapshots
- Overwrite volume content from a snapshot
- Set bandwidth and IOPS limits for snapshots
- Lock and unlock snapshots
- Delete snapshots
- Map snapshots
- Unmap snapshots
- Increase the size of a snapshot
- Migrate a snapshot vTree
- Pause snapshot vTree migration
- Roll back snapshot vTree migration
- Set snapshot vTree migration priority
- Snapshot policies
- Remote protection
- Extract and upload certificates
- Journal capacity
- Add a peer system
- Restart the replication cluster
- SDRs
- Replication consistency group
- Replication direction and mapping
- Create an RCG
- Map RCG target volumes to hosts
- Unmap a host from RCG target volumes
- Set the target to inconsistent mode
- Set the target to consistent mode
- Modify RPO
- Add a replication pair to an RCG
- Pause replication for an RCG
- Resume replication for an RCG
- Create a snapshot of an RCG volume
- Add an RCG snapshot policy
- Perform a failover
- Reverse replication
- Restore replication
- Test Failover
- Stop a failover test
- Freeze an RCG
- Unfreeze an RCG
- Activate an RCG
- Terminate replication in an RCG
- Delete an RCG
- Pause creation of an initial copy
- Resume creation of initial copy
- Set copying priority
- Unpair from RCG
- Snapshots
- Performing lifecycle operations for a resource group
- Deploying a resource configuration in a resource group
- Basic tasks
- Deploying a resource group
- Adding an existing resource group
- Updating a resource group with new firmware and software
- Viewing a compliance report
- Entering and exiting service mode
- Replacing a drive
- Replacing NVDIMM node or battery
- Reconfiguring MDM roles
- Migrating vCLS VMs to shared storage
- Adding components to a resource group
- Resize a volume
- Removing resources from a resource group
- Adding NVMe/TCP storage access
- Additional resource group management tasks
- Basic tasks
- Preparing a template for a resource group deployment
- Basic tasks
- Additional template management tasks
- Deploying a resource configuration in a resource group
- Managing resources
- Basic tasks
- Additional resource management tasks
- Monitoring events and alerts
- Configuring system settings
- User management
- Repositories
- Getting started
- Networking
- Events and alerts
- License management
- Security
- Serviceability
- Software upgrade
- PowerFlex Manager user interface reference
- Additional administration activities
- Retrieving logs for the PowerFlex nodes
- Retrieving logs for PowerFlex components
- Retrieving additional PowerFlex logs
- Enabling audit logging
- Managing storage devices using CloudLink
- Understanding NVMe over TCP load balancing
- Managing NAS server configuration
- Migrating to NVMe/TCP on ESXi
Dell PowerFlex 4.5.x Administration Guide
Snapshot policies
Snapshot policies enable you to define policies for the number of snapshots that PowerFlex takes of one or more defined volumes at a given time.
Snapshots are taken according to the defined rules. You can define the time interval between two rounds of snapshots, as well as the number of snapshots to retain, in a multi-level structure. For example, take snapshots every x minutes/hours/days/weeks. You can define a maximum of six levels, with the first level having the most frequent snapshots.
For example:
Rule: Take snapshots every 60 minutes
Retention Levels:
- 24 snapshots
- 7 snapshots
- 4 snapshots
After defining the parameters, select the source volume to add to the snapshot policy. You can add multiple source volumes to a snapshot policy, but only a single policy per source volume is allowed. Only one volume per vTree may be used as a source volume of a policy (any policy).
When you remove the source volume from the policy, you must choose how to handle snapshots. Snapshots created by the policy are referred to as auto snapshots. This is indicated if a snapshot policy is displayed for the snapshot.
- If the source volume has auto snapshots, you cannot unassign the source volume from the snapshot policy. You can remove auto snapshots from Snapshots.
- If the source volume has auto snapshots but none of them are locked, you are prompted to confirm that you would like to delete all auto snapshots. If any of the auto snapshots are locked, the locked auto snapshots are just detached from the snapshot policy, but not deleted. You can manually delete auto snapshots. It doesn't matter if the auto snapshot is locked or not, you can still delete.
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: <>()\