How to remove the Managed Backup Exec Server(MBES / MMS) feature when communications have been lost to the Central Admin Server (CAS) and the feature is grayed out.
Problem
This document will outline the steps that need to be followed to get a Managed Backup Exec server back to standalone even though the option is grayed out and communications has been lost between it and the Central Admin Server (CAS).
Solution
1. Open Windows Programs and Features on the Managed Backup Exec Server.
2. Select Backup Exec from the list and click the 'Change' button.
3. Select the Next button with the default selection.
4. Click past the 'Add Licenses, 'Review Licenses', 'Configure Features' and 'Choose Language'.
5. Select the 'Locally managed Backup Exec Server' radio button and click the Next button.
6. An error pops up explaining that the MBES was unable to contact CAS.
7. Click OK on the Error dialog box, and then choose the SQL Instance used for the BE installation of MBES.
Note: If the ERROR popup does NOT happen then Backup Exec detected a server with the same name as the CAS on the network. If it is the real Central Admin Server(CAS) and it is still running correctly you should be able to remove the MBES from the storage tab on the CAS and this will remove it from that system and make the MBES standalone after service restart on the MBES.
8. Click Next. Then from the Summary page click Install to complete the process.
9. After the installation has complete, open the Backup Exec Console/UI and add any storage devices that may be needed.
10. Once the Central Admin server is back online, the MBES can be re-joined using the traditional method.
NOTE: When CAS is down, MBES backup exec device and media service will not start. With help of above steps the MBES can be brought online i.e. its services will start. Since all device and media information resides on the CAS, on this MBES when the services start the storage will need to be inventoried and catalog (depending on what catalog mode was set on the MBES earlier. If centralized was set then catalog job will need to be run on the storage. If replicated or distributed catalog mode is set then catalog will not be needed. Inventory would be enough. These steps will help to restore data in absence of CAS.
References
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.