Challenge

Cause

Solution

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

More Information

Cause

Solution

Customizing synchronization intervals between ConnectWise plug-in and Veeam Availability Console:

On the Veeam Availability Console server:

1. Open Windows registry editor snap-in and navigate to the following registry path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\VAC\ConnectWiseManage
2. Create a new registry key and set preferable synchronization interval:

Name:  VacCompanySyncPeriodMin
Type:   String
Purpose: Companies synchronization interval
The default value (minutes):  5

Name:  VacStoredObjectsPeriodMin
Type:   String
Purpose: Configuration (VAC Agents) and tickets synchronization interval
The default value (minutes):  5

Name:  VacBillingPeriodMin
Type:   String
Purpose: Subscription plans synchronization interval
The default value (minutes):  5

3. Restart Veeam Availability Console service to apply the changes:
 

Customizing synchronization intervals between ConnectWise Manage and ConnectWise plug-in:

On the Veeam Availability Console server:

1. Open Windows registry editor snap-in and navigate to the following registry path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\VAC\ConnectWiseManage
2. Create a new registry key and set preferable synchronization interval:

Name:  IntegratorCompanySyncPeriodMin
Type:   String
Purpose: Companies synchronization interval
The default value (minutes):  240

Name:  IntegratorBillingPeriodMin
Type:   String
Purpose: Billing synchronization interval
The default value (minutes):  240

Name:  ServiceBoardsPeriodMin
Type:   String
Purpose: Alarms and configurations synchronization interval
The default value (minutes):  240

3. Restart Veeam Availability Console service to apply the changes:

NOTE: It is not recommended to set the low synchronization intervals in order not to cause high Veeam Availability Console service load.

More Information

Challenge

Product Information:

Product Family: EonStor GS
Status: Veeam Ready - Repository 
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: GS 1000 Gen 2 - GS1016R2C0F0D-0032
Storage Category: Hybrid RAID Storage Array (SAN/NAS)
Drive quantity, type, size, : 16, NL-SAS, 10TB
Storage configuration: RAID5 configured storage pool with 8GB controller cache (12Gb/s SAS connectivity)
Firmware version: 133H02
Connection protocol and speed: 1 X 10 GbE (SMB)
Additional support: All models and configurations of EonStor GS with specifications equivalent or greater than the above. This includes:

• EonStor GS 1000 Series (1012, 1016, 1024, 1024B)
• EonStor GS 2000 Series (2012, 2016, 2024, 2024B)
• EonStor GS 3000 Series (3012, 3016, 3024, 3024B, 3025B, 3060)
• EonStor GS 4000 Series (4016, 4024B)
• EonStor GS 5000 Series (5100, 5200)

Veeam testing configuration:

Veeam Build Number: 9.5.0.1536
Veeam Settings:

• Repository Type: Shared Folder
• Deduplication: Yes
• Compression: Optimal
• Storage Optimization: LAN Target
• Per-VM Backup Files: Yes
• Decompress before storing: No
• Align backup file blocks: No

Vendor recommended configuration:

Vendor Settings:

• Read-ahead option for NAS file transfer: 1M

More Information

Company Information:

Company name: Infortrend Technology, Inc.
Company overview: Infortrend stands as one of the few fully integrated technology firms in the world to be completely dedicated to storage systems as well as related software and services. We research, design, and manufacture our products in-house with complete control over the entire process, leveraging leading expertise in engineering, industrial design, manufacturing and service.

Infortrend places great emphasis on providing customers with choice and flexibility, with a product range that meets diverse needs – from those of small businesses to large-scale big data applications including the ever-increasing demands of cloud computing and virtualization infrastructures.

Our attention to details and customer care translate into products that are carefully balanced and optimized to offer the finest performance, dependability, and ease of access.

Challenge

Cause

Solution

• VMware vSphere 6.7 support. Includes the new HTML5 version of vSphere Web Client plug-in for Veeam Backup & Replication, and asynchronous NBD/NBDSSL support for improved read performance of network transport mode with ESXi 6.7.
• VMware vSphere 6.5 U2 preliminary support. This update addresses all outstanding U2-specific compatibility issues that can be managed from the Veeam side. However, there is a major regression in ESXi 6.5 U2 code that makes the vSphere API fail randomly during high host CPU load periods, consequently impacting a variety of Veeam Backup & Replication functionality. VMware is currently troubleshooting this bug, and fixing one will most likely require the new ESXi 6.5 U2 build issued.
• VMware vCloud Director 9.1. Update 3a provides compatibility for existing vCloud Director support functionality.
• VMware Cloud on AWS version 1.3 support and preliminary out-of-the-box compatibility with future VMC updates through removal of the API version match requirement.
• Microsoft Windows 10 April 2018 Update. Includes support as guest virtual machines and for installation of Veeam Backup & Replication and all of its components.
• Microsoft Windows Server 1803. Update 3a provides Windows Server 1803 support as guest virtual machines, for installation of Veeam Backup & Replication remote components, and as a domain controller for Veeam Explorer™ for Microsoft Active Directory.
• Microsoft Windows Server Hyper-V 1803. Update 3a provides Hyper-V 1803 support as a hypervisor host, including support for processing VMs with virtual hardware version 8.3.
• Microsoft System Center Virtual Machine Manager 1801 support.

