Challenge

Product Information:

Company name: Pure Storage
Product Family: FlashBlade
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: Pure Storage FlashBlade
Drive quantity, size, type: 7 Blades / 8TB per blade - SSD
Firmware version: Purity//FB 2.1.0
General product family overview:

FlashBlade is a fast and dense unstructured data platform from Pure Storage that provides on-premise rapid backup and recovery of archival data. Additionally, Pure Storage FlashBlade provides high-performance in a dense-form factor for other unstructured data primary use cases such as machine learning, deep learning, and electronic design automation (EDA), among others.

Veeam testing configuration:

Veeam Build Number: 9.5.0.823

Job Settings:

Repository Settings:

Challenge

Product Information:

Company name: Pure Storage
Product Family: ObjectEngine
Status: Veeam Ready – Object
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier features.

Solution

Product Details:

Model number: ObjectEngine //A
Storage Category: Appliance
Drive quantity, size, type: ObjectEngine //A270 includes the minimum of 4 nodes.  Nodes can be added to the cluster, in increments of 2, to provide additional throughput.  ObjectEngine reduces the data inline (via deduplication and compression) as it’s being written to the permanent storage media.  FlashBlade provides the underlying object storage and can be configured with a minimum of 7 and up to 15 blades per chassis, and each blade can be 17TB or 52TB of flash storage.  Up to 5 FlashBlade chassis can be connected together.
Storage configuration: Tests were performed on 4-Node Pure Storage ObjectEngine //A270, with 15 blade (17TB per blade) FlashBlade using erasure encoding for unstructured data storage.
Firmware version: OES 5.0.0
Connection protocol and speed: 8x 10 GbE
Additional support: All models and configurations of ObjectEngine for S3 compatible storage with specifications equivalent or greater than the above.

General product family overview: ObjectEngine’s cloud-native technology reduces storage and bandwidth costs, enabling flash plus cloud solutions across a variety of use cases, including data protection. The FlashBlade solution provides an all-flash storage for this unstructured data platform.
 

Veeam testing configuration:

Veeam Build Number: 9.5.4.2753

Vendor recommended configuration:

Vendor Settings:

• Array deduplication used during testing
• Aray compression used during testing
• Default S3 connection settings

Challenge

Product Information:

Company name: Red Hat, Inc.
Product Family: Red Hat Ceph Storage
Status: Veeam Ready – Object
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier features.

Solution

Product Details:

Model number: 3.1
Storage Category: Software Defined Storage
Drive quantity, size, type: 7 - 1TB SATA hard drives per cluster node, for a total of 21 drives across the cluster.
Storage configuration: Hard drives were all used in single, standalone mode. No hardware or software RAID used.
Firmware version: ceph version 12.2.5-59.el7cp
Connection protocol and speed: 1GbE
Additional support: All models and configurations of Red Hat Ceph 3.1 or higher for S3 compatible storage with specifications equivalent or greater than the above.

General product family overview:
Red Hat Ceph Storage 3.1 running on a 3-node cluster, with all nodes running the Object Storage Daemons (OSDs), and one node dedicated for the Monitor daemon (MON), Manager daemon (MGR), and Object Gateway daemon (RGW).

Veeam testing configuration:

Veeam Build Number: 9.5.4.2282

Vendor recommended configuration:

Vendor Settings:

• No hardware deduplication used in testing
• No hardware compression used in testing

Challenge

Product Information:

Company name: Scality
Product Family: Scality RING
Status: Veeam Ready – Object
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier features.

Solution

Product Details:

Model number: Scality RING
Storage Category: Web-scale Software Defined Storage
Drive quantity, size, type: 156x 6TB NL-SAS, 12x 400GB SSD
Storage configuration: ARC 9+3
Firmware version: 7.4.2
Connection protocol and speed: 40GbE
Additional support: All models and configurations of Scality RING for S3 compatible storage with specifications equivalent or greater than the above.

General product family overview:
The Scality RING is software that turns any standard x86 servers into web-scale storage. With the RING, you can store any amount of data, of any type, with incredible efficiency and 100% reliability, guaranteed—all while reducing costs by as much as 90% over legacy systems.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2753

