Assured Recovery (AR) Test Related

Important! If you select test type as Instant Virtual Machine for the assured recovery, the Instant Virtual Machine-related known issues are applicable.

On vSphere 8.0, when Assured Recovery creates the Guest OS information for the Windows 11 VMs, it appears as Windows 10.
On vSphere 8.0, when Assured Recovery creates the Guest OS information for the Rocky Linux and AlmaLinux VMs, it appears as Red Hat Enterprise Linux 8.
Folders and files remain on the AR proxy server after completion of the Assured Recovery job.
Symptom
Folders created by Assured Recovery job are left on the AR proxy server. This issue happens because other processes, such as antivirus process or Windows system process are accessing those folders or files during the AR job.
For Assured Recovery IVHD test, folder like 'IVHD_JobId_<ID>_<UUID>' could be left under the Virtual Hard Disk Files Folder as specified in the AR task.
For Assured Recovery IVM test, folder like 'UDPARVM_<NodeName>_<UUID>' could be left under the VM Files Folder as specified in the AR task.
Solution
As a workaround, manually delete them later.
Assured Recovery (AR) test fails.
Symptom
When the source node has Windows 2008 SP1, Windows 2008 R2 SP2 or lower versions of Windows operating system installed, the Assured Recovery to Hyper-V 2016 or 2019 might fail and display the following error message:
cannot detect heartbeat.
Solution
As a workaround, change the Hypervisor to other versions or use VMware.
Unable to verify the virtual machine heartbeat when the destination is Windows 2016 Hyper-V.
Symptom
In Windows 2016 Hyper-V, the virtual machine heartbeat is not detected if the source machine has never applied the update related to the Hyper-V heartbeat where the Windows 2016 Hyper-V fails to contact the heartbeat of virtual machine. As a result, the assured recovery test may fail and displays the following warning message in the activity log:
Integration Service ISO file [C:\Windows\System32\vmguest.iso] does not exit
Solution
As the Integration services are delivered through Windows Update, the vmguest.iso image file is no longer needed and not included with Hyper-V on Windows Server 2016.
To install the services manually, refer to link.
Unable to verify the virtual machine heartbeat on Windows 2008 source machine.
Symptom
Unable to verify the virtual machine heartbeat when using Instant Virtual Machine type to VMware if the source machine is a Windows 2008 Server and boot from EFI system. The Assured Recovery may fail.
Solution
As a workaround, you need to manually add a Windows boot entry into the EFI enviornment.
Follow these steps:

After the VM boots into EFI environment, enter Boot Maintenance Manager for ESXi 5.x or 'Enter Setup' for ESXi 6.x.
Enter Configure boot options.
Select Add boot option.
Select the bootmgfw.efi file from the following folder path available on the EFI partition:

EFI\Microsoft\Boot\

Type the description as Windows Boot Manager.
Select Commit Changes and exit.
Select Reset the system to reboot the virtual machine.

Windows boots up successfully.
Assured Recovery fails to verify data integrity of the critical Windows system file.
Symptom
When you submit the Assured Recovery job, the job fails to verify data integrity of the critical Windows system file due to the compatibility issue of the NTFS file system between Windows 10 and Windows 2008 R2. In the lower version of Windows, the File System extension attribute of Windows 10 is not supported. As a result, the signature of system file does not match with the signature available in the Windows 2008 R2 Assured Recovery proxy and the command line chkdsk reports error.
Solution
As a workaround, upgrade the OS of Assured Recovery proxy to the matching OS version or higher.
Assured Recovery test fails to display the list of recovery points in node view.
Symptom
If you create an agentless backup plan and specify a local path as the backup destination, then Assured Recovery fails to display the list of recovery points when you manually start the Assured Recovery Test from node view.
Solution
As a workaround, use the shared folder as the backup destination or you can manually start the Assured Recovery Test from the plan view.
The Test most recent recovery points from date and time option does not work.
Symptom
When you launch Assured Recovery Test from plan for Linux node, the Test most recent recovery points from date and time option does not work.
Note: This issue occurs only for Linux agent-based plan and Linux virtual machines in Host-based agentless plan.
Solution
As a workaround, launch the Assured Recovery Test from node level with selected recovery point.
Assured Recovery Test job fails when you perform Instant Virtual Machine Test Type on Windows Hyper-V 2012 R2.
Symptom
Assured Recovery Test job fails when you perform Instant Virtual Machine Test Type on Windows Hyper-V 2012 R2 and displays the following error message:
Failed to communicate with deduplication Data role on server xxxxxx. Network error = [Connection timeout].
Failed to process the virtual disk file [C:\Folder\disk2061091111.vhdx] by the disk GUID [{097D7E83-E9C8-40D0-B766-7567E9CDD674}]. Error Message: No waiter is present for the filter's reply to this message.
Failed to process the virtual disk file [C:\Folder\disk2061091111.vhdx] by the disk GUID [{097D7E83-E9C8-40D0-B766-7567E9CDD674}]. Error Message: Failed to read disk data from the backup destination.
This issue occurs when all the following conditions are met:
- The Assured Recovery Test job is configured as Instant Virtual Machine Test Type and the target hypervisor is Windows Hyper-V 2012 R2.
- The backup destination is Recovery Point Server, the Recovery Point Server is installed inside a virtual machine, and the virtual machine is on the same Hyper-V server.
- The VM files folder is set in Assured Recovery Task and the VHDX files of Recovery Point Server are on the same volume of that Hyper-V server.
Note: The issue does not occur on Windows Hyper-V 2016.
Solution
As a workaround, perform any one of the following options:

Set the VM files folder on a different volume in Assured Recovery Task.
Use another Windows Hyper-V server as the destination.
Use Instant Virtual Disk Test Type instead.

The scheduled assured recovery test fails.
Symptom
If you modify the source node hostname and schedule the assured recovery test, the new backup job skips the scheduled assured recovery test and displays the following error message:
Sessions unavailable to be checked. The Assured Recovery job has been skipped.
Solution
Perform a new full backup job and deploy the plan again.
Assured Recovery (AR) job fails with UDP 8.0 Linux Agent.
Symptom
If the Linux Backup Server is installed on RHEL/Centos/OEL 8.3, which has default Red Hat kernel version 4.18.0-240.x.x.el8_3.x86_64 (for example: 4.18.0-240.1.1.el8_3.x86_64), the Assured Recovery job fails.
Solution
As a workaround, do the following:

Downgrade the RHEL/Centos/OEL 8.3 Red Hat kernel version (4.18.0-240.1.1.el8_3.x86_64) to the following kernel version:
4.18.0-193.el8.x86_64
Install the UDP 8.0 Linux Backup Server.
Run the AR job.
The AR job is completed.