Hello Experts,
Firstly, please accept my apologies for my lengthy post.
I need your assistance with a problem we're having while performing granular data recovery of VM data from Azure Library.
We have VSA backups with extended retention in an Azure cloud library (hot+Archive tier) that are shared by two Windows media agents.
Attempting to recover data from a File Server instance.This file server has multiple virtual drives (vollumes), with three drives (C: E: H: each drive less than 1 TB) on one datastore and two more on another datastore (S: V: - with S: volume of 10 TB and V: volume of 5 TB). This VM/Subclient is backed up with intellisnap, and the backup is then copied to Azure.
When attempting to browse through the "Files and Folders" option from the Azure backup, the VSA subclient fails with the error " Browse failed due to error while mounting virtual machine."
I have already completed a recall index and Recall Archive storage workflow with success.
I thought the pseudomount was working because I could browse through a few volumes.
However, I later discovered that the S: and V: drives were not showing any data and were throwing pseudo mount errors.
I can drill down and see all of the volumes (as shown in photo 1), but I can't drill down any further for volumes S: and V: ; we are seeing the errors below with the live browse/pseudomount.
The pseudomount logs show repeated failures.
We also tried increasing the "SRV CLIENT RCV TIMEOUT" to 36000, but the problem persisted.
Could this be a problem with WAN latency (it's only 400ms)?
Should we copy the entire job to local disc and then attempt granular recovery via live browse?
What are your recommendations? Greatly appreciate your advise to fix this problem.
2022-11-01\ma02\PSEUDOMOUNT.log:
2932 17bc 11/01 10:17:48 ###### CPostRecallHandlerKernel::Done(1387) - One or more errors occurred while processing the request. (ERROR_ERRORS_ENCOUNTERED.774), Failed to complete IO request for ReqId=[1973] Lun=[0:0:2] Extents=[6203167-6203167] isRead=[1] (W32.774): 0x80070306:{CPostRecallHandlerKernel::Done(1387)/0x80070306:{CKernelIoHandler::SendIoResponseToKernel(1054)/W32.774.(One or more errors occurred while processing the request. (ERROR_ERRORS_ENCOUNTERED.774))-Failed to complete IO request for ReqId=[1973] Lun=[0:0:2] Extents=[6203167-6203167] isRead=[1]}} + {CKernelIoHandler::SendIoResponseToKernel(1054)/W32.774.(One or more errors occurred while processing the request. (ERROR_ERRORS_ENCOUNTERED.774))-Failed to complete IO request for ReqId=[1973] Lun=[0:0:2] Extents=[6203167-6203167] isRead=[1]}
. . .
2932 17bc 11/01 10:17:48 ###### CRecallContext::RecallComplete(82) - Job completed Status: Status FAIL; JobId=0; Path=503468fa-fea2-964b-aa65-283c0e080341\scsi0-2-.vmdk\0005T9OV
So you know, we can browse into the S: volume on newer backups that are on local disc copy and not on Azure extended retention backups.
Also, I'd like to keep the idea of copying the Job ID from Azure to the local disc copy as a last resort because we're talking about close to 5TB of data (Post-compression) and I'd like to avoid egress charges as much as possible.