• Performance of Direct Storage Access (DirectSAN) and Virtual Appliance (Hot Add) transport modes has been improved for backup infrastructure configurations through optimizing system memory interaction.

• Added support for Direct Restore to Microsoft Azure for environments with ExpressRoute or site-to-site VPN connectivity to Azure, in which case proxy and helper appliances may have private IP addresses only. To enable, create AzurePreferPrivateIpAddressesForProxyandLinuxAppliance (DWORD, 1) registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key on the backup server.

• Added support for Linux SUID and SGID preservation to "Copy To" operation.
• Added support for Btrfs volumes located on an LVM volume.

• Installing Universal Storage API plug-ins on each backup console (in addition to the backup server) is no longer required.
• Storage snapshot-only vCloud Director backup jobs are now supported for all storage integrations which support storage snapshot-only jobs. Previously, it was supported for NetApp only.
• Cisco HyperFlex integration will no longer delete the base sentinel snapshot during each job run to improve processing performance and reduce storage load.

• Improved performance of enumeration in File to Tape jobs with very large number of files.

• User interface performance has been improved for large environments, including faster VM search and lower CPU consumption while browsing through job sessions history.
• Restores through Direct NFS transport should no longer produce corrupted VMDKs on storage devices with advanced NFS server implementations.
• VeeamZIP™ operations should no longer consume a license.
• Backup copy job should no longer trigger health checks outside of the scheduled start time when GFS retention is in use, and will behave more reliably in a few corner cases.
• Incremental backup runs should no longer keep setting ctkEnabled VM setting to "true", resulting in unwanted events logged by vCenter Server.
• SATA X:7 disks should no longer be skipped with backup jobs by default.
• Windows file level recovery (FLR) should now process large numbers of NTFS reparse points faster and more reliably.
• Linux FLR should now correctly process directories with . and \ symbols in their names. In addition, encountering a named pipe object should no longer cause FLR to hang.
• Direct Restore to Microsoft Azure should now process Linux machines with EFI boot more reliably.
• Veeam Agent for Microsoft Windows’ jobs should no longer fail when the backup server uses custom certificate.
• Veeam Explorer for Storage Snapshots now supports VMs located on LUNs larger than 16TB.
• An HPE 3PAR integration should now handle large number of concurrent jobs more reliably, thanks to multiple improvements implemented based on support cases.
• An HPE StoreOnce Catalyst SDK host process will now be restarted automatically when a Catalyst API call hangs, preventing Veeam jobs from hanging as a result.
• IBM SVC integration should no longer fail at collecting iSCSI adapters.

More Information

Challenge

This document lists registry values mentioned in other public documents, with either usage information or links to those documents. This is not a comprehensive list of all registry values in Veeam Backup & Replication, because some values should not be altered, or should only be altered with assistance from Veeam Support.

Some values are added or changed in each update, so some values will not be present in older versions of the product. Some values may no longer be as relevant in the current version as when they were created, but complete removal from the product is unusual.

Solution

Most values should only be altered in the specific circumstances described in a knowledge base, other linked articles, or with assistance from Veeam Support.  

In most cases, the registry value will not be present, and will need to be created under the specified key; the default value represents the behavior of the product when the registry value does not exist. In some cases, the key containing the value will also need to be created. All numeric values are in decimal unless otherwise noted.

For most registry values, restart the Veeam Backup Service to apply changes. Make sure no jobs or restores are running before restarting services.

For ease of navigation, you may select a section to view:

• General
• MS SQL & Oracle
• Hyper-V
• Tape
• VMware

General

BackupCopyLookForward

Originally published in What’s New in v8.
Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Type: DWORD
Default Value: 0 (Disabled)
Description: If you do not want backup copy jobs to transfer the latest point after each restart, set this to 1 to only look for restore points newer than the start time.

BlockSnapshotThreshold

Currently in Veeam Backup & Replication Best Practices. Originally published in What’s New in v9. This applies to both VMware and Hyper-V.

BodyPayloadCompressionDisabled

See Veeam Backup & Replication Best Practices

CloudReplicaNoStaticIpSDetectedWarning

See Veeam Cloud Connect Administrator Guide

