Challenge

Cause

Solution

msiexec /update c:\VAC.ApplicationServer.x64_2.0.2.1807.msp /l*v C:\ProgramData\Veeam\Setup\Temp\VACApplicationServerSetup.txt

msiexec /update c:\VAC.ConnectorService.x64_1.0.0.254.msp /l*v C:\ProgramData\Veeam\Setup\Temp\VACConnectorServiceSetup.txt

More Information

Challenge

Cause

• Under certain conditions password in the SMTP server settings is reset
• Veeam Management Portal Service cannot be started after installing Update 1
• After deleting WAN accelerator component from the Veeam Cloud Connect inventory, records about backup resources available to the tenant might be duplicated

• Management agent RAM consumption might significantly increase when running computer discovery process

• After deploying Patch 1824 discovery rules cannot install backup agents to remote computers. To resolve this, install the latest patch and re-create all discovery rules.

• Sub-tenant’s password is reset when changing cloud quota in the assigned backup policy 

• After upgrading to Update 1, backup resources of the managed company cannot be adjusted when backup portal is running under heavy load. 

• Job name filtering is ignored in the job session state alarm.
• Storage snapshots are treated as a backup repository resulting in triggered alarms for the repository free space.
• Under certain conditions Computer with no backup alarm can send false-positive notifications
• “Item with the same key has already been added” message is displayed when opening the Managed Backup Servers tab in the UI

• Multiple email addresses cannot be specified in the Global Notification Settings

• Cloud repository quota usage may report incorrect values when Veeam Agent backups are sent to the cloud repository via backup copy jobs
• Under certain conditions Cloud replication quota usage is not displayed on the dashboard when logged in using managed company user account
• Management agent re-installation results in losing collected data about protected VMs from the managed backup server. This affects Overview dashboard and Protected VMs report that display zero protected VMs
• Overview dashboard and Protected VMs report can display zero protected VMs when using Veeam Cloud Connect 9.5 Update 3a
• After changing report scheduling settings, reports are sent out using the previous and the new time schedule

• Under certain conditions ConnectWise Manage configurations cannot be created.
• Under certain conditions not all products created in ConnectWise Manage are accessible for mapping when using the billing function.
• Companies data cannot be collected from ConnectWise Manage due to the following error "An item with the same key has already been added"
• Companies with multiple types cannot be collected from ConnectWise Manage  
• Product quantity in agreements might not be updated when VAC and Manage servers are located in different time zones 

Solution

msiexec /update c:\VAC.ApplicationServer.x64_2.0.2.1850.msp /l*v C:\ProgramData\Veeam\Setup\Temp\VACApplicationServerSetup.txt

msiexec /update c:\VAC.ConnectorService.x64_1.0.0.336.msp /l*v C:\ProgramData\Veeam\Setup\Temp\VACConnectorServiceSetup.txt

msiexec /update c:\VAC.ConnectorWebUI.x64_1.0.0.336.msp /l*v C:\ProgramData\Veeam\Setup\Temp\VACConnectorWebUI.txt

More Information

Challenge

Cause

New Features

• Veeam Backup & Replication 9.5 Update 4 along with the corresponding Veeam Explorer for Microsoft Exchange, Veeam Explorer for Microsoft SharePoint compatibility support.

• Veeam Cloud Connect 9.5 Update 4 compatibility support.

Resolved Issues

SharePoint Online and OneDrive for Business processing

• Slow backup processing which may finally be affected by throttling and may fail with the error 429.
• Backup of default system lists with versioning enabled may fail with the “Failed to request item versions for list: User Information List (list ID: {}). Access denied. You do not have permission to perform this action or access this resource” warning.
• Backup of an item with an attachment containing non-ASCII symbols in its file name may fail with the “File Not Found” error.
• Backup job runs for a long time with seemingly no progress and may fail with the “The underlying connection was closed” error.
• Backup of an item which content type is not defined (ContentTypeId is null) may fail on saving item’s version with the “JetError -1504, JET_errNullInvalid” error.

Exchange Online processing

• Adding group mailboxes to on-premises Microsoft Exchange 2010 backup jobs may fail with the following error: “Exception occurred while executing a task. Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "GroupMailbox" could not be converted to type Microsoft.Exchange.Data.Directory.Recipient.RecipientTypeDetails.” .

Restore

