Challenge

Cause

• Backup of failover clusters is supported in Veeam Agent for Microsoft Windows managed by Veeam Backup & Replication only. You cannot process a failover cluster by Veeam Agent for Microsoft Windows operating in the standalone mode.
• Agent license with a server counter must be installed in Veeam Backup & Replication to enable Agent Management features including failover cluster support.
• Veeam Agent for Microsoft Windows supports Windows Server Failover Clusters running Microsoft Windows Server 2008 R2 and later.
• Workgroup clusters, multi-domain clusters, and mixed OS version clusters are not supported.
• Cluster Shared Volumes (CSV) are skipped automatically during the backup.
• The following Microsoft Failover Cluster applications are supported: Microsoft SQL Server Failover Cluster Instances (Microsoft SQL Server 2008 SP4 or newer), Microsoft SQL AlwaysOn Availability Groups, Microsoft Exchange Database Availability Groups (Microsoft Exchange Server 2010 or newer).
• When using Basic Availability Groups on Microsoft SQL Server 2016 Standard Edition, consider that secondary replica node cannot be backed up because the secondary node is not readable. See the following article for more information.
• AlwaysOn Clusterless Availability Groups are not supported.
• Managed by backup server job with failover cluster type does not support the file-level backup mode.
• Recovery must be performed via Veeam Backup & Replication console.

Solution

Microsoft Windows Server Failover Clusters, Microsoft SQL Server Failover Cluster Instances, SQL Always On Availability Groups

Microsoft Exchange Database Availability Group

Starting Veeam Backup & Replication Update 4 Microsoft Exchange database availability groups (DAG) nodes are now automatically processed in a sequential manner, so it is possible to use Veeam Agent for Microsoft Windows to process Microsoft Exchange Database Availability Groups (DAGs).

The procedure of adding a DAG to a Veeam Agent backup job differs depending on the type of the DAG that you want to process:

• For a regular DAG, the backup job configuration procedure is the same as for any failover cluster mentioned above, so all the steps above are relevant
• For an IP Less DAG (a DAG without an Administrative Access Point), the backup job configuration procedure is similar to the same procedure for standalone servers (the steps below show it in detail)

Then just add servers that act as DAG nodes to a Veeam Agent backup job for servers configured in Veeam Backup & Replication.

During the backup process, Veeam Backup & Replication detects that servers in the backup job are part of a DAG, and creates a transactionally consistent backup of Microsoft Exchange databases running on these servers (Veeam Agent process only passive database copies, active ones are excluded from VSS freeze operations).

Application-aware processing should be enabled for a consistent backup, log truncation and application-item restore possibility.

Challenge

Product Information:

Company name: Oracle Inc, America
Product Family: Oracle ZFS Storage Appliance
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: ZS5-4
Storage Category: Hybrid Storage
Drive quantity, size, type: 80 - 7200 RPM 8TB HDD | 4 - 200GB SSD Write Cache | 2 - 3.2TB SSD Meta Device
Storage configuration: ZFS RAID single parity, narrow stripes w/ 4 write cache SSDs in mirrored profile w/ 2 meta device SSDs in striped profile (for deduplication)
Firmware version: OS 8.8.x
Connection protocol and speed: SMB/CIFS, ISCSI, or NFS | 10GbE
Additional support: All models and configurations of ZFS Storage Appliance models with specifications equivalent or greater than the above

Oracle ZFS Storage Appliance is a powerful multi-protocol, multi-purpose, enterprise class storage solution that provides the flexibility for both primary and backup storage. Features such as variable compression, data deduplication, and large (1M) block sizes enables efficient, high throughput data storage for backup environments.

Veeam testing configuration:

Veeam Build Number: 9.5.0.1922

Job Settings:

Repository Settings:

Vendor recommended configuration:

Hardware Settings:

• Array deduplication used in testing – yes
• Array compression used in testing – yes (LZ4)
• Jumbo frames used in testing (MTU=9000)

Challenge

1. Memory exhaustion on Repository Servers with ReFS
2. Synthetic operations take a considerable amount of time
3. The Repository server becomes unresponsive or has significantly reduced performance

