11-04-2011 07:13 AM
Please help!
Although CASO was sharing dedupe storage to MMS,
Although the CASO server has been downed by the hardware failure,
if it looks at, it is Backup EXE 2010 R3 at the server of MMS.
If a management console is seen, answering will become "nothing" and it will not start.
A CASO server's restoration is in a difficult situation,
Although it thought that restoration environment
when something is with obstacles was securable by the server of MMS,
he will be in the state where operation by MMS cannot be performed,
either, and I am troubled very much.
Although irregular correspondence may be sufficient, isn't there any good means to work something???
11-05-2011 06:31 AM
Hi,
OK, so what I see has happened is this:
1. CASO server died due to a hardware failure.
2. As a result, the MMS server cannot start up its services?
If this is the case, then you centralised your device and media information on the CASO, meaning that if something caused the CASO to stop, all MMS servers would be affected too.
Open up the registry of the MMS and back it up BEFORE making any changes. Once you do, do a search for the name of the CASO server and replace it with the name of your MMS. This basically defaults all the settings so that the MMS points to its own internal BEDB again. You can't use BEutility as it's going to try contacting the CASO...which it will fail in doing.
Thanks!
11-05-2011 05:46 PM
Hi,Thanks!
This case,not centralised your device and media information on the CASO.
So,"deduplication storage" is shared between caso.
Only MMS using the share does not start.
MMS which does not use the share is having started.
11-06-2011 01:32 AM
...OK, then open up BEutiility and remove it from the CASO...so you make it a stand-alone again. Then readd it to the CASO.
Lastly...any specific error messages you're receiving, please add them here...
11-06-2011 03:44 AM
Thanks,but....
I challenged remove it from the CASO by BEutiility,
but can't becaouse CASO is not running.
CASO Server is not start.
I don't have no idea that restore data.
11-06-2011 05:41 PM
From the registry, change the name of the HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows Server\Adamm\Database Server Name
to the local server name instead of the CASO server
Also, you may try a solution per this KB - http://www.symantec.com/docs/TECH44702
11-07-2011 04:57 AM
Well, you need to read my first post where I told you to edit the name of the CASO server out of the registry.
11-07-2011 05:37 AM
OK,thenk you.
I try in the near future.
Does it suit, although it is "Backup Exec 2010 R3" ?
.