Offhost backup failures when using VSFW as a provider

Following are the most common causes of snapshot failure and offhost backup failure when using the Veritas Storage Foundation for Windows (VSFW) software provider:

Volume has not been snap started. Backup Exec requires that you first snap start all volumes using the Veritas Enterprise Administrator administration console or command-line interface before attempting an offhost job.

See Using Snap Start on a Veritas Storage Foundation volume.

If you already performed the snap start for a previous snapshot operation, you must either snap start the volume again (to another physical disk) or snap back the previous snapshot volume. For details on how to snap back, refer to the documentation for the Veritas Storage Foundation for Windows software provider.
Volumes to be backed up are basic volumes. VSFW allows only dynamic volumes to be snapped.
You are trying to back up a volume that resides on a disk with other volumes and so the disk group cannot be deported.
Any attempt to split the snapshot volumes from the source volumes will fail if the snapshot volumes and the source volumes share the same physical disks. The administrator must keep the source volumes and the snap volumes from sharing the same physical disks.
Offhost backup requires that VSFW version 4.1 or later be installed on both the remote computer and on the media server. Previous releases are not supported. Compatible VSFW software versions must reside on both the media server and the remote computer. It is recommended that the same version of VSFW be installed on both computers.
All dynamic volumes designated for backup must be in the same Disk Group (DG). Multiple disk groups in the same offhost job are not supported.
Ensure that there are no more than seven volumes in a single snapshot operation. When more volumes are installed, they cannot all be snapped within the ten-second time-out that VSS imposes for snapshots to complete, and the snapshot will fail.
Basic volumes and dynamic volumes cannot be mixed in a backup job that uses the offhost feature. A workaround is to make sure that the option Process logical volumes for offhost backup one at a time is selected. This restriction also applies to dynamic volumes that are mounted by mount points on basic volumes.
Dynamic boot and system volumes are restricted from VSFW FlashSnap functionality for compatibility reasons. Therefore, dynamic boot and system volumes are not supported for an offhost backup.

Note:

Most VSS providers have some limitation about the types of volumes that are transportable. Therefore, it is recommended that you do not use offhost backup jobs for complete system protection. A best practice is to use offhost backup jobs to back up databases and logs when all of the dependent volumes on which data resides are transportable. Any volumes that are used to host mount points for data volumes must also be transportable because the offhost backup must snap both the data volumes and the volume with the mount point for backup.