Loading...
Loading...
Before installing Everpure FlashArray Plug-In v2.2.331, ensure that you are running Veeam Backup & Replication 12.3.0.310 or later. To check the version, open the main menu of the Veeam Backup & Replication console and select Help > About.Note: Customers using an earlier 12.x version of Veeam Backup & Replication may use the previous plug-in version. Everpure FlashArray Plug-In v2.2.331 supports integration with the following storage systems: Purity 6.3 or later
Fixed incorrect handling of the SafeMode policy when manual eradication is disabled. Backup jobs no longer report false warnings or failures for snapshots and volume clones that have already been destroyed and are awaiting automatic eradication by the storage system. Fixed a potential memory leak caused by background garbage collector processes in certain scenarios.
Source/target side selection for synchronous replication relationships occurs based on the host mapping information from the arrays. If a volume only on one side of the relationship is mapped to a host, that side is considered the source. If volumes on both sides are mapped, the 'Preferred Arrays' setting in the storage management console's host settings is used. If that setting is not configured, the first array in alphabetical order is considered the source. Volumes that are part of a Volume Group are not supported for asynchronous snapshot replication. For asynchronous snapshot replication, the volume should be added to the Protection Group by explicitly selecting it in the Protection Group settings. In case you've added the volume to the Protection Group via Host/Host Group, make sure to manually trigger the transfer of at least one Protection Group snapshot before adding the target volume to Veeam Backup & Replication otherwise the replication relationship will not be detected. For volumes with multiple different asynchronous snapshot replication relationships, the snapshot chain is only kept on one of the targets. For volumes on the target side of an asynchronous snapshot replication relationship, the volume size is displayed in Veeam Backup & Replication as '0'. Archived snapshots that have been destroyed but not eradicated can still be visible in Veeam Backup & Replication Console and can be used for restores until being eradicated by the storage cleanup mechanisms. In case a backup job with the snapshot offload option enabled is not configured to keep snapshots on the primary array, the latest archived snapshot cannot be used for restore from archive. This is due to the fact that the latest snapshot is always kept on the storage as a temporary transfer snapshot, so it cannot be downloaded from the archive. As a workaround, it is recommended to configure the job to keep at least one primary storage snapshot. In cases where a Managed Directory has several NFS exports, to indicate a preferred one (the one with an NFS datastore created on it), a nfsDirectoryExportPreference.json config file can be used. The file must be located in the plug-in installation folder (C:\Program Files\Veeam\Backup and Replication\Plugins\Storage\Pure Storage FlashArray\nfsDirectoryExportPreference.json) and have a json format with the directory name as the key and the export name as the value. Example:
DOWNLOAD Plug-In Filename: 0208_EverpureFlashArrayPlugin_2.2.331.zip Updated: 2026-05-15 MD5: F79549A4A46B76E5705E7141989C42C9 SHA1: 7DC95E8176612E78C62707AAAE85E51283235059 SHA256: C032A3CEEC9E0EEBA0F26F01A754F4F7F62070EBF705ABABAD547706F5DE7241
Prior to version 2.2.331 the plug-in was named "Pure Storage Plug-In for Veeam Backup & Replication" Pure Storage Plug-In for Veeam Backup & Replication [2.1.400] Addressed destroyed snapshot deletion issues on the secondary storage in SafeMode configurations.
Veeam Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.