Failed to start createIndex on MediaAgent

[NATD]

Another post CV7 question, this time on a newly installed server, but no different to 3 others done in past 2 weeks.

Windows 2003 R2 Standard
Exchange 2003 Standard

Installed File System & Exchange Mailbox iDA along with Media Agent.
Trying to do full backup of EITHER of the agents to a local magnetic library results int he following for which I can find no useful reference:

"Error Code: [14:96] Description: Failed to start createIndex on MediaAgent [hostname.domain.com*hostname*8400*8402]. Please check the following: network connectivity between client and MediaAgent, MediaAgent's name can be resolved, and this product's services are running on the MediaAgent. "

This absolutely isn't a network or DNS issue, even the CV console will say "ready if I ask it to check connectivity".

I've already reinstalled, repatched and tried recreating the ML on the servers onboard disks instead of my usual external USB but no difference.

I'll have a job opened tomorrow but if I can fix it tonight, even better

Thanks

 

[JG5]

Do you have any spaces or special characters in the display name of your Media Agents? Not the actual host name, but the media agent name. Check to make sure the host name and display name match. This may not be what's causing your issue, but I identified this bug shortly after upgrading. I was getting the exact same errors as you. Connectivity check was successful, all updates applied, etc.

Hope this helps.

 

[birky]

Hi

If comms are ok and the connectivity check returns 'ready' (so you can connect to port 8400) then I'd log a call...have you tried to telnet to port 8400?

Here's a CV KB article for error 1496...

KB Article ID: 10803
Article Type: Troubleshooting
Published: 2/21/2007 8:04:42 PM


Backup pending with error "Failed to start createIndex on MediaAgent.."
--------------------------------------------------------------------------------

Description:
Backups go to pending with the following error:

Failed to start createIndex on MediaAgent [..]. Please check the following: network connectivity between client and MediaAgent, MediaAgent's name can be resolved, and Galaxy services are running on the MediaAgent.
--------------------------------------------------------------------------------

Cause:
This error is typically a result of the client being unable to reach the MediaAgent.

1. Ensure that the Galaxy services are running on the MediaAgent.
2.Verify connectivity by entering the following from the client machine's command prompt:
telnet "mediaagent name" 8400
3. If you see the following connection error, then the client is unable to reach the MediaAgent:

Connecting To ma1...Could not open connection to the host, on port 8400: Connect failed
--------------------------------------------------------------------------------

Resolution:
In most cases this error is caused by a firewall between the client and MediaAgent. You will need to open up ports 8400-8403 in both directions to allow the client and MediaAgent to communicate with each other.

For more information on, please refer to the following document to ensure the firewall is properly configured for use with Galaxy:
Firewall Considerations

If there is no firewall or blocked ports between the Client and MediaAgent and the problems persist, please check your network to ensure that the Client can communicate with the MediaAgent.
--------------------------------------------------------------------------------

Additional Info:

--------------------------------------------------------------------------------

Keywords:

--------------------------------------------------------------------------------

ErrorCodes:
14:96
--------------------------------------------------------------------------------


Cheers



Birky
CommVault Certified Engineer

 

[NATD]

JG5: I saw your post before posting (although with the different wording thought it was something slightly different) and removed an underscore from the magnetic library name...didn't help me.

Birky: I'd seen that KB too...alas it didn't help. The telnet connects fine.

I'll post back with whatever the fix turns out to be.

As always, thanks for the replies.

 

[NATD]

I got this sorted last week but only just remembered to post back.

Sad thing is that the solution we had to settle for was to remove the media agent, iDAs and do the client from scratch.

The one thing we did see that was clearly wrong was that the media agent had managed to install to a second install directory (same path other than a '2' on the end) which I neither saw during installation or know why it did it, but I did add the media agent after the iDAs so I guess something made it pick a new path.