• For a complete list of supported platforms, snapshot methods, data types, and database agents, and supported combinations of platform and snapshot methods, see NetBackup 7.x Snapshot Client Compatibility:

  http://www.netbackup.com/compatibility

• Further information is also available.

Note the following restrictions:

• Snapshot Client does not support the ALL_LOCAL_DRIVES entry in the policy's Backup Selections list.

• The VxFS_Checkpoint and VxVM snapshot methods support VxFS multi-volume file systems only.

• For the NetBackup media server or Third-Party Copy Device methods, the client disk must be either a SCSI or Fibre Channel device.

• For off-host backup that uses a data mover with the nbu_snap, VxFS_Checkpoint, or VxVM snapshot methods: The NetBackup media server must have access to all the disks that make up the snapshot. The disk(s) can be connected to a SAN. For each of these snapshot methods, note the following:

  • nbu_snap: Media server requires access to the active disk and the cache disk.

  • VxFS_Checkpoint: Media server requires access to the primary or an active disk.

  • VxVM: Access requirements depend on layout of the volume group. Media server must be able to access all disks that make up the SnapMirror volume.

• Backup of an AIX 64-bit client with the NetBackup media server (data mover) method and the VxVM or VxFS_Checkpoint snapshot method may fail with NetBackup status code 11. This failure may occur if the client volumes are configured with Storage Foundation 5.0 MP3. A NetBackup message similar to the following appears in the job's Detailed Status tab:

  12/09/2010 23:23:23 - Error bpbrm (pid=458874) from
  client p5201: ERR - bp_map_open, err 2059

  This error occurs because the required VxVM libraries for 64-bit AIX are not installed in the correct location. The libraries should be installed in /opt/VRTSvxms/lib/map/aix64/.

  cp /usr/lpp/VRTSvxvm/VRTSvxvm/5.0.3.0/inst_root/
  opt/VRTSvxms/lib/map/aix64/* /opt/VRTSvxms/lib/map/aix64/ 

  Note:

  This issue is fixed in Storage Foundation versions starting with 5.0MP3RP3, 5.1RP1, and 5.1SP1.

• For off-host backups that use the NDMP data mover option to replicate snapshots, see the NetBackup Replication Director Solutions Guide for a list of limitations.

• In a clustered environment, Instant Recovery point-in-time rollback is not supported for the backups that were made with a disk array snapshot method. The disk array snapshot methods are described in the chapter titled Configuration of snapshot methods for disk arrays.

  See About the new disk array snapshot methods.

• For the TimeFinder, ShadowImage, or BusinessCopy legacy snapshot methods (when you use the NetBackup media server or Third-Party Copy Device backup methods): The NetBackup clients must have access to the mirror (secondary) disk containing the snapshot of the client's data. The NetBackup clients must also be able to access the primary disk. The NetBackup media server only needs access to the mirror (secondary) disk.

• For the TimeFinder, ShadowImage, or BusinessCopy legacy snapshot methods, a Volume Manager disk group must consist of disks from the same vendor.

• The NetBackup media server off-host backup method does not support the clients that use client deduplication. If the client is enabled for deduplication, you must select Disable client-side deduplication on the policy Attributes tab.

• For the NetBackup media server or Third-Party Copy Device backup method: The disk must return its SCSI serial number in response to a serial-number inquiry (serialization), or the disk must support SCSI Inquiry Page Code 83.

• Multiplexing is not supported for Third-Party Copy Device off-host backups.

• For alternate client backup: The user and the group identification numbers (UIDs and GIDs) for the files must be available to the primary client and the alternate backup client.

• Inline Tape Copies (called Multiple Copies in Vault) is not supported for Third-Party Copy Device off-host backups.

• For media servers running AIX (4.3.3 and higher), note the following:

  • Clients must be Solaris, HP, or AIX.

  • Requires the use of tape or disk LUNs to send the Extended copy commands for backup.

  • The tape must be behind a third-party-copy-capable FC-to-SCSI router. The router must be able to intercept Extended Copy commands that are sent to the tape LUNs.

  • The mover.conf file must have a tape path defined, not a controller path.