Release Information for NEC Storage V Series Plug-In for Veeam Backup & Replication

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

• The Snapshot Advanced feature is only supported for volumes with the DRS attribute. The attribute must be inherited by snapshots.
• The NEC Plug-In does not support backing up failover clusters using Veeam Agent for Microsoft Windows.
• When backing up an Active Mirror volume, note that the copy group name to which the volume belongs must be prefixed with "VBR_" otherwise, backup jobs will fail. This requirement applies even if only one volume from an Active Mirror replication relationship is added to a Veeam Backup & Replication instance.
• Adding NEC V Series storage to the Veeam Backup & Replication infrastructure via Service Processor (SVP) IP is not supported. 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.
  
• NEC 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 maintenance. 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.
• 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.
• Ensure at least two FC ports are available on the storage; configurations with a single FC port are not supported.
  
• [New for v2.2.271] Information about the snapshot immutability period is not collected during storage rescan. As a result, snapshots created outside of Veeam Backup & Replication, or those collected after removing and re-adding the storage in Veeam Backup & Replication, do not display the 'Immutable Until' date in the UI. Additionally, such snapshots cannot be deleted manually because they are actually immutable.
• [New for v2.2.271] The Immutability feature is only available for volumes that have the DRS attribute. If jobs reference volumes without the DRS attribute but have immutability enabled, they will display the snapshot immutability expiration time, which matches the snapshot creation time.