ConnectByIPsTimeoutSec

See KB1976

CorePath

See KB2086

DataMoverLocalFastPath

Originally published in Release Notes for Veeam Backup & Replication 8.0 Patch 1. Beginning in v8 Update 2, the feature is no longer experimental, so the default has changed from 0 to 2.

DefaultCASServer

See Release Notes for Veeam Backup & Replication 9.0 Update 2

DisablePublicIPTrafficEncryption

See KB2055 and Veeam Backup & Replication Best Practices

DisableVBKRename

See KB1076

EnableRestoreSNMPTraps

See Release Notes for Veeam Backup & Replication 8.0 Update 2b

ForceDeleteBackupFiles

See KB1154

HashRepositoryBasePath and HashRepositoryGlobalDedupBasePath

See KB1828

IgnoreFileDeletionErrorInRetention

See KB1358

InfrastructureCacheExpirationSec

Originally published in What’s New in v9.
Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Type: DWORD
Default Value: 900 (15 minutes)
Description: To remove the wait time for virtual infrastructure objects to be loaded, the user interface now uses an infrastructure cache in certain places, such as in the Backup Job wizards and in the Virtual Machines tab.

MaxPerlSoapOperationTimeout

See KB1176

NetUseShareAccess

See KB1735

PayloadChecksumsDisabled

See Veeam Backup & Replication Best Practices

PostJobScriptTimeoutSec

Originally published in What’s New in v8.
Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Type: DWORD
Default Value: 900 (15 minutes)
Description: Execution timeout for scripts run after a job.

PreJobScriptTimeoutSec

Originally published in What’s New in v8.
Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Type: DWORD
Default Value: 900 (15 minutes)
Description: Execution timeout for scripts run before a job.

Remoting_MachineName and Remoting_UseIPAddress

See KB2098

remotingTimeout

See KB1237 and KB2166

RootFolder

See KB1094 and Veeam Backup & Replication Best Practices

ShowSplashScreen

Originally published in What’s New in v8.
Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Type: DWORD
Default Value: 1 (enabled)
Description: To hide the splash screen that appears while the console is loading, set this value to 0.

SqlDatabaseName, SqlInstanceName, and SqlServerName

Mentioned in KB1109, KB1250, KB1443, KB1448, and KB1471.
The DBConfig utility largely replaces any need to manually alter these values.

SshFingerprintCheck

See Release Notes for Veeam Backup & Replication 9.0 Update 1

UseLowBandwithMode

See Veeam Backup & Replication Best Practices

VBRCatalog

Mentioned in KB1453, KB1999, and KB2139.

VdkMaxDisksNum

See KB1772

VSSGuestSnapshotTimeout

See Release Notes for Veeam Backup & Replication 9.0 Update 1

WanRootCachePath

See KB1828

MS SQL & Oracle

DisableOracleProcessing

See Release Notes for Veeam Backup & Replication 9.0 Update 1

EnableDBExclusions

See KB1051

IscsiMountFsCheckRetriesCount

See Release Notes for Veeam Backup & Replication 9.0 Update 2

OracleSkipNoArchiveLogDB

See Release Notes for Veeam Backup & Replication 9.0 Update 1

OracleTempLogPath

See KB2093

SqlBackupDatabasesToSkip and delimiters

See KB2104 or Backup and Restore of SQL Server Databases

SqlBackupLogsAgeDaysToSkipLogBackup and SqlBackupLogsAgeDaysToSkipTruncate

See KB2029

SqlExecTimeout

See KB2027

SqlTempLogPath

See Backup and Restore of SQL Server Databases

Debug Log

For LoggingLevel, see KB1247. For all other values, see KB1825.

Hyper-V

CutHvVmSecuritySettings

See KB2021

EnableHvVDK

Originally published in What’s New in v8.
Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Type: DWORD
Default Value: 1 (enabled)
Description: By default, the Veeam VDK driver is used to mount VM disks for file level restore. To use the native Hyper-V disk mount driver instead, set this value to 0. Prior to v8 Update 2, this must be set to 0 to mount native 4K disks. In the current version, this setting is only useful for isolation troubleshooting.

HvDelayBeforeSnapshotImportCompleteSec

See KB1844

MaxVmCountOnHvHardSnapshot

Originally published in What’s New in v8.
Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Type: DWORD
Default Value: 8
Description: For reliability reasons caused by Hyper-V backup architecture, when a hardware VSS provider is used the maximum amount of VMs per snapshot is limited to eight by default. This value can be increased on fast storage, or decreased for troubleshooting purposes. See also “Allow processing of multiple VMs with a single volume snapshot” in the user guide.

MaxVmCountOnHvSoftSnapshot

