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.
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.
CAUTION: You must reboot the controller after restoring a database. Service will be LOST during this reboot.
Notes:
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 restore a database from a 100-user, CX, CXi, CX II, CXi II, or MX controller to an MXe controller; however, the Layer 2 switch on the MXe will require configuring after the Restore. The AMB and AOB may also require re-configuration. An LX or 700-user database may also be restored to an MXe subject to the condition described in the following Note.
You may not restore an LX or 700-user database onto an MX controller if the database had CIM 3 or 4 configured. You must first delete the unsupported CIM configuration.
You can only restore an AX controller database to an AX controller. You cannot restore a database from another type of controller to an AX controller.
You cannot restore an MXe Server database on another controller.
To restore a database
In the Selection menu, choose Maintenance and Diagnostics and then click Restore.
Choose the location of the backup file (archived file) that you want to restore:
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.
click Local hard drive to obtain the file from the client PC. Type the location of the database that is being restored, or use the browse facility.
Click Include Guest Room information if you want to include Hotel/Motel wake-up information in your restore.
Choose the Dimension Selections:
click From archived file to use the Dimension Selections from the backup file, OR
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.
Click Start Restore.
Notes:
To perform a restore, your current user account on the computer must have Java Plug-in version 1.6.0_01 or later installed.
The MXe server has a blank NTP server field, so when a restore is performed from an MXe server to a 100-user CX, CXi, CX II, CXi II, or MX controller, you must reprogram the Date and Time form to restore synchronization.
Click OK. The system shows an "in progress" message.
When the status window shows "complete", click OK.
Enter
the "Reset System" maintenance command. When the reboot
is complete, the database is converted, and the system automatically
resets (prior to Release 4.0, another manual reboot was required).
- If you have programmed Dimension Selection, the system reboots automatically
one more time.
Notes:
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.
When restoring system information on a 3300 ICP 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.
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.