Please enter search query.
Search <book_title>...
NetBackup™ Snapshot Client Administrator's Guide
Last Published:
2022-05-23
Product(s):
NetBackup & Alta Data Protection (10.0)
- Introduction
- Installation
- Policy configuration
- Selecting the snapshot method
- About using alternate client backup
- Configuring alternate client backup
- Policy configuration tips
- About disabling snapshots
- NAS snapshot configuration
- Dynamic data streaming for D-NAS workloads
- Setting up a NAS-Data-Protection policy
- FlashBackup configuration
- Instant Recovery configuration
- About Instant Recovery
- About sizing the cache for Instant Recovery copy-on-write snapshots
- About storage lifecycle policies for snapshots
- Configuration of software-based snapshot methods
- Support for Cluster Volume Manager Environments (CVM)
- Configuration of snapshot methods for disk arrays
- OS-specific configuration tasks
- 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
- Snapshot management
- 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
Backup from snapshot parent job fails with error 4213: Snapshot import failed
Job details shows an error like:
"Snapshot export failed. Failed to export share: data_lif is not online. Please check data_lif status on vserver: VSERVER_1."
where, VSERVER_1 is the vserver that is offline.
For a NAS-Data-Protection policy, all the vservers are listed in the client's section of the policy, irrespective of their state. So, you are able to include backup selection from offline SVM, and policy validation succeeds. However, at the time of backup-from-snapshot, export operation for those shares fails if the corresponding vserver is offline.
To overcome this error, check the status of the vserver and whether that vserver is reachable. Whenever client and vserver connection is established, SLP retry is successful.