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
Snapshot errors encountered with IBM4000 arrays (NetBackup status code 156)
The following table lists explanations and recommended actions for status code 156.
Table: Explanations and recommended actions for status code 156
Problem | Description and recommended action for status code 156 |
|---|---|
The array does not have enough free space. | FlashCopy logical drives are created under the same logical array as is the base or primary logical drive. The storage subsystem might have free space, but if the logical array has insufficient space, the FlashCopy operation fails. The following messages may appear in the /usr/openv/netbackup/logs/bpfis log: 23:44:48.007 [655588] <2> onlfi_vfms_logf: INF - snapshot services: ibmdsfi:Wed Mar 12 2008 23:44:48.007721 <Thread id - 1> FlashCopy could not be created. command [create FlashCopyLogicalDrive baseLogicalDrive="angela_javelin_4" userLabel="angela_javelin_4_flcp_4";].23:44:48.012 [655588] <2> onlfi_vfms_logf: INF - snapshot services: ibmdsfi: FlashCopy creation failed for source volume angela_javelin_4 on storage unit ibmds4700. In addition, the following messages may appear in /usr/openv/netbackup/logs/bpfis/ibmdsfi.log.date: Mon Mar 31 2008 14:25:23.036588 <Pid - 1065104 / Thread id - 1> FlashCopy could not be created. command [create FlashCopyLogicalDrive baseLogicalDrive="drive-claix11-1" userLabel="drive-claix11-1_flcp";]. Mon Mar 31 2008 14:25:23.037164 <Pid - 1065104 / Thread id - 1> OUTPUT=[Unable to create logical drive "drive-claix11-1_flcp" using the Create FlashCopy Logical Drive command at line 1. Error - The operation cannot complete because there is not enough space on the array. The command at line 1 that caused the error is: create FlashCopyLogicalDrive baseLogicalDrive="drive-claix11-1" userLabel="drive-claix11-1_flcp"; Recommended action: Make sure that the array has enough space available for the snapshot. |
The maximum number of FlashCopies (4) already exist on the array. | The following messages may appear in /usr/openv/netbackup/logs/bpfis/ibmdsfi.log.date: Mon Mar 31 2008 14:25:23.036588 <Pid - 1065104 / Thread id - 1> FlashCopy could not be created. command [create FlashCopyLogicalDrive baseLogicalDrive="drive-claix11-1" userLabel="drive-claix11-1_flcp";]. Mon Mar 31 2008 14:25:23.037164 <Pid - 1065104 / Thread id - 1> OUTPUT=[Could not create a flashcopy logical drive using the Create FlashCopyLogicalDrive command at line 1. Error 129 - The operation cannot complete because the maximum number of flashcopy logical drives have been created for this base logical drive. Recommended action: Delete any FlashCopies that NetBackup did not create. |
The Access Logical Drive is not mapped for the NetBackup client or alternate client at LUN 31 or 7. | On the IBM DS4000, the Access Logical Drive communicates with the storage subsystem. Any client that is connected to and needs to communicate with the storage subsystem should have an Access Logical Drive mapped to it. If an Access Logical Drive is not mapped to the client, the client is unable to communicate with the array. As a result, any NetBackup client operation involving the array fails. Recommended action: Create and map an Access Logical Drive. Contact IBM technical support or refer to your IBM array documentation. |
The DAR driver is not functional. | Recommended action: Make sure that the RDAC package is installed on the AIX host. |
More Information