Cause

Solution

Operating System
 

• Windows Server 2019 (not officially supported until Veeam Backup and Replication 9.5 Update 4. Lab use only)
• Windows Server 2016 patched to at least September 2018 updates (KB4343884 or later)
• Windows 10 Pro for Workstations

Hardware
 

• CPU: at least 1 core per each concurrent backup proxy task and at least 1 core for each two concurrent repository tasks recommended
• RAM: Backup repository server running other backup roles should have an appropriate amount of RAM for each role
• Storage: 64K ReFS volume formatting is recommended

3rd Party Software
 

• Antivirus software (except Windows Defender)
• Microsoft Configuration Manager Client

More Information

Challenge

Cause

Solution

Challenge

Cause

Solution

Challenge

Cause

• Backup of failover clusters is supported in Veeam Agent for Microsoft Windows managed by Veeam Backup & Replication only. You cannot process a failover cluster by Veeam Agent for Microsoft Windows operating in the standalone mode.
• Agent license with a server counter must be installed in Veeam Backup & Replication to enable Agent Management features including failover cluster support.
• Veeam Agent for Microsoft Windows supports Windows Server Failover Clusters running Microsoft Windows Server 2008 R2 and later.
• Workgroup clusters, multi-domain clusters, and mixed OS version clusters are not supported.
• Cluster Shared Volumes (CSV) are skipped automatically during the backup.
• The following Microsoft Failover Cluster applications are supported: Microsoft SQL Server Failover Cluster Instances (Microsoft SQL Server 2008 SP4 or newer), Microsoft SQL AlwaysOn Availability Groups, Microsoft Exchange Database Availability Groups (Microsoft Exchange Server 2010 or newer).
• When using Basic Availability Groups on Microsoft SQL Server 2016 Standard Edition, consider that secondary replica node cannot be backed up because the secondary node is not readable. See the following article for more information.
• AlwaysOn Clusterless Availability Groups are not supported.
• Managed by backup server job with failover cluster type does not support the file-level backup mode.
• Recovery must be performed via Veeam Backup & Replication console.

Solution

Microsoft Windows Server Failover Clusters, Microsoft SQL Server Failover Cluster Instances, SQL Always On Availability Groups

Microsoft Exchange Database Availability Group

Starting Veeam Backup & Replication Update 4 Microsoft Exchange database availability groups (DAG) nodes are now automatically processed in a sequential manner, so it is possible to use Veeam Agent for Microsoft Windows to process Microsoft Exchange Database Availability Groups (DAGs).

The procedure of adding a DAG to a Veeam Agent backup job differs depending on the type of the DAG that you want to process:

• For a regular DAG, the backup job configuration procedure is the same as for any failover cluster mentioned above, so all the steps above are relevant
• For an IP Less DAG (a DAG without an Administrative Access Point), the backup job configuration procedure is similar to the same procedure for standalone servers (the steps below show it in detail)

Then just add servers that act as DAG nodes to a Veeam Agent backup job for servers configured in Veeam Backup & Replication.

During the backup process, Veeam Backup & Replication detects that servers in the backup job are part of a DAG, and creates a transactionally consistent backup of Microsoft Exchange databases running on these servers (this by design processes only passive database copies, active ones are excluded from VSS freeze operations).

Application-aware processing should be enabled for a consistent backup, log truncation and application-item restore possibility.

Challenge

Cause

Solution

More Information

Challenge

Cause

vprob.storage.connectivity.lost
esx.problem.storage.connectivity.lost

Solution

More Information

Challenge

This article is intended to document how Forward Incremental works, and how its retention is enforced.

Solution

Forward Incremental Forever Backup Method – New in V8

Forward incremental-forever backup method is a default method for backup chain creation. To use this backup method, you must specify the following options in the backup job settings:

1. Select the Incremental backup mode.
2. Do not enable synthetic full backups and/or active full backups. If you enable synthetic and/or active full backups, Veeam Backup & Replication will produce a forward incremental backup chain (documented below).

