The following is a list of known major issues for Hitachi Plug-In for Veeam Backup & Replication. If you experience any issue listed below, contact Hitachi support directly.

• Adding Hitachi storage to the Veeam Backup & Replication infrastructure via Service Processor (SVP) IP is only supported for VSP 5000 series. For other storage models, use one of the CTL1/CTL2 IP addresses when adding the storage.
• DNS names (hostnames/FQDNs) cannot be used to add the storage; only IP addresses are allowed. Additionally, IPv6 can only be used if the IPv4 management address is not configured on the storage.
  
• Hitachi Plug-In does not return information about volumes that are not mounted to a host. To restore from snapshots residing on such volumes, mount a volume to a host and perform a rescan in the Veeam Backup & Replication console. For details, see Rescanning Storage Systems.
• This plug-in version does not support Freeze-only snapshots. If you want to enable VM processing using VMware snapshots, contact Veeam support to change the value of a dedicated registry key.
• After deleting a snapshot, logical device (LDEV) records with the _DEL suffix may remain on storage until the subsequent automatic or manual storage rescan operation. However, such snapshots can occasionally be exported and displayed in the storage infrastructure UI as regular volumes if the storage rescan fails to purge them - in this case, they can be unexported or deleted manually.
  
• The same applies to clones that are purged during rescan only if synchronization between the source snapshot and its clone is not underway.
• Retention-based snapshot removal may fail if synchronization between the snapshot and its clone has not been completed or is still running.
• Only one volume from a GAD replication relationship should be added to a Veeam Backup & Replication instance.
• If jobs and rescan operations are running in parallel or at the moment when the storage system is processing other tasks, the operations may fail.
• Hitachi Plug-In does not support backing up failover clusters using Veeam Agent for Microsoft Windows.
• Veeam Backup Service restart causes subsequent Veeam Agent for Microsoft Windows job to fail. The issue occurs because the job triggers storage information caching, and it exceeds the VSS freeze timeout.
• Ensure at least two FC ports are available on the storage; configurations with a single FC port are not supported.
• In Veeam Backup & Replication 12, in case of a multi-path configuration where a volume is exported to a host via several ports simultaneously, backup jobs will fail due to a LUN SCSI ID collision (LUNs with different LUN IDs having the same SCSI Unique ID). To address the issue, please install Veeam Backup & Replication 12 P20230412 or later and set the SanScsiIdCollisionFail
  • Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
  • Value Name: SanScsiIdCollisionFail
  • Value Type: DWORD (32-Bit) Value
  • Value Data: 0
  registry value to 0.

1. Ensure Veeam Backup & Replication has a valid license.
2. If you're running Veeam Backup & Replication 11a P20220302, download and install the following private fix (required for the plug-in to pass a signature check).
   The fix is not required for Veeam Backup & Replication 11a P20230227 or 12.
3. Download and run the plug-in setup program on the Veeam Backup Server.