Challenge

Product Information:

Company name: Quest Software, Inc.
Product Family: QoreStor
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: DELL OEM R340p
Storage Category: Software Defined Storage
Drive quantity, size, type: 8 – 1.745TB SATA SSD
Storage configuration: RAID5
Firmware version: V5.1.0 Build 377
Connection protocol and speed: SMB, 2-10GbE bonded LACP
Additional support: All models and configurations of QoreStor 5.1 on hardware platforms with specifications equivalent or greater than the above

Veeam testing configuration:

Veeam Build Number: 9.5.4.2753

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings:

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

Challenge

Cause

Before installing this update, make sure you are running Veeam Backup & Replication version 9.5.0.1536 or later.

To check the version, do the following:

1. Open the Veeam Backup & Replication console.
2. In the main menu, click Help and select About.

Solution

• Added support for volume snapshots created as part of a Pure Storage Protection Group. 

• The default HTTP timeout value was Increased from 5 to 60 seconds to make the plug-in more resilient to network issues.
• vVol volumes are no longer displayed in the list of volumes.

More Information

Challenge

Release Notes for Pure Storage Plug-In for Veeam Backup & Replication 1.2.45.0

Cause

Before installing this update, make sure you are running Veeam Backup & Replication version 9.5.4.2866 or later.

To check the version, do the following:

1. Open the Veeam Backup & Replication console.
2. In the main menu, click Help and select About.

Solution

• Snapshots created by Timing Snapshot Schedule on Huawei OceanStor Dorado are now filtered out by the plug-in and not returned to Veeam B&R.

More Information

Challenge

Cause

1. Open the Veeam Backup & Replication console.
2. In the main menu, click Help and select About.

Solution

• Snapshots created by Timing Snapshot Schedule on Huawei OceanStor Dorado are now filtered out by the plug-in and not returned to Veeam B&R.

More Information

Challenge

Cause

Solution

ls -l /usr/bin/nohup

chmod 755 /usr/bin/nohup

Challenge

Cause

Solution

• Support for port binding (iSCSI protocol).

More Information

Challenge

Cause

1. Open the Veeam Backup & Replication console.
2. In the main menu, click Help and select About.

Solution

• Snapshots created by Timing Snapshot Schedule on Huawei OceanStor Dorado are now filtered out by the plug-in and not returned to Veeam B&R.

More Information

Challenge

Solution

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

The Used Space value may be greater than the Capacity value in the following cases:

1. You have imported backups that can be found in the Home view under the Backups > Disk (Imported) node.
   
   Such imported backups are not stored directly on disks, but the size of these backups is still considered during calculation of the Used Space value. 
   
   If duplicates of imported backups appear under the Backups > Disk (Imported) node, this may mean that the recycle bin feature is enabled for a backup repository which holds copies of .vbm files from each backup session. When the backup repository is re-scanned, each .vbm file is considered as a separate backup, and the size of such a backup chain is added to the Used Space value. Alternatively, there may be backups under the Backups > Disk (Imported) node which were manually deleted but never removed from the configuration.
    
2. You have a ReFS repository in which synthetic full backups are created using the Fast Clone technology.

Solution

1. To correct the Used Space value that is shown for imported backups, you can remove these backups from the configuration and disable the recycle bin feature. If you have a large number of imported backup duplicates, a database edit might be required in order to save time, as manual removal may become impractically slow. In such a scenario, make sure to contact Veeam technical support.
    
2. For synthetic full backups with ReFS Fast Clone, backup files will be displayed as full-sized, even though only unique blocks are stored for each full backup file. In such a scenario, it is expected that the size that is shown under the Used Space column is a combined total value of the displayed file sizes in the backup repository. Refer to the Free Space column that should have an accurate value. The Used Space value will be displayed correctly if you check the properties for the ReFS volume in Windows.

Challenge

Solution

1. Go to /usr/sap/<SID>/SYS/global/hdb/ and check if the "opt" folder exists. If this folder does not exist, login as the <sid>adm user and create the folder.
2. Run the following command to create a symbolic link (use SID of your database instead of <SID>):
   ln -s /opt/veeam/VeeamPluginforSAPHANA/hdbbackint /usr/sap/<SID>/SYS/global/hdb/opt/hdbbackint
   If there is already a symbolic link from another backup product, you need to replace it if you want to use Veeam Plug-in for SAP HANA. 
3. Continue configuring the Veeam Plug-in as described in the Configuring Veeam Plug-in for SAP HANA.

Challenge

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

Cause

Solution

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

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

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

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

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

More Information

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

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

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

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

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

Challenge

Solution