Originally published in What’s New in v8.
Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Type: DWORD
Default Value: 4
Description: For reliability reasons caused by Hyper-V backup architecture, when a software VSS provider is used the maximum amount of VMs per snapshot is limited to four by default. This value can be increased on fast storage, or decreased for troubleshooting purposes. See also “Allow processing of multiple VMs with a single volume snapshot” in the user guide.

UIShowAllVssProvidersForVolume

See KB1861

Tape

DisableTapeSubsystem

See KB1816. Originally published in Veeam Backup & Replication 7.0 R2 update.

TapeDevices

See KB1842

TapeDeviceWatcherTimeoutSec

See KB1887

TapeIgnoreReturnMediaToOriginalSlot

See KB1943

VMware

DisableAutoSnapshotConsolidation

See KB2091

EagerZeroedDiskRestore

Originally published in What’s New in v9.
Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Type: DWORD
Default Value: 1 (enabled)
Description: In 8.0, the Direct SAN restore process creates lazy zeroed disks. In 9.0, Direct SAN restore instead creates eager zeroed disks, since this was found to improve performance in most cases. To create lazy zeroed disks in full VM restore in version 9.0, set this value to 0.

EnableSameHostDirectNFSMode

See Veeam Backup & Replication Best Practices

EnableSameHostHotaddMode

See KB1681 and Veeam Backup & Replication Best Practices

InverseVssProtocolOrder

See Veeam Backup & Replication Best Practices. Also mentioned in KB1230. Originally published in Patch 1 Release Notes for Veeam Backup & Replication 6.1.0.181.

IrMountLeaseTimeOut

See KB2166. Originally published in Veeam Backup & Replication 7.0 R2 update.

IrVcdMountLeaseTimeOut

See KB2166. Originally published in Veeam Backup & Replication 7.0 R2 update.

MaxSnapshotsPerDatastore

See Veeam Backup & Replication Best Practices. Originally published in Veeam Backup & Replication 7.0 R2 update.

MountLeaseTimeOut

See KB1237

NetAppOrderedIPList

See Release Notes for Veeam Backup & Replication 8.0 Update 2b

RemoveBiosUuid

Originally published in What’s New in v8.
Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\Surebackup\
Type: DWORD
Default Value: 0 (disabled)
Description: SureBackup jobs can automatically remove BIOS UUID from the VMX file of tested VMs to prevent problems with VMware SRM and similar tools that track VMs using this parameter. To enable UUID removal, set this value to 1.

RemoveVmSnapshot

See User Guide for VMware vSphere

ResetCBTOnDiskResize

See KB1940

SanMonitorTimeout and SanRescan_Periodically_Days

See Veeam Backup & Replication Best Practices

StrictDatastoreScope

See Release Notes for Veeam Backup & Replication 9.0 Update 1

VDDKLogLevel

See Veeam Backup & Replication Best Practices

ViHostConcurrentNfcConnections

See Veeam Backup & Replication Best Practices

vixExecutionTimeoutSec and vixOperationTimeoutSec

See Veeam Backup & Replication 7.0 R2 update

VssOtherGuest

See KB1062

VssPreparationTimeout

See KB1377

Challenge

Cause

Solution

• VMware vSphere 6.7 support. Includes the new HTML5 version of vSphere Web Client plug-in for Veeam Backup & Replication, and asynchronous NBD/NBDSSL support for improved read performance of network transport mode with ESXi 6.7.
• VMware vSphere 6.5 U2 preliminary support. This update addresses all outstanding U2-specific compatibility issues that can be managed from the Veeam side. However, there is a major regression in ESXi 6.5 U2 code that makes the vSphere API fail randomly during high host CPU load periods, consequently impacting a variety of Veeam Backup & Replication functionality. VMware is currently troubleshooting this bug, and fixing one will most likely require the new ESXi 6.5 U2 build issued.
• VMware vCloud Director 9.1. Update 3a provides compatibility for existing vCloud Director support functionality.
• VMware Cloud on AWS version 1.3 support and preliminary out-of-the-box compatibility with future VMC updates through removal of the API version match requirement.
• Microsoft Windows 10 April 2018 Update. Includes support as guest virtual machines and for installation of Veeam Backup & Replication and all of its components.
• Microsoft Windows Server 1803. Update 3a provides Windows Server 1803 support as guest virtual machines, for installation of Veeam Backup & Replication remote components, and as a domain controller for Veeam Explorer™ for Microsoft Active Directory.
• Microsoft Windows Server Hyper-V 1803. Update 3a provides Hyper-V 1803 support as a hypervisor host, including support for processing VMs with virtual hardware version 8.3.
• Microsoft System Center Virtual Machine Manager 1801 support.

• Performance of Direct Storage Access (DirectSAN) and Virtual Appliance (Hot Add) transport modes has been improved for backup infrastructure configurations through optimizing system memory interaction.

