- Notes, cautions, and warnings
- Preface
- Overview of NetWorker Snapshot Features
- Data Protection Policies
- Default data protection policies in NMC's NetWorker Administration window
- Strategies for storage array snapshot backups
- Overview of configuring a new data protection policy
- Creating a policy
- Create a workflow for a new policy in NetWorker Administration
- Protection groups for snapshot backups
- Actions supported in snapshot backups
- Supported actions in snapshot workflows
- Visual representation of snapshot workflows
- Software Configuration
- Backup group resource migration
- Roadmap for snapshot configurations
- Snapshot configuration prerequisites
- Configuring the user privileges
- Configuring snapshot backups with the client wizard
- Configuring snapshot backups manually
- Configuring the Application Information variables
- Configuring preprocessing and postprocessing scripts
- Configuring ProtectPoint on VMAX
- Overview
- ProtectPoint on VMAX3 prerequisites
- Enabling vDisk on a Data Domain system
- Provisioning protection devices on Data Domain systems
- Completing the VMAX system configuration
- Considerations for ProtectPoint device and NetWorker ProtectPoint enabled pools
- Configuring NetWorker ProtectPoint, RecoverPoint and VMAX devices and pool with the wizard
- VMAX3 SRDF/S support
- Configuring Data Domain NsrSnapSG device groups for intelligent pairing
- Configuring ProtectPoint on RecoverPoint with XtremIO
- Overview
- Basic backup workflow
- Basic restore workflow
- ProtectPoint for RecoverPoint on XtremIO prerequisites
- Enabling vdisk on the Data Domain
- Provisioning protection devices on Data Domain systems
- Configuring RecoverPoint and XtremIO storage
- Configuring NetWorker ProtectPoint, RecoverPoint and VMAX devices and pool with the wizard
- Configuration for restore to secondary VMAX with the wizard
- Considerations for ProtectPoint device and NetWorker ProtectPoint enabled pools
- Configuring Data Domain NsrSnapSG device groups for intelligent pairing
- Configuring snapshots on XtremIO arrays
- Configuring snapshots on PowerStore arrays
- Configuring snapshots on VMAX Storage Arrays
- Configuring snapshots on VNX Block Storage Arrays
- Configuring snapshots on RecoverPoint
- Configuring snapshots in a Cluster Environment
- Data Management and Recovery
- Snapshot lifecycle management
- Management and recovery of file system snapshot data
- Snapshot recovery support and limitations
- Restoring from a snapshot with the Recovery Wizard
- Restoring a snapshot by rollback
- Troubleshooting
- Snapshot backup on Unity fails
- NAS Isilon snapshot mount fails on Linux
- Backup on Windows fails with a Delayed Write Failed error
- Backup fails and hangs when NMC user has insufficient privileges
- Snapshots fail to mount for AIX managed file systems
- Snapshots fail for Linux Volume Manager on VNX with PowerPath
- Linux Logical Volume Manager snapshots fail with an error
- NetWorker to Media-Clone stops responding and the backup fails
- File-by-file or saveset restore fails
- Restore of raw devices fails on Linux with permission issue
- Command nsrsnap_recover -I runs but fails to restore a file
- Restore fails with disk signature error
- Directed restore files and folder permission issue
- Snapshot mount might fail because VMAX does not release the lock on Restore FTS LUN
- NSM with XtremIO leaves snapshots mounted
- Application Information Variables
- Command-Line Operations for Snapshot Management
- Migrating Legacy PowerSnap Configurations
NetWorker 19.7 Snapshot Management Integration Guide
Intelligent Pairing allocates vDisk for mount, validate, and restore
When over subscribing the vDisk devices to multiple hosts a vDisk is locked once Intelligent Pairing has selected it. This locking prevents the device to allocate to a concurrent mount/validation or restore operations. The lock is released to the pool for subsequent operations.
Locking of vDisk LUN for restore/mount operations is done by adding a specific key-value metadata key to the vDisk. Intelligent pairing inspects the vDisk for the presence of the key-value pair and if absent considers the vDisk "available." It removes the key at the end of the operation.
Both the Data Domain pool and disk group that is used by IP can optionally be specified using client resource attributes. These must be typed manually into the client resource at the end of client configuration:
- NSR_DD_VDISK_RESTORE_POOLNAME=<dd vdisk restore pool>
- NSR_DD_VDISK_RESTORE_DEVGRPNAME=<dd vdisk restore devgrp>
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: <>()\