The forward incremental-forever backup method produces a backup chain that consists of the first full backup and a set of forward incremental backups following it.

Veeam Backup & Replication creates a forward incremental-forever backup chain in the following way:

1. During the first run of a backup job, Veeam Backup & Replication creates a full backup file (VBK) on the backup repository.
2. During subsequent backup job sessions, Veeam Backup & Replication copies only VM data blocks that have changed since the last performed backup (full or incremental) and saves these blocks as an incremental backup file (VIB) in the backup chain.

Within this animation the lettered squares represent blocks on a disk.
 
Information regarding how retention works for this backup method can be found here:
https://helpcenter.veeam.com/docs/backup/vsphere/retention_forever_incremental.html?ver=95u4

Forward Incremental Backup Method

During the first run of a forward incremental backup, or simply incremental backup, Veeam Backup & Replication creates a full backup file (.vbk). During subsequent runs of the backup job, it will only retrieve changes that have taken place since the last run of the job (whether full or incremental) and saves this information as an incremental backup file (.vib). Each full backup files (.vbk) and its incremental files (.vib) that depend upon it are treated as a chain. Meaning that each incremental restore point depends on the one that came before it, the full restore point has no dependencies.




Within this animation the lettered squares represent blocks on a disk.

Incremental backup is the best choice if company regulation and policies require you to regularly move a created backup file to tape or a remote site. With incremental backup, you move only incremental changes, not the full backup file, which takes less time and requires less tape. You can initiate writing backups to tape or a remote site in Veeam Backup & Replication itself, by configuring Backup to Tape jobs.

If you decide to use the forward incremental backup method, it is necessary to schedule the creation of periodic active full or synthetic full backups. This will help you avoid long chains of increments, ensure safety of backup data, and allow you to meet the requirements of your retention policy. Below are animated examples of these things.










Within this animation the lettered squares represent blocks on a disk.

For more information please review the follow portions of the Help Center:
https://helpcenter.veeam.com/docs/backup/vsphere/incremental_forever_backup.html?ver=95u4
https://helpcenter.veeam.com/docs/backup/vsphere/retention_forever_incremental.html?ver=95u4
https://helpcenter.veeam.com/docs/backup/vsphere/forward_incremental_backup.html?ver=95u4
https://helpcenter.veeam.com/docs/backup/vsphere/retention_incremental.html?ver=95u4
https://helpcenter.veeam.com/docs/backup/vsphere/active_full_backup.html?ver=95u4
https://helpcenter.veeam.com/docs/backup/vsphere/backup_copy_remove_missing_point.html?ver=95u4

Challenge

Cause

Solution

1. Download private fix for Veeam Backup & Replication 9.5 U4 and extract on the Veeam Backup Server. 
2. Right-click on the installation file and click "Run as administrator"
3. Go through the wizard to install private fix.
4. Relaunch Veeam Backup Console and let Veeam automatically update hosts added to the Veeam server.

More Information

Challenge

Cause

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

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
• \\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

Cause

Solution

Antivirus Exclusions:

Folders on the Veeam Availability Orchestrator Server:

• C:\Program Files\Veeam
• C:\Program Files (x86)\Veeam
• C:\Program Files\Common Files\Veeam
• C:\Program Files (x86)\Common Files\Veeam
• VBRCatalog ( [HKLM\SOFTWARE\Veeam\Veeam Backup Catalog] CatalogPath value)
• C:\Windows\Veeam
• %programdata%\Veeam

Due to the complex nature of antivirus software some additional exclusions may be needed.

More Information

Challenge

Product Information:

Company name: Western Digital
Product Family:  IntelliFlash T-Series, HD-Series
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: T4100
Drive quantity, size, type: 3x 500GB SSD | 13x 2TB HDD
Firmware version: 3.7
Connection protocol and speed: iSCSI, 10GbE
Additional support: All models and configurations of T or HD-Series with specifications equivalent or greater than the above

