Veritas NetBackup™ Snapshot Client Administrator's Guide
- Introduction
- Snapshot Client features
- About snapshot basics
- Off-host backup overview
- Off-host backup methods
- Snapshot Client requirements
- Installation
- Policy configuration
- Selecting the snapshot method
- Configuration parameters for Snapshot Client
- About using alternate client backup
- Configuring alternate client backup
- Policy configuration tips
- About disabling snapshots
- FlashBackup configuration
- Instant Recovery configuration
- About Instant Recovery
- About sizing the cache for Instant Recovery copy-on-write snapshots
- About configuring VxVM
- About storage lifecycle policies for snapshots
- Network Attached Storage (NAS) snapshot configuration
- Configuration of software-based snapshot methods
- Support for Cluster Volume Manager Environments (CVM)
- Configuration of snapshot methods for disk arrays
- About the new disk array snapshot methods
- Disk array configuration tasks
- OS-specific configuration tasks
- About VSS configuration (Windows)
- About EMC CLARiiON arrays
- Configuring NetBackup to access the CLARiiON array
- Configuring a NetBackup policy for a CLARiiON array method
- About EMC Symmetrix arrays
- About configuration for EMC_TimeFinder_Mirror
- About configuration for EMC_TimeFinder_Clone
- About HP EVA arrays
- Verifying connectivity from clients to array using SSSU 5.0
- About IBM DS6000 and DS8000 arrays
- Configuring NetBackup to access the IBM DS6000 or DS8000 array
- About IBM DS4000 array
- About Hitachi SMS/WMS/AMS, USP/NSC, USP-V/VM
- Hitachi array software requirements
- About HP-XP arrays
- About array troubleshooting
- Notes on Media Server and Third-Party Copy methods
- Backup and restore procedures
- About restores from a FlashBackup backup
- Instant Recovery restore features
- About configurations for restore
- About restoring from a disk snapshot
- Troubleshooting
- Logging directories for UNIX platforms
- Logging folders for Windows platforms
- FlashBackup and status code 13
- Appendix A. Managing nbu_snap (Solaris)
- Appendix B. Overview of snapshot operations
- Appendix C. NetBackup integration with CloudPoint for snapshot managment
Troubleshooting NetBackup and EMC Symmetrix arrays
Note the following issues:
Table: Issues with NetBackup and EMC Symmetrix arrays
Issue | Explanation/Recommended Action |
---|---|
Point in time rollback fails and the following message appears in the Invalid clone state, cannot restore from device-ID to device-ID, where the first device ID is the source and the second is the clone. | See Verifying that the clone is complete before doing a point in time rollback. |
If all Save Device space is consumed on the Symmetrix, a backup with EMC_TimeFinder_Snap or EMC_ TimeFinder_Clone fails with the following error in the bpfis log: An internal Snap or Clone error has occurred. Please see the symapi log file | Check the symapi log (often found at /var/symapi/log on UNIX) to determine the exact error. If the log indicates there is no Save Device space, add Save Devices to the Save Device pool on your Symmetrix array. |
EMC_TimeFinder_Mirror backups fail and the following message appears in the bpfis log: emcsymfi: Invalid STD-BCV pair state | This message indicates that the STD-BCV pair is not in a state that allows the mirror to be created. Verify that the pair were fully synchronized before the backup attempt. |
TimeFinder backups fail and a message similar to the following appears in the bpfis log: device 00A4 to director/port that is not accessible to the HBA port 210000e08b86b34f emcsymfi: 2 of 2 HBA WWNs assigned to director/port combinations for accessing device 00A4 are not accessible due to misconfiguration of the array. emcsymfi: Since there were no valid mappings the device import will fail. To resolve this issue you must reconfigure your array 000187910258 to bind device 00A4 to director ports accessible to host. | Device 00A4 has not been mapped to any Symmetrix director ports that are zoned to the host. All Symmetrix devices (source devices and target devices) must be mapped to an array director port that is zoned to the import host. For a local backup policy, the import host is the host where the source device is mounted. For an off-host backup policy, the import host is the alternate client. |
More Information