Veritas NetBackup Snapshot Client Administrator's Guide
- Introduction
- Snapshot Client features at a glance
- Snapshot Client features
- About snapshot basics
- Benefits of copy-on-write versus mirror
- About local backup of a snapshot
- Off-host backup overview
- Off-host backup methods
- Snapshot Client requirements
- Snapshot Client terminology
- Snapshot Client assistance
- About open file backups for Windows
- Installation
- Policy configuration
- Notes on Snapshot Client policies
- Configuring a Snapshot Client policy
- Backup Selections tab options when configuring a policy
- Off-host backup configuration options
- Automatic snapshot selection
- Selecting the snapshot method
- Snapshot methods
- Configuration parameters for Snapshot Client
- Cache device path parameter
- Delay in seconds between disk group split retries parameter
- IBC receive timeout parameter (seconds)
- IBC send timeout parameter (seconds)
- Keep snapshot after backup parameter
- Maximum number of volumes to resynchronize concurrently parameter
- Maximum Snapshots parameter (Instant Recovery only)
- Number of times to retry disk group split parameter
- Provider Type parameter
- Resynchronize mirror in background parameter
- Snapshot Attribute parameter
- Sync I/O delay in milliseconds parameter (UNIX only)
- Sync region size in MB parameter (UNIX only)
- Wait for mirror sync completion parameter
- Important note on VSS and disk arrays
- Synchronize mirror before the backup parameter
- Snapshot Resources
- Configuring backup scripts
- About using alternate client backup
- Configuring alternate client backup
- Policy configuration tips
- About disabling snapshots
- 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
- About configuring VxVM
- Modifying the VxVM or FlashSnap resync options for point in time rollback
- Instant Recovery for databases
- 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
- EMC CLARiiON software requirements for UNIX
- Veritas support for VSS Snapshot and EMC CLARiiON
- Diagram of installed software for EMC CLARiiON
- Verifying connectivity from client to array
- About resolving host names on the network
- Configuring NetBackup to access the CLARiiON array
- Adding clients to a CLARiiON storage group
- Configuring for EMC_CLARiiON_SnapView_Clone
- Creating a clone private LUN with the EMC Navisphere Web interface
- Creating a clone group and select a LUN as source
- Adding clone LUNs to the clone group
- Obtaining the device identifier for each source and clone LUN
- About configuration for EMC_CLARiiON_SnapView_Snapshot
- Configuring a reserved LUN pool for the storage processors
- Configuring a NetBackup policy for a CLARiiON array method
- Common CLARiiON array configuration problems
- About EMC Symmetrix arrays
- EMC Symmetrix DMX software requirements
- Clone emulation flag can cause snapshots to fail
- EMC snapshot operation fails
- Support for EMC Symmetrix with Volume Shadow Copy Service
- Prerequisites for using EMC Symmetrix disk arrays
- Configuring NetBackup clients to use EMC Symmetrix
- About configuring NetBackup to access the Symmetrix array
- About configuration for EMC_TimeFinder_Mirror
- About configuration for EMC_TimeFinder_Clone
- About configuration for EMC_TimeFinder_Snap
- Configuring a policy for EMC_TimeFinder methods
- About HP EVA arrays
- Prerequisites for working with HP EVA arrays
- HP EVA software requirements for UNIX
- Diagram of installed software for HP EVA
- Veritas support for VSS Snapshot and HP EVA
- Verifying connectivity from clients to array using SSSU 5.0
- Configuring NetBackup to access the EVA array
- Configuring a NetBackup policy for an HP EVA array method
- HP EVA restrictions
- 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
- About performing a backup
- About performing a restore
- About restores from a FlashBackup backup
- Restoring a large number of files in a clustered file system (VxFS on UNIX Only)
- Instant Recovery restore features
- Notes for restoring individual files from an Instant Recovery snapshot
- About configurations for restore
- About restoring from a disk snapshot
- 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 Snapshot Client
- Snapshot Client 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
- 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
- An NDMP snapshot policy for wildcard backup fails with error 4201
- Troubleshooting with bpfis log
- Limitations of using HP-UX 11.31
- Appendix A. Managing nbu_snap (Solaris)
- Appendix B. Overview of snapshot operations
- Appendix C. NetBackup integration with CloudPoint for snapshot managment
About Solaris sd.conf file
The /kernel/drv/sd.conf file must have sufficient entries to allow for the dynamic import of snapshot devices. Snapshot devices are created when the backup starts, and must be made visible on the NetBackup client without restarting the operating system. Entries should be added to the sd.conf file for the persistent target numbers that were configured for the HBA.
Note:
The sd.conf file does not have to be modified if you use Leadville drivers.
Veritas recommends that you add LUNs 0-15 for all disk array targets on which snapshots are to be created. This creates 16 host-side LUNs on each target that can be used for importing the snapshots (clones, mirrors, and copy-on-write snapshots) required for backups. If 16 host-side LUNs are not enough for a particular disk array target, add more LUNs for that target. Note that snapshots are imported to a NetBackup client in sequential order starting with the lowest unused host-side LUN number. The host-side LUN number pool is managed on the disk array. The disk array cannot determine which host-side LUN numbers have been configured in sd.conf. The array can only determine which host-side LUN number it has not yet assigned to the host. If the array adds a device at a host-side LUN number that has not been configured in sd.conf, that device is not visible on the host. Also, if alternate client backups are being used, be sure to properly configure sd.conf on the alternate client.
You must restart after modifying sd.conf.
Symmetrix arrays pre-assign host-side LUN numbers (that is, the LUN numbers are not set at the time the device is imported). These pre-selected LUN numbers must be entered into sd.conf for the Symmetrix target number.
Note:
If you use EMC Control Center interface (ECC) to determine Symmetrix host-side LUN numbers, note that ECC shows host-side LUN numbers in hexadecimal format. Since the LUN entries in sd.conf must be in decimal format, convert the hexadecimal value to decimal before adding it to sd.conf.
If the Symmetrix array was persistently bound at target 5, and the host-side LUN numbers of the Symmetrix devices are 65, 66, 67, then the following entries should be added to sd.conf.
name="sd" class="scsi" target=5 lun=65;
name="sd" class="scsi" target=5 lun=66;
name="sd" class="scsi" target=5 lun=67;