Challenge

Cause

Solution

Challenge

Cause

Solution

<configuration>
  <appSettings>
    <add key="ExposeShadowVolumes" value="True"/>
  </appSettings>
</configuration>

More Information

Challenge

Cause

Solution

ssh -i "<backup server's .pem key>" ubuntu@<Public DNS (IPv4) parameter of the backup server>

sudo systemctl restart veeamawsbackup.service

Challenge

Cause

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

Solution

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

More Information

Challenge

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

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

Solution

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

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

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

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



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

More Information

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

• Windows 2003, XP – C:\Documents and Settings\All Users\Application Data\Veeam\Backup\
• Windows Vista, 7 - C:\Users\All Users\Veeam\Backup\
• Windows 2008/2008 R2/2012 - C:\ProgramData\Veeam\Backup\
• Linux - /var/log/VeeamBackup/

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

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

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

Please note that information provided to Veeam for purposes of customer support may be considered protected under certain data protection regulations and/or internal company policies. A list of potentially sensitive data types is available in the following KB article. The Support team may provide with a log scrubbing utility upon request. Veeam will only utilize this information for the specific purpose of providing customer support to you and will protect the information in accordance with its privacy policy. In any event, the information provided will be securely deleted after 45 inactive days as of the last upload to the FTP. If you would like it deleted sooner, please express this request directly to your support contact once the issue has been resolved. For more information on how we process the collected data, please visit: https://vee.am/processing_of_personal_data

Challenge

Cause

Solution

To improve Veeam ONE SQL database performance, partitioning can be used. Note, that SQL Server Enterprise Edition is required to use partitioning.

NOTE: Do not deploy database partitioning if you use Always On Availability Groups on the SQL server.

Partitioned tables and indexes are created by two scripts. Before running the scripts, it is recommended to create a backup of Veeam ONE database. The scripts can be executed in any order. Before applying them, you will need to specify the following values:

1. Locate %UserName% parameter in the script and specify DB admin (sa or any domain account that has full control permissions to Veeam ONE DB).
2. Locate %Path% parameter and specify directory where database partitions will be created/stored.
3. If Veeam ONE database name is different from default, then change the name of the database (VeeamOne) in both scripts manually
4. Make sure SQL Agents are running before executing the scripts

After successful script execution you should see new functions and partition schemes: 



SQL Server agent will have two maintenance jobs created:



The directory specified for database partitions will have files like this:

VeeamOneLow_FG1.ndf
...
VeeamOneLow_FG13.ndf

VeeamOneMed_FG1.ndf
...
VeeamOneMed_FG15.ndf

More Information

Challenge

Cause

Solution

• When your machine boots, press the F8 key before the Windows logo appears. Select the Last Known Good Configuration option.
• Remove the Veeam CBT driver with Veeam Recovery Media. For details, see Removing CBT Driver with Veeam Recovery Media.

Challenge

Cause

• Starting from Windows 10 version 1809, the WinPE component is an add-on to the Windows Assessment and Deployment Kit (ADK).
• Veeam Agent machine has a hardware recovery partition instead of the system partition.

Solution

1. Start the command prompt.
2. Run the command: reagentc /info.
   • If the command returns Enabled, there is a possibility that system might be corrupted. It is worth checking system integrity. Use the dism.log command that may point to a possible cause.
   • If the command returns Disabled, it is most likely that the Windows RE/PE components are not installed or configured on the Veeam Agent machine.

1. Run regedit.exe.
2. Locate the HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam EndPoint Backup key.
3. Add the following value under the key:
   • Name: DisableRECollection
   • Type: REG_DWORD
   • Value: 1
4. Go to Control Panel > System and Security > Administrative Tools > Services.
5. Restart the Veeam Agent for Microsoft Windows service. 

After the registry key is created, Veeam Agent for Windows does not start the the Recovery Media collection process at the end of the backup job.

Challenge

Solution

• C:\Program Files\Veeam
• C:\Program Files (x86)\Veeam
• C:\Program Files\Common Files\Veeam
• C:\Program Files (x86)\Common Files\Veeam
• C:\Windows\Veeam
• %programdata%\Veeam
• The folder that contains repository databases

• C:\Windows\Veeam
• %programdata%\Veeam
• The folder that contains repository databases.

More Information

Challenge

When backing up to a deduplication storage appliance from Veeam Backup & Replication, performance or deduplication ratio is low without using best practice settings. 

Solution

The default options of Veeam Backup & Replication are intended for non-deduplication storage.

