Enabling SAN Access

To use the SAN transport method, your backup server where the vSphere Plugin is installed should have access to all LUNs which are exported to your ESXi server(s). The multipathd tools will avoid problems with multiple device paths to SAN devices.

Once your SAN LUNs are visible to your backup server as /dev/sda, /dev/sdb, … The vSphere Plugin will open each LUN to get the UUID and compare it with what the ESXi server is providing. For example, when using iSCSI, the lsscsi command will display them as:

% lsscsi
[5:0:0:0]    disk    IET      VIRTUAL-DISK     0     /dev/sdb

You can verify that SAN transport is used during backup by using the debug option in the vSphere Plugin command line. If SAN transport mode is used, the vddk trace file will have an entry showing “Opened san://…” like in the following example:

% grep san: /opt/bacula/working/vsphere/<moref>/<seq>/0.log
DISKLIB-LIB   : Opened "san://3-snapshot-18[datastore2] test/test_2.vmdk...

When the SAN mode is not available, the vSphere Plugin will automatically switch to the NBD transport mode.

See also

Go back to:

• Enabling Block Level Incremental Backup

Go to:

• Check User Permissions

• <QueryInformationAboutvSphereEnvironment>

Go back to the main vSphere Plugin Configuration page.

Go back to the main vSphere Plugin page.