• State Suggested Answer
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 27 subscribers
  • Views 5386 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

RR 6.1 exchange 2013 in DAG mode checksum and mount failed

guillaume.chartrand
over 7 years ago

Hi, I have 2 server Exchange 2013 Mailbox server in DAG mode and when the nighly job (cheksum and mount) try to run on the active database server, an error occurs:

An argument was not valid in code located in or called by 'CheckJobHelper.GetVolumeImageFromPath'

The other server with the passive database no error occurs and the green light appears on each recovery point.

 

Do you ever seens this kind of errors?

I didn't try to switch the active/passive to see if the errors will occurs on the second one. I will try it but before that I asked the question for you.

Thanks

  • 0 over 7 years ago

    Hi Guillaume:
    Please try mounting a recovery point from the active node and see if you can navigate to the database location -- sometimes due to specific permissions this is not possible.
    In other cases, the checksum job my conflict with other nightly job and thus fails.
    To take this out of the picture, make sure that no RR jobs on the node are running and force a checksum check and a mountability one.
    Let us know how it goes.

  • 0 over 7 years ago
    I got an error on both recovery point( on agent with active DB and on agent on passive DB) The same errors is
    The core service is unavailable, please verify network connexion or if the service is running.

    I know all these thins is up because if I mount a restore point from an filesystem agent, I can browse the file and folder.
  • 0 over 7 years ago
    Hi Guillaume:
    Please open a case with our support team. Looks that there is some in depth troubleshooting to be performed...
  • 0 over 7 years ago
    Hi, The problem is resolved. Stupid error, I don't know why but it's the only protected machine who the agent wasn't updated to 6.1, it was still on 5.4.3. So when I updated the agent, run a snapshot again the mount and checksum was successfull.

    Try to looking deeper that I should.
    Thanks for your suggestion