T-Series and HD-Series enterprise storage arrays accommodate different grades of storage media—from hard disks to high-performance flash memory. Using patented IntelliFlash™ software architecture, data is organized and placed on the most appropriate media to deliver optimal performance with the best possible economics. Native SAN and NAS protocols enable you to simplify data management by storing application data, virtual machines, and unstructured data—all on a single array.

Veeam testing configuration:

Veeam Build Number: 9.5.0.1038

Job Settings:

Repository Settings:

Challenge

This article documents general performance expectations, best practices, and configuration advice, when using an EMC Data Domain appliance with deduplication as a repository for Veeam Backup & Replication.

Solution

For further information regarding how Veeam Backup & Replication works with EMC Data Domain DDBoost please review: https://helpcenter.veeam.com/docs/backup/vsphere/emc_dd.html

Performance Expectations

EMC Data Domain Deduplication Storage Systems provide both high compression and deduplication ratios so that data can be kept for extended periods. When a Data Domain is configured as a repository for Veeam Backup & Replication, write performance may vary depending upon the particular EMC Data Domain Deduplication System model, protocol, and backup infrastructure architecture.

When attempting to read data from a Data Domain it must rehydrate and decompress each block, for this reason operations which read from the Data Domain will perform slower than non-deduplicated storage, this is more noticeable with operations which use random I/O. All restores will occur as fast as the environment can accept new information, and as fast as the Data Domain can decompress and rehydrate the blocks.

For quick recovery you may consider using fast primary storage and keeping a several restore points (3-7) for quick restore operations such as Instant Recovery, SureBackup, Windows or Other-OS File restores since they generate the highest amount of random reads. Then use the DataDomain as a secondary storage to store files for long term retention. If an EMC Data Domain Deduplication System will be used as primary storage, it is strongly suggested to leverage alternative restore capabilities within Veeam Backup & Replication such as Entire VM restore and VM files restore. This may result in faster recovery capabilities when used with EMC Data Domain Deduplication Systems than Instant Recovery and File Level Restore operations.

Instant Recovery

• This type of restore can be effected adversely by the aforementioned limitations of a Data Domain appliance, and also the type of VM being restored. Highly transactional VMs will require more IOPS from the Data Domain during the Instant Recovery than others. With this in mind you can expect to only be capable of running only a few Instant Recoveries simultaneously. Instant Recovered VMs that are started from a backup file stored on a Data Domain may react or start slowly as the majority of their read operations will be hindered by the Data Domain.
• For VMware users it is highly advised when performing an IR that the user select to have virtual disk updates redirected to a high performance Datastore. This will improve performance by caching written blocks to low latency storage.
• It is advised that if the VM is intended to be made permanent that the VM be migrated to production storage as soon as possible after the Instant Recovery has begun.

File Level Restores

When performing Veeam Backup & Replication File Level Restore (FLR) capabilities slow recovery times may be experienced. During Veeam FLR recovery capabilities, a significant amount of read activity occurs when accessing the Veeam “service data” metadata for each individual file as the Veeam backup files are not arranged in sequence. This read activity must be performed to determine the location of the data block(s) associated with each file during granular restore sessions. This significant level of random access is not recommended with archive tier storage devices because they are designed for optimal performance with sequential read operations. Veeam recommends implementing EMC Data Domain Deduplication Storage Systems as a secondary target for these use cases as the more random read operations, the slower the restore will be with EMC Data Domain Deduplication Systems.

• The backup browser may take longer than usual to open if an increment is selected and furthermore by that increments distance from the full restore point.
• Navigating between folders within the Backup Browser may take additional time as each folder’s content must retrieved from the backup file to display it.

Backup

• Reverse Incremental performance will be very poor due to its highly random I/O.
  Note: When the Backup Job is configured with a DDBoost repository, Veeam Backup & Replication will prevent Reversed Incremental from being selected by the user.
• Synthetic Full creation will be very slow to a Data Domain, unless using DDBoost.
• Synthetic Full with Transforms are not advised.

Backup Copy

• A retention longer than 30 is not advisable as restore operations will diminish in performance.
• The Health Check option may take a very long time as it is performing a read operation.

