This issue has been solved.

Mount error. it's only on one SQL server the others work fine

Created: 20 Nov 2012 | Updated: 23 Nov 2012
Login to vote
0 0 Votes

I get the mount error (it's attached) here on one of my SQL servers. The other one runs fine. They both save to the same location as well. This just started last nite. There is nothing I can find in my error logs yet as there isn't any information other than what the error shows. All volumes are healthy and mounted as well. i'm using BE2012 and B2D only.

 

View Inline Image

this is all I have as of yet but i'm still looking as well.

Quick Look Solution

Hello,   The error clearly

Hello,

 

The error clearly states that media mount has failed due to the system shutdown in progess.

Seems the Backup Exec Job Engine Service lost connection with the Remote Agent for Windows Servers Service on the SQL Server.

Check the event viewer for any warnings or errors related to the shutdown.

Is this an ongoing issue with the backup or has it occurred only once ?

Check what is frequency of Windows Updates set to. And is it set to reboot the server after the updates are installed?

 

Filed Under

Comments

theOnkar's picture
theOnkar
Symantec Employee
20
Nov
2012
Votes
+1
SOLUTION

Hello,   The error clearly

Hello,

 

The error clearly states that media mount has failed due to the system shutdown in progess.

Seems the Backup Exec Job Engine Service lost connection with the Remote Agent for Windows Servers Service on the SQL Server.

Check the event viewer for any warnings or errors related to the shutdown.

Is this an ongoing issue with the backup or has it occurred only once ?

Check what is frequency of Windows Updates set to. And is it set to reboot the server after the updates are installed?

 

If this response answers your concern, please mark it as a "solution"

21
Nov
2012
Votes
0

Yeah I know about the system

Yeah I know about the system shutdown error but can't find anything in my event viewer not to mention the devices are actually online (and being written too) when I get this error.

The only thing that happened was a critical update which rebooted the server;that could have caused it.

It has only happend one time.

theOnkar's picture
theOnkar
Symantec Employee
22
Nov
2012
Votes
+1

  The only thing that

 

The only thing that happened was a critical update which rebooted the server;that could have caused it.

It has only happend one time.

So i guess this is what must have caused the server to reboot.

If this response answers your concern, please mark it as a "solution"