Event Code 13:30 Unable to communicate with MediaAgent

Last post 08-07-2018, 7:12 PM by georgeparker. 4 replies.
Sort Posts: Previous Next
  • Event Code 13:30 Unable to communicate with MediaAgent
    Posted: 07-27-2018, 12:06 AM

    Hi,

    Running Commvault V11.

    I'm running 4 restore jobs where the traffic flow is coming from the one MediaAgent/disklibrary to one target client. 2 of these jobs have started reporting "event code 13:30 - unable to communicate with mediaagent on host [IP address of MA]. Please check the network connectivity between the client and mediaagent...". These events are repeating every 2 minutes. I can't see any comms issues between the MA and client.

    Any ideas what could be causing this?

    George.

  • Re: Event Code 13:30 Unable to communicate with MediaAgent
    Posted: 07-27-2018, 3:02 PM
    • Aplynx is not online. Last active: 08-14-2018, 3:33 PM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Expert
    • Points 1,366

    The end of that error should give you a machine and the process generating that error. The process willl have a corresponding log in the logs folder on the machine. Track for that time frame and it should give you an idea. 

  • Re: Event Code 13:30 Unable to communicate with MediaAgent
    Posted: 08-02-2018, 6:50 PM

    Hi Liam, thanks for your help.

    The logs don't reveal all that much. I have suspended 3 of the 4 restore jobs and the one that I've kept running isn't reporting error 13:30, but it virtually ground to a halt.... The Job Details box says "Last Job Update Time: 3 days 15 hours 57 mins ago". On the client I'm restoring to, the ExMBRestore.log is being constantly written to, with just a whole bunch of:-

    08/03 04:23:30 409744 FclRestore::receiveRestoreMsgs() - Received FSR_MSG_KEEPALIVE
    19340 8e4   08/03 04:23:30 409744 Sent Keep Alive Message to FSRestoreHead
    19340 8e4   08/03 04:53:31 409744 FclRestore::receiveRestoreMsgs() - Received FSR_MSG_KEEPALIVE
    19340 8e4   08/03 04:53:31 409744 Sent Keep Alive Message to FSRestoreHead
    19340 8e4   08/03 05:23:32 409744 FclRestore::receiveRestoreMsgs() - Received FSR_MSG_KEEPALIVE
    19340 8e4   08/03 05:23:32 409744 Sent Keep Alive Message to FSRestoreHead
    19340 8e4   08/03 05:53:34 409744 FclRestore::receiveRestoreMsgs() - Received FSR_MSG_KEEPALIVE
    19340 8e4   08/03 05:53:34 409744 Sent Keep Alive Message to FSRestoreHead
    19340 8e4   08/03 06:23:35 409744 FclRestore::receiveRestoreMsgs() - Received FSR_MSG_KEEPALIVE
    19340 8e4   08/03 06:23:35 409744 Sent Keep Alive Message to FSRestoreHead
    19340 8e4   08/03 06:53:35 409744 FclRestore::receiveRestoreMsgs() - Received FSR_MSG_KEEPALIVE
    19340 8e4   08/03 07:23:36 409744 FclRestore::receiveRestoreMsgs() - Received FSR_MSG_KEEPALIVE
    19340 8e4   08/03 07:23:36 409744 Sent Keep Alive Message to FSRestoreHead
    19340 8e4   08/03 07:53:37 409744 FclRestore::receiveRestoreMsgs() - Received FSR_MSG_KEEPALIVE
    19340 8e4   08/03 07:53:37 409744 Sent Keep Alive Message to FSRestoreHead
    19340 8e4   08/03 08:23:38 409744 FclRestore::receiveRestoreMsgs() - Received FSR_MSG_KEEPALIVE
    19340 8e4   08/03 08:23:38 409744 Sent Keep Alive Message to FSRestoreHead

    George.

  • Re: Event Code 13:30 Unable to communicate with MediaAgent
    Posted: 08-07-2018, 10:48 AM

    If the log is being written to, is the restore destination being written to as well? Please let us know if you're still having an issue.

  • Re: Event Code 13:30 Unable to communicate with MediaAgent
    Posted: 08-07-2018, 7:12 PM

    Hi,

    No the restore destination was not being written to as well.

    I logged a support case with Commvault and they discovered that the ExchRestore process on the destination client's Process Manager was hung, so he killed it, then suspended and resumed one of the restore jobs which spawned a new ExchRestore PID and the data began restoring ok again. After a while I resumed one of the other restore jobs which created a second ExchRestore PID on the destination client's Process Manager and it too began restoring data ok, but after a while one or both restore jobs seemed to grind to a halt again - their ExchRestore PIDs disapeared even though they were still in a "running" state. I suspended both jobs and resumed just one of them which spawned a new ExchRestore PID and data once again began restoring. So it appears that I seem to be able to have just a single restore job running to the destination client. The destination client itself is not a busy server, so is the issue with the MA perhaps?

    George.

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2018 Commvault | All Rights Reserved. | Legal | Privacy Policy