Challenge

Product Information:

Company name: Zadara
Product Family: VPSA (Virtual Private Storage Array)
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: VPSA Storage Array
Storage Category: Software Defined Storage
Drive quantity, size, type: 4 x 1.6TB SSD
Storage configuration: RAID10
Firmware version: 18.11
Connection protocol and speed: 40 GbE iSCSI
Additional support: All models and configurations of VPSA running v18.11 and above with hardware specifications equivalent or greater than the above

Zadara VPSA Storage Array provides:

• Unified storage with both Block volumes and File shares exposure
• Data Protection (RAID-1, 6, 10, 60)
• Advanced Data management (Thin Volumes, Snapshots & Clones)
• Management GUI and Rest API
• Flexibility to grow and shrink resources such as CPU, RAM, cache and drive allocations.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2753

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings:

• Multipathing used in testing – yes (MPIO)
• All VPSA volumes should be connected using Zadara’s best practices for VMware

More Information

Challenge

Cause

• After upgrade from Veeam Management Pack 8.0 Update 5 to Update 6, some Veeam Backup Reports start displaying incorrect data or the “No relevant data found” message in the output. For example, the ‘Protected VMs’ report considers a number of analyzed VMs to be Unprotected.
• Some Veeam Backup & Replication views in the Ops Mgr console show incorrect data for a number of Veeam Backup & Replication servers.
• The ‘Veeam Backup Repository Maintenance Mode Renewal’ monitor tends to change its state from Healthy to Warning once in a while (every 1 hour by default).

Solution

1. Check that you have Veeam Management Packs version 8.0.0.2467 installed. To do that, navigate to Administration > Management Packs in the Ops Mgr console.
2. Download the archive file using the link provided in the ‘More Information’ section.
3. Unpack the archive.
4. Import Veeam management packs included in the patch to the Ops Mgr console. To do that, navigate to Administration > Management Packs > Import MPs. For detailed instructions about importing management packs, see this Microsoft KB article.
5. Ensure that the Veeam Backup Monitoring and Veeam Backup Discovery management packs now have the following build numbers: Veeam Backup Monitoring MP — 8.0.0.2477, Veeam Backup Discovery MP — 8.0.0.2474.

More Information

Challenge

During the snapshot removal step of a Veeam job, the source VM loses connectivity temporarily.

Cause

Veeam does not remove the snapshot itself, Veeam sends an API call to VMware to have the action performed.

The snapshot removal process significantly lowers the total IOPS that can be delivered by the VM because of additional locks on the VMFS storage due to the increase in metadata updates, as well as the added IOP load of the snapshot removal process itself. In most environments, if you are already over 30-40% IOP load for your target storage, which is not uncommon with a busy SQL/Exchange server, then the snapshot removal process will easily push that into the 80%+ mark and likely much higher. Most storage arrays will see a significant latency penalty once IOP's get into the 80%+ mark which will of course be detrimental to application performance.

Solution

Isolation Test

The following test should be performed during a time when connectivity to the VM is not sensitive, for instance during off peak hours.

To isolate this issue to the specific VMware snapshot removal event, Veeam suggests the following isolation test:

1. Create a snapshot on the VM in question.
2. Leave the snapshot on the VM for duration of time that a Veeam job runs against that VM.
3. Remove the snapshot.
4. Observe the VM during the snapshot removal.

If while performing the test above you observe the same connectivity issues as during the Veeam job run, the issue very likely exists within the VMware environment itself. Please review the following list of troubleshooting steps and known issues. If none of the following work to resolve the issue, we advise that you contact VMware support directly regarding the snapshot removal issue.

Common Troubleshooting Tasks

