Prerequisites to Disaster Recovery
The following pre-requisites must be addressed prior to attempting system restoral:
- Resolution of Hardware issues - Resolve all hardware issues prior to attempting recovery unless you are standing up or bringing up a new machine.
- Upgrade Issues - Sometimes the EMS is being moved to a newer OS or machine and the EMS is being upgraded. This section lists issues related to upgrade.
- Hostname: To use the existing EMS license, you must have the same hostname. If your recovery strategy involves changing your hostname, a new license would need to be issued by Tellabs TAC.
- Version Upgrade:
- License: If you are upgrading to a new major version, you will need to have license re-issued by TAC.
- Restore prior to upgrade: You should install the same version as the failed EMS, then restore the EMS database, then upgrade to the new release to ensure proper upgrade of the database.
- Upgrade from Releases prior to 31.3 to 31.4 with and above when using Postgres for the database: Postgres does not provide for schema migration from 9.x used in SR31.3 releases to 14.x used in SR31.4 and above. As a result the schema of the EMS cannot be upgraded. See this section for instructions.
- Preserve Security: Ensure that you perform the OS and machine hardening steps prior to re-installing the EMS so that security is preserved.
- Ensure only one EMS Online: Best practice is prior to bringing the new EMS server online, you must ensure that the previous instance of the server is down and has been down for a minimum of 10 minutes. The OLT will only accept one EMS connection and the previous EMS instance if still up can block the ability of the new EMS instance to manage the OLT. Care should also be taken to ensure the previous EMS instance cannot come online as it could block management of the OLT.
Select one of the following mechanisms for EMS Recovery and follow the link to that section:
Previous | Next
FEEDBACK: Are you happy with this material?
Thank you Your feedback helps us to continually improve our content.