Vendor recommended configuration:

Vendor Settings:

• Jumbo frames used during testing
• Storage Servers used in testing:6x Cisco UCS S3260 M4 Dual Node, 2x Intel(R) Xeon(R) CPU E5-2650 v4@ 2.20GHz, 128GB RAM

Challenge

Product Information:

Company name: SwiftStack
Product Family: SwiftStack Storage
Status: Veeam Ready – Object
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier features.

Solution

Product Details:

Model number: N/A
Storage Category: On-premise cloud-native storage
Drive quantity, size, type: 27 X 12 TB 10000 RPM hard disk drives (HDDs) are used per node to store objects and 1 X 400 GB SSD is used per node to store account information and metadata only
Storage configuration: 6-node cluster comprising UCS S3260 servers were used to test the solution
Firmware version: v6.24
Connection protocol and speed: 10GbE
Additional support: All models and configurations of SwiftStack Storage with specifications equivalent or greater than the above.

General product family overview:

SwiftStack is a cloud-native storage platform for managing unstructured data in a single namespace that is policy-driven and can scale across both private and public infrastructure.  Supports all drive types. Size and quantity of drives per node will vary depending on deployment configuration and use cases. SwiftStack supports scale-out object storage clusters comprised of standard Intel-based servers, starting with 3 nodes or greater.
 

Veeam testing configuration:

Veeam Build Number: 9.5.4.2753

Vendor recommended configuration:

Vendor Settings:

• Triple replicas and Erasure coding storage policy settings to protect data in the storage cluster.

Challenge

Cause

Solution

Challenge

Cause

Solution

• Constant
• Carp
• Cwd
• Data::Dumper
• Encode
• Encode::Alias
• Encode::Config
• Encode::Encoding
• Encode::MIME::Name
• Exporter
• Exporter::Heavy
• File::Path
• File::Spec
• File::Spec::Unix
• File::Temp
• List::Util
• Scalar::Util
• SOAP::Lite
• Socket
• Storable
• Threads

More Information

Challenge

Cause

• Veeam Backup&Replication related reports in Veeam Management Pack result in displaying incorrect data or “No relevant data found” message. Protected VMs report show all VMs as Unprotected.
• Backup Jobs data is missing in Veeam MP views in SCOM for particular Veeam Backup & Replication servers.
• "Veeam Backup Repository Maintenance Mode Renewal" monitor changes its state from Healthy to Warning every interval (1 hour, by default).

Solution

1. Unpack the archive.
2. Import the Management Packs to SCOM: SCOM > Administration > Management Packs > Import MPs.
3. Ensure that the build number for Veeam Backup Monitoring and Veeam Backup Discovery management packs became 8.0.0.2474.

1. Open SCOM > Authoring > Object Discoveries > Veeam Backup Job Discovery (Discovered type: Veeam Backup Abstract Job).
2. Right-click and select "Override for all objects of class: Veeam Backup Jobs".
3. In the Override Properties change the Discovery SQL Job parameter value from True to False.
4. Save the overrides to the dedicated Management Pack.

More Information

Challenge

Solution

More Information

Challenge

Cause

Last-minute kernel patches for Red Hat Enterprise Linux and its derivatives may cause Veeam Agent for Linux to go unstable (veeam.com/kb2786).
 

Challenge

In some cases a SP backup server receives "Success" status of a tenant job even when the job has failed on the Tenant's server.

Cause

• All cloud gateways are unavailable
• There is not enough space on the disk
• An existing connection was forcibly closed by the remote host
• Repository quota exceeded

Challenge

Cause

Solution

