# Restore Database

It is possible that the system database may become corrupted. If this occurs then you will need to restore an uncorrupted database from a database backup file to the system.

WARNING!

- Restoring a database replaces the current database and requires a manual system reboot after restoring the database. It is recommended to back up the current database incase the database restore fails.

- If you are migrating from MCD 6.0 or later to MiVoice Business Release 9.0 or later, ensure that the database you attempt to restore is audited and corrected. You cannot restore an incompatible database in MiVoice Business Release 9.0 or later, leading to a default database. You have to perform a reverse migration to the release from which you migrated, run the pre-migration audit to ensure your database is compatible for migration, and then perform the migration. For details on how to perform reverse migration, see the Reverse Migration appendix in the MiVoice Business Migration Guidelines document.

NOTE: If a database that you attempt to restore contains any corrupted files, the system generates an Audit Failure alarm. You must restore an uncorrupted database to clear the alarm. See Database Verification for more information.

You can restore a database backup file to the system

- from the hard drive of the System Administration Tool client PC, or

- from an external FTP server.

IMPORTANT: If the database being restored originated from a different MiVoice Business system, see Restoring a Database from another MiVoice Business System before you start.

To perform a Restore (and Backup), you will need to install a security certificate which allows the FTP or SFTP server to write to your hard drive. The certificate is in a file called identitydb.obj. Use the links provided in the Restore form to obtain and install the file.

CAUTION: You must reboot the controller after restoring a database. Service will be LOST during this reboot.

NOTES

- Restoring a database must be completed before the User Session Inactivity Period (System Properties > System Administration > System Security Management) expires. Otherwise, the restore fails. The time taken for restoring a backup file depends on the size of the backup file. The system takes approximately one minute to restore a 30 MB backup file. Depending on the backup file size, adjust the User Session Inactivity Period accordingly. For example, to restore a backup file of 450 MB, set User Session Inactivity Period to 18 minutes.

- When restoring system information on an MiVoice Business system that shares data through the System Data Synchronization feature, the restore applies only to the element you are logged in to. During a system restore, the network element rejects all data update distribution attempts. See Performing Backups and Restores for more information on performing and managing restores on SDS network elements.

- You can only restore a Release 3.3 or later database onto a system running Release 4.1 or later software. You may not restore a database saved on software prior to Release 3.3.

- You can also perform backup from the Server Manager, whereas you can perform a restore from the Server Console. However, you cannot restore a backup file created from the Server Manager in to the MiVoice Business System Administration Tool (Does not apply to Container-based MiVoice Business (cMiVB)).

- For Container-based MiVoice Business (cMiVB), you can perform a restore from Solution Manager > Restore.

To restore a database

1. Select Maintenance and Diagnostics > Backup/Restore.

2. Click Restore.

3. Choose the location of the backup file (archived file) that you want to restore:

4. click FTP server configured on node to obtain the file from an FTP server in the network. The FTP server parameters must be configured in the External FTP Server form ( ).

5. click Local hard drive to obtain the file from the client PC and use the browse facility to select the backup file.

4. Click Include Guest Room information if you want to include Hotel/Motel wake-up information in your restore.

5. Choose the Dimension Selections:

4. click From archived file to use the Dimension Selections from the backup file, OR

5. click Use current if you are restoring the database after programming new Dimension Selection information. See Change Licenses and Options for more information about changing the system dimension.

6. Click Start Restore.
   A confirmation dialog box is displayed.

   NOTE To perform a restore, your current user account on the computer must have Java Plug-in version 1.6.0_01 or later installed.

7. Click OK.
   The File Upload in progress message is displayed. When the restore is successful, a confirmation message is displayed.

8. In the Maintenance Commands form, enter RESET SYSTEM in the Command field, and then press the Enter key. When the reboot is complete, the database is restored, and the system automatically is resetted (prior to MCD Release 4.0, another manual reboot was required).

9. If you have programmed Dimension Selection, the system reboots automatically one more time.

NOTES

- If the database restore fails due to incompatible database, click Resolving Restore issues in the Recent Messages dialog box to know how to resolve the restore failure. You may have to perform a reverse migration. See chapter Reverse Migration in the MiVoice Business Migration Guidelines document.

- The data restore may fail due to incompatible version.

If the backup file is from a release of software that is no longer supported (older than MCD Release 7.0) then the message Data Save is from an older load. Convert not supported. is displayed in the call control journal and data restore logfile.

If the backup file is from a release of software which is later than the one currently running then the message Data Save is from a later load. Convert not supported. is displayed in the call control journal and data restore logfile.

- The system does not allow you to log in during the restore and reset period. Once the system has completed the restore and reset, you should see "deleting/ ipservicesdb.tar" in the RTC. This is a good indication that you can log back in to the System Administration Tool.

- While the System Administration Tool is restoring the database, no other users can access any of the web-based tools (5140/5240 IP Phone Online Services, Visual Voice Mail, Desktop Tool, Group Administration Tool, or System Administration Tool), access Visual Voice Mail, or save changes. To avoid blocking other users, we recommend that you perform restores outside of business hours.

- If you chose to back up the Call History records, then they will be restored during the database restore process. If you do not want to keep the Call History records, then you can delete them using the History Delete All maintenance command. See History for more information on using the History Delete All command.

TIME: The system takes approximately 30 to 90 minutes to restore an average-sized database, during which time the files are copied to the controller. Once the files have been copied, you must reset the controller. Note that the system can take up to an additional 1 hour to reset.