• A successfully backed up mailbox may not be visible during a restore session under certain conditions.
• SharePoint Online lists’ and libraries’ fields may not be restored for certain content types (i.e. “Comments” for “Document Sets”)
• SharePoint Online items with shared links may restore successfully, but the following error is shown upon completion in the restore session summary: “Object reference not set to an instance of an object on server. The object is associated with property File.”  
• Adding Microsoft Exchange database manually to the Veeam Explorer for Microsoft Exchange scope may fail with the “Value does not fall within the expected range” error.

Server

• Some restore points are not synced properly between a management server and a backup proxy after recreating/moving a corresponding repository.

Solution

1. Download VBO2.0-KB2809.msp.
2. Execute VBO2.0-KB2809.msp as administrator on the Veeam Backup for Microsoft Office 365 server.
3. Execute VeeamExplorerForExchange.msi as administrator on the on each machine where Veeam Explorer for Exchange is installed.
4. Execute VeeamExplorerForSharePoint.msi as administrator on the on each machine where Veeam Explorer for SharePoint is installed.

More Information

Challenge

Cause

Solution

Challenge

Cause

Solution

Challenge

You need to remove an existing Veeam Backup and Replication (VBR), Veeam Agent for Windows (VAW) or Veeam Agent for Linux (VAL) license from Veeam Backup and Replication (VBR) or Enterprise Manager (EM).

Cause

A license has to be removed from VBR/EM.

Solution

In order to determine which section of this article to use, you must know if Enterprise Manager is controlling the licenses within Veeam Backup & Replication. If you are unsure, attempting to change the license file within Veeam Backup & Replication will tell you. If it allows you to click the Install button within the license section without a message about Enterprise Manager then Enterprise Manager is not in use.

If licenses are managed by Enterprise Manager:

1. Open an administrative command prompt.
2. Navigate to the EM installation folder (default path in the example below):

   cd C:\Program Files\Veeam\Backup and Replication\Enterprise Manager

3. Remove the license by running

   Veeam.Backup.EnterpriseService.exe -removelicense [vaw, val]

4. After running this command, restart Veeam Backup Enterprise Manager service so that the license information is updated in the UI.

If licenses are managed by Veeam Backup & Replication

1. Open an administrative command prompt.
2. Navigate to the VBR installation folder (default path in the example below):

   cd C:\Program Files\Veeam\Backup and Replication\Backup

3. Remove the license by running

   Veeam.Backup.Manager.exe -removelicense [all, vbr, vaw, val]

More Information

Note:These commands can also be run from PowerShell.

Note: specify the desired parameter without brackets.

Example commands:

• To remove the Veeam Agent for Windows license from Veeam Enterprise Manager:

  Veeam.Backup.EnterpriseService.exe -removelicense vaw

• To remove Veeam Agent for Linux from Veeam Backup & Replication:

  Veeam.Backup.Manager.exe -removelicense val

If no parameter is specified, all existing licenses will be removed.

Challenge

Product Information:

Company name: Quest Software
Product Family: DR Series Appliance
Status: Veeam Ready - Tape
Classification Description: Tape solution where available hardware features have been tested to work with Veeam.

Solution

Product Details:

Model number: DR4300, DR4300e and DR6300
Library Firmware Version 0104
Drive firmware version: 0104
Driver for tape drive: 6.2.4.8
Driver for media changer: (Veeam Option: Use native SCSI commands instead of Windows driver)
Media type tested: DR-VTL
Additional Support:

General product family overview:
DR’s Virtual Tape Library (VTL) is an emulation of a physical tape library (SUN/STK L700) on a disk-based deduplication and compression system such as the DR Series system. The tape library is exposed to a Data Management Application (DMA) as if it is a physical library with tape drives and cartridges, which the application uses for backup.

Veeam testing configuration:

Veeam Build Number: 9.5.0.823

Vendor recommended configuration:

Vendor Settings:

• Changer gets detected as "Unknown Medium Changer" and it is supported for Veeam. Just need to change the changer properties in Veeam to use native SCSI commands.
• DR series system using iSCSI to access VTL
• IBM tape Drivers are mandatory to install for Drives and can be downloaded from IBM site: Driver name - IBMTape.x64_w12R2_6248_WHQL_Cert

Challenge

1. Veeam ONE 9.5 server may lose a connection to the SQL Server for runtime operations
2. Veeam ONE 9.5 server may lose a connection to the SQL Server during the initial installation
3. “Veeam Licensing” web server is unavailable when only TLS 1.2 protocol is enabled
4. Veeam ONE Reporter website doesn’t work when only TLS 1.2 protocol is enabled

Cause

Solution

