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
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 -al A 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