• Added support for Direct Restore to Microsoft Azure for environments with ExpressRoute or site-to-site VPN connectivity to Azure, in which case proxy and helper appliances may have private IP addresses only. To enable, create AzurePreferPrivateIpAddressesForProxyandLinuxAppliance (DWORD, 1) registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key on the backup server.

• Added support for Linux SUID and SGID preservation to "Copy To" operation.
• Added support for Btrfs volumes located on an LVM volume.

• Installing Universal Storage API plug-ins on each backup console (in addition to the backup server) is no longer required.
• Storage snapshot-only vCloud Director backup jobs are now supported for all storage integrations which support storage snapshot-only jobs. Previously, it was supported for NetApp only.
• Cisco HyperFlex integration will no longer delete the base sentinel snapshot during each job run to improve processing performance and reduce storage load.

• Improved performance of enumeration in File to Tape jobs with very large number of files.

• User interface performance has been improved for large environments, including faster VM search and lower CPU consumption while browsing through job sessions history.
• Restores through Direct NFS transport should no longer produce corrupted VMDKs on storage devices with advanced NFS server implementations.
• VeeamZIP™ operations should no longer consume a license.
• Backup copy job should no longer trigger health checks outside of the scheduled start time when GFS retention is in use, and will behave more reliably in a few corner cases.
• Incremental backup runs should no longer keep setting ctkEnabled VM setting to "true", resulting in unwanted events logged by vCenter Server.
• SATA X:7 disks should no longer be skipped with backup jobs by default.
• Windows file level recovery (FLR) should now process large numbers of NTFS reparse points faster and more reliably.
• Linux FLR should now correctly process directories with . and \ symbols in their names. In addition, encountering a named pipe object should no longer cause FLR to hang.
• Direct Restore to Microsoft Azure should now process Linux machines with EFI boot more reliably.
• Veeam Agent for Microsoft Windows’ jobs should no longer fail when the backup server uses custom certificate.
• Veeam Explorer for Storage Snapshots now supports VMs located on LUNs larger than 16TB.
• An HPE 3PAR integration should now handle large number of concurrent jobs more reliably, thanks to multiple improvements implemented based on support cases.
• An HPE StoreOnce Catalyst SDK host process will now be restarted automatically when a Catalyst API call hangs, preventing Veeam jobs from hanging as a result.
• IBM SVC integration should no longer fail at collecting iSCSI adapters.

More Information

Challenge

Cause

Solution

• Linux user account used by Veeam Backup and Replication server for any Veeam Agent for Linux deployment and management operations must have /bin/bash shell set by default.
• /etc/sudoers file should contain a line with ‘requiretty’ parameter negated explicitly for desired Linux user account
• The account must have either ‘root’ permissions or permissions to execute a specific list of commands as a sudoer on the target Linux machine.

Defaults:username !requiretty


# Protection Group Rescan
username ALL=(root) NOPASSWD: /bin/hostname
username ALL=(root) NOPASSWD: /bin/uname
username ALL=(root) NOPASSWD: /bin/arch
username ALL=(root) NOPASSWD: /bin/cat
username ALL=(root) NOPASSWD: /usr/bin/test
username ALL=(root) NOPASSWD: /usr/mkdir
username ALL=(root) NOPASSWD: /usr/rmdir
username ALL=(root) NOPASSWD: /usr/chown
username ALL=(root) NOPASSWD: /tmp/*/usernameid
username ALL=(root) NOPASSWD: /usr/bin/scp
 
# Agent config/backup
username ALL=(root) NOPASSWD: /usr/bin/veeamconfig
 
# Agent deployment
username ALL=(root) NOPASSWD: /usr/bin/zypper
username ALL=(root) NOPASSWD: /bin/rm
 
# FLR Restore via VBR console
username ALL=(root) NOPASSWD: /bin/sh
username ALL=(root) NOPASSWD: /bin/touch
username ALL=(root) NOPASSWD: /bin/chmod
username ALL=(root) NOPASSWD: /tmp/Username*-*-*-*
username ALL=(root) NOPASSWD: /usr/rm
username ALL=(root) NOPASSWD: /usr/ps
username ALL=(root) NOPASSWD: /usr/mv

Challenge

The logging level needs to be changed.

Solution

Logging level is changed by altering the value of the DWORD ‘LoggingLevel’ on the Veeam server in the registry key: HKLM\Software\Veeam\Veeam Backup and Replication.

In Version 8.x and earlier, after changing the value, the Veeam Backup Service must be restarted. Make sure no jobs or restores are running before restarting this service. In Version 9.x, the Veeam Backup Service periodically rescans the registry. The logging level will adjust automatically after no more than 15 minutes.

This value can be modified from 1-6. (6 being the highest)

• Logging level: [1 (LowDetailed)]
• Logging level: [2 (BelowNormal)]
• Logging level: [3 (Normal)]
• Logging level: [4 (AboveNormal)]*
• Logging level: [5 (HighDetailed)]
• Logging level: [6 (UltimateDetailed)]

*The value of 4 for the LoggingLevel DWORD is the default setting.

More Information

Increasing the LoggingLevel value increases details in the logs along with the general size of the logs. By that same token, the LoggingLevel value can also be reduced to lower the disk load on the location the log files are being written to.

Challenge

Cause

Solution

1. Open the services snap-in on Veeam Cloud Connect server and locate the Veeam Management Agent service.
2. Right-click on it > Propeties > Log On tab.

1. Open Veeam Cloud Connect console.
2. Click the menu button in the upper left corner > Users and Roles.

More Information

Challenge

Cause

Solution

rm -r /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/com.veeam.backupui.VeeamBackupUi-*/ 
rm -r /etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/com.veeam.backupui.VeeamBackupUi-*/ 
rm /etc/vmware/vsphere-client/cmCatalog/com.vmware.cis.com.veeam.backup.quickbackup.zip 
rm /etc/vmware/vsphere-ui/cmCatalog/com.vmware.cis.com.veeam.backup.quickbackup.zip 
rm /etc/vmware/vsphere-client/cmCatalog/com.vmware.cis.com.veeam.backup.veeamzip.zip 
rm /etc/vmware/vsphere-ui/cmCatalog/com.vmware.cis.com.veeam.backup.veeamzip.zip 

