Release Information for Fsas ETERNUS EP300 Plug-In for Veeam Backup & Replication

Before installing Fsas ETERNUS EP300 Plug-In v2.2.309, make sure that you are running Veeam Backup & Replication build 13.0.1.180 or higher. You can check the build number in the Veeam Backup & Replication Console's Main Menu (≡) under Help > About.

Fsas ETERNUS EP300 Plug-In v2.2.309 supports integration with the following storage systems:

• Fsas ETERNUS EP300 (A3-03-01-x0/01 or later)

ETERNUS EP300 is an OEM product of Hitachi VSP One Block B20 series, and its features and operation are identical to those of VSP One Block B20 series. Please refer to Hitachi documentation for user guides and other materials.

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

• Thin Image Advanced feature is only supported for volumes with the DRS attribute. The attribute must be inherited by snapshots.
• When backing up a Global Active Device (GAD) 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 a GAD replication relationship is added to a Veeam Backup & Replication instance.
• When adding ETERNUS EP300 storage to the Veeam Backup & Replication infrastructure, use the Service IP address.
• 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.
• Fsas ETERNUS EP300 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 (application-aware processing performed without creating a VMware snapshot, see Configuring Snapshot-Only Jobs). In some cases, this processing mode can exceed the Windows VSS timeout, which may result in inconsistent backups. To switch to VM processing using VMware snapshots instead of Freeze-only processing, 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.
• Fsas ETERNUS EP300 Plug-In does not support backing up failover clusters using Veeam Agent for Microsoft Windows.
• 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.
• 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.