Replication

• Using the Datadomain to store Replica metadata is not advisable.
  Note: Veeam Backup & Replication will prevent the user from selecting a DDBoost repository.

Veeam Backup & Replication Configuration

Parallel processing (global option):

This option significantly accelerates the backup process and decreases the backup window since virtual disk data is gathered simultaneously. It also dramatically increases fragmentation in the backup files causing high random read for any restore operation. The greater volume of VMs or disks processed simultaneously will increase fragmentation and result in slow restore times. You may consider disabling Parallel Processing, this will decrease backup performance, but increase restore performance.

Storage optimization (job option):

Setting the storage optimization to Local 16TB+ has been shown to improve the effectiveness of Data Domain’s deduplication. The larger this value is, the smaller the preparation phase will be for a backup task and less memory will be used to keep storage metadata in memory.

Inline-deduplication (job option):

Since EMC Data Domain Deduplication Systems have excellent hardware deduplication and compression capabilities, it is highly advised that Veeam built-in deduplication be disabled to decrease load on the backup proxy.

Decompress backup block before storing(repository option):

Veeam strongly recommends enabling this option so that raw data is sent to the EMC Data Domain Deduplication System, leveraging its global deduplication and compression capabilities. Leaving Veeam compression enabled may significantly impact EMC Data Domain deduplication capabilities resulting in high load and slow backup jobs.

Use Per-VM Backup Files(repository option):

Veeam recommends enabling this option so that there is improved performance writing and reading data from the EMC Data Domain Deduplication System. This option is enabled by default when adding the repository as a Deduplicating Storage Appliance.

Backup Mode

• For CIFS/NFS presented repositories Forward incremental mode with periodic Active full backups is recommended to avoid the rehydration penalty during synthetic operations.
• For DDboost enabled repositories Forward incremental mode with either Active full or Synthetic full backups is recommended. Synthetically produced full backups will generally have the best restore performance and reduce the time VM is run off of a snapshot during the backup job run. However in some environments an Active Full job may run faster.
• Transforming previous backup chains into rollbacks is not advisable for both repository types.
• For forever forward incremental backup and backup copy on DDboost enabled repositories, the option “Defragment and compact full backup file” should be enabled if available. In most cases a weekly schedule is appropriate. This helps to avoid excessive growth of pre-compression data size for the full backup file.

Repository Performance Expectations and Configuration

If DDBoost is not licensed on the Data Domain system it must be added as a CIFS type or Linux type repository. It is advised to use a Linux server with the volume mounted via NFS as a relay server to help improve performance. Under some circumstances, CIFS or NFS communication may perform better than DDBoost with Veeam Backup & Replication v8 because of the limitation of a single thread per backup job when using DDBoost. DDBoost has been shown to improve performance when performing Synthetic Fulls.

With Veeam Backup & Replication v9, support for EMC Data Domain Boost is enhanced with the introduction of the following capabilities:

• Support EMC Data Domain Boost 3.0
• Reduced impact of storage fragmentation during restore operations even with enabled parallel processing. This feature allows Veeam to store the VM backup in the dedicated backup chain so that fragmentation ratio will be minimum.
• Reduce the impact of the block size so you may define any block size without impact on the restore process. Veeam will be able to read data granularly so amount of the redundant will be minimum.

With DDBoost

If the Data Domain System is licensed for DDBoost please proceed to configure it using the following steps.

1. Launch the creation of a new Repository, on the Type tab select Deduplication storage appliance.
2. Select the deduplication storage as EMC Data Domain.
3. On the next tab configure the information to for connecting to the Data Domain appliance.
4. On the Repository tab click Browse and select the necessary location from the list of available paths.
5. The default settings can be taken for the last steps in repository configuration.
   Unless your environment requires you to specify a different vPower NFS Server.

Without DDBoost

CIFS

1. Launch the creation of a new Repository, on the Type tab select CIFS
2. On the next tab configure the path to which the Repository will write to, and set credentials to access that share.
3. On the Repository tab within the advanced section, enable “Decompress backup data blocks before storing”
4. The default settings can be taken for the last steps in repository configuration.
   Unless your environment requires you to specify a different vPower NFS Server.

