Recovery After System Downtime 

The various processes of synchronization or replication are performed across the three systems i.e. the client, MI Server and the back end. There might be times where one of the processes cannot be performed, e.g. because one of the systems has a downtime. If this happens it is essential that there is a backup available. For information on performing a backup, see the documentation of the back-end system.

When all systems are working again, there might be some additional steps necessary to recover all data and make it consistent again. The following describes the various scenarios of system failures and the steps that need to be taken to handle such circumstances:

●      Temporary Unavailability of the Back End

●      Temporary Unavailability of MI Server 

●      Incomplete Recovery of the Back End

●      Incomplete Recovery of MI Server 

The following is only applicable for Smart Synchronization applications on Mobile Infrastructure 2.5 or higher. For Generic Synchronization applications running on MI 2.5 or higher, since the MI Server does not hold any business data, the scenarios described here are not applicable. However if you assigned or unassigned any applications during an incomplete MI Server recovery, you need to perform the assignment or unassignment again.