Challenge

A license file installed to your Veeam software replaces the information from the previous license. A merged license file allows for increased socket capacity by combining licenses from multiple Support IDs.

Please note that the merged license key will use the earliest support expiration date of all product keys.

Solution

NOTE! Licenses can be merged only when they have the same:

• Account Name
• Product Name and Edition
• Product Version
• Support Terms
• License Administrator
• They must all be Active on Support.

Your License Administrator may obtain a merged license file by following the steps below.

1. Log on to the Veeam My Account dashboard and go to License management >> Production Licenses (https://my.veeam.com/#/licenses/production)
2. In the Action column for the appropriate product, select Merge
   
3. From this page, select each of the boxes to the left of all the individual licenses you would like to merge
   
4. In the box that appears below, select the appropriate version of the key for your software and whether you would like to download the license directly or have a copy of the key emailed to your License Administrator email.
   

More Information

Please note that the license auto-update feature does NOT correctly update merged licenses created on the license management portal. If you have enabled auto-update, disable it before installing a merged license from the license management portal.

Challenge

This article documents how to install the optional PowerShell Snapin when Veeam Backup & Replication version 8 or less is installed.

Note: Starting with Veeam Backup & Replication 9.x the PowerShell Snapin is automatically installed by default. Veeam PowerShell Guide

Solution

Please find and execute BPS_x64.msi from the “Backup” folder found on the Veeam Backup & Replication installation media.

More Information

Challenge

VMware Cloud on AWS needs some specific preparation to allow Veeam Backup & Replication v9.5 Update 3 or newer to work with it.

Some of VMware features and permissions are not granted by default at the start of VMware Cloud on AWS (VMC). Thus, some depending Veeam Backup & Replication features will be limited or not operating. Depending on VMware update releases for VMware Cloud on AWS, the situation may change and the features from the table below may become available. Please contact your VMware administrator for timely update.

Solution

1. Use a new Windows Server and install Veeam Backup & Replication v9.5 Update 3 or newer.
2. Add DNS network settings so that this Server can resolve Internet DNS names.
3. Check the below information carefully for any know limitations and configuration steps before you proceed.

Firewall Configuration for vCenter connection

1. Open Port TCP 443 from Backup Server and Proxy Server to the predefined vCenter object on the Compute Network.
   
2. Allow the Compute Gateway Public IP to communicate over TCP 443 with the predefined vCenter object on the Management Network.
   

1. Create a vCenter User with required rights (Active Directory linked mode) described here, or use the cloudadmin@vmc.local user.
2. When adding a vCenter server, specify the fully qualified domain name (FQDN) that ends with vmwarevmc.com or vmc.vmware.com (depending on the URL shown in the VMC interface for the vCenter).

1. On the Compute Network:
   1. Open TCP 22 (SSH) port from Veeam Backup server and Veeam proxy server to the Amazon VPC where the EC2 Server was installed. You can as well define the exact IP addresses of the repository server as Destination.
   2. Open TCP 2500-5000 ports for Veeam Data Transport in both directions for same servers. It is recommended to use the ENI Network Tunnel to avoid any traffic costs.
2. Open the same ports on the Inbound Firewall of the Amazon EC2 server used as a repository server.
   
   

More Information

VMware Cloud on AWS specific problems and solutions:

Problem

Solution

1. Create a vCenter User with required rights (Active Directory linked mode) described here, or use the cloudadmin@vmc.local user.
2. When adding a vCenter server, specify the fully qualified domain name (FQDN) that ends with vmwarevmc.com or vmc.vmware.com (depending on the URL shown in the VMC interface for the vCenter).

Problem

Solution

• vsanDatastore datastore
• Management VMs folder
• Mgmt-ResourcePool resource pool

Problem

Solution

Problem

Solution

Challenge

Task fails with the error message, “Task failed Error: Object with reference '<moref>' was not found in hierarchy cache”

This issue can be confirmed by editing the job, navigating to "Virtual Machines" and clicking the [Recalculate] button. VM's whose RefID have changed will report as having a "0 B" size.

Note: Older version of Veeam Backup & Replication may report the error as "Task failed Error: Object <vmname> not found"

Cause

This error is caused by the VM’s unique inventory reference identification number (MOREF, or Managed Object Reference) changing within the virtual infrastructure, or the VM having been deleted. Veeam is still attempting to find the VM by its old reference ID number based on a “find vm by NAME where REFID = X” query.

Note: The most common events that cause a VM MOREF ID to change are:

• Reinstallation or creation of a new vCenter server where the old VC database is not reused.
• A VM is removed from inventory and then added back to inventory.
• In rare cases a host crash, which prompts the host to be removed and added back to the VC may cause the VMs on that host get new MOREF IDs.

Solution

Resolution

1. Rescan the vCenter Servers
   1. Navigate to [Backup Infrastructure]
   2. Expand [Managed Servers]>[VMware vSphere]
   3. Right-Click on [vCenter Servers] and select [Rescan]
      
2. Re-add the VM to the Job
   1. Edit the Job
   2. Navigate to the Virtual Machines tab.
   3. Select the VM whose MoRef has changed.
   4. Click Remove
   5. Click Add...
   6. Click Refresh*
      
   7. Add the VM removed in step 4.
   8. Click [Finish] to save the Job settings.

*Veeam Backup & Replication caches infrastructure information to improve performance, the refresh function purges the cached data. The refresh function must be used when resolving this issue.

Validate Resolution

Resolution can be confirmed without running the job. Edit the job, navigating to "Virtual Machines" and click the [Recalculate] button. Note that the VM's whose MoRefs changed now report as having the correct size.

Important Note

Please be aware that VM's are tracked by their unique MoRef ID. When the MoRef changes the VM is considered an entirely different VM. As such Veeam Backup & Replication will treat them accordingly and create a Full restore point for the "new" VM.

Challenge

Solution

Challenge

Solution

More Information

Challenge

Solution

Challenge

You need to force a Backup job or Backup Copy job to create a new backupset.

or

The backup files have been removed from disk, and you need to remove the file references from Veeam's configuration database.

Solution

Note: Please ensure that the destination will have the space needed to start a new backup set.

Step 1: Remove Existing Backup Set

Steps on removing backup files from configuration can be found here:
https://helpcenter.veeam.com/docs/backup/vsphere/remove_from_backups.html

Step 2: Run the Job

Run the job, a new backup set will be started.

More Information

Important Notes:

• The files that are removed from configuration will no longer be controlled by the job's retention policy. They will remain on disk where they were left until they are manually removed.
• There may be multiple entries under Backups>Imported for the files that were removed from backups previously then were brought back in after a rescan of the repository.
• For Backup Copy Jobs with Archival fulls enabled - Make sure to check the box to remove archived fulls when removing from configuration. Otherwise a new incremental from the most recent archived restore point will be created. 

Challenge

Job may report warning: "Failed to finalize guest processing. Details: Failed to process 'TruncateSQLLog' command. Failed to truncate transaction logs for SQL instances: <instance name>. Possible reasons: lack of permissions, or transaction log corruption."

Solution

SQL logs truncation is done under user account specified in AAIP in Job settings, if it fails then GuestHelper tries to truncate transaction logs under LocalSystem account.

In order to understand why SQL logs truncation failed you will need to open the GuestHelper log on the Guest VM, and search for "Truncation Statistics".

• Windows 2008 or higher
  \\GUESTVM\c$\ProgramData\Veeam\Backup\VeeamGuestHelper_%date%.log
• Windows 2003
  \\GUESTVM\c$\Documents and Settings\All Users\Application Data\Veeam\Backup\VeeamGuestHelper_%date%.log

Know Errors and Solutions

1. Error: OpenFromInitializationString failed. [Login failed for 'DOMAIN\user'.]
   Solution: give DOMAIN\user permissions on SQL instance and add db_backupoperator role for all FULL and BULK databases, or give it a sysadmin role.
    
2. OLEDB Error: 'The server principal "DOMAIN\user" is not able to access the database "DATABASE" under the current security context.', HelpCtx: '0'
   Solution: give DOMAIN\user db_backupoperator role for all FULL and BULK databases, or give it a sysadmin role.
    
3. OLEDB Error: 'BACKUP detected corruption in the database log. Check the error log for more information.', HelpCtx: '0'
   Solution: error points to possible corruption and issues with SQL server
    
4. OLEDB Error: 'BACKUP LOG cannot be performed because there is no current database backup.'
   
   As a rule this is an issue with the secondary node of the SQL always on cluster. You can solve this by making a backup of the DB in question via SQL Management Studio. Otherwise, you can set the secondary node as primary for just one run of your backup job. As a result all its DBs will be backed up without "copy only" flag and the error will disappear.
   
   The issue occurs when the secondary node has always been backed up with "copy only" flag and its standalone DBs do not have any full backup. Thus during the truncation of the standalone DB logs we get the above-mentioned message.
   
   The same solution applies if you get this message with regard to the excluded vCenter database / Veeam database.
    
5. "Query timeout expired" If you see this entry in VeeamGuestHelper log, it usually means that we couldn't truncate SQL logs in allotted time (by default timeout is only 60 seconds). Usually you might experience such issues with rather large databases, and with large amount of transaction logs
   Solution: Implement the following registry value in affected VMs in [KLM\SOFTWARE\Veeam\Veeam Backup and Replication\] and [ HKLM\SOFTWARE\Wow6432Node\VeeaM\Veeam Backup and Replication] (if either location does not exist, create it):
   • SqlExecTimeout
   • Type: REG_DWORD
   • Default value: 60 (in seconds, decimal)
   Try to expand that value and run a backup afterwards, safe guess here is to set it for 600 seconds.

More Information

If you observe the following warning "Failed to truncate transaction logs for SQL instances: MICROSOFT WID" on Veeam B&R version 8.0.0.2084, please contact Veeam Support for the hot-fix.

Challenge

Product Information:

Product Family: Spectra Logic Tape Libraries 
Status: Veeam Ready - Tape 
Classification Description: Tape device where available hardware features have been tested to work with Veeam.  

Solution

Product Details

Model number: T-50e, T-120, T-200, T-380, T-680, T-950 
Library firmware version: BlueScale 12.6.45.3 
Drive firmware version: G9Q0 
Driver for tape drive: IBM Ultrium 7 Tape Driver v 6.2.5.5 
Driver for media changer: 2.0.2.5 
Media Type: LTO-6 
General product family overview: Spectra’s tape library family delivers the industry’s best combination of capacity, performance, scalability, reliability, support and affordability. Spectra’s highly compact tape library architecture and innovative design provides industry-best density. Optimized storage allows users to continually realize dynamic growth, increased performance and energy efficiencies throughout the storage management process and infrastructure. 

Veeam Details: 

Veeam Build Number: 9.5.0.1038 

More Information

Company Information

Company name: Spectra Logic 
Company overview: Spectra Logic develops data storage solutions that solve the problem of short and long-term digital preservation for business and technology professionals dealing with exponential data growth. Dedicated solely to storage innovation for nearly 40 years, Spectra Logic’s uncompromising product and customer focus is proven by the adoption of its solutions by industry leaders in multiple vertical markets globally. Spectra enables affordable, multi-decade data storage and access by creating new methods of managing information in all forms of storage—including archive, backup, cold storage, private and public cloud. 

Challenge

Product Information:

Product Family: Spectra Logic Tape Libraries 
Status: Veeam Ready - Tape 
Classification Description: Tape device where available hardware features have been tested to work with Veeam.  

Solution

Product Details

Model number: Spectra Stack
Library firmware version: 1.44
Drive firmware version: HB81
Driver for tape drive: IBMTape.x64_w12_6266 non-exclusive
Driver for media changer: Spectra Logic Medium Changer
Media Type: LTO-8

General product family overview:
Built with maximum flexibility at its core, the Spectra® Stack Tape Library meets your backup, archive, and perpetual storage requirements. Designed to be easily installed, expanded and managed, each module of the Spectra Stack holds an additional 10 to 80 tape slots and 1 to 6 tape drives. Supporting both full-height and half-height tape drives, Spectra Stack’s extreme flexibility provides affordability and expandability for unrivaled investment protection. Spectra Stack is verified Veeam Ready as a viable Tier 2 storage option combining the best in backup and recovery with archival storage to protect your data efficiently and securely without breaking the bank. The Spectra Stack accommodates multiple tape generations with backwards compatibility, including M7 media which expands LTO-7 tape capacity when read by an LTO-8 drive. For more information visit www.spectralogic.com/

Veeam Details

Veeam Build Number: 9.5.0.1038 

More Information

Company Information

Company name: Spectra Logic 
Company overview: Spectra Logic develops data storage solutions that solve the problem of short and long-term digital preservation for business and technology professionals dealing with exponential data growth. Dedicated solely to storage innovation for nearly 40 years, Spectra Logic’s uncompromising product and customer focus is proven by the adoption of its solutions by industry leaders in multiple vertical markets globally. Spectra enables affordable, multi-decade data storage and access by creating new methods of managing information in all forms of storage—including archive, backup, cold storage, private and public cloud.

Challenge

Cause

Solution

More Information

Challenge

Solution

• Delete your personal information
• Unsubscribe from marketing communications
• Get or update your personal information
• or for any general legal requests and GDPR compliance questions

More Information

Challenge

In the course of working with Veeam Support you may be asked to provide log files. If a security policy is in place that prevents you from uploading those logs via FTP protocol, this article documents how to upload the diagnostic log files via Secure FTP (SFTP).

Solution

Configure your FTP client to use Explicit Secure FTP (SSL/TSL).

Using WinSCP with SFTP

More information can be found here: https://winscp.net/eng/docs/guide_connect

Use the following settings:

• Host Name: supportftp.veeam.com
• Port: 21
• User Name: received from ticket/engineer.
  Example: ftp######## (where # is the ticket number)
• Password: received from ticket/engineer
• Protocol: FTP with SSL Explicit encryption or FTP with TSL Explicit encryption
  
  

Using FileZilla with SFTP

More information can be found here: https://wiki.filezilla-project.org/Using

Within FileZilla simply paste the URL with SFTP information into the Host field and click quickconnect.
Example: [sftp://ftp######:XYZXYZ@supportftp2.veeam.com]

More Information

If you have any questions or problems, please contact Veeam Support at http://www.veeam.com/support

Challenge

If you are a Cloud Provider gathering logs from your infrastructure please see:  https://www.veeam.com/kb2096

This article covers how to properly compile your logs in Veeam Backup & Replication v8.x and v9.x, as well as what to include when submitting a Support case for technical assistance.
 

Solution

The following animation demonstrates how to compile logs in Veeam Backup & Replication.

1. To compile your logs via the log compilation wizard, click the blue Menu button in the top left-hand corner of the gui and go to Help -> Support Information in the Veeam Backup & Replication console. 
2. This wizard will allow you various methods to compile logging. For Backup, Replication, and other jobs, select “export logs for this job.” If multiple jobs are affected, you can multiple-select. For problems with restore or replica failover, you should select “Export logs for this VM” and choose the  production VM  that was backed up or replicated. For issues with the GUI or problems that don’t fall into any of the above categories, select “Export all logs for selected components” and choose “This server.”
3. If possible, compile the logging for each job with issues for at least the last week.
4. You may save these logs to any location. Ensure that the location referenced has free space for compilation. Using the "Prepare logs package for technical support" checkbox will result in this wizard producing a .zip archive.
5. When selecting "Next", the wizard will notify of its progress in the compilation process. Please attach these to your case, or in the event that the total attachment size is under 3.5MB, you may attach via email reply. If none of these options for upload are working, please notify Veeam Support and an engineer will provide FTP credentials for the case.

Below is an animation demonstrating how to upload logs to the Veeam Support FTP.

Note: Please use the FTP account provided to you by the engineer for your case. When submitting logging data for analysis by request of an engineer, ensure that the case is replied to when the log submission has completed. In this reply, please include the names of any tasks and associated VMs with issues.



Note: SFTP is now supported when uploading to supportftp2, please place files in the \upload\ folder.

More Information

Below are the relative log path lists for Veeam Backup & Replication. If there are difficulties compiling the logging requested via the wizard-based instructions above, please obtain the files from the appropriate directory below and provide Veeam Support a .zip file copy. 

• Windows 2003, XP – C:\Documents and Settings\All Users\Application Data\Veeam\Backup\

• Windows Vista, 7 - C:\Users\All Users\Veeam\Backup\

• Windows 2008/2008 R2/2012 - C:\ProgramData\Veeam\Backup\

• Linux - /var/log/VeeamBackup/

Typical log files requested for a manual log compilation will be:

• The task's folder located in the parent directory, zipped. This will contain all relevant job/task/agent data.

• All logs from the parent directory named svc.*.log, util.*.log, as well as the VeeamBackupManager.log and VeeamShell.log

Please note that information provided to Veeam for purposes of customer support may be considered protected under certain data protection regulations and/or internal company policies. A list of potentially sensitive data types is available in the following KB article. Veeam will only utilize this information for the specific purpose of providing customer support to you and will protect the information in accordance with its privacy policy. In any event, the information provided will be securely deleted after 45 inactive days as of the last upload to the FTP. If you would like it deleted sooner, please express this request directly to your support contact once the issue has been resolved.

Challenge

Solution

Using SQL Server Management Studio

1. Open Microsoft SQL Server Management Studio (May need to be installed separately)
2. Connect to the "ServerName\Instance" of the server that has the DB you want backed up.
3. Expand the Databases tab to get to the DB you want to back up.
4. Right click the desired DB --> Tasks --> Back Up...
5. Set "Backup Type" to "Full"
6. Go through the rest of the General and Options tab information to set the options to what you want. 
7. Click OK to start the Backup process.

Using sqlcmd

If SQL Management Studio is not installed, the Veeam database can be collected using SQLCMD:

1. Check the name of the SQL instance and Veeam database in windows registry
   • HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication\SqlDatabaseName
   • HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication\SqlInstanceName
   • HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication\SqlServerName
2. Open an Administrative Command Prompt and connect to SQL instance:

   SQLCMD -S (SqlServerName)\SqlInstanceName

   
   Note: In case you have SQL server authentication enabled you may define username using '-U' parameter.

3. Backup the Veeam database:

   BACKUP DATABASE SqlDatabaseName TO DISK = 'C:\VeeamDB.bak'
   GO

More Information

Challenge

This KB article shows how to collect the diagnostic information that may be needed if you create a Veeam Agent for Microsoft Windows support case.

Solution

Gather logs using the four sections below. Once logs have been gathered, upload them to the FTP provided by the Veeam Support engineer. After the upload is completed you must notify the Veeam Support engineer.

If you need to use a secure FTP, this article contains secure FTP instructions.

All steps below are to be done from within the OS of the machine that is having an issue.

1. Veeam Agent guest logs

Navigate to and ZIP the contents of this folder:

C:\%programdata%\veeam\endpoint

2. VSS Diagnostics

Run the following commands from administrative command prompt, then zip the resulting files.

vssadmin list writers > C:\vss_writers.log
vssadmin list providers > C:\vss_providers.log
vssadmin list shadows > C:\vss_shadows.log
vssadmin list shadowstorage > C:\vss_shadow_storage.log

Once submitted to Veeam Support, these log files can be deleted.

3. Event Logs

Export the logs in .evtx format, with Display Information.

Export the System and Application logs as follows:

1. Open Event Viewer (eventvwr.msc).
2. Locate the log to be exported in the left-hand column.
3. Right-click the name of the log and select Save All Events As.
4. Enter a file name that includes the log type and the server it was exported from.

   For example, when exporting the Application event log from a server named HV01, enter Application_HV01.

5. In Save as type, select Event Files.
6. Include the display information.

7. Be sure to include the LocaleMetaData folder when packaging the logs for upload.

4. File System Minifilter Diagnostics

Run the command below from an administrative command prompt. 

fltmc instances > C:\filter.log

Once submitted to Veeam Support, this log can be deleted.

More Information

Challenge

This article explains how to manually revert a replica to its base disks allow it to be remapped to a replication job and used as a seed in the case that the replicas snapshot files become corrupt.

NOTE: The actions take here should never be performed on a production server as a data loss could occur. These actions are only to be taken on a replica as Veeam has the ability to bring the replica up to date.

The following are error messages that may prompt the use of this KB article:

• A replication job may fail with a message such as “Unable to repair replica VM.”
• When the replication job attempt to create a snapshot on the replica it fails with “File or folder already exists.” In this case most often there is a loose file that is named like a snapshot but not associated with the replica. E.g. a file named DC01-0000001.VMDK, and when VMware goes to create the first snapshot on the replica it can’t because the file it was going to create already existed.
• Replication job fails with “Invalid Snapshot Configuration,” and you are able to determine that the error is coming from the replica by checking the replicas Tasks & Events.
• Replication job fails “CID mismatch error: The parent virtual disk has been modified since the child was created,” and you are able to determine that the error is coming from the replica by checking the replicas Tasks & Events.

Cause

An old or orphaned Snapshot file is linked to the vmx, and a new Snapshot is trying to use that file name.

Solution

Please be aware that as an alternative to performing the steps below, you may first attempt to clone the faulty replica within VMware, if it succeeds map the Replication job to the clone of the replica.

Note: Prior to beginning:

• Stop all replication jobs to target location of the replica in question.
• Manually check each target side proxy for stuck replica hotadded disks. (Consider switching the target proxies to use Network transport mode to prevent this if it becomes a problem). See KB1775 for details.

I. Gather Information

1. Edit the Replica
2. Note what disk files correlate to each SCSI ID.
   Example:
   [Datastore1] DC01_replica\DC01-00000023.vmdk on SCSI0:0
   [Datastore1] DC01_replica\DC01_1-00000023.vmdk on SCSI0:1
   [Datastore2] DC01_replica\DC01-00000023.vmdk on SCSI0:2

II. Prepare the Replica

1. Open the Snapshot manager and starting with the oldest snapshot delete the snapshots one at a time. The intention here is to get as much new information in to the base disks as possible. At some point there will be a snapshot that will not remove.
2. If there are any snapshots left in the snapshot manager try using the Delete All option in snapshot manager.
3. Use the consolidate function to consolidate any orphaned snapshots.
   Note: that it is expected for these steps to fail at some point. When you receive a failure move on to the next step.

III. Preparing Veeam Backup & Replication

Within the Veeam console under Replicas find the replica that you will be repair and right-click it, from the context menu choose “Remove from replicas…” ("Remove from configuration")
After you use the “Remove from replicas…” ("Remove from configuration") function it will remove the VM from the Replication job. You will have to manually add the VM back to the replication job.

IV. Detach Snapshot Disks and Attach Base Disks

1. Edit the replica, and select each of the disks and click remove. It will put a strikethrough the drive and show the word (removing).
2. After selecting all the disks for removal, press OK.
3. Edit the replica again, now reattach the base disks to the replica, choose to add an existing disk and then navigate to the location of the base disks for the replica. Attach them to the same SCSI nodes that were noted earlier.
   When using the vSphere Web Client if you run into a disk that displays “0” as the disk size, it won’t let you remove that disk from the VM. In order to remove this disk, you need to add a size to the disk. The number that you input here does not matter. We just want to make sure the size of the disk no longer displays “0”. At this point, it will allow you to remove that disk.
   This does not apply to the vSphere Thick Client, as it already allows you to remove disks that display “0” as the disk size.

V. Datastore Cleanup

Using datastore browser go to the folder of the replica.

Most likely there will be many files, keep in mind that the only files that are required are:

• VMX
• VMXF
• NVRAM
• VMDK for each disk.

So for example here is a folder precleanup post repair.

We can remove the following files:

Leaving the VMX, VMXF, NVRAM, and the VMDK for each disk. Removing the associated snapshot files that are no longer needed.

VI. Test the replica

1. Create a snapshot on the replica.
2. Remove the snapshot.
3. If no error occurs, map to the replica in a replication job and see if the job runs successfully.

Challenge

This document contains information on how to use Microsoft© DiskSpd to simulate Veeam Backup & Replication disk actions to measure disk performance.

The test file created by DiskSpd does not contain any diagnostic information and must be removed manually after testing has concluded. All diagnostic information regarding the performance test is displayed in the command line. Please do not send the testfile.dat to support, as its contents will not help with troubleshooting.

DiskSpd and additional info can be found here: https://aka.ms/diskspd

Solution

More Information

Q: Can diskspd be used to stress-test NAS boxes for reliability ("specified network name is no longer available" errors in Veeam)
A: Unfortunately, no. If the SMB share disappears, diskspd will just ignore that issue. It is better to use Wireshark.



Q: Active full starts fast but then gradually becomes slower and slower. Target agent runs on Windows 2008 (not R2).
A: This is a known (yet undocumented) performance degradation issue on Windows 2008. Upgrade to or deploy 2008 R2 (or newer). In case of a CIFS repository you can force some other 2008 R2 server to be used as gateway/proxying. The issue itself can be demonstrated with diskspd if you set it to run for several hours, then observe how the write rate slowly goes down in Resource Monitor.

Q: I am getting extremely high I/O speed like 4 GB/s in any test I try, even though I have set the -Sh flag, what's going on?
A: Most likely you're running diskspd on a Hyper-V VM, testing performance of a virtualised (.vhdx) disk, so the data is cached by the Hyper-V host. Run the test on the datastore where that .vhdx is located instead.

Challenge

Product Information: 

Product Family: 3PAR 
Status: Veeam Ready - Integrated 
Classification Description: Integrated storage where joint development activities between the manufacturer and Veeam have occurred to create advanced backup or restore functionalities.

Solution

Product Details: 

Model number: All 
Number of Drives: Any 
Drive type: Any 
Firmware version: 3.1.2 - 3.3.1 
Additional support: Any 3PAR configuration with supported firmware 
General product family overview: HPE 3PAR StoreServ was built to meet the extreme requirements of massively consolidated cloud service providers. It’s remarkable speed—3M+ IOPS—and proven system architecture has been extended to transform mainstream midrange and enterprise deployments, with solutions from a few TBs up to more than 20PB scale.  

Veeam Details: 

Veeam Build Number: 9.5.0.823 

More Information

Company Information: 

Company name: Hewlett Packard Enterprise 
Company overview: HPE delivers high-quality, high-value products, consulting, and support services in a single package. That’s one of their principal differentiators. They have industry-leading positions in servers, storage, wired and wireless networking, converged systems, software, services and cloud.