3) Restart VMware services responsible for web-interface: 

• Either via appliance command line: 
  service-control --stop vsphere-client 
  service-control --stop vsphere-ui 
  service-control --start vsphere-client 
  service-control --start vsphere-ui 

• Or via Appliance Manager (port 5480) by restarting these services: 
  VMware vSphere Web Client ​
  VMware vSphere Client 

​4) Install Veeam vSphere Web Client Plugin from Enterprise Manager.

5) Login to vSphere Web Client HTML5.  

Please note the last step should be performed twice – on first login plugin will be installed, however, it will only appear after the second login.  

Challenge

Cause

Solution

Challenge

Solution

Restore through file-level recovery wizard

Restoration via backup Import

Challenge

Solution

 Implementation step 1 - Backup & Replication  

1. Use a new Windows Server and install Veeam Backup & Replication v9.5 Update 3a or newer if you do not have a Veeam Backup Server. The Server can run within any VMware cloud on AWS SDDC, AWS S3 or on-premises environments, if the network connection to the VMC vCenter/Veeam Servers potentially the VMs (for Guest processing) is possible.
2. Add DNS network settings so that this Server can resolve Internet DNS names to be able to resolve the full qualified domain name of the VMC vCenter
3. Check the below information carefully for any known limitations and configuration steps before you proceed.

Implementation step 2 - VMware Cloud on AWS

Firewall Configuration for vCenter connection

1. Usage of the vCenter public IP for customers with NSX-v (default) 
   • Open Port TCP 443 from Backup Server and Proxy Server to the predefined vCenter object on the Compute Network.
   • Allow the Compute Gateway Public IP to communicate over TCP 443 with the predefined vCenter object on the Management Network.
     
2. Usage of a VPN tunnel for customers with VMware NSX-v 
   To be able to directly access the vСenter within VMC, please follow the VMC internal guidelines to create a VPN tunnel from the compute network to the management network: https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws.getting-started/GUID-30BED7B3-D312-4DF3-BD7A-66F8D1C619DC.html
   Please update your DNS Servers to resolve the FQDN of the vСenter to its private IP address. If you want to use hosts entries on the Veeam Server for it, add them on all Veeam Backup and Proxy Servers.
   If your Backup & Replication (Management) Server is outside of the VMC cluster, please implement the same VPN connection for it.

• Usage of the local connection for customers with VMware NSX-t 
  NSX-t allows VMC customers to directly access the management network over the built-in firewall. TCP Port 443 needs to be opened from all Veeam Backup and Veeam Proxy Servers as a Source with the vCenter internal IP as a target.
  Please add the VMC compute gateway as a DNS Server IP to all Veeam Servers so that the FQDN of the vCenter can be resolved.
  Configure the vCenter DNS resolution as internal which allows the DNS Gateway that runs on the Compute Gateway to resolve the vCenter name with its internal IP address.

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 VMware Cloud on AWS integrated high throughput/low latency ENI network connection to avoid any traffic costs.
2. Open the same ports on the Inbound Firewall of the Amazon EC2 server used as a repository server. As the Firewall Rule Source you should add all Veeam Backup Servers (including Proxy/Repository/MountServer/Console/…) instead of 0.0.0.0/0                                                                                                                                                                 

