TRY NOW
book meeting
BACK TO KB LIST

Release Information for Everpure Fusion Plug-In for Veeam Backup & Replication

KB ID: 4129
Product: Veeam Backup & Replication | 13.1
Published: 2021-03-15
Last Modified: 2026-10-29
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

This plug-in leverages the Veeam Universal Storage API, which enables storage OEMs to allow Veeam Backup & Replication integration to the arrays for backup and replication jobs.

Requirements

Before installing Everpure Fusion Plug-In v2.2.595, ensure that you are running Veeam Backup & Replication 13.1.0.411 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 version of Veeam Backup & Replication may use the previous plug-in version.

Everpure Fusion Plug-In v2.2.595 requires Everpure Fusion. Storage systems must be added to Veeam Backup & Replication as members of an Everpure Fusion fleet.

What's New

  • Added support for Veeam Software Appliance.
  • Added support for Everpure Fusion.
  • Added support for asynchronous snapshot replication for volumes that are part of a volume group.

Known Issues

Coexistence with Everpure FlashArray Plug-In for Veeam Backup & Replication

  • This plug-in version supports only storage arrays that are part of Everpure Fusion. For standalone storage arrays, use Everpure FlashArray Plug-In for Veeam Backup & Replication 2.2.331.
  • Upgrade and migration from Everpure FlashArray Plug-In for Veeam Backup & Replication are not supported. This plug-in is installed as a separate component and can coexist with previous versions of Everpure FlashArray Plug-In for Veeam Backup & Replication.
  • You cannot use the same storage array with both plug-ins at the same time. To move a storage array from the standalone plug-in to the Everpure Fusion plug-in, remove the array from Veeam Backup & Replication, then add it again with the Everpure Fusion plug-in and create new jobs. Retention of the new jobs does not apply to existing snapshots, so you will need to manage these snapshots manually.

Asynchronous snapshot replication

  • For volumes that are part of a volume group, at least one snapshot must be replicated to the target volume for it to be registered correctly.
  • 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'.

NFS

  • NFS support requires Purity 6.10.1 or later.
  • This plug-in version provides limited support for NFS datastores with FlashArray File Services. Only backing up from storage snapshots is supported, while restoring from storage snapshots or replication functionality with FlashArray File Services are not.
  • NFS is supported only on arrays added to Veeam Backup & Replication as the fleet entry point. NFS support for other fleet member arrays is experimental.
  • If several backup jobs process VMs on the same NFS datastore at the same time, one of the jobs can fail. When one job finishes, it removes the NFS export that the other jobs still use to read their snapshots, and their VM processing fails with the “No such file or directory” error. To work around the issue, schedule such jobs so that they do not overlap.
  • In cases where a Managed Directory has several NFS exports, to indicate a preferred one (the one with an NFS datastore created on it), use the nfsDirectoryExportPreference setting in the storage_plugin_advanced_settings.json configuration file. The file is located in the following folder:
    Example:
{
  "nfsDirectoryExportPreference": {
    "myFA1::FileSystem3:md1": "myexp4",
    "myFA1::myPod1::FileSystem2:md1": "myexp3"
  }
}

Snapshot Offload

  • 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.

Other

  • 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.
  • Enabling Kerberos for Everpure storage requires additional configuration on both the storage and proxy sides:
    1. On the storage side, create the export policy VEEAM_RO_POLICY if it does not already exist, then configure it to allow only the supported Kerberos security level (krb5, krb5i, or krb5p).
    2. Add every Veeam Backup Proxy to VEEAM_RO_POLICY as a client. For each proxy, add the IPv6 address first, followed by the IPv4 address.
    3. Depending on the environment, additional proxy-side configuration may be required. For details, see Kerberos Authentication (Storage Systems) in the User Guide.
  • If an error occurs while you edit a fleet member storage system in Veeam Backup & Replication 13.1, and you ignore the error and complete the wizard, Veeam Backup & Replication adds a duplicate entry for the same storage system to the backup infrastructure instead of updating the existing one. The error can be, for example, a failed certificate retrieval, a connection error, an unavailable plug-in service or a configuration database failure. To work around the issue, remove the duplicate entry from the Storage Infrastructure view.
  • When you edit a fleet member storage system in Veeam Backup & Replication 13.1, the wizard lists all storage protocols, including protocols that the plug-in does not support, for example, NVMe-oF. If you select an unsupported protocol, Veeam Backup & Replication displays a warning during storage rescan. Backup infrastructure operations are not affected.

Download Information

For Veeam Backup & Replication on Windows

Download Everpure Fusion Plug-In

