(12.03-en) Disaster Recovery: UMS with an External Database

The following instructions require a proper backup of your environment, see the "External Database" section under (12.03-en) Creating a Backup of the IGEL UMS.

Execution Order in Case of the Disaster Recovery

1. Install the UMS on the server, see (12.03-en) IGEL UMS Installation. All the UMS components must be installed like before: 
   1. The same UMS version
   2. The same network configuration of the host (the same IP addresses, ports)
   3. For High Availability (HA) installations only: During the installation, use the backed-up IGEL network token. See the "Starting the Installation" section under (12.03-en) Adding Further Servers to the HA Network.
      
      
2. Stop the existing UMS Server(s). For the details on how you can do it, see (12.03-en) IGEL UMS HA Services and Processes.
   
   
3. Copy all the saved files and firmware updates from [IGEL installation directory]/rmguiserver/webapps/ums_filetransfer to the new UMS Server(s) – without the WEB-INF folder.
   If you deploy the HA environment, see also (12.03-en) Which Files Are Automatically Synchronized between the IGEL UMS Servers?.
   
   
4. Restore the database backup using the procedures recommended by the DBMS manufacturer.
   
   
5. Add the database connection to your external database on each UMS Server: UMS Administrator > Datasource > Add.
   
   
   
6. Click Activate to enable the data source. 
   The UMS Server will start automatically after that.
   
   
7. In the UMS Administrator > Backups > Restore, restore the backup of server configurations on each UMS Server.  If necessary, transfer host-specific server configurations to the new server(s).
   
   
8. In the UMS Administrator > UMS ID Backup > Restore, restore the backup of the UMS ID.
   
   
9. For HA and Distributed UMS installations only: Check host assignments for job execution and, if required, adjust them. See (12.03-en) Updating Host Assignment for Job Execution.

If you have a UMS installation with an embedded database, you may find it useful to read: (12.03-en) Restore and Recover Corrupted UMS Embedded DB.