• Check the VM for snapshots while no job is running and remove any that are found.
• Check for orphaned snapshots on the VM. (See: http://kb.vmware.com/kb/1005049)
• Reduce the number of concurrent tasks that are occurring within Veeam, this will in turn reduce the number of active snapshot tasks on the datastores.
• Move VM to a datastore with more available IOPS, or split the disks of the VM up into multiple datastores to more evenly spread the load.
• If the VMs CPU resources spike heavily during Snapshot consolidation, consider increasing the CPU reservation for that VM.
• Ensure you are on the latest build of your current version of vSphere, hypervisors, VMware Tools and SAN firmware when applicable.
• Move VM to a host with more available resources.
• If possible, change the time of day that the VM gets backed up or replicated to a time when the least storage activity occurs.
• Use a workingDir to redirect Snapshots to a different datastore than the one the VM resides on. http://kb.vmware.com/kb/1002929
• Disable VMware Tools Sync driver on the VM: http://kb.vmware.com/kb/1009886

Known Issue with NFS 3.0 Datastores

Note: This issue will present as multiple minutes worth of stun. Normal snapshot stun is only mere seconds.

At the time of the writing of this KB there is a known issue with NFS Datastores and Virtual Appliance (HOTADD) transport mode. The issue is documented in this VMware KB article: http://kb.vmware.com/kb/2010953

Veeam advises that if this issue occurs one of three things can be done to work around this:

1. Use Direct NFS Mode

More details available here:
https://helpcenter.veeam.com/docs/backup/vsphere/direct_nfs_access.html

2. Configure Veeam Backup & Replication to use a Proxy on the same host as the VM

Note: This option is only available in versions newwer than 7.0.0.839

1. Create a VM proxy on every host in your VMware cluster where backups occur
2. On the server where the Veeam Backup & Replication console is installed open ‘Registry Editor’
3. Create the following registry value in the key below:
   HKLM\Software\Veeam\Veeam Backup and Replication\
   Type: DWORD
   Name: EnableSameHostHotaddMode
   value: 
   For the value there are two options, "1" or "2" these options are explained below:
   • 1- if proxy on same host as VM is unavailable, Veeam Backup & Replication will fail over to a proxy on a different host and use available transport mode, which may cause stun
   • 2 - If proxy on same host as VM is unavailable, Veeam Backup & Replication will use an available proxy on a different host, but force it to use network transport mode, so that no stun occurs; this may be preferable when stun is not tolerable.

Note: Both values 1 or 2 will enable the SameHostHotaddMode, which forces Veeam B&R to first attempt to use the Proxy that is on the same host as the VM to be backed up.

3. Reconfigure proxies to use Network Transport mode.

1. Edit the proxies listed under [Backup Infrastructure]>[Backups Proxies]
2. Click the [Choose] button next to “Transport mode”
3. Select the radio option for “Network” mode
4. Click [OK] to close the prompt and then [Finish] to commit the change.

More Information

The following links are provided to help understand more about the Snapshot Removal process within VMware:

http://up2v.nl/2011/05/09/know-the-performance-impact-of-snapshots-used-for-backup/

http://kb.vmware.com/kb/1002836
 

Challenge

Solution

• Microsoft System Center Virtual Machine Manager 2019 is now supported.
• VMware vCloud Director 9.7 compatibility at the existing Update 4 feature level.
• VMware vSphere 6.7 U2 readiness including support for VMs with virtual hardware version 15. 
• Dell EMC Data Domain using DD OS 6.2 is now supported as the backup repository via both DDBoost and CIFS/NFS protocols. 
• Microsoft Windows 10 May 2019 Update and Microsoft Windows Server version 1903 support as guest VMs, and for the installation of Veeam ONE. 
• VMware vSphere 6.5 U3 and VMware vSphere 6.7 U3 are officially supported with Update 4a. 

• High CPU usage is observed on the Veeam Backup & Replication 9.5 Update 3/3a/4 server after upgrading Veeam ONE to v9.5 Update 4
• Business View grouping expression raises an error “invalid expression” if the length is longer than 25 rows
• Exporting Business View objects in the Veeam ONE Monitor client does not include category names
• Object Properties collection task returns error or warning with “Failed to retrieve empty storage controller list for Hyper-V host” message in the session details
• High load on Veeam ONE SQL Server after upgrading Veeam ONE to v9.5 Update 4
• Under certain circumstances Veeam ONE cannot connect to the database after upgrading Veeam ONE to v9.5 Update 4
• Failed to download clients.xml from the vCenter server after upgrading Veeam ONE to v9.5 Update 4
• Under certain circumstances performance data cannot be collected from SCVMM server and its objects
• Veeam ONE cannot collect data from Veeam Backup Enterprise Manager and its objects
• Veeam ONE tries to connect to already deleted hosts from the monitoring

More Information

Challenge

Cause

The full list of ESXi/ESX hosts and compatible VM hardware versions is available in this VMware KB article.

Solution

• Downgrade the version of the original VM hardware. For details, see this VMware KB article;
• Upgrade the target host.

Challenge

Solution

• Microsoft System Center Virtual Machine Manager 2019 is now supported.
• VMware vCloud Director 9.7 compatibility at the existing Update 4 feature level.
• VMware vSphere 6.7 U2 readiness including support for VMs with virtual hardware version 15. 
• Dell EMC Data Domain using DD OS 6.2 is now supported as the backup repository via both DDBoost and CIFS/NFS protocols. 
• Microsoft Windows 10 May 2019 Update and Microsoft Windows Server version 1903 support as guest VMs, and for the installation of Veeam ONE. 
• VMware vSphere 6.5 U3 and VMware vSphere 6.7 U3 are officially supported with Update 4a. 

• High CPU usage is observed on the Veeam Backup & Replication 9.5 Update 3/3a/4 server after upgrading Veeam ONE to v9.5 Update 4
• Business View grouping expression raises an error “invalid expression” if the length is longer than 25 rows
• Exporting Business View objects in the Veeam ONE Monitor client does not include category names
• Object Properties collection task returns error or warning with “Failed to retrieve empty storage controller list for Hyper-V host” message in the session details
• High load on Veeam ONE SQL Server after upgrading Veeam ONE to v9.5 Update 4
• Under certain circumstances Veeam ONE cannot connect to the database after upgrading Veeam ONE to v9.5 Update 4
• Failed to download clients.xml from the vCenter server after upgrading Veeam ONE to v9.5 Update 4
• Under certain circumstances performance data cannot be collected from SCVMM server and its objects
• Veeam ONE cannot collect data from Veeam Backup Enterprise Manager and its objects
• Veeam ONE tries to connect to already deleted hosts from the monitoring

More Information

Challenge

• Backup to certain tape libraries fails with error 1117. Restore from encrypted tapes fails if a tape library has its hardware encryption setting is set to "Application managed" (data stored on tapes is however consistent, so the restore can be performed successfully once the hotfix is deployed). For more information and to download the hotfix, see KB2981

Cause

Solution

• Microsoft Windows 10 May 2019 Update and Microsoft Windows Server version 1903 support as guest VMs, and for the installation of Veeam Backup & Replication and its components.
• Microsoft Windows 10 May 2019 Update and Microsoft Windows Server version 1903 support by the Veeam Agent for Windows 3.0.2 (included in the update).
• Linux Kernel version 5.0 support by the updated Veeam Agent for Linux 3.0.2 (included in the update).
• Ubuntu 19.04, SLES 15 SP1, RHEL 8 and openSUSE Leap 15.1 distributions support in the Veeam Backup & Replication agent management functionality.
• VMware vCloud Director 9.7 compatibility at the existing Update 4 feature level.
• VMware vSphere 6.5 U3 readiness based on the pre-release build. The official support will still require the full regression testing performed on the generally available (GA) build. UPDATE: vSphere 6.5 U3 GA is officially supported with Update 4b.
• VMware vSphere 6.7 U3 readiness based on the pre-release build. The official support will still require the full regression testing performed on the generally available (GA) build. UPDATE: vSphere 6.7 U3 GA is officially supported with Update 4b.

• Oracle 19c on Linux support for RMAN-based and OCI-based application-aware processing, redo log backup and Veeam Explorer for Oracle in most configurations. Due to the recent availability of Oracle 19c, testing of DataGuard and RAC configurations is still being performed. UPDATE: Oracle 19c on Linux is officially supported with Update 4b.
• Oracle 19c on Windows support for RMAN-based and OCI-based application-aware processing, redo log backup and Veeam Explorer for Oracle in basic configurations only. Due to the most recent availability of Oracle 19c for Windows, testing of advanced configurations (DataGuard, RAC, ASM, Pluggable DB, flashback, virtual accounts) is still to be performed. UPDATE: Oracle 19c on Windows is officially supported with Update 4b.

• Veeam Backup & Replication will now periodically update the list of supported Amazon AWS regions from the Veeam update server. The list will be updated as Veeam QC validates compatibility with the newly added Amazon region. This functionality requires that you opt in for automatic product update check via the existing Check for product and hypervisor updates periodically check box in the Notification settings.

• Dell EMC Unity OE version 4.5 support.
• The proprietary NFS client has been updated for compatibility with the Western Digital IntelliFlash (formerly Tegile) Universal Storage API plug-in. The plug-in will be made generally available along with the Update 4b release.

• Tape virtual full backup reliability and performance, tape drive detection logic, WORM media support and NDMP backup reliability.
• Agent-based backup jobs may create unnecessary full backups under certain circumstances, or fail in the environments with very long backup repository paths.
• Scale-out backup repository race condition causes synthetic backup operations to dead lock when a very powerful backup proxy server is used.
• PowerShell Direct calls may hang under certain circumstances in the application-aware processing logic of Hyper-V backup.
• Veeam Agent for Windows: CBT driver block map reset issue; inability to failover to backup cache when it is hosted on a USB storage; inability to open a support case from the product UI under a restricted user account; improved command line tool for the Recovery Media creation.
• Veeam Agent for Linux: Dell servers with NUMA enabled may crash during the snapshot creation; intermittent backup jobs failures when processing XFS volumes; entire computer backup failure on Ubuntu 18.04 with Intel Software RAID; enhanced encrypted devices compatibility through redesigned device enumerator; CLI improvements for backup scope specification.
• NetApp ONTAP Snapvault retention processing in 7-mode clusters.
• Performance and resource usage optimizations in a number of backup infrastructure components.

More Information

If you have 9.5 Update 4 installed (RTM build 9.5.4.2399, GA build 9.5.4.2615, or Update 4a build 9.5.4.2753), you can upgrade to Update 4b using the following update package:

[[DOWNLOAD|DOWNLOAD UPDATE|https://www.veeam.com/download_add_packs/vmware-esx-backup/update4b_exe/]]
MD5: 5b75cb6da06b656c18b7ba782109273d
SHA1: a80968efe6d265dd4494ff1854a0132092c5a0fa

For new installations and upgrades from the previous versions, use the 9.5 Update 4b ISO image:

[[DOWNLOAD|DOWNLOAD ISO|https://www.veeam.com/download_add_packs/vmware-esx-backup/update4b_iso/]]
MD5: 9bd7f50c393bf368f42d6bd58dd9d3c1
SHA1: 24e230f19244d64d23db2b3660ebbc991835076f

Should you have any questions at all, please contact Veeam Support and we'll be happy to assist you with the upgrade.

Challenge

Cause

Solution

1. Depends on you version please download private fix and extract on the Veeam Backup Server. 
2. Right-click on the installation file and click "Run as administrator"
3. Go through the wizard to install private fix.
4. Relaunch Veeam Backup Console and let Veeam automatically update hosts added to the Veeam server.

More Information

Challenge

A job fails with an error related to NFC (Network File Copy) connectivity. For example:

Error: NFC storage connection is unavailable.

Failed to create NFC download stream.

Failed to create NFC upload stream.

Cause

The cause of the majority of NFC errors fall in to 3 primary categories:

• Port (902)
• Permissions*
• DNS

*If the account that Veeam Backup & Replication is using to communicate with the VMware Environment has granular permissions set please confirm all permissions are set according to the Granular Permissions Guide.
 
Due to the natue of NFC as a client server type connection, there is also potential that all things may be correct on the Veeam client side and there exists an issue within the VMware Infrastructure itself.

Solution

Note: When investigating this issue it is advisable to reconfigure the job to use a specific proxy. This is done to isolate an issue specific to a single proxy, as well as make it easier to identify which server the logs will found on.

Port, Permission, or DNS: Investigation

To investigate the potential of a Ports, Permissions, or DNS issue you will need to review the Agent logs.

1. Navigate to the following location, on the Veeam Proxy:

   %programdata%\Veeam\Backup

2. Open the folder that matches the name of the job that is having an issue.
3. Within this folder you will need to find the agent log for the specific VM.
   • For a Backup Job:

     Agent.<JobName>.Source.<VMName>.log

   • For a Replication Job:

     Agent.<JobName>.Source.<VMName>.log

     Agent.<JobName>.Target.<VMName>.log

4. Search for the following:

   Creating NFC download stream

5. Here you will want to look for the following items that could point to the cause of the error.
   1. Port
      If there is an issue with ports, there will be an error after the following:

      nfc| Establishing connection with the host [esx1]. Port: [902]. Failed.

   2. Permissions
      If there is an issue with permissions, there will be an error after the following:

      nfc| Sending authd message: [SESSION ID NUMBER].
      nfc| Sending authd message: [Name of Host].
      nfc| Waiting for the authd reply message...

   3. DNS
      If there is an issue with DNS, the following error will be found.

      nfc| Resolving host name (esx1) to IP address...
      nfc| Resolving host name (esx1) to IP address... Failed.

Port Issues

Further testing can be done using the following PowerShell command, the destination should be the hostname/FQDN/IP shown in the logs for the host.

Test-NetConnection -ComputerName "<destination_host>" -Port 902

If the Proxy is unable to reach port 902, check all applicable Firewalls between the server and the ESXi host.
 

Permissions Issues

When a vCenter server or standalone ESXi host is added to the [Backup Infrastructure] section of Veeam Backup & Replication, the user assigns an account to be used. That account should have sufficient privileges to all objects related to the VM being backed up. 
 

DNS Issues (Most Common)

The proxy must be able to resolve the hostname or FQDN of the hosts in the Virtual Infrastructure.
 

Host-side Issues

Restarting the Management Agents for the ESXi host may be required to correct NFC connection issues.



Other Isolation Ideas:
These are not solutions, they are only meant to help pinpoint a cause.

• Try a different proxy. (Isolates issue to specific Veeam Proxy)
• Try vMotioning the VM to a different host. (Isolates issue to specific ESXi host)
• Try Storage vMotioning the VM to a different datastore. (Isolates possible missing permission at datastore level)
• Try adding the ESXi host the VM is on as a standalone host to Veeam, then create a backup job to pull the VM from the standalone host.
  (This will help isolate if the Management Agents need to be restarted on the ESXi host)
  Remember to remove the job and standalone host from Veeam's configuration after the issue is resolved.

More Information

The proxy being used to process a VM can be identified by opening the “Task” log specific to the VM from inside the folder named after the job in %programdata%\Veeam\Backup. Searching the Task log for the words “starting agent” will allow for the identification of which server performed the task.

Further information can be found in this forum post: http://forums.veeam.com/veeam-backup-replication-f2/failed-to-create-nfc-download-stream-t2991-15.html#p69806

The NFC connection requires the following:

• DNS Resolution of target host
• Port 902 is open to/from Backup Server/Proxy to ESX(i) host
• Permissions to download files via ESX(i) host and/or vCenter

 
An issue with Port 902 may represent an issue with a firewall on the ESXi host, Veeam Proxy, or the connection between the two.

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

More Information

• VMware Cloud on AWS and Veeam - VMware KB
• VMware Cloud on AWS SDDC 1.6 - VMware Compatibility Guide Listing
• VMware Cloud on AWS SDDC 1.5 - VMware Compatibility Guide Listing
• VMware vSAN and Veeam - VMware KB
• VMware vSAN 6.7 U1 - VMware Compatibility Guide Listing
• VMware vSAN 6.0-6.5 - VMware Compatibility Guide Listing

Challenge

Cause

Solution

• Additional Hypervisor support vSphere 6.7. VMware vSphere 4.0 and later (including vSphere 6, vSphere 6.5, vSphere 6.7, vSphere 6.7 U1, vSphere 6.7 U2 and vSphere 6.7 U3) 
• 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

Product Information:

Company name: Fujitsu
Product Family: ETERNUS CS
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: CS8000
Drive quantity, size, type: 10 - SAS HDD
Firmware version: V6.1A7120-SP03
General product family overview:

ETERNUS CS8000 is a datacenter solution for backup storage for mainframe and open systems. Its intelligent process automation and pooling of storage capacity reduces the TCO for complex backup environments by 40%. Unique scalability in capacity and performance makes ETERNUS CS8000 a viable solution, delivering ongoing cost savings.

Veeam testing configuration:

Veeam Build Number: 9.5.x

Job Settings:

Repository Settings:

More Information

Challenge

Product Information:

Company name: Fujitsu (Fujitsu Technology Solutions)
Product Family: ETERNUS CS
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: CS8000 V7.1
Storage Category: RAID Storage Array
Drive quantity, size, type: 24 – 960GB SSD 2.5” drives
Storage configuration: RAID5
Firmware version: V7.1A2140-SP00
Connection protocol and speed: CIFS 10GbE
Additional support: All models and configurations of ETERNUS CS8000 with specifications equivalent or greater than the above

Veeam testing configuration:

Veeam Build Number: 9.5.4.2615

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings:

• No array deduplication used in testing
• No array compression used in testing
• Jumbo frames used in testing (MTU=9000)

More Information

Challenge

Product Information:

Company name: Adistec
Product Family: Data Protection Appliance Series
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: DPA M (M24)
Storage Category: Integrated Data Protection Appliance
Drive quantity, size, type: 4, 8TB, SAS HDD | (32TB total)
Storage configuration: RAID5 configured HDDs (12Gbps SAS) with read/write cache
Firmware version: V2
Connection protocol and speed: 10GbE ISCSI
Additional support: All models and configurations of DPA M with specifications equivalent or greater than the above: M, L & XL

Adistec Data Protection Appliances for VEEAM combine: customized Intel hardware platform, Veeam Availability Suite software, and Adistec Enterprise Cloud services resulting in a robust solution to protect your customer’s data supported by Adistec Total Support and Veeam. Simplify the Backup Storage’s infrastructure, eliminate complexity and maximize data availability and protection with this turnkey solution at an affordable price. Three models available in one and two RUs, with single Quad-Core or dual Octa-Core processors configuration. Starting with four 3.5” disks up to twelve, getting 16TB to 120TB of usable capacity.

Veeam testing configuration:

Veeam Build Number: 9.5.0.1536

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings:

• HDD – 1GB read cache on RAID controller, write back policy using backup battery
• Jumbo Frames used during testing (9000 MTU)
• Multipathing using Windows Server NIC teaming

More Information

Challenge

Product Information:

Company name: Hedvig Inc.
Product Family: Hedvig Distributed Storage Platform
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: Hedvig Distributed Storage Platform
Drive quantity, size, type: 1x 300GB SSD | 15x 1TB HDD (x3 Nodes)
Firmware version: 3.7.2
Connection protocol and speed: iSCSI, 10GbE
Additional support: All configurations of Hedvig Distributed Storage Platform with specifications equivalent or greater than the above

Hedvig provides multi-site software-defined storage for primary and secondary applications for private-, multi-, and hybrid-cloud deployments. Unique capabilities like replication policy, deduplication, compression, and encryption can be enabled per application. This programmable platform can scale from 10’s of TB to multi-PB with no practical limit.

Veeam testing configuration:

Veeam Build Number: 9.5.0.711

Job Settings:

Repository Settings:

More Information

Challenge

Product Information:

Company name: Panzura, Inc.
Product Family: Freedom NAS
Status: Veeam Ready - Repository*
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: 5500
Storage Category: Cloud-out NAS Storage
Drive quantity, size, type: 12 - 800GB, SAS SSD
Storage configuration: RAID50 via automatic software configuration
Firmware version: 7.0.2.5
Connection protocol and speed: SMB, 2 x 10GbE
Additional support: All models and configurations of Freedom NAS with specifications equivalent or greater than the above

Panzura FreedomTM is an intelligent hybrid cloud storage solution underpinned by Panzura CloudFS. Panzura CloudFS is a scale-out, distributed file system purpose-built for the cloud. Programmatically accessible through REST APIs, it utilizes high performance flash in the data center, and integrates the cloud for economics, scalability, and durability. Unlike NAS, it scales globally across multiple sites and multiple clouds.

Veeam testing configuration:

Veeam Build Number: 9.5.0.1536

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings: The default configuration enables auto-tuning for all Panzura settings, which work well with the Veeam application. The caching policy should be set to pinned (as opposed to autotune) to ensure the administrator controls which backup sets are available locally. All Veeam backup data must be pinned locally to ensure fast restores and effective data operations within Veeam, without cloud reads.

More Information

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

This KB article provides a list of all versions and respective build numbers for the following products:

• Veeam Agent for Windows
• Veeam Agent for Linux
• Veeam Endpoint Backup

Solution

Veeam Agent for Windows

Veeam Agent for Linux

Veeam Endpoint Backup

Challenge

Cause

• After upgrade from Veeam Management Pack 8.0 Update 5 to Update 6, some Veeam Backup Reports start displaying incorrect data or the “No relevant data found” message in the output. For example, the ‘Protected VMs’ report considers a number of analyzed VMs to be Unprotected.
• Some Veeam Backup & Replication views in the Ops Mgr console show incorrect data for a number of Veeam Backup & Replication servers.
• The ‘Veeam Backup Repository Maintenance Mode Renewal’ monitor tends to change its state from Healthy to Warning once in a while (every 1 hour by default).

Solution

1. Check that you have Veeam Management Packs version 8.0.0.2467 installed. To do that, navigate to Administration > Management Packs in the Ops Mgr console.
2. Download the archive file using the link provided in the ‘More Information’ section.
3. Unpack the archive.
4. Import Veeam management packs included in the patch to the Ops Mgr console. To do that, navigate to Administration > Management Packs > Import MPs. For detailed instructions about importing management packs, see this Microsoft KB article.
5. Ensure that the Veeam Backup Monitoring and Veeam Backup Discovery management packs now have the following build numbers: Veeam Backup Monitoring MP — 8.0.0.2477, Veeam Backup Discovery MP — 8.0.0.2474.

More Information