• Additional Hypervisor support vSphere 6.7. VMware vSphere 4.0 and later (including vSphere 6, vSphere 6.5, vSphere 6.7 and vSphere 6.7 U2) 
• Monitoring SQL Transaction Log Backup Job. Veeam MP separately monitors SQL Transaction Log Backup jobs running inside backup jobs with the enabled application-aware processing option. For this purpose, Veeam MP includes a new Veeam SQL Transaction Log Backup Jobs view and Veeam Backup: SQL Transaction Log Job Status monitor.
• Improved performance of Morning Coffee Dashboards. In previous versions, Morning Coffee Dashboards tended to load slowly for large-scale environments. In Veeam MP 8.0 Update 6, the performance of Morning Coffee Dashboards has been significantly improved.
• A new metric for Veeam VMware Collector. Due to the Ops Mgr Health Service (Monitoring Agent Service) limitations that appear when a Veeam VMware Collector processes a large amount of data, it is required to distribute monitoring load among multiple Veeam VMware Collectors in large environments. To assess the monitoring load on Veeam VMware Collectors more precisely, Veeam MP provides a new % Object Monitoring Load metric.

• No monitoring for Hyper-V hosts that exceeded the license limit. Veeam MP license limits the number of Hyper-V hosts enabled for monitoring in Ops Mgr. Earlier, if the number of licensed Hyper-V hosts was exceeded and new hosts were added to the Ops Mgr infrastructure, Ops Mgr automatically stopped monitoring the old infrastructure and started monitoring the newly added hosts. In Veeam MP 8.0 Update 6, the issue was resolved, and Ops Mgr continues monitoring the old infrastructure.
• Ops Mgr event log shows excessive BackupCopyJobSessionFinished events. In previous versions, the Ops Mgr event log contained a large number of 3101 events caused by errors in the backup copy job status collection process. In Veeam MP 8.0 Update 6, the issue was resolved.

• Collector Autodeploy limitations. If you use the Collector Auto-Deployment feature to automatically deploy Veeam VMware Collectors on Management Servers, keep in mind that it will install clear 8.0 version without patches. When the installation completes, run the ISO\Update\VeeamMP80_Update6.exe installation file on each Veeam Collector to install patches.  
• Veeam MP for Hyper-V stops collecting storage metrics. If storage migrates to another volume, the storage performance collection will halt and Veeam MP will stop collecting the following metrics: Storage IOPS, Storage KB Total/sec, Storage Flush Count and Storage Error Count. Note that this issue does not affect migration between hosts. To work around the issue, restart the Ops Mgr agent after storage migration.

More Information

Challenge

When attempting to backup a SQL server that is hosting a significant amount of databases the following error is thrown:
 

Unable to release guest. Error: Unfreeze error: [Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{}]. Instance ID: [{}]. Writer's state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].]

Error: Unfreeze error: [Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{}]. Instance ID: [{}]. Writer's state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].]

Cause

Veeam Backup & Replication sends a VSS API request to freeze an entire SQL server including all databases. In SQL Server, the snapshot backup of each database uses five threads in the Sqlservr.exe process. Additionally, other activities may also use threads in the Sqlservr.exe process. Depending on the configuration of SQL Server, the available threads may be used up if you create a snapshot backup of many databases at the same time. 

It is possible to process the VM in a crash-consistent manner by disabling Application-Aware Image Processing within the job.

Solution

Microsoft does not recommend creating a snapshot for more than 35 databases at the same time. It is advised to create another SQL Server and move the databases that are causing failure to the other SQL server. Adding additional CPU cores and RAM may also fix the issue.
In certain scenarios changing the max worker threads Server Configuration Option may help negate the issue. However, it is advisable to contact Microsoft support for verifying this step.

For further troubleshooting, Microsoft recommends figuring out which SQL instance has the problem. Usually, the problematic SQL instance will be named in the first recorded SQLVDI error.

Please refer to the following articles for details:

• https://support.microsoft.com/en-us/kb/943471
• http://blogs.msdn.com/b/psssql/archive/2009/03/03/how-it-works-sql-server-vdi-vss-backup-resources.aspx
• https://msdn.microsoft.com/en-us/library/ms190219.aspx?f=255&MSPPError=-2147217396
• https://support.microsoft.com/en-us/kb/2157129

More Information

Note: Veeam Support is not able to provide assistance with modifying the number of threads within SQL. Please contact Microsoft Support for assistance.

Challenge

Cause

