Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ for VMware Administrator's Guide
  3. Notes and prerequisites
  4. NetBackup for VMware support for SAN multi-pathing
Veritas NetBackup™ for VMware Administrator's Guide

NetBackup for VMware support for SAN multi-pathing

NetBackup for VMware on Windows supports dynamic multi-pathing (DMP) between the vSphere ESXi storage and the NetBackup for VMware agent (Windows backup host). Dynamic multi-pathing can provide SAN I/O high-availability and improved backup throughput.

For NetBackup for VMware on a Linux backup host, the following items describe the support for dynamic multi-pathing in a SAN environment:

NetBackup appliance

The NetBackup appliance (beginning with the 2.6.0.2 release) supports SAN dynamic multi-pathing for VMware backups. I/O is redirected through the volume manager dynamic multi-pathing node.

For more information, see the NetBackup Appliance Administrator's Guide for version 2.6.0.2 and later:

http://www.veritas.com/docs/DOC2792

Non-appliance Linux host

NetBackup supports backups and restores for multi-pathing under the following conditions:

  • The virtual disk SAN transport whitelist specifies the device node paths that you want to use for multipathing. The virtual disk vixDiskLib.transport.san.whitelist API function defines the whitelist. For NetBackup purposes, Veritas recommends that you include the DMP nodes in the whitelist; the following is an example:

    vixDiskLib.transport.san.whitelist = /dev/vx/dmp/
    hitachi_usp-v0_00a0,/dev/vx/dmp/hitachi_usp-v0_00
    a0s1,/dev/vx/dmp/hitachi_usp-v0_00a0s2,/dev/vx/dm
    p/hitachi_usp-v0_00a0s3,/dev/vx/dmp/hitachi_usp-v
    0_00a0s4,/dev/vx/dmp/hitachi_usp-v0_00a0s5
  • The virtual disk SAN transport blacklist specifies the device node paths you want to exclude from multipathing. The virtual disk vixDiskLib.transport.san.blacklist API function defines the blacklist. For NetBackup purposes, Veritas recommends that you set the blacklist to all; the following is an example:

    vixDiskLib.transport.san.blacklist = all

Specify the whitelist and the blacklist in the following file on the backup host:

/usr/openv/lib/shared/vddk/lib64/vixDiskLib.ini

For more information about the whitelist and the blacklist, see the appropriate VMware documentation. For example, for Virtual Disk Development Kit 6.0 the whitelist and the blacklist function descriptions are in the VMware Virtual Disk Programming Guide.

Note:

This support or limitation does not affect NetBackup support for VMware's Native Multipathing, which is multi-pathing between the ESXi host and storage.

This support or limitation does not affect NetBackup for VMware on Windows backup hosts. The Windows operating system has integrated multi-pathing support. The following Microsoft guide contains more information:

http://microsoft.com/mpio

Feedback

Was this page helpful?
Previous

Notes on the NetBackup appliance as a VMware backup host

Next

NetBackup for VMware support for fault tolerant VMs

Feedback

Was this page helpful?