• State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 28 subscribers
  • Views 12401 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Virtual standby to ESXi 6 host failed -

kenton.doerksen
over 7 years ago

I recently moved from using the agent to an agentless deployment (yep, archived all my old recovery points first!), and have run into a few hiccups on the way.  The initial backups all work well, replication works well, but the virtual standby's that I'm creating have been running into odd errors.  Anyone else see this?

 

Anyone else run into this?  A google of the error doesn't return much of anything.  The Core's subsequent attempt to export was very odd.  Originally it only attempted to export the 9GB of changed data, which surprised me, given the failure on the initial export, but then when the status got to 8.2/9GB, then it changed to 8.8/9.6, and kept rising until it got to 18.83/19.82GB at which time I got the "post-processing" message, which ultimately resulted in the same error messages.

Here's the stack trace from the original error:

Server side:

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. ---> Replay.Common.Contracts.TevoLib.TevoLibraryErrorException: TevoDismountVolume failed with error -2147024893 (0x80070003 - The system cannot find the path specified) at Replay.Common.NativeWrapper.TevoLib.TevoLibraryErrorException.Throw(String functionName, Int32 errorCode) at Replay.Common.NativeWrapper.TevoLib.TevoLibWrapper.DismountVirtualDiskVolume(VolumeName volumeName) at Replay.Core.Implementation.Mounts.LocalMount.DismountInternal() at Replay.Core.Implementation.Mounts.LocalMount.Dismount() at Replay.Core.Implementation.Export.VirtualMachineExporterWindows.<>cDisplayClassa.b7(Exception e) at System.AggregateException.Handle(Func`2 predicate) at Replay.Core.Implementation.Export.VirtualMachineExporterWindows.PostProcessExportedVolume(ExporterSourceVolume exporterSourceVolume, IPAddress replayServerAddress, IDiagnosticContext context)

--- 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()

 

Replay.Common.Contracts.TevoLib.TevoLibraryErrorException: TevoDismountVolume failed with error -2147024893 (0x80070003 - The system cannot find the path specified) at Replay.Common.NativeWrapper.TevoLib.TevoLibraryErrorException.Throw(String functionName, Int32 errorCode) at Replay.Common.NativeWrapper.TevoLib.TevoLibWrapper.DismountVirtualDiskVolume(VolumeName volumeName) at Replay.Core.Implementation.Mounts.LocalMount.DismountInternal() at Replay.Core.Implementation.Mounts.LocalMount.Dismount() at Replay.Core.Implementation.Export.VirtualMachineExporterWindows.<>cDisplayClassa.b7(Exception e) at System.AggregateException.Handle(Func`2 predicate) at Replay.Core.Implementation.Export.VirtualMachineExporterWindows.PostProcessExportedVolume(ExporterSourceVolume exporterSourceVolume, IPAddress replayServerAddress, IDiagnosticContext context)

Close
Parents
  • 0 over 7 years ago
    They're suggesting the following, which may be, but I doubt. When I was backing these systems up using the agent, then the Virtual standby worked fine, but I began having the issues when I converted to using the agentless backup.

    That said - I found a new symptom - when setting up my initial virtual standby it gave me an error that the boot disk was on disk2000, or some such thing. I'll have to see what I can find out about that one.


    "Cause
    Filesystem corruption more than likely exists on the production protected server. Investigation of the System Event logs on the Core may reveal disk and ntfs errors referencing the AppAssure mount point.

    Source: Ntfs
    ID: 55
    Date: 06/23/2015 17:09:04
    Description: A corruption was discovered in the file system structure on volume C:\ProgramData\AppRecovery\ExportMounts\AgentName_247168f0-3e65-4dc4-a378-c49f1ae26ea7.

    The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x9000000000009. The name of the file is "".
    Resolution
    On the Agent machine, schedule a chkdsk /f /r on the volume showing failure in the logs. Once complete continue to monitor the virtual standbys on the Core.
Reply
  • 0 over 7 years ago
    They're suggesting the following, which may be, but I doubt. When I was backing these systems up using the agent, then the Virtual standby worked fine, but I began having the issues when I converted to using the agentless backup.

    That said - I found a new symptom - when setting up my initial virtual standby it gave me an error that the boot disk was on disk2000, or some such thing. I'll have to see what I can find out about that one.


    "Cause
    Filesystem corruption more than likely exists on the production protected server. Investigation of the System Event logs on the Core may reveal disk and ntfs errors referencing the AppAssure mount point.

    Source: Ntfs
    ID: 55
    Date: 06/23/2015 17:09:04
    Description: A corruption was discovered in the file system structure on volume C:\ProgramData\AppRecovery\ExportMounts\AgentName_247168f0-3e65-4dc4-a378-c49f1ae26ea7.

    The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x9000000000009. The name of the file is "".
    Resolution
    On the Agent machine, schedule a chkdsk /f /r on the volume showing failure in the logs. Once complete continue to monitor the virtual standbys on the Core.
Children
No Data