1. Veeam Backup Copy Job to a second EC2 Server used as an additional Repository. The second EC2 Server can be placed on another AWS Availability Zone or AWS Geo Location.
2. AWS Storage Gateway Software in VTL mode can be used to emulate a Tape Library to write data to S3. Veeam Backup to Tape Jobs can be used with it. For details see: https://www.veeam.com/wp-using-aws-vtl-gateway-deployment-guide.html
3. Veeam Backup Copy Job to on premises or Veeam Cloud Connect (Enterprise). There is no special configuration needed for this use case beside network and firewall connections. For standard Repository usage on premises it is recommended to create a VPN tunnel from VMware Cloud on AWS to the on premises datacenter. This can be done by the VMC integrated VPN functionality, by Veeam PN or Third Party.

1. VMware Cloud on AWS used as Restore target. 
   1. Implementation steps 1-4 are needed.
2. Veeam VM Replication.
   1.  Implementation steps 1-5 are needed. The Repository Server (when NOT used for Backups, can run within the VMware Cloud on AWS SDDC to store the Veeam Replication data. On premises to VMC, VMC to VMC and VMC to on premises is possible. Usage of Veeam Availability Orchestrator is possible in specific scenarios, see VAO deployment guide: https://helpcenter.veeam.com/docs/vao/deployment/welcome.html?ver=10

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

Veeam Backup & Replication job using Application-Aware Processing to process a Domain Controller fails with one the following errors:

Unable to release guest. Details: Unfreeze error: [Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [NTDS]. Class ID: [{b2014c9e-8711-4c5c-a5a9-3cf384484757}]. Instance ID: [{66fddc15-0e4c-4a2a-ad31-32eaf6dae8a3}]. Writer\'s state: [VSS_WS_FAILED_AT_POST_SNAPSHOT]. Error code: [0x800423f4].]

Error: VSSControl: 0 Backup job failed.
Cannot create a shadow copy of the volumes containing writer's data.
Cannot prepare the [NTDS] data to a subsequent restore operation.
Cannot process NTDS data.
Cannot create a backup copy of the BCD.

Error: VSSControl: -1 Backup job failed.
Cannot create a shadow copy of the volumes containing writer's data.
Cannot prepare the [NTDS] data to a subsequent restore operation.
Cannot process NTDS data.
Cannot create a backup copy of the BCD. Cannot get [BcdStore] object. COM error: Code: 0xffffffff

Solution

The actions listed in this section are to be performed within the Guest OS of the DC that is having these issues.

The cause is most likely one of the following. If a listed troubleshooting step requires attention, test the Veeam job after performing that troubleshooting task, before proceeding on to further troubleshooting steps.

Verify that the NTDS VSS writer is stable.

From an elevated command prompt run the following command:

vssadmin list writers

The results will appear as:

Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {ee24b741-eaf7-4663-8f95-b92ae8c5e164}
State: [1] Stable
Last error: No error

If the NTDS writer is not listed as "State: [1]Stable", reboot the DC (Domain Controller).

Verify that Automatic mounting of new volumes enabled.

From a Run prompt (Win+R) run the program 'diskpart'.

From within DiskPart run the following command.

automount

If the results do not show “Automatic mounting of new volumes enabled.” Run the following command:

automount enable

Verify that there are no .bak keys in the ProfileList within the Registry.

Open the Registry Editor (regedit.exe)

Within the registry navigate to:

HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList

There will be a list of Keys, you must remove any ending in .bak

More Information

The Majority of cases are resolved uses the above 3 troubleshooting steps. However in rare cases the WMI repository must be rebuilt. To do this please refer to the following article:
http://blogs.technet.com/b/askperf/archive/2009/04/13/wmi-rebuilding-the-wmi-repository.aspx

Challenge

Solution

 Implementation step 1 - Backup & Replication  

1. Use a new Windows Server and install Veeam Backup & Replication v9.5 Update 3a or newer if you do not have a Veeam Backup Server. The Server can run within any VMware cloud on AWS SDDC, AWS S3 or on-premises environments, if the network connection to the VMC vCenter/Veeam Servers potentially the VMs (for Guest processing) is possible.
2. Add DNS network settings so that this Server can resolve Internet DNS names to be able to resolve the full qualified domain name of the VMC vCenter
3. Check the below information carefully for any known limitations and configuration steps before you proceed.

Implementation step 2 - VMware Cloud on AWS

Firewall Configuration for vCenter connection

1. Usage of the vCenter public IP for customers with NSX-v (default) 
   • Open Port TCP 443 from Backup Server and Proxy Server to the predefined vCenter object on the Compute Network.
   • Allow the Compute Gateway Public IP to communicate over TCP 443 with the predefined vCenter object on the Management Network.
     
2. Usage of a VPN tunnel for customers with VMware NSX-v 
   To be able to directly access the vСenter within VMC, please follow the VMC internal guidelines to create a VPN tunnel from the compute network to the management network: https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vmc-aws.getting-started/GUID-30BED7B3-D312-4DF3-BD7A-66F8D1C619DC.html
   Please update your DNS Servers to resolve the FQDN of the vСenter to its private IP address. If you want to use hosts entries on the Veeam Server for it, add them on all Veeam Backup and Proxy Servers.
   If your Backup & Replication (Management) Server is outside of the VMC cluster, please implement the same VPN connection for it.

• Usage of the local connection for customers with VMware NSX-t 
  NSX-t allows VMC customers to directly access the management network over the built-in firewall. TCP Port 443 needs to be opened from all Veeam Backup and Veeam Proxy Servers as a Source with the vCenter internal IP as a target.
  Please add the VMC compute gateway as a DNS Server IP to all Veeam Servers so that the FQDN of the vCenter can be resolved.
  Configure the vCenter DNS resolution as internal which allows the DNS Gateway that runs on the Compute Gateway to resolve the vCenter name with its internal IP address.

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 VMware Cloud on AWS integrated high throughput/low latency ENI network connection to avoid any traffic costs.
2. Open the same ports on the Inbound Firewall of the Amazon EC2 server used as a repository server. As the Firewall Rule Source you should add all Veeam Backup Servers (including Proxy/Repository/MountServer/Console/…) instead of 0.0.0.0/0                                                                                                                                                                 

1. Veeam Backup Copy Job to a second EC2 Server used as an additional Repository. The second EC2 Server can be placed on another AWS Availability Zone or AWS Geo Location.
2. AWS Storage Gateway Software in VTL mode can be used to emulate a Tape Library to write data to S3. Veeam Backup to Tape Jobs can be used with it. For details see: https://www.veeam.com/wp-using-aws-vtl-gateway-deployment-guide.html
3. Veeam Backup Copy Job to on premises or Veeam Cloud Connect (Enterprise). There is no special configuration needed for this use case beside network and firewall connections. For standard Repository usage on premises it is recommended to create a VPN tunnel from VMware Cloud on AWS to the on premises datacenter. This can be done by the VMC integrated VPN functionality, by Veeam PN or Third Party.

1. VMware Cloud on AWS used as Restore target. 
   1. Implementation steps 1-4 are needed.
2. Veeam VM Replication.
   1.  Implementation steps 1-5 are needed. The Repository Server (when NOT used for Backups, can run within the VMware Cloud on AWS SDDC to store the Veeam Replication data. On premises to VMC, VMC to VMC and VMC to on premises is possible. Usage of Veeam Availability Orchestrator is possible in specific scenarios, see VAO deployment guide: https://helpcenter.veeam.com/docs/vao/deployment/welcome.html?ver=10

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

Cause

Solution

1. Verify that the account used to connect to Veeam Backup and Replication server in Veeam ONE has correct permissions. To check the account name, go to Veeam ONE Monitor > Data Protection View > right-click on the Veeam Backup and Replication object. Note the specified account.
2. On the Veeam Backup and Replication server, confirm that this account as well as the Veeam ONE service account are added to the Event Log Readers Group and Administrators group in Local Systems and Groups
3. Even if the Firewall is off, activate the following firewall rules on the Veeam Backup and Replication server side: Remote Event Log Management and COM+ Network Access (DCOM-In)
4. Check UAC settings.

1. Change the type of the all Public network connections to Private using the following Powershell cmdlet: 

Set-NetConnectionProfile -NetworkCategory Private

Or using the registry editor (machine restart will be required):

More Information

Challenge

Cause

Solution

Recommended Method:
 
If Veeam Backup & Replication is already installed, apply the latest update.
 
If it is not installed:

1. Choose a new database name during installation. An empty database will be created with this name.
2. Once installation has completed, apply the latest update.
3. Switch from the empty database to the original configuration database using the Configuration Database Connection Settings utility.

1. In Object Explorer, connect to the instance containing the empty database (such as localhost\VEEAMSQL2012).
2. Expand Databases, right-click the empty database, and then click Delete.
3. Confirm the correct database is selected, and then click OK.

 
Do not attempt to revert to a previous release of the software (such as to v8 from v9).

More Information

Challenge

This KB article provides a list of all versions of Veeam Backup & Replication and the respective build numbers.

Solution

The following table lists Veeam Backup & Replication versions and their build numbers. Also provided is a link to the specific version release notes.