NFS

The Data Domain will need to be configured for NFS access, and configure a Linux server to mount the volumes from the Data Domain via NFS. Please refer to the following links for further information regarding connecting Linux to the Data Domain via NFS:

http://forums.veeam.com/veeam-backup-replication-f2/veeam-datadomain-and-linux-nfs-share-t8916.html

http://tsmith.co/2014/veeam-and-datadomain/

1. Launch the creation of a new Repository, on the Type tab select Linux
2. On the next tab select the Linux server that we be connected to. If it is not present in the list select “Add New…”
3. On the Repository tab specify the path on the Linux server that leads to where you mounted the Data Domain via NFS. On this tab in the advanced section enabled “Decompress backup data blocks before storing”.
4. The default settings can be taken for the last steps in repository configuration.
   Unless your environment requires you to specify a different vPower NFS Server.

Challenge

Cause

Solution

More Information

Challenge

This KB article is to create merged licenses that are for Veeam Backup & Replication v9.5 Update 3a and earlier. For Veeam Backup & Replication 9.5 Update 4, please follow this guide: https://www.veeam.com/kb2879

This KB only applies to versions Veeam Backup & Replication v9.5 U3a and earlier, Veeam ONE v9.5 Update 3a and earlier, and Veeam Agents v2.

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

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

Solution

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

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

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

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

More Information

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

Challenge

Cause

Solution

More Information

Challenge

Veeam Lifecycle Policy

End-of-Fix
When a product version reaches this stage, no further Updates, Patches or Hotfixes will be created for it (exceptions may be made on case-by-case basis). A version that has reached End of Fix, but that has not reached End of Support is still fully supported. However, if Veeam determines that an issue you are facing is fixed in a generally available version, you will be required to update to it.

End-of-Support
When a product version reaches this stage, this version will no longer be supported by Veeam. To get support, you need to have an active maintenance contract, and perform an upgrade to at least the version that has not reached End of Support stage yet.

End-of-Life
When a product version reaches this stage, it is no longer available for download from Veeam web site. Exceptions may be made on a case-by-case basis.

Solution

More Information

The latest version of all Veeam products can be found at: https://www.veeam.com/downloads.html

Previous version of Veeam software products can be found at: https://www.veeam.com/older-versions-download.html

Further details can be found in Veeam's EULA. 

Challenge

Cause

• each guest VM should have the cluster feature installed
• all members of guest cluster should be on-line
• VHDSet shouldn't be used as Cluster Shared Volume (CSV)
• folder on CSV containing VHDSet files should have proper permissions settings
• guest operating system should be Windows 2016
• All VHDSet files must reside on CSV or SMB shares
• Microsoft supports legacy shared VHDX on Windows 2016, but this feature cannot be used like a workaround, because it cannot be included in application-consistent checkpoints, therefore Veeam doesn't support backup of such disks on Windows Server 2016

Solution

1. Determine the GUIDS of all VMs that use the folder. To do this, start PowerShell as administrator, and then run the following command: 

   get-vm | fl name, id

   sample output: 

   Name : BackupVM
   Id : d3599536-222a-4d6e-bb10-a6019c3f2b9b
   Name : BackupVM2
   Id : a0af7903-94b4-4a2c-b3b3-16050d5f80f

2. For each VM GUID, assign the VMMS process full control by running the following command:

   icacls <Folder with VHDS> /grant "NT VIRTUAL MACHINE\<VM GUID>":(OI)F

   Example:

   icacls “c:\ClusterStorage\Volume1\SharedClusterDisk” /grant "NT VIRTUAL MACHINE\a0af7903-94b4-4a2c-b3b3-16050d5f80f2:(OI)F"
   icacls “c:\ClusterStorage\Volume1\SharedClusterDisk” /grant "NT VIRTUAL MACHINE\d3599536-222a-4d6e-bb10-a6019c3f2b9b:(OI)F"