More Information

Challenge

When performing a Bare Metal restore using Veeam Agent Recovery Media storage or network devices are not visible in the system. When you try to load a driver for the device an ERROR_NO_DEVICE_ID error is being received:

Solution

Make sure that the driver *.inf file is a correct one and has DEVICE_ID entries specific for your device. You can compare DEVICE_IDs by clicking “Show unknown devices” in the “Tools - Load Driver” window.

Close the “Load Driver” window, click “Command Prompt” and type

drvload path_to_your_driver_inf_file:

Challenge

Cause

Solution

There are several ways of applying the hotfix:

Using SQL Server Management Studio
 

1. Open Veeam ONE Monitor client and check the lower part of the window for the SQL instance name and Veeam ONE database name.

2. Open Microsoft SQL Server Management Studio with the Administrator permissions (may need to be installed separately KB1761).
3. Connect to the ServerName\Instance of the server that has the Veeam ONE database.
4. Expand the Databases tree and select "VeeamOne" database. 
5. Right-click on the database > New Query.

5. Copy the following query and run it against the database:

IF OBJECT_ID('monitor.[ENUM_CTVI_PV]', 'C') IS NOT NULL
  ALTER TABLE monitor.BpCloudTenantVersionInfo
   DROP CONSTRAINT [ENUM_CTVI_PV];​​

6. If the query was performed correctly, you will get the following status in the SQL Server Management Studio: Commands completed successfully.

1. Open Veeam ONE Monitor client and check the lower part of the window for the SQL instance name and Veeam database name.

2. Open Windows command line or PowerShell prompt using the Veeam ONE Service account and run the hotfix against the Veeam ONE database:
   for default instances (change the database name in the query if it differs from yours):

More Information

Challenge

Cause

Solution

More Information

More information regarding this workaround can be found here: https://forums.veeam.com/vmware-vsphere-f24/vsphere-6-7-u1-support-t54673.html

This is a temporary workaround against the specific error, which will allow the jobs to complete successfully. Overriding VMware API version may potentially cause issues with other Veeam functionality, because we don't know the specific API changes that made VMware increment the API version. We're working with VMware to obtain these details while continuing to test vSphere 6.7 U1 with the workaround applied.

The release vehicle for the official out-of-the-box support for vSphere 6.7 U1 will be our next release (Update 4). We'll be able to determine supportability of vSphere 6.7 U1 with the workaround applied after full regression testing cycle is done against the U1 GA code (usually takes 3-4 weeks).

All auto-tests of Update 3a with the workaround enabled have completed successfully, so all base Veeam Backup & Replication functionality is now confirmed to work with vSphere 6.7 U1. The forum post above will be updated once the full regression testing cycle completes.

Challenge

Cause

Solution

• remove the existing Veeam Agent backup job from jobs (right click > Delete)
• remove the backup files from configuration: right click Disk (backups) > Endpoint Backups > Remove from configuration. 

2. Place the backup chain into the required folder.

2.1 Example for a non-cloud repository

Backup files reside in C:\VeeamBackup\Backup Job 1 and need to be moved to a Veeam Backup & Replication repository into the following folder: C:\Backup.

Under C:\Backup you will need to create a folder named after the account that is used to access the repository. In this example, the account is DOMAIN1\user1, so the folder name would be DOMAIN1_user1.

The complete path to the backup files would be C:\Backup\DOMAIN1_user1\Backup Job 1

2.2 Example for a cloud repository

The backup files reside in C:\VeeamBackup\Backup Job 1 and need to be moved to a cloud Veeam repository into following folder: C:\Backup.

Under C:\Backup you will need to create a folder named after the tenant account that is used to access the repository. If the account name is Tenant2, the complete path to the backup files would be C:\Backup\Tenant2\Backup Job 1

If a subtenant is used with the account name Subtenant3, the path will be C:\Backup\Tenant2\users\Subtenant3\Backup Job 1

3. Rescan the Veeam Backup & Replication repository. Here is a brief guide on repository rescan. 
Note: For backups that you are mapping to cloud, rescan the repository hosting the tenant backups on the provider side.

4. The Veeam Agent backup should appear under Disk > Imported.
Note: When a backup chain is mapped to cloud, it will not be displayed under Disk > Imported.

5. Point the Veeam Agent job to the required Veeam Backup & Replication repository. Do not run it immediately, just close the wizard after making the changes.

6. On the Veeam Backup & Replication machine, the backup should be moved from the Imported section to Backup > Disk. Make sure that backups are located in Backups > Disks (not Disk (imported)).