If you use deduplication storage systems, you need to additionally configure the backup architecture and Veeam settings to achieve best performance. Below are some hardware and software configuration options that can be used with deduplication storages. In some cases, you may need to combine more than one option, but in all cases, it is strongly encouraged that you consult your deduplication appliance vendor and/or a value added reseller to discuss individual needs.

For the general architecture planning, Veeam’s best practices is to follow the industry 3-2-1 backup rule:

3: Maintain at least three copies of your data and applications. That’s the one copy you’re using and two backups. This way, if one of your backups is unavailable for any reason (for example, if you store the backup in the same locations with the copy you use and both go down), you can still recover what you need.

2: Store your backups on at least two different types of media or storage controller logics. One reason for this is that each type of media has its own vulnerabilities, and you don’t want both of your backups susceptible to the same problem. 

For example: run your business on a general purpose fast storage system and store your backups on a storage system that is specialized for this purpose, or a separate server with local disks.

1: Keep one of the backups in a different location. Consider a crisis in your primary data center, such as a fire or power failure. If all your copies are collocated, they can all be affected, taking down your organization.

To achieve this, use the Veeam best practices. However, each deduplication storage vendor has specific unique feature sets that allow the usage of their storages in different ways. Please check the following links for vendor specific guidelines:

• Best Practices for HPE
• Best Practices for ExaGrid
• Best Practices for Dell EMC DataDomain
• Best Practices for Quantum

General Deduplication Storage Best Practices

Step 1:  Creating backups on the first site with long term retention.

Step 2: Add offsite target.

In addition to the above scenarios, you can use the following options to create an offsite copy of your data.

3. Place a deduplication storage on primary side and use object storage or tape on second site. Use Veeam backup to tape jobs or Veeam scale-out backup repository cloud tier (connection to object storages) to store data offsite.

The scenario above reflects general best practices. Please contact your deduplication storage vendor for further guidance and check the vendor links provided above for additional usable scenarios with the specific storage.
 

Best Practices For Deduplication Storage Systems

Backup Chains

• General Deduplication Storages + Backup Copy Job That Reads From Source Backup Chain (Exagrid, Quantum DXi, Infinidat InfiniGuard and Fujitsu Eternus CS800):

 

•  HPE StoreOnce Catalyst / Dell EMC DataDomain DDboost  + Copy Over WAN + Backup Copy Job:

The previous described option provides fast processing in situations that do not involve transport over WAN links. Also, optimized integration with Catalyst and Dell EMC DDBoost allows using synthetic processing. For these environments uncheck the “Read the entire restore point from source backup instead of synthesizing it from increments” but leave the weekly GFS backup enabled.

• Special Scenarios Based on Vendor Own Guidelines + Backup Job With Active Full or Synthetic Full Backup:

Inline Deduplication

However for deduplication devices that have a non deduplicated landing zone (Like ExaGrid) and backup only VMs, you can save some space: to do this, enable inline deduplication



 

Compression

Block Size

• Storage optimization: Local target (large blocks)

• Storage optimization: Local target 

Use this option for ExaGrid.

Block Alignment

Encryption

Health Check

  
Veeam Defragmentation And Compact Settings

More Information

Challenge

Solution

1. Navigate to the ESXi host Firewall screen within the vSphere client under <hostname>/Configure/System/Firewall. Click Edit.

2. Under Edit Security Profile, use the “NFS” filter. Select NFSAccess to modify settings.

3. Enter IP addresses of all proxies that will be used to back up data from the HyperFlex Cluster. Once complete, click OK.

4. Repeat steps 1 through 3 for all ESXi hosts within the HyperFlex cluster.

Challenge

Solution

1. Get the current Office 365 plan IDs assigned for the organization. You can do this via ‘MSOnline’ AzureAD module and the following PowerShell One-Liners: *
   Note: This script is provided as-is as a courtesy for Gathering Plan IDs from MSOnline. Please be aware that the commands and parameters may be altered by Microsoft in the future, which may cause the script to function incorrectly. There is no support provided for this script, and should it fail, we ask you to contact Microsoft support. This script may be updated in the future to reflect changes to the Office 365 Powershell Environment
   1. To call "get-msolaccountsku" (use the CMDLET), call "Connect-MsolService" first. This requires the following modules to be installed and activated:
      • install-module AzureAD
      • install-module AzureADPreview
      • install-module MSOnline
   2. To get the list of Exchange Online service plans IDs:
      • (get-msolaccountsku).servicestatus.serviceplan | where {$_.ServiceType -match "Exchange"} | ft ServiceName,ServicePlanId
   3. To get the list of SharePoint Online service plans IDs:
      • (get-msolaccountsku).servicestatus.serviceplan | where {$_.ServiceType -match "SharePoint"} | ft ServiceName,ServicePlanId
