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

Before installing NEC Storage M Series Plug-In v1.0.9, ensure that you are running Veeam Backup & Replication 11.0.0.837 or later. To check the version, open the main menu of the Veeam Backup & Replication console and select Help > About.

NEC Storage M Series Plug-In v1.0.9 supports integration with the following storage systems:

• M120, M320, M320F, M520, M720, M720F (Storage Control Software revision 1234 or later)

The following licenses are required on the NEC storage:

• BaseProduct
• AccessControl
• ThinProvisioning
• DynamicDataReplication
• DynamicSnapVolume
• Volume Clone

Follow detailed instructions on configuring the NEC Storage M Series Plug-in and the storage system in the NEC documentation [ ENG | JPN ].

The following is a list of known major issues for NEC Storage M Series Plug-In for Veeam Backup & Replication.

• For iSCSI, the NEC plug-in requires the host OS platform for backup proxies to be explicitly specified using the "OS Type" setting in the VeeamProxyOSType.xml configuration file. By default, hosts are auto-created with the Windows ("WN") type; to use a Linux proxy, the "OS Type" setting needs to be set to "LX". The proxy type for existing hosts can be changed later using the "Platform" setting for the host (LD Set) in the storage settings.
• Setups with IPv6 ports configured on the storage are not supported. Make sure the storage doesn't have IPv6 addresses configured.
• Virtual FC is not supported for connections between proxy and NEC storage.
• NEC storage plug-in will not work with FIPS policy enabled on the Veeam Backup & Replication server.
• The backup of VMs on datastores built with multiple disks (LUNs) is not supported.
• When there is a high load on the storage, the storage may fail to handle some plug-in requests. Please contact technical support to verify the reasons for the failures and get assistance with increasing the number of operation retries and retry timing.
• Some operations may fail with the message "The solution map is not large enough" when storage resource limitations in terms of Logical Disk size are reached. This might result from a large number of snapshots and clones created on the storage. You may want to try running fewer jobs in parallel and create jobs with fewer VMs to avoid that.
• To reduce the processing time of the rescan operation, the snapshot clones created during a rescan (one clone per snapshot) are not immediately removed during the unexport operation; instead, they are removed when the snapshot itself is deleted.
• If parallel backup jobs attempt to delete different snapshots on the same volume, the operation may fail with the "iSM19108: The volume under deletion exists" message. If this happens frequently, stagger the execution timing of backup jobs.
• Storage can only be added to Veeam Backup & Replication using storage management account credentials. The management account of the storage management software cannot be used.
• Storage time zone and backup server time zone must match.
• The NEC plug-In does not support backing up failover clusters using Veeam Agent for Microsoft Windows.
• Using Veeam Agent for Microsoft Windows to create backups from storage snapshots requires Veeam Backup & Replication 11a or later.
• When using Veeam Agent for Microsoft Windows, the maximum LUN size depends on the amount of RAM available on the storage (e.g., 48TB LUN for 64GB RAM).