7. Run the Veeam Agent backup job. It should continue the imported backup chain.

Note: The described solution works for Veeam Backup & Replication repository and Veeam Cloud Connect repository.

More Information

1. Map the backup to a simple VBR repository.
2. Run said backup.
3. Add the simple repository to the SOBR repository (make sure VBR processed the existing backup to SOBR extent – as an indication, you will be prompted for it with a special message first and by the end of the process SOBR’s extents will have job’s VBM).
4. Put a new SOBR extent into maintenance mode and evacuate all the backups from it. This procedure will place the existing temporary repository’s backup to other active extents.
5. Change the backup job configuration on the VAW side to the SOBR repository and then check the backup from there.

1. Create two identical VAC backup policies – one for a local backup and one for a cloud backup
2. Apply the Local policy to the desired machine. You can find how to apply a policy here
3. Let the Local Policy Job run to its desired location. In our example, that is “E:\VeeamBackup” and under this folder will be a new folder named “Backup Job <Hostname>”.
4. Apply the Cloud Policy *NOTE: It is important to only apply the policy at this step*. After the policy applies, a folder will be created on the cloud repository for the machine under the tenant folder. The final folder path will be <Default Repository Path>\<Tenant account>\Users\<Tenant Account>_<Hostname>. For example, in our test we are going to the default repository with the path of C:\Backup, using a tenant account named “test”, and the machine name is AgentHostname, so the final path will be: C:\Backup\test\Users\test_AgentHostname
5. Copy the local backups “Backup Job <Hostname” to the Cloud folder made in the previous step “<Default Repository Path>\<Tenant account>\Users\<Tenant Account>_<Hostname>” to end up with a final path of “<Default Repository Path>\<Tenant account>\Users\<Tenant Account>_<Hostname>\Backup Job <Hostname>”. For subtenant-based policy - C:\Backup\[TenantName]\Users\[SubtenantName]\Backup job [CompName], for tenant-based policy - C:\Backup\[TenantName]\Backup job [CompName]
6. Rescan the Veeam Backup & replication repository hosting the tenant backups on the provider side. Here is a brief guide on repository rescan
7. On the Backup Agent machine, delete the local backup that we made with the local policy
8. Begin the backup to the Cloud Repository, run the job on Agent site (if VAC account related issue occurs - restart VAC Management Agent Service on Tenant site);

Challenge

Cause

Solution

More Information

More information regarding this workaround can be found here: https://forums.veeam.com/vmware-vsphere-f24/vsphere-6-7-u1-support-t54673.html

This is a temporary workaround against the specific error, which will allow the jobs to complete successfully. Overriding VMware API version may potentially cause issues with other Veeam functionality, because we don't know the specific API changes that made VMware increment the API version. We're working with VMware to obtain these details while continuing to test vSphere 6.7 U1 with the workaround applied.

The release vehicle for the official out-of-the-box support for vSphere 6.7 U1 will be our next release (Update 4). We'll be able to determine supportability of vSphere 6.7 U1 with the workaround applied after full regression testing cycle is done against the U1 GA code (usually takes 3-4 weeks).

All auto-tests of Update 3a with the workaround enabled have completed successfully, so all base Veeam Backup & Replication functionality is now confirmed to work with vSphere 6.7 U1. The forum post above will be updated once the full regression testing cycle completes.

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:

%Programdata%\veeam\endpoint (This folder is hidden by default, please copy, paste provided path and archive this folder)

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

• Restoring single lost DC in a multi-DC environment
• Restoring entire AD infrastructure (AKA “all DC’s are lost”)
• Restoring from Active Directory corruption

Solution

• Start the Registry Editor 
• Navigate to "HKLM\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup" 
• Double-click on "BurFlags" 
• Assign it a value of D4 (hex) or 212 (dec) 
• Stop the NTFRS Service 
• Start the NTFRS Service 

• REG ADD "HKLM\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup" /v BurFlags /t REG_DWORD /d 212 /f 
• NET STOP NTFRS 
• NET START NTFRS 

More Information

Challenge

Solution

• Solution 1:
  In some instances, you may receive this error when permissions are not correctly set. To confirm, please follow the steps outlined in the following KB article to test ports, permissions, and DNS resolution
  http://www.veeam.com/kb1198

• Solution 1:
  https://www.veeam.com/kb1054
  VMware Tools must be installed and up-to-date on the Veeam server and any Veeam proxies
   