2. Make sure that no backup jobs or restore sessions are running.
3. Stop the Veeam.Archiver.Service and Veeam.Archiver.Proxy services.
4. Navigate to the C:\ProgramData\Veeam\Backup365 directory on the Veeam Backup for Microsoft Office 365 server, create a backup of the Congif.xml file by copying it to another location, then (only after making the pre-edit copy) edit the Config.xml file by adding the following lines between <Archiver> tags:
5. Repeat Step 4 but for the Proxy.xml file instead.

<Options>
<O365Plans AdditionalExchangePlans="your-Exchange-plans-IDs" AdditionalSharePointPlans="your-SharePoint-plans-IDs" />
</Options>

If you do not have any SharePoint plans, do not add the AdditionalSharePointPlans to the line mentioned

NOTE: You will have to add the Plans as the examples shown in the following screenshot. The GUIDs are entered in Coma Separated Value within the Quotation after each of the key values in the <O365Plans line.

6. Start the Veeam.Archiver.Service and the Veeam.Archiver.Proxy services.
7. Open the Add organization wizard and retry the procedure.

Challenge

Cause

Log Name:      System
Source:        Win32k
Event ID:      243
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:     
Description:
A desktop heap allocation failed.

Solution

To resolve this issue, update the registry key to increase the desktop heap memory size. Mind that this change affects the desktop heap of all services, so do not make the value larger than necessary. To update the registry key, do as follows:

1. Run regedit.exe.
2. Locate the HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems key.
3. Locate the Windows string.

4. Edit the third "SharedSection" value in the Value data field as shown below:

       Before:

        After:

5. Click OK.
6. Reboot the Veeam Agent machine.

More Information

• Microsoft Support article
• Microsoft Developer Network article

You can check the desktop heap memory usage on your own in the following way:

1. Download Windows Software Development Kit (SDK).
2. Run Sdksetup.exe and install Debugging Tools for Windows.
3. Download LiveKd.
4. Copy livekd.exe to C:\Program Files (x86)\Windows Kits\10\Debuggers\x64.
5. Run Command Prompt.
6. Type the following commands:

livekd -y srv*http://msdl.microsoft.com/download/symbols
!dskheap

Command Prompt returns the list of sessions. If the desktop heap is running out of memory, the Used Rate(%) value for the session is close to 100%.

0: kd> !dskheap

  Winstation\Desktop            Heap Size(KB)   Used Rate(%)
------------------------------------------------------------
  WinSta0\Default                  20480                 0%
  WinSta0\Disconnect                  96                 4%
  WinSta0\Winlogon                   192                 2%
  Service-0x0-3e7$\Default           768                 4%
  Service-0x0-3e4$\Default           768                 1%
  Service-0x0-3e5$\Default           768                 0%
  Service-0x0-17eac$\Default         768                 2%
  Service-0x0-afb53$\Default         768                 0%

7. Take the last part of the session name and convert the HEX value into Decimal:
   1. Open PowerShell.
   2. Paste the last part of the session name (after the last dash).
   3. Add 0x before the last part of the session name.

8. Return to Command Prompt.
9. Type the following WMI query to retrieve all objects related to the session and the name of the account:

Get-WmiObject -Query "ASSOCIATORS OF {Win32_logonsession.LogonId=999}"

Command Prompt returns the list of processes running under that account and the name of the account:

Caption                    Name                       SID
-------                    ----                       ---
SUP-A2025\SYSTEM           SYSTEM                     S-1-5-18
LsaIso.exe                 LsaIso.exe
lsass.exe                  lsass.exe
svchost.exe                svchost.exe
…

If one of the processes running under Local System Account consumes too much memory, we recommend to kill non-Microsoft processes one by one and re-run the !dskheap command (Step 6) to find the leaking application.

Challenge

Cause

Solution

Challenge

Cause

Solution

• Usernames;
• Customer specific infrastructure object names: hosts, datastores, VMs, clusters;
• VM file names and paths;
• FQDN/Hostname or NetBIOS names;
• IP addresses: IPv4 and IPv6;
• Customer specific paths to backup files;
• Backup file names;
• SharePoint information: DB names, paths to DBs, SP URL;
• Exchange information:  DB names, paths to DBs;
• SQL information: DB and Instance Name, paths to DBs;
• Oracle information: DB name, Home Name, Oracle SID, DB global name, paths to DBs;
• File Copy: Customer specific paths and names of files;
• File to tape: Customer specific paths and names of files.

