Affects users with VMs protected agentlessly which are turned off on the host side. After powering on the agentless VM on host and taking a new incremental snapshot, the VS export to Azure is successful and an incremental one.
Expected result:
Virtual standby export to Azure for ESXi agentless VMs should be successful even if the protected VM is turned off. 0 byte incremental should be transferred and exported.
Stack trace:
Replay.Core.Contracts.Export.ExportException: One or more dependent export tasks have failed. --> System.AggregateException: One or more errors occurred. -> System.AggregateException: One or more errors occurred. --> System.NullReferenceException: Object reference not set to an instance of an object.
at Replay.Core.Implementation.Export.VirtualMachineExporterBase.GenerateMountPointPath(String mountPointBasePath)
at Replay.Core.Implementation.Export.VirtualMachineExporterWindows.PostProcessExportedVolume(ExporterSourceVolume exporterSourceVolume, IPAddress replayServerAddress, IDiagnosticContext context)
at Replay.Core.Implementation.Export.VirtualMachineExporterWindows.
at Replay.Common.Implementation.VolumesAndDisksWorker.VolumesAndDisksWorker2.ForEachSourceVolume(Action1 action, Boolean includeAll, Boolean throwIfException)
-- End of inner exception stack trace --
-- End of inner exception stack trace --
-- End of inner exception stack trace --
at Replay.Core.Implementation.Export.ExportJob.ExportTask()
at System.Threading.Tasks.Task.Execute()
Workaround: Bring all exporting agentless VMs back online.
Our development team has created a patch to permanently fix this problem. Please open a case with technical support to retrieve this patch.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center