- Notes, cautions, and warnings
- Preface
- PowerProtect Data Manager for Storage Direct Agent Overview
- Enabling the Storage Direct Agent for VMAX Systems
- Managing Storage, Assets, and Protection
- About asset sources, assets, and storage
- Add protection storage
- Manage the Storage Direct agent
- Enable an asset source
- Add and discover the SMIS server for the Storage Direct agent
- Replication triggers
- Add a self-service protection policy for Storage Direct
- Add a centralized protection policy for Storage Direct
- Add a service-level agreement
- Extended retention
- Add assets to an existing storage group protection policy
- Remove assets from an existing storage group protection policy
- Edit the retention period for backup copies
- Delete backup copies
- Restoring a Storage Direct VMAX storage group
- Restore backup copies from replication DD when source Storage Direct agent host, PowerProtect Data Manager server, and VMAX are unavailable
- Manage the PowerProtect agent service
- About the PowerProtect agent service
- Start, stop, or obtain the status of the PowerProtect agent service
- Troubleshooting PowerProtect agent service installations
- Troubleshooting PowerProtect agent service operations
- Register the PowerProtect agent service to a different server address on Windows
- Recovering the PowerProtect agent service from a disaster
- Storage Direct Best Practices and Troubleshooting
- Storage Direct agent limitations
- Troubleshooting agent registration
- Troubleshooting PowerProtect agent service installations
- Troubleshooting PowerProtect agent service operations
- Troubleshooting PowerProtect Data Manager UI display of localhost.localdomain hostname
- Troubleshooting when protection policies cannot be created from an imported configuration file that uses VMAX
- Troubleshooting when protection policies cannot be created from an imported configuration file that uses replication
- Troubleshooting initiation of SMIS server discovery job
- Troubleshooting SDFSA install/update failure when using absolute path
- Troubleshooting when encapsulation fails during policy creation
- Troubleshooting when restart of encapsulation fails
- Troubleshooting when encapsulation fails with error "SYMAPI_C_NET_HANDSHAKE_FAILED"
- Troubleshooting failure of configuration file validation
- Troubleshooting failure of MTree replication
- Troubleshooting replication for assets already configured for a stand-alone agent
- Troubleshooting creation of new snapshot after restart of failed backup
- Troubleshooting a configuration file that is generated by PowerProtect Data Manager and imported during an agent update
- Troubleshooting storage policy backup failure and PowerProtect config validation error
PowerProtect Data Manager 19.11 Storage Direct User Guide
Troubleshooting creation of new snapshot after restart of failed backup
Storage Direct agent creates a new snapshot when restarting failed backup jobs in PowerProtect Data Manager
If a backup fails and you restart the backup job, the Storage Direct agent creates a new snapshot and does not reuse the snapshot that was created during the failed backup. This is expected behavior, and the latest snapshot is used for the new backup.
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: <>()\