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
About NetBackup and CloudPoint integration for snapshot management
NetBackup interfaces with snapshot management servers to manage arrays for discovery of devices and snapshot lifecycle management. Snapshot management severs are installed separately apart from NetBackup and they have plugins for various storage arrays. Veritas CloudPoint (TM) is an example of a snapshot management server for NetBackup. Using the NetBackup Snapshot management framework, you can use CloudPoint for taking snapshots of your images. You can protect all the on-premises storage arrays that are supported by CloudPoint.
The following table describes the underlying tasks.
Table: Tasks for snapshot management
Task | Description |
|---|---|
Configure the CloudPoint server in NetBackup. | You can configure the CloudPoint server as a snapshot management server. To configure the CloudPoint server in NetBackup you need to add the credentials of the CloudPoint server. |
Configure the CloudPoint plug-ins in NetBackup. | The CloudPoint plug-ins that are installed on the CloudPoint server must be registered and configured in NetBackup with the associated CloudPoint server. |
Configure a Standard policy to use VSO snapshot method. | See Configuring a policy. |
Backup and restore procedures |
Consider the following when integrating NetBackup with CloudPoint:
Deletion of CloudPoint host entry and its associated plug-ins is not supported in NetBackup.
Using CloudPoint, if you delete plug-ins that are configured in NetBackup, the images of snapshots that are taken using CloudPoint will be unusable.
Back up from snapshot and index from snapshot is supported. Replication operations are not supported.
For snapshot and index for snapshot, you can use any available storage unit.
Post integration, all the related operations must be performed from NetBackup. Results of operations that are performed outside NetBackup, will not be visible in NetBackup. CloudPoint has its own RBAC, where NetBackup is one of the users and operations performed only through NetBackup will be visible in NetBackup. For example, even though you can add CloudPoint plug-in from CloudPoint, you must add the plug-in from NetBackup, or the plug-in may not be visible in NetBackup.
HP-UX Native volume group Version 2.0 and later is not supported.
Raw device and raw partitions are not supported.
File system verification is not supported. You must skip the verification step and perform a force rollback. In the Restore Marked Files dialog box, select the check box.
Consider all the CloudPoint limitations.
Refer to the Veritas CloudPoint Installation and Upgrade Guide.
NetBackup integration is not supported with the CloudPoint freemium version.
It is recommended not to reinstall the CloudPoint server but to upgrade it. However, if you reinstall the CloudPoint server you need to reconfigure the CloudPoint server and the associated CloudPoint plug-ins.
Perform the following tasks for RHEL:
In the recent RHEL version, there are changes in usage of partition delimiter. Based on last character in the device path, OS decides if partition delimiter must be added or not. To address the change, update the udev rule to add partition delimiter 'p' on RHEL
Open the
/lib/udev/rules.d/62-multipath.rulesfile.Update the existing line:
RUN+="$env{MPATH_SBIN_PATH}/kpartx -an $tempnode", \ ENV{DM_MULTIPATH_NEED_KPARTX}=""To
RUN+="$env{MPATH_SBIN_PATH}/kpartx -an -p p $tempnode", \ ENV{DM_MULTIPATH_NEED_KPARTX}=""Restart the multipath service. Run the following command:
# service multipathd restart
For devices in LVM, if multiple paths are used, ensure that multipathing service is enabled.
On SUSE Linux, ensure that the automount service is disabled.
Junction mount point on filler or array is not supported for snapshot operations with VSO FIM snapshot method.
For client-side nested mount points, rollback of parent mount points is not supported.