Operation: [Shadow copies commit]. Code: [0x80042306]

Solution

Verify Sufficient Free Space

(Optionally) Redirect Shadow Copies

Shadow Copies Utility (Server OS Only)

1. Select the volume with insufficient space;
2. Click Settings…
3. In the dropdown labeled Located on this volume, select a volume with sufficient space to store the shadow copies.

Command Line (Client or Server OS)

How to Check Which Volume is Causing the Error

1. Select a volume;
2. Click Create Now;
3. If this is successful, select the shadow copy and click Delete Now;
4. Repeat steps 1-3 for each volume.

This can also be performed using the Diskshadow utility, which may provide a better match for the behavior of the VSS API used by Veeam Backup & Replication.

If the affected volume has sufficient free disk space, the shadow storage limit may be too small. Redirect the shadow copies as shown above, or increase the shadow storage limit.

More Information

Challenge

Guest VMs will fail to engage VSS when application-aware image processing is enabled generating an error:

Error Guest processing skipped (check guest OS VSS state and integration components version) (System.Exception)

Cause

This issue has multiple potential causes, usually related to the Integration Services version of the failing guest server. This issue occurs when Application-Aware image processing is utilized in the Backup or Replication job settings for transactional quiescence using Microsoft VSS

Solution

Please Note:

• A list of supported Guest OSes for each version of Hyper-V can be found here. 
• Important! Server 2012 R2 and higher guests are not supported for VSS-enabled (AAIP) backups on 2008 R2 hosts due to integration components incompatibility.
• If the VM Guest OS is 2012 and the Host is 2008R2:
  • View the Guest OS Application Event logs for errors with source: vmicvss and Event ID: 13.
  • If this error is present, open the Registry Editor (regedit) and navigate to:
    HKLM\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\SystemRestore\
    Within that key create a new DWORD
    Name: ScopeSnapshots
    Value: 0
  • Note: If the SystemRestore key is not present, you will have to create it.

The solution section of this knowledge base article has been split into four different sections. Please review each step of the following sections.

1. Integration Services
2. Within the Guest
3. VM Configuration
4. Verification

1. Integration Services

Click here for a list of Hyper-V Integration Services and their corresponding build numbers.

How to identify…

1. Using Event Viewer

This section will provide directions on ensuring the Hyper-V Integration Services are up to date within the Guest OS of the VM that is failing to backup.

If Hyper-V Integration Services are out of date you will find Event ID 4000 within the Hyper-V-Integration section of the Event Viewer on the Hyper-V host where the VM is located.

2. Using PowerShell (Server 2012 or newer)

Run the follow command in an Administrative PowerShell prompt on the host where the VM that failed to backup resides.
 

Get-VM | select VMName, IntegrationServicesState

The results of which will list out each present VM, and the state of its integration services.

How to correct:

Note: A reboot of the virtual machine will most likely be required to complete the Integration Services update.

The following information is from the Microsoft page found here.

Install or update integration services

For hosts earlier than Windows Server 2016 you'll need to manually perform install the update from within the guest operating system. These steps cannot be automated or executed within a Windows PowerShell session.

1. Open Hyper-V Manager. From the Tools menu of Server Manager, click Hyper-V Manager.
2. Connect to the virtual machine. Right-click the virtual machine and click Connect.
   
3. From the Action menu of Virtual Machine Connection, click Insert Integration Services Setup Disk. This action loads the setup disk in the virtual DVD drive.
   
   Depending on the guest operating system, you may need to start the installation manually.
   
4. After the installation finishes, you may be prompted to restart.
   

2. Within the Guest

The following steps and checks are to be performed within the Guest OS of the VM that is failing to backup.

1. Make sure Windows is running the most recent service pack.
    
2. Ensure that the VSS Storage Area and Volume Match
   1. From an Administrative Command Prompt, run the command ‘VSSUIRUN.exe”
      
   2. Check the [Settings] for each Volume and ensure that the Volume and the Storage area match.
      
       
