NetBackup™ Snapshot Client Administrator's Guide
- Introduction
- Installation
- Policy configuration
- Notes on policies
- Configuring a policy
- Backup Selections tab options when configuring a policy
- Off-host backup configuration options
- Selecting the snapshot method
- Configuring backup scripts
- About using alternate client backup
- Configuring alternate client backup
- Policy configuration tips
- About disabling snapshots
- NAS snapshot configuration
- About NAS snapshot overview
- Dynamic data streaming for D-NAS workloads
- Prerequisites for NetBackup DNAS configuration
- Configuring dynamic data streaming with backup host pool
- Configuring a backup host pool
- Discover plugins
- Minimum supported backup host versions for different features
- Limitations and considerations
- Setting up a NAS-Data-Protection policy
- FlashBackup configuration
- Instant Recovery configuration
- About Instant Recovery capabilities
- Instant Recovery requirements
- Instant Recovery restrictions
- Giving full server privileges to the media server
- About Instant Recovery
- Configuring a policy for Instant Recovery
- About sizing the cache for Instant Recovery copy-on-write snapshots
- Instant Recovery for databases
- 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
- IBM DS6000 and DS8000 software requirements
- Preconfiguration for IBM arrays
- Configuring NetBackup to access the IBM DS6000 or DS8000 array
- Configuring the IBM array for NetBackup
- Using DSCLI commands to obtain unique IBM identifiers
- Configuring a NetBackup policy for IBM_DiskStorage_FlashCopy
- For further reference on IBM arrays
- About IBM DS4000 array
- About Hitachi SMS/WMS/AMS, USP/NSC, USP-V/VM
- Hitachi array software requirements
- Preconfiguration for Hitachi
- About communication between NetBackup and the Hitachi array
- Determining if the Hitachi command devices are visible
- About configuring the Hitachi array for NetBackup
- Obtaining the Hitachi array serial number and the unique device identifiers
- Configuring a NetBackup policy for Hitachi_ShadowImage or Hitachi_CopyOnWrite
- About HP-XP arrays
- HP-XP array software requirements
- Preconfiguration for HP-XP
- About communication between NetBackup and the HP-XP array
- Determining if the HP-XP command devices are visible
- About configuring the HP-XP array for NetBackup
- Obtaining the array serial number and unique HP-XP identifiers
- Configuring a NetBackup policy for HP_XP_BusinessCopy and HP_XP_Snapshot
- About array troubleshooting
- Notes on Media Server and Third-Party Copy methods
- Disk requirements for Media Server and Third-Party Copy methods
- Directives for Media Server and Third-Party Copy methods
- Storage units for Media Server and Third-Party Copy methods
- Preventing multiplexing on a third-party copy backup
- Raw partition backups
- Increasing the client read timeout for all clients
- Further information on off-host data mover backups
- Backup and restore procedures
- Snapshot management
- Troubleshooting
- About gathering information and checking logs
- Logging directories for UNIX platforms
- Logging folders for Windows platforms
- Customer support contact information
- Latest patches and updates
- Snapshot provider information
- Important notes on &newProductName;
- &newProductName; installation problems
- FlashBackup and status code 13
- Single file restore from a FlashBackup Instant Recovery snapshot of a file protected by Windows VSS writer fails
- Identifying and removing a left-over snapshot
- Removing a VxVM volume clone
- Alternate client restore and backup from a snapshot fails
- Restore from a snapshot fails with status 2800
- Raw Partition restore fails with the message 'FlashBackup-Windows policy restore error'
- Snapshot creation fails with error 156
- Snapshot fails with error 20
- Restore from a snapshot fails with status 133
- Backup from snapshot fails with error 50
- Backup from snapshot parent job fails with error 4213: Snapshot import failed
- Snapshot job fails and the snapshot command does not recognize the volume name
- Snapshot creation fails with error 4220
- Snapshot creation fails when the same volume is mounted on multiple mount points of the same host
- Snapshot-based backup and restore failure
- Multiple snapshot jobs fail with code 156 or 1541.
- FlashBackup policy fails, with multiple backup selections [Cache =]
- Partial backup failure with 'Snapshot encountered error 156'
- Backup of file system validation fails with error 223
- Policy validation fails if the specified CIFS share path contains a forward slash
- Policy validation fails with status code 223
- An NDMP snapshot policy for wildcard backup fails with error 4201
- Troubleshooting with bpfis log
- Limitations of using HP-UX 11.31
- While configuring a policy for snapshot operations, the NetBackup Administration Console hangs
- Accelerator enabled incremental backup of NetApp NAS volume
- Snapshot method: Auto
- Appendix A. Managing nbu_snap (Solaris)
- Appendix B. Overview of snapshot operations
- Index
NetBackup policy validation fails with Hitachi arrays
Note these possible explanations:
Table: NetBackup policy validation fails
Issue | Explanation/Recommended Action |
|---|---|
Look for the following error in the /usr/openv/netbackup/logs/bpfis/hitachi.log.<date> log: Library RMLIB init failed | Make sure that the RMLIB 64-bit library is installed. This requirement applies when you upgrade from a 6.5.x system (requires 32-bit RMLIB) to a 7.1 system, and when you install a fresh 7.1 system. |
The Hitachi command device is not unmasked. See the sample log messages in the next row. | Refer to Hitachi documentation for creating and unmasking command devices. |
The Hitachi command device is unmasked but is not visible to client, or the enclosure ID specified in the policy's Snapshot Resources is invalid. The /usr/openv/netbackup/logs/bpfis/hitachi.log.<date> log may contain messages similar to the following: Fri Mar 21 2008 16:26:46.431046 <Pid - 9477 / Thread id - 1> Entering Function delayedInit [110, providers/hitachi/hitachi_plugin.cpp] Fri Mar 21 2008 16:26:49.173893 <Pid - 9477 / Thread id - 1> <Device name="/dev/rdsk/c4t50060E801029F700d2s6" udid="UDID##HITACHI##HDS##75040816##3" bus="0" target="0" lun="0" vendor="HITACHI" product="DF600F-CM" /> Fri Mar 21 2008 16:26:49.174493 <Pid - 9477 / Thread id - 1> Exiting Function delayedInit [110, providers/hitachi/hitachi_plugin.cpp] If the delayedInit message does not include at least one entry for the enclosure ID that was entered in the policy's Snapshot Resources, the command device is not unmasked or is not visible to NetBackup client (host). | Make sure that the command device is recognized by the operating system and that the enclosure ID is entered correctly in the policy's Snapshot Resources. To determine if the command device is recognized by the operating system, try device discovery commands such as the following: devfsadm
cfgadm -alA log message for the enclosure ID would include an entry such as the following: c3t50060E801029F700d28 <HITACHI-DF600F-CM-0000 cyl 52 alt 2 hd 50 sec 768> which shows that the device is visible as c3t50060E801029F700d28. |
A mismatch exists between the policy's snapshot method and the type of LUNs specified for the Snapshot Devices. For example, if you select the Hitachi_ShadowImage method but specify snapshot LUNs instead of clone LUNs for the Snapshot Devices, an error occurs. See the sample log messages in the next bullet. | Specify the correct snapshot method or snapshot devices. |
A disk pair was not created for the source device and snapshot device specified in the NetBackup policy's Snapshot Resources. The /usr/openv/netbackup/logs/bpfis/hitachi.log.<date> log may contain messages similar to the following. If the snapshot method is Hitachi_CopyOnWrite: Fri Mar 21 2008 16:26:49.173893 <Pid - 9477 / Thread id - 1> HITACHI_FIM_SNAPSHOT not supported for 10 If the snapshot method is Hitachi_ShadowImage: Fri Mar 21 2008 16:26:49.173893 <Pid - 9477 / Thread id - 1> HITACHI_FIM_SHADOW_IMAGE not supported for 10 | Set up a disk pair (primary and secondary) for the source device and snapshot device that are specified in the policy's Snapshot Resources. Refer to the Hitachi documentation. |
In the policy's Snapshot Resources, the device identifier for the source device or snapshot device is invalid. The /usr/openv/netbackup/logs/bpfis/hitachi.log.<date> log may contain messages similar to the following: Fri Mar 21 2008 16:26:49.173893 <Pid - 9477 / Thread id - 1> getrminfo failed. Fri Mar 21 2008 16:26:49.173893 <Pid - 9477 / Thread id - 1> operation failed with error number <> with message <msg>'. The above message may indicate that a device ID in the policy's Snapshot Resources is incorrect or does not exist. For example, if the specified snapshot device ID does not exist: Mon May 12 2008 21:32:32.088876 <Pid - 8040 / Thread id - 1> getrminfo is called for '9999'. Mon May 12 2008 21:32:32.089736 <Pid - 8040 / Thread id - 1> getrminfo failed. Mon May 12 2008 21:32:32.090003 <Pid - 8040 / Thread id - 1> operation failed with error number '-1' with message '[EL_CMDRJE] An order of the control command rejected.'. | Recommended action: Make sure that the identifiers are correctly entered in the policy's Snapshot Resources. Specify source and snapshot IDs without leading zeros. See Configuring a NetBackup policy for Hitachi_ShadowImage or Hitachi_CopyOnWrite. |
The RAID Manager library libsvrrm.so software is not installed in the /usr/lib/ directory. | Recommended action: Install the RAID Manager package in /usr/lib/. See the Hitachi documentation. |
The installed version of RAID Manager library libsvrrm.so is not supported. | Recommended action: Look for the Library RMLIB version message in the /usr/openv/netbackup/logs/bpfis/hitachi.log.<date> log. |
More Information