Filename: 0216_EverpureFusionPlugin_2.2.595.zip
Updated: 2026-10-26
SHA256: B2A8E8167E0263D12CBA055224714F7324F5FCD00A28E876C9710B068801089D

For Veeam Backup & Replication on Veeam Software Appliance

Download Plug-In for VSA

Filename: 0216_everpure-fusion-2.2.595.0.bndl
Updated: 2026-10-26
SHA256: 3BBFE20FCC5D238CF7FEB6BF379A59628A6EBA6BF0CE216265CEF10D5120D9B9

Previous Versions

Everpure FlashArray Plug-In for Veeam Backup & Replication [2.2.331]

Requirements

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.

Pure Storage FlashArray Plug-In v2.2.331 supports integration with the following storage systems:

  • Purity 6.3 or later
Resolved Issues
  • 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.
Known Issues
  • 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:
{
    "myFileSystem1:md": "myexp5",
    "myFileSystem1:md2": "myexp1",
    "myPod1::FileSystem2:md1": "myexp3",
    "myFA1::FileSystem3:md1": "myexp4"
}
  • Enabling Kerberos for Everpure storage requires additional configuration on both the storage and proxy sides:
    1. On the storage side, create the export policy VEEAM_RO_POLICY if it does not already exist, then configure it to allow only the supported Kerberos security level (krb5, krb5i, or krb5p).
    2. Add every Veeam Backup Proxy to VEEAM_RO_POLICY as a client. For each proxy, add the IPv6 address first, followed by the IPv4 address.
    3. Depending on the environment, additional proxy-side configuration may be required. For details, see Kerberos Authentication (Storage Systems) in the User Guide.
Download 2.2.331 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.

Pure Storage FlashArray Plug-In for Veeam Backup & Replication [2.1.388]

What's New
  • Adds limited support for NFS datastores with FlashArray File Services, enabling customers to utilize USAPI capabilities with Managed Directories configured as vSphere NFS datastores for Purity 6.4.10 or later.
    Note that this plug-in version does not currently support restoring from storage snapshots or replication functionality with FlashArray File Services.
  • Adds support for asynchronous replication for pod volumes for Purity 6.6.1 or later.
Resolved Issues

  • Replication relationships in setups involving both active/active asynchronous replication and automatic asynchronous replication from ActiveCluster synchronous arrays were not properly detected and processed.

  • A comma could not be used as a decimal delimiter on Veeam Backup & Replication servers configured with certain Windows locales, leading to formatting inconsistencies.

  • Auxiliary volumes were automatically added to the default protection group by default, which unnecessarily increased snapshot quota consumption.
    Customers can now manually add volumes they wish to persist into the default protection groups.

  • Resolved the most commonly reported support issues.

Pure Storage FlashArray Plug-In for Veeam Backup & Replication [2.0.47]

  • Support for Universal Storage API v2, which enables the following additional functionality:
    • Snapshot replication orchestration – allows backup jobs to leverage existing Pure Storage FlashArray Replication relationships to create storage-based snapshot replicas as additional restore points. This also enables performing backup from secondary storage arrays, to avoid any load from backup activities on the primary storage array.
      • Snapshot archiving orchestration – allows backup jobs to manage the offload of volume snapshots to a different type of storage device via Pure Storage FlashArray Offload functionality and track them there as additional available restore points.
      • Synchronous replication support – allows backup jobs to create coordinated storage snapshots and track them as additional available restore points and perform backup from volumes on both sides on dual Pure Storage FlashArray ActiveCluster configurations that serve the same production volume from multiple storage management backends.
  • Also, processing of snapshot deletion attempts on arrays with SafeMode enabled no longer produces job warnings and doesn't lead to an increased Veeam Backup & Replication service load.

Pure Storage Plug-In for Veeam Backup & Replication [1.3.18]

This update resolves the most commonly reported support issues.

Pure Storage Plug-In for Veeam Backup & Replication [1.2.45]

This update resolves the most common support issues and features the following enhancement:

  • Added support for replicated volume snapshots on the target array. For details, review KB3023.

Pure Storage Plug-In for Veeam Backup & Replication [1.1.40]

This update features the following enhancements:

  • Added support for volume snapshots created as part of a Pure Storage Protection Group.

This update also resolves the most common support issues, including the following:

  • The default HTTP timeout value was Increased from 5 to 60 seconds to make the plug-in more resilient to network issues.
  • vVol volumes are no longer displayed in the list of volumes.

Pure Storage Plug-In for Veeam Backup & Replication [1.0.37] 2018-04-10

  • Initial plug-in version

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Start using Veeam:
Download the product
&
Activate the license key
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.