More Information

Challenge

• Organization A that has one active backup job (Backup Job 2), and a backup job that has been deleted at some point (Backup Job 1).
• Organization B that has two active backup jobs — Backup Job 3 and Backup Job 4.

Each of these jobs has several restore points in total (deletion of a backup job does not delete the corresponding restore points from the database).

Solution

Exploring Backups: Job Scope

Exploring Backups: Organization Scope

To explore backups created by all backup jobs of the selected organization, right-click an organization and select any Explore option.

When exploring backups of any of the organizations, Veeam Backup for Microsoft Office 365 works as follows:

• Scans all backup repositories in the backup infrastructure and finds all restore points that have been created by both existing and deleted backup jobs.
• Finds restore points that were created on the specified date or on the closest earlier date.
• Merges found restore points into a single one according to the following:
  • If there are two or more copies of the same item in several restore points, then only one copy will be loaded into the Veeam Explorer scope.
  • If there are two different versions of the same item, then only the latest one will be loaded into the Veeam Explorer scope.
  • Otherwise, all unique versions of all items will be loaded into the Veeam Explorer scope.

Note: The same method is used during Veeam Cloud Connect (BAAS) restores.

Exploring Backups: All Organizations Scope

To explore backups created for each of the organizations ever added to the backup infrastructure, right-click the root Organizations node and select any Explore option.

This method works in the same way as the previous one, except for it applies to each of the organizations added to the application scope.

Challenge

Solution

1. Click Download Script at the bottom of this KB article to download the .zip archive with the script.
2. Transfer the file to the Veeam Availability for Nutanix AHV (proxy appliance) server. Note that SSH is disabled on the proxy appliance server by default. To see how to enable SSH/SFTP, see the Security Considerations section of the Veeam Availability for Nutanix AHV User Guide.
3. Log in to the shell terminal of the proxy appliance server.
4. Install the script dependencies (make sure the backup proxy has an internet connection):

   $ sudo apt-get install python-requests

5. Unpack the .zip archive using the unzip command:

   	$ unzip <the_zip_file_with-script>

6. Make the script file executable:

   	$ chmod +x run_active_full.py

7. Run the script:

$ ./run_active_full.py -j "backup_policy_name" -a backup_appliance_ip_address_or_hostname -u admin -p "password_of_admin_user_for_web_interface"

Where:

• "backup_policy_name" is a backup job name in quotes.
• backup_appliance_ip_address_or_hostname - the proxy appliance IP address or hostname. Make sure the hostname is resolved to an external IP address.
• "password_of_admin_user_for_web_interface" - the password for admin user in quotes.

For example:

$ ./run_active_full.py -j "Backup policy" -a ahvproxy.local -u admin -p "W3bP@ssw0rd"

Use crontab to run the script on a defined schedule.

More Information

Challenge

Product Information:

Company name: Datera Inc.
Product Family: Datera Data Services PlatformDCP (software platform)
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: DCP (software platform)
Storage Category: Software Defined Storage
Drive quantity, size, type: 12 – 7TB HDD, 11 – 1.5TB NVMe across three nodes
Storage configuration: 4 node Datera cluster with 1 All Flash Node (SSD) and 3 Hybrid nodes, caching using NV-DIMM
Firmware version: V3.3.4
Connection protocol and speed: 10 GbE iSCSI
Additional support: All models and configurations of Datera Data Services Platform with specifications equivalent or greater than the above

Datera enables commodity servers from many different vendors, to form software defined storage clusters, which deliver Tier 1 block (iSCSI) and Object Storage. The Datera platform enables bare metal, VM and container workloads to operate concurrently, within a single cluster. The clusters can scale to 64 nodes and may be comprised of a heterogeneous mix of Persistent Storage Class media, such as Intel Optane or Samsung’s Z-SSD, as well as NVMe, SAS and STA Flash. The platform supports rotational media as well, in hybrid nodes.

Veeam testing configuration:

Veeam Build Number: 9.5.4.2866

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)
• Datera default storage settings were used for testing
• Multi-pathing used during testing (MPIO)

Challenge

• enumerating of the resources 
• taking EBS snapshots of selected EC2 instances volumes
• rehydrating of snapshots back to volumes
• attaching volumes to the worker instance
• and so on - see permissions below

Solution

Isolated from production backup deployment

