NOTE: THIS PROCESS IS ONLY FOR enVision version 3.3.X and not 3.5.X and above.

NOTE: If requested to fill in a sitename, please be aware that the site name is case-sensitive.

NOTE: Recovery is done by pulling the database from the Master DSrv. For Dsrv slave sites, the slave Dsrv database must be recovered first. Instructions on how to recover a Master Slave site are covered in the section " To Recover the Database on an DSrv(Master)"

To Recover the Database (ASrv, LC, Slave DSrv):

Note: Instructions on restoring a master DSrv are at the end of this document.

1. Verify that the NIC DB Replication Server and NIC DB Server services are running on the DSrv.
2. Stop all NIC services on the node you want to restore the database on.
3. On the node, open a command prompt in the E:\enVision\database\cmd directory and execute the following command:
   
   For ASrv, LC:
   recover_multinode_install.cmd sitename nodetype %COMPUTERNAME% nodeip NONE NONE DSrvHostname
   
   For Slave DSrv, RC:
   recover_multinode_install.cmdsitename nodetype %COMPUTERNAME%nodeip masterhostip mastersitename %COMPUTERNAME%
   
   Where sitename is the name of the site being restored, nodeip is the node's LAN IP address, masterhostip is the IP address to connect to the site's Master D-SRV, and mastersitename is the hostname of the site's Master D-SRV.
   
   EX: recover_multinode_install.cmd Boston LC3 %COMPUTERNAME% 192.168.1.3 NONE NONE Boston-DS1
4. Reboot the LC or RC.
5. Check the timestamp of the file E:\enVision\logs\dbmlsync_succeeded file, it should be within one minute of the current time.
6. Verify the operation of the LC or RC.

To Restore the Database on an DSrv(Master):
The Master D-SRV recovery process recreates the nic.db file from the sites A-SRV database by temporarily setting the A-SRV as the Master database.

NOTE: Use these instructions if you do not already have a database backup of the Master Dsrv.

1. Stop all NIC Services running on the D-SRV.
2. Verify the NIC DB Server is running on the master A-SRV.
3. Stop the NIC DB Replication Client Service on the master A-SRV.
4. Open a command prompt in the E:\enVision\database\cmd directory on the sites A-SRV and run the startmlsrv.cmd
5. Open a command prompt in the E:\enVision\database\cmd directory on the D-SRV and run the following command:
   
   sitename DS1 %COMPUTERNAME% nodeip 10.0.0.2 sitename %COMPUTERNAME%
   
   Where sitename is the name of the D-SRV site being restored, and nodeip is the node's LAN IP address.
6. From the command prompt on the D-SRV, run the startmlsync.cmd
7. Verify the timestamp of the E:\enVision\logs\dbmlsync_succeeded file is within one minute of the current time.
8. From the command prompt on the A-SRV, run:
   
   stopmlsrv.cmd
9. From the command prompt on the D-SRV, run:
   
   set_mobilink_host.cmd NONE
10. Restart the D-SRV (Master Site). Wait until the D-SRV is completely up and running.
11. Synchronize the database using the instructions listed below.

Synchronizing the Databases:

For each node that replicates directly with the D-SRV, follow the steps below to re-initialize the database replication process. This includes all A-SRVs and LCs in the same site, or any RCs or D-SRVs that are hosted by this D-SRV.

1. Stop all NIC Services except the NIC DB Server.
2. On the LC or RC, open a command prompt in the E:\enVision\database\cmd directory execute the following command:

   For ASrvs and LCs:
   recover_from_missing_transaction_log_file.cmd masterHostname %COMPUTERNAME%
   
   For Hosted RCs and D-SRVs:
   recover_from_missing_transaction_log_file.cmd masterhostip %COMPUTERNAME%

   Where masterhostip is the IP address to connect to the restored D-SRV.

3. Verify the timestamp of the E:\enVision\logs\dbmlsync_succeeded file on each node, from the previous step, is within one minute of the current time
4. Restart the NIC Services, and verify operation of the system.