3. Ensure there are no Dynamic disk or FAT\FAT32 volumes
   1. Open Disk Management (diskmgmt.msc)
   2. Review the Type and File System columns
   3. VSS is not compatible with Dynamic disks or FAT\FAT32
      Note: The VHD(X) that the VM runs off can be dynamic. The volume within the Guest OS cannot.
      
      All volumes must be NTFS or ReFS
       
4. Check System Reserved partition free space.
   1. System Reserved partition must have more than 42MB of space free.
   2. If less than 42MB is free, try creating a shadow copy for the volume.
      
   3. Remember to delete the Shadow Copy if it is successful.
       
5. Start\Restart the “Hyper-V Volume Shadow Copy Requestor
   1. Open Services (services.msc)
   2. Find the “Hyper-V Volume Shadow Copy Requestor” service.
   3. If it is ‘Stopped’, Start it. (If the service will not start, check in the VM settings under Integration Services, and ensure the "Backup (volume Checkpoint)" option is enabled.)
   4. If it is ‘Running’, restart it.

3. VM Configuration

The following steps and checks are to be performed from the Hyper-V host level.

1. Make sure the VM has a SCSI controller. One must be present, even if there are no devices to use the SCSI controller.
   •  The error will present itself in the Hyper-V VMMS > Admin Event log. Example:
     “The virtual machine ' Vm-Name' cannot be hot backed up since it has no SCSI controllers attached. Please add one or more SCSI controllers to the virtual machine before performing a backup. (Virtual machine ID).”
2. Within the Virtual Machine settings verify that the “Backup (Volume Snapshot)” option is enabled.
3. Make sure that the virtual machine files (VHD files) are not sitting in the root folder of the CSV, as this may prevent correct snapshot creation due to permission restrictions. We strongly recommend keeping virtual machine files in separate folder. More information regarding this can be found here.

Verification

Performing the following will allow you to determine if the steps performed above have corrected the issue without the need to run the Veeam Backup & Replication job again.

1. 1. Open an Administrator Command Prompt.
   2. Run the command:

      Diskshadow /L C:\writers.txt

   3. Run the command:

      list writers

Open the file that was created and and locate the VM name in the section for the Hyper-V writer. For each VM there's a "Caption" entry. The caption should read "online" or "child partition", and not "offline" or "saved state".

More Information

PowerShell script to tell you if you need to update your Integration Services
https://blogs.msdn.microsoft.com/virtual_pc_guy/2013/04/29/powershell-script-to-tell-you-if-you-need-to-update-your-integration-services/

Recommended hotfixes for Hyper-V servers:

http://www.veeam.com/kb1838
http://blogs.msdn.com/b/virtual_pc_guy/archive/2009/02/02/looking-at-the-hyper-v-event-log.aspx
http://blogs.technet.com/b/virtualization/archive/2008/08/29/backing-up-hyper-v-virtual-machines.aspx

Challenge

Product Information:

Company name: Cloudian
Product Family: HyperStore
Status: Veeam Ready – Object
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier features.

Solution

Product Details:

Model number: Cloudian HyperStore 1508
Storage Category: Scale-out Object Storage System
Drive quantity, size, type: Each node has 2x480 GB SSD mirrored for boot devices and 12x 8 GB SAS disks for object storage to store user data
Storage configuration: 3 nodes minimum. Storage policies with either replication factor (RF) or erasure coded (EC) or a combination of both define protection levels and are applied on a per bucket basis. For test bucket, storage policy used RF replication factor.
Firmware version: v7.1.3
Connection protocol and speed: 2x 10 Gb/s ports on single NIC (Ethernet) per node
Additional support: All models and configurations of HyperStore for S3 compatible storage with specifications equivalent or greater than the above.

General product family overview:
Break through the capacity barrier with Cloudian HyperStore S3 object storage. Gain simplicity and one-click data management in your data center, across sites, around the world, or in the cloud. Cloudian’s limitless capacity, global data fabric and single management view lets you do more, at less cost, and derive more value from your data.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2282

Vendor recommended configuration:

Vendor Settings:

• At least one S3 bucket with a folder for Veeam data is required
• Cloudian HyperStore SSL must be enabled to use the https S3 endpoint. After deploying HyperStore, the included online documentation and administration manual describes the detailed procedure.