• Solution 2:
  https://www.veeam.com/kb1775
  Stuck Hotadded Disks – Review all virtual proxies for disks attached that do not belong to the VM in question, remove the disks not owned by this VM without deleting from the datastore. Once deleted, consolidate snapshots on the affected VMs.
   
• Solution 3:
  kb.vmware.com/kb/2003638
  Orphaned Snapshots – Consolidate snapshots on affected VMs
   
• Solution 4:
  http://www.veeam.com/kb1875
  Permissions - Please configure the account leveraged to access the vCenter as an Administrator within vCenter
   
• Solution 5:
  http://www.veeam.com/kb1882
  Automount – In some cases, it may be necessary to perform an automount scrub to clear any existing mount points that are no longer in the system.
  
  Run the following via CMD Prompt on the proxy server:
  diskpart
  automount disable
  automount scrub
  exit
   
• Solution 6:
  http://www.veeam.com/patches.html
  Patching – Please ensure that all VMware and Veeam components are fully up to date.
   
• Solution 7:
  In some rare instances, performing a storage vMotion has been known to resolve the issue due to a locked VM file on the datastore where the VM files reside.
   
• Solution 8:
  In some rare instances, restarting the vCenter appliance or alternatively restarting the ESXi management agents (https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003490) may yield positive results if all above testing does not resolve the issue.
   
• Solution 9:
  Veeam Proxy has a Veeam replica with the same bios UUID within the vCenter Server. The following can be observed in 
  
  Job.Job_name.log:
  [time stamp] < threadID> Info VM VeeamProxy _replica(vm-100001) has the same bios uuid as proxy VeeamProxy.local in the DB
  
  Agent.Job_name.VM_name.Hotadd.Attacher.log:
  [time stamp] < threadID> vdl| [vddk] time stamp  error -[07132] [Originator@6876 sub=transport] Cannot use mode hotadd to access [datastore_name] VM_name/VM_name.vmdk: Cannot mount using this method. (Mounting VM vm-101 using transport hotadd failed : Cannot access datastore for one of the disks of Virtual Machine VM_name..)
  
  The behavior is observed when a Veeam Proxy is replicated with Veeam B&R, the replication process preserves the original VM bios UUID for restore purposes. To work around the issue setup a dedicated VM as a Veeam Proxy, replicating Veeam Proxies is not usually necessary due to ease of deployment.

• Solution 10:

More Information

• Manual Hotadd - http://www.veeam.com/kb1184
• Hotadd Requirements - http://www.veeam.com/kb1054
• Deploy an additional standalone proxy to isolate failures to a single specified proxy
• To isolate a specific transport mode as the point of failure, you may also test the other transport modes to ensure that connectivity is correctly established and backup jobs work as intended via the other transport mode.

Challenge

• Unexpected End of File
• Exchange Web Services error code: ErrorExceededConnectionCount
• Error: Failed to get folder properties
• Error: You have exceeded the available concurrent connections for your account.  Try again once your other requests have completed.
• Error: Unexpected end of file has occurred. The following elements are not closed: m:Data, m:ExportItemsResponseMessage, m:ResponseMessages, m:ExportItemsResponse, s:Body, s:Envelope. Line 1, position 21397505.

Cause

Solution

Challenge

Solution

• Solution 1:
  In some instances, you may receive this error when permissions are not correctly set. To confirm, please follow the steps outlined in the following KB article to test ports, permissions, and DNS resolution
  http://www.veeam.com/kb1198

• Solution 1:
  https://www.veeam.com/kb1054
  VMware Tools must be installed and up-to-date on the Veeam server and any Veeam proxies
   
• Solution 2:
  https://www.veeam.com/kb1775
  Stuck Hotadded Disks – Review all virtual proxies for disks attached that do not belong to the VM in question, remove the disks not owned by this VM without deleting from the datastore. Once deleted, consolidate snapshots on the affected VMs.
   
• Solution 3:
  kb.vmware.com/kb/2003638
  Orphaned Snapshots – Consolidate snapshots on affected VMs
   
• Solution 4:
  http://www.veeam.com/kb1875
  Permissions - Please configure the account leveraged to access the vCenter as an Administrator within vCenter
   
• Solution 5:
  http://www.veeam.com/kb1882
  Automount – In some cases, it may be necessary to perform an automount scrub to clear any existing mount points that are no longer in the system.
  
  Run the following via CMD Prompt on the proxy server:
  diskpart
  automount disable
  automount scrub
  exit
   