1. Go to /usr/sap/<SID>/SYS/global/hdb/ and check if the "opt" folder exists. If this folder does not exist, login as the <sid>adm user and create the folder.
2. Run the following command to create a symbolic link (use SID of your database instead of <SID>):
   ln -s /opt/veeam/VeeamPluginforSAPHANA/hdbbackint /usr/sap/<SID>/SYS/global/hdb/opt/hdbbackint
   If there is already a symbolic link from another backup product, you need to replace it if you want to use Veeam Plug-in for SAP HANA. 
3. Continue configuring the Veeam Plug-in as described in the Configuring Veeam Plug-in for SAP HANA.

Challenge

Solution

This solution applies ONLY if the vCenter Server database has not changed.
If the Name/FQDN/IP of the vCenter changed due to a reinstall or upgrade and a new vCenter database was used, the Ref-IDs will have changed. Due to the changed Ref-IDs you will need to follow the documented process in www.veeam.com/KB1299 to resolve the "Object "VM_Name" not found" errors if the original jobs are kept.
 
Before starting you will have to find out the Name\FQDN\IP Veeam is using to communicate with the VC presently. To do this, edit the entry for the VC under Backup Infrastructure and note the “DNS name or IP address”.



Next perform the following steps, checking that same location again afterward to confirm the change. 

1.  Launch PowerShell from inside the Veeam Backup & Replication console. You can find the "PowerShell" button under the File-menu's "Console" section.

2.  

$Servers = Get-VBRServer -name "Current-VCName/IP"


3.  Run the following command next:

$Servers.SetName("New-VCName/IP")


4.  

More Information

Challenge

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

Cause

Solution

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

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

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

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

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

More Information

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

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

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

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

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

Challenge

"HotAdd is not supported for this disk, failing over to network mode"

Solution

Requirements:

1. If the Veeam Proxy being used to process the source VM is on a VMFS 3 datastore it must be formatted with proper block size to be able to mount the largest virtual disk of the hot added VMs:
   • 1MB block size – 256GB maximum file size
   • 2MB block size – 512GB maximum file size
   • 4MB block size – 1024GB maximum file size
   • 8MB block size – 2048GB maximum file size
2. The Proxy being used to back up the VM must be a Virtual Machine on a host that is able to access the datastore where the source VM’s disks are stored
3. For vSphere 5.1 the maximum supported VMDK size is 1.98 TB
4. For vSphere 5.5 and older the maximum supported VMDK size is 62 TB
5. HotAdd is a SCSI feature and does not work for IDE disks
6. VMware Tools must be installed and up-to-date on the Veeam server and any Veeam proxies
7. Datastore needs sufficient space for a VM snapshot
8. Backup and restore of SATA disks in the Virtual appliance mode is supported if you use VMware vSphere 6.0 and later

Known Issues:

• If the VM disk resides on a Vvol the Hot Add Proxy VM's configuration files must also be on the same Vvol.
• HotAdd may fail if any disk was created with a newer hardware version than the VM being backed up. For example, if a disk was moved from a hardware version 8 VM to a hardware version 7 VM. To resolve, upgrade the hardware version of the VM.
• A single SCSI controller can have a maximum of 15 disks attached. To run multiple concurrent jobs with more than 15 disks, you need to add more SCSI controllers to your Veeam Proxy server that is responsible for hot adding the disks. (kb.vmware.com/kb/1037094)
• In case of standalone host connection (no vCenter added to the console), you can only hot add disks of VMs which are located on the same host as the proxy server.  This may require additional proxy servers to be configured on each host in the environment.
• HotAdd may fail if you are trying to back up the VM through the host added as a standalone server into Veeam Backup Infrastructure but actually being managed by vCenter. The following error message can be found in the source agent log:

  "Reconfigure attempt failed for VM "" with Vmomi::MethodFault::Exception ("vim.fault.HostAccessRestrictedToManagementServer")"

• If you plan to process VMs that store disks on the NFS datastore, you must deploy the backup proxy on the same ESX(i) host where these VMs reside.
• Virtual Appliance backup job fails after you’ve cloned or restored your VBR server. The reason for that is incorrect UUID reference for Veeam Backup VM which can be found in the following registry key of the Veeam server. Please see http://www.veeam.com/kb1332
• HotAdd fails if VM disks being backed up don't have unique ddb UUIDs across the vCenter, for example if such VMs were deployed from a single template to different hosts.  Please refer to the VMware KB article for details: http://kb.vmware.com/kb/2006865
• Backup in HotAdd mode may fail if there is a SATA controller configured on proxy virtual machine. Please refer to the VMware KB article for details: https://kb.vmware.com/s/article/2151091 

Troubleshooting:

• Test to see if the disk of the VM to be backed up can be manually hotadded to the proxy. See: http://www.veeam.com/kb1184
• Check all Veeam Proxies for unmounted HotAdded disks and release them manually. See: http://www.veeam.com/kb1775
• Disable Automount option on the backup proxy, as documented in http://www.veeam.com/kb1882.

More Information

Please contact Veeam Technical Support for further assistance.

Challenge