{
	"Version": "2012-10-17",
		"Statement": [
		{
			"Action": [
				"ec2:CopySnapshot",
				"ec2:CreateSnapshot",
				"ec2:CreateSnapshots",
				"ec2:CreateTags",
				"ec2:DeleteSnapshot",
				"ec2:DescribeAvailabilityZones",
				"ec2:DescribeImages",
				"ec2:DescribeInstances",
				"ec2:DescribeSnapshots",
				"ec2:DescribeSubnets",
				"ec2:DescribeTags",
				"ec2:DescribeVolumes",
				"ec2:ModifySnapshotAttribute",
				"events:DeleteRule",
				"events:DescribeRule",
				"events:ListTargetsByRule",
				"events:PutRule",
				"events:PutTargets",
				"events:RemoveTargets",
				"iam:GetRole",
				"iam:ListAttachedRolePolicies",
				"iam:ListInstanceProfilesForRole",
				"iam:ListRolePolicies",
				"iam:ListRoleTags",
				"iam:UpdateAssumeRolePolicy",
				"s3:GetBucketLocation",
				"sns:CreateTopic",
				"sns:DeleteTopic",
				"sns:ListSubscriptionsByTopic",
				"sns:ListTopics",
				"sns:SetTopicAttributes",
				"sns:Subscribe",
				"sns:Unsubscribe",
				"sqs:CreateQueue",
				"sqs:DeleteQueue",
				"sqs:SetQueueAttributes",
				"sts:AssumeRole",
				"sts:GetCallerIdentity"
				],
				"Resource": "*",
				"Effect": "Allow"
		}
	]
}

2. Navigate to Roles.
3. Choose "Create role".
4. Select type of trusted entity "Another AWS Service".
5. In the "Account ID" enter the ID of your second Backup Account (you can obtain this number if you login in AWS console of the Backup Account and select "My account" in top right menu).
6. Select the checkbox "Require external ID" and enter a pass phrase to raise level of security for the role.
7. Press "Next: Permissions" button.
8. Enter the name of the policy selected on step 1 in "filter policies" edit box.
9. Select the policy with ticking on the checkbox in the first column.
10. Press "Next: Tags" button.
11. Enter tagging info if desired and press "Next: Review" button.
12. Give a name to the IAM Role - you will be using this name in the Veeam Backup for AWS UI (e.g. vb4aws_pol2role).
13. Press "Create role" button.
14. After successful creation of the role you will be able to see it in the list of all available roles.

Backup inside production deployment 

{
	"Version": "2012-10-17",
		"Statement": [
		{
			"Action": [
				"ec2:CopySnapshot",
				"ec2:CreateSnapshot",
				"ec2:CreateSnapshots",
				"ec2:CreateTags",
				"ec2:DeleteSnapshot",
				"ec2:DescribeAvailabilityZones",
				"ec2:DescribeImages",
				"ec2:DescribeInstances",
				"ec2:DescribeSnapshots",
				"ec2:DescribeSubnets",
				"ec2:DescribeTags",
				"ec2:DescribeVolumes",
				"ec2:ModifySnapshotAttribute",
				"events:DeleteRule",
				"events:DescribeRule",
				"events:ListTargetsByRule",
				"events:PutRule",
				"events:PutTargets",
				"events:RemoveTargets",
				"iam:GetRole",
				"iam:ListAttachedRolePolicies",
				"iam:ListInstanceProfilesForRole",
				"iam:ListRolePolicies",
				"iam:ListRoleTags",
				"iam:UpdateAssumeRolePolicy",
				"s3:GetBucketLocation",
				"sns:CreateTopic",
				"sns:DeleteTopic",
				"sns:ListSubscriptionsByTopic",
				"sns:ListTopics",
				"sns:SetTopicAttributes",
				"sns:Subscribe",
				"sns:Unsubscribe",
				"sqs:CreateQueue",
				"sqs:DeleteQueue",
				"sqs:SetQueueAttributes",
				"sts:AssumeRole",
				"sts:GetCallerIdentity"
				],
				"Resource": "*",
				"Effect": "Allow"
		}
	]
}

Challenge

Cause

Solution

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

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

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

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

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

More Information

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

[[DOWNLOAD|DOWNLOAD UPDATE|https://www.veeam.com/download_add_packs/vmware-esx-backup/update4b_exe/]]
MD5: 34d20a0f21bdee7a2e639e7bf332e993
SHA1: 5254b2130bc76aebb2e74e926a73a4bee36058cd

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: 302e41d90862728efb372518a053807d
SHA1: dd7bb3a519ea886bea280b591f4fe49eeaed5e20

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