• Solution 6:
  http://www.veeam.com/patches.html
  Patching – Please ensure that all VMware and Veeam components are fully up to date.
   
• Solution 7:
  In some rare instances, performing a storage vMotion has been known to resolve the issue due to a locked VM file on the datastore where the VM files reside.
   
• Solution 8:
  In some rare instances, restarting the vCenter appliance or alternatively restarting the ESXi management agents (https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003490) may yield positive results if all above testing does not resolve the issue.
   
• Solution 9:
  Veeam Proxy has a Veeam replica with the same bios UUID within the vCenter Server. The following can be observed in 
  
  Job.Job_name.log:
  [time stamp] < threadID> Info VM VeeamProxy _replica(vm-100001) has the same bios uuid as proxy VeeamProxy.local in the DB
  
  Agent.Job_name.VM_name.Hotadd.Attacher.log:
  [time stamp] < threadID> vdl| [vddk] time stamp  error -[07132] [Originator@6876 sub=transport] Cannot use mode hotadd to access [datastore_name] VM_name/VM_name.vmdk: Cannot mount using this method. (Mounting VM vm-101 using transport hotadd failed : Cannot access datastore for one of the disks of Virtual Machine VM_name..)
  
  The behavior is observed when a Veeam Proxy is replicated with Veeam B&R, the replication process preserves the original VM bios UUID for restore purposes. To work around the issue setup a dedicated VM as a Veeam Proxy, replicating Veeam Proxies is not usually necessary due to ease of deployment.

• Solution 10:

More Information

• Manual Hotadd - http://www.veeam.com/kb1184
• Hotadd Requirements - http://www.veeam.com/kb1054
• Deploy an additional standalone proxy to isolate failures to a single specified proxy
• To isolate a specific transport mode as the point of failure, you may also test the other transport modes to ensure that connectivity is correctly established and backup jobs work as intended via the other transport mode.

Challenge

Product Information:

Company name: QNAP Systems, Inc
Product Family: TS-x32XU series
Status: Veeam Ready – Archive
Classification Description: Verified disk archive storage that can be used as a Backup Copy target. Synthetic full backups, granular restores, and vPower features may not provide sufficient performance or be supported.

Solution

Product Details:

Model number: TS-1232XU-RP
Storage Category: RAID Storage Array
Drive quantity, size, type: 12- 4TB SATA HDD
Storage configuration: RAID6
Firmware version: 4.3
Connection protocol and speed: SMB, 10 GbE
Additional support: All models and configurations of TS-x32XU with specifications equivalent or greater than the above

The TS-1232XU-RP is built to deliver high performance, flexible expansion capabilities and versatile applications at an affordable and cost-effective price for small/medium-sized businesses. Two 10GbE SFP+ ports are capable of high-speed transmission of time-critical business data and a PCI Express (PCIe) 2.0 ×2 slot (×4 length) provides flexibility for expanding connectivity and/or storage with M.2 SATA/PCIe NVMe SSDs, via QNAP's QM2 expansion cards. The TS-1232XU-RP is also equipped with a redundant power supply to ensure uninterrupted services.

Veeam testing configuration:

Veeam Build Number: 9.0.0.1922

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings:

• Array compression used during testing – no
• Array deduplication used during testing – no
• Jumbo frames used during testing (MTU=9000)

Challenge

Product Information:

Company name: QSAN Technology, Inc.
Product Family: XCubeNAS XN8000
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: XN8012R
Storage Category: Hybrid RAID Storage
Drive quantity, size, type: 4 – 2TB SSD
Storage configuration: RAID5
Firmware version: QSM 3.1.1
Connection protocol and speed: iSCSI, 10 GbE
Additional support: All models and configurations of XCubeNAS XN8000 with specifications equivalent or greater than the above

QSAN Storage Manager 3 (QSM 3) is a NAS operation system specially designed for QSAN XCubeNAS series. The core of QSM is Linux kernel and in-house fine-tuning 128-bit ZFS. The ZFS has high scalability and can be managed easily, also with the ability to maintain the data integrity. QSM 3 not only inherits the amazing native features of ZFS, its powerful storage features ensure persistent, reliable storage management, protection against data corruption, seamless capacity expansion, several data integrity mechanisms, pool and disk encryption protection, unlimited snapshots, and unlimited clones.

Veeam testing configuration:

Veeam Build Number: 9.0.0.1922

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings:

• Array deduplication used in testing – No
• Array compression used in testing – Yes