Disaster Recovery Guidelines and Information

Owned by Mahnoor Khan (Deactivated)
Last updated: Apr 30, 2024 by Micah Gallant
2 min read

Summary

This article describes the baseline disaster recovery scenario for an EngageIP billing system using one webserver and one SQL server. It does not attempt to cover every implementation, scenario, configuration, or module set (i.e. Telecom, Provisioning etc.) This document makes a number of assumptions about the quality of backup material, network configurations and other items which will be listed below.

Assumptions

This document makes the following assumptions (in no particular order):

Note: The reason for these assumptions is that EngageIP uses encrypted connection strings which will need to be replaced and cannot be edited.

  • A recent backup of the EngageIP databases was made and backed up off server / off site (including: Boss, BossCollector, BossRate, EngageIP Master, alternatively named EngageIP, EngageIPCollector)

  • The new server IP addresses are the same as the original IPs that EngageIP was using

  • The SA username and password used by EngageIP is the same

  • The databases are restored using the same names

  • EngageIP Billing directory was fully backed up including:

    • UDR Usage data

    • Usage Importer and Rater

    • Any custom customer portal files used

  • EngageIP Billing is installed in the same directory on the webserver

  • You have recorded the full license key for EngageIP

  • You have a backup copy of the EngageIP 9.x billing installer executable for the version that was installed on the server (LogiSense can also provide installers here as needed)

  • EngageIP Billing services (EngageIP Billing, EngageIP Event Manager)

  • The EngageIP registry is backed up

    • [HKEY_LOCAL_MACHINE/SOFTWARE/EngageIP/Parameters]

Scenario

Both the SQL server and Webserver have crashed and are inaccessible - Backups were made the previous night of the databases and the full EngageIP billing directory, and including all the assumed backups above.

  1. Reinstall MSSQL, assign the same SA username and password or create the user that was used previously again with the same password and permissions

    • See the related article specific to the service area configuration for MSSQL 2019

  2. Install IIS

  3. Run the EngageIP installer, install it to the same location as was previously installed. Follow the knowledge base article for installing EngageIP

    • Paste the backed up copy of the EngageIP Billing directory over top the newly installed directory so that all customization, usage directories etc. are back in place

  4. Restore the exported Registries as listed under the assumptions

  5. Restore the backed up databases over top the new databases on the SQL server

  6. Configure any scheduled tasks that may have existed related to EngageIP modules or integrations including (if previously a scheduled task)

  7. Start EngageIP Services

    • EngageIP Billing

    • EngageIP Event Manager

    • EngageIP Job Service

    • EngageIP Rating service

    • Others as required

  8. Review the Configuration link in the AdminPortal, it will list whether the services are successful and provide information on particular issues relating to the configuration of EngageIP

  9. If applicable confirm that RADIUS authentication is working and / or FTP for usage data transfer and access to AdminPortal is available

See related articles for specific instruction on items discussed.