Solution

1. Go to /usr/sap/<SID>/SYS/global/hdb/ and check if the "opt" folder exists. If this folder does not exist, login as the <sid>adm user and create the folder.
2. Run the following command to create a symbolic link (use SID of your database instead of <SID>):
   ln -s /opt/veeam/VeeamPluginforSAPHANA/hdbbackint /usr/sap/<SID>/SYS/global/hdb/opt/hdbbackint
   If there is already a symbolic link from another backup product, you need to replace it if you want to use Veeam Plug-in for SAP HANA. 
3. Continue configuring the Veeam Plug-in as described in the Configuring Veeam Plug-in for SAP HANA.

Challenge

Solution

This solution applies ONLY if the vCenter Server database has not changed.
If the Name/FQDN/IP of the vCenter changed due to a reinstall or upgrade and a new vCenter database was used, the Ref-IDs will have changed. Due to the changed Ref-IDs you will need to follow the documented process in www.veeam.com/KB1299 to resolve the "Object "VM_Name" not found" errors if the original jobs are kept.
 
Before starting you will have to find out the Name\FQDN\IP Veeam is using to communicate with the VC presently. To do this, edit the entry for the VC under Backup Infrastructure and note the “DNS name or IP address”.



Next perform the following steps, checking that same location again afterward to confirm the change. 

1.  Launch PowerShell from inside the Veeam Backup & Replication console. You can find the "PowerShell" button under the File-menu's "Console" section.

2.  

$Servers = Get-VBRServer -name "Current-VCName/IP"


3.  Run the following command next: $Servers.SetName("New-VCName/IP")


4.  

More Information

Challenge

Solution

 Implementation step 1 - Backup & Replication  

1. Use a new Windows Server and install Veeam Backup & Replication v9.5 Update 4b + Patch 2414 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 fully qualified domain name of the VMC vCenter server
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.
3. 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.
   a) Configure DNS entry of the vCenter for local IP address usage.

   Go to your SDDC Management – Settings – vCenter FQDN and select the Private vCenter IP address.
   Hint: If you configure the vCenter DNS record for the internal IP address, you will lose VMC connection from Backup and Replication Server outside of VMC. You can use the local hosts file or any other DNS method to resolve the vCenter FQDN with the public IP address on the Veeam Server outside of VMC. Optionally, use the Public IP address for the VMC internal and external Veeam Server.

   b) Open firewall ports for vCenter Server access

   On the Management Network
   
   On the Compute Gateway
   

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. Download the hotfix.
2. Check that you have version 9.5.4.2866 of Veeam Backup & Replication installed.
3. Make sure that no jobs are running, close the Veeam console and stop all Veeam services on the Veeam Backup server.
4. On the Veeam Backup server, rename following original files by adding _original in the end of the file name in folders: C:\Program Files\Veeam\Backup and Replication\Backup
   and C:\Program Files\Veeam\Backup and Replication\Console:
   • Veeam.Backup.Common.dll
   • Veeam.Backup.Core.dll
   • Veeam.Backup.Interaction.VMware.dll
   • Veeam.Backup.PowerShell.dll
   • Veeam.Backup.ServiceLib.dll
   • Veeam.Backup.SureBackup.dll
   • Veeam.Backup.UI.FileRestore.dll
   • Veeam.Backup.VcdLib.dll
   • Veeam.Backup.ViSoap.dll
5. Copy all files from the hotfix into folders C:\Program Files\Veeam\Backup and Replication\Backup
   and C:\Program Files\Veeam\Backup and Replication\Console Veeam Backup server.
6. Start Veeam services on Veeam Backup server.

Problem

Solution

5. Create a vCenter User with required rights (Active Directory linked mode) described here, or use the cloudadmin@vmc.local user.
6. 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

Antivirus Exclusions:

Folders that need to be excluded on Veeam Availability Console server and Web UI:

• C:\Program Files\Veeam
• C:\ProgramData\Veeam
• C:\Windows\Veeam
• C:\Program Files\Common Files\Veeam
• C:\Program Files (x86)\Common Files\Veeam

Folders that need to be excluded on computers with VAC management agents:

• C:\Program Files\Veeam
• C:\ProgramData\Veeam
• C:\Windows\Veeam
• C:\Program Files\Common Files\Veeam
• C:\Program Files (x86)\Common Files\Veeam
• \\localhost\admin$\Veeam
• \\localhost\admin$\Veeam\Availability Console\Agent for Windows\VeeamAgentWindows.exe

Files:

• VeeamAgentWindows.exe
• ManagementAgent.exe
• VAC.CommunicationAgent.x64.msi
• VAC.CommunicationAgent.x86.msi

Due to the complex nature of antivirus software, some additional exclusions may be needed.
If your antivirus has a logging or history system please review this to see actions it may have taken that may affect Veeam Availability Console operations.

More Information