Challenge

Product Information:

Company name: Huawei Technologies Co., Ltd.
Product Family: FusionStorage
Status: Veeam Ready – Object
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier features.

Solution

Product Details:

Model number: FusionStorage
Storage Category: Scale-out Cloud Storage
Drive quantity, size, type: Storage Mediums: HDD\SSD | Cache type: SSD, NVDIMM, and RDIMM
Storage configuration: FusionStorage uses EC (erasure coding) technology to achieve data redundancy. Optional, FusionStorage uses 2 SSDs for cache.
Firmware version: v7.0.0
Connection protocol and speed: Ethernet, RoCE, and InfiniBand
Additional support: All models and configurations of FusionStorage for S3 compatible storage with specifications equivalent or greater than the above.

General product family overview:
Fully distributed cloud storage with excellent scalability. The on-board system software integrates the local storage resources of general-purpose servers into fully distributed storage pools, to provide block, object, or file storage resources to the upper layer.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2753

Challenge

Product Information:

Company name: Wasabi Technologies
Product Family: Wasabi Hot Cloud Storage
Status: Veeam Ready – Object
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier features.

Solution

Product Details:

Object Storage Tiers: Wasabi Hot Cloud Storage (Wasabi currently has one tier of storage)
Object Storage Service Description: Wasabi is a S3-compatible public cloud object storage service

General product family overview:
Wasabi is a cloud-based object storage service for a broad range of applications and use cases. Wasabi is designed for individuals and organizations that require a high-performance, reliable, and secure data storage infrastructure at minimal cost.
Wasabi has much higher sustained read and write speeds. In addition, with Wasabi, the time to first byte is a fraction of the time comparatively. Wasabi is accessed over any public or private network speeds.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2753

Challenge

Product Information:

Company name: NetApp
Product Family: StorageGrid
Status: Veeam Ready – Object
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier features.

Solution

Product Details:

Model number: SG5760
Storage Category: Webscale Object Storage
Drive quantity, size, type: 240 x 4TB NS-SAS drives
Storage configuration: 4x SG5760s each with 60x4TB NL-SAS drives, configured using dynamic disk pools (8+2)
Firmware version: 11.1.1.3-20181130.1854.43f37b8
Connection protocol and speed: 10GbE
Additional support: All models and configurations of StorageGrid for S3 compatible storage with specifications equivalent or greater than the above.

General product family overview:
NetApp StorageGRID Webscale (SGWS) is an Object Storage platform which is flexible and highly scalable while supporting multiple RESTful APIs for storing and managing data. Efficient, Durable, and Flexible. Drive cost savings without sacrificing durability with NetApp StorageGRID Webscale’s hierarchical erasure coding. Protecting at the node level and with geo-distributed coding, customers can create policy-driven data protection with multiple levels of granularity. They can choose a combination of full copies and/or geo-distributed coded copies to balance performance needs and cost savings between different sets of data or during the object’s lifecycle.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2399

Vendor recommended configuration:

Vendor Settings:

• For data protection, used default 2-copy rule

Challenge

Product Information:

Company name: Pure Storage
Product Family: FlashBlade
Status: Veeam Ready – Object
Classification Description: Verified object storage solutions that has been tested with Veeam Backup & Replication Cloud Tier features.

Solution

Product Details:

Model number: FlashBlade
Storage Category: All Flash Storage
Drive quantity, size, type: 7x 8TB Blades – supports up to 15 blades with various capacities available
Storage configuration: N/A
Firmware version: 2.2.11
Connection protocol and speed: 40 GbE
Additional support: All models and configurations of FlashBlade for S3 compatible storage with specifications equivalent or greater than the above.

General product family overview:
FlashBlade is a fast and dense unstructured data platform from Pure Storage that provides on-premise rapid backup and recovery of archival data. Additionally, Pure Storage FlashBlade provides high-performance in a dense-form factor for other unstructured data primary use cases such as machine learning, deep learning, and electronic design automation (EDA), among others.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2399