System Recovery

You can often restore the system from damage by human or natural causes by way of online and offline system recovery procedures.

Oracle recommends that you include a system recovery plan for the session border controller in your business continuity plan. The system recovery plan should note location of the system recovery procedures, the software image .exe file, and the USB flash drive containing the prepared boot file.

Common Disaster Causes

Aside from natural disasters, common causes of system disasters include the following:

• Someone replaces the /boot/bzimage file or the boot/bootloader file with a corrupt file.
• The hard disk on a Common Off the Shelf (COTS) system becomes unresponsive.

Online System Recovery

From the maintenance sub-menu of the USB boot menu, you can boot directly to /boot/bzimage in failsafe mode, or you can reinstall the software image onto the /boot file system and preserve the existing configuration, licensing, and nvram contents.

Offline System Recovery

From a USB flash drive created with the Acme Packet Boot Media Creator, you can reinstall the software image and reboot the system. You can install /boot on a new hard disk on the Acme Packet 1100, Acme Packet 3900, and COTS system or reinstall the software to the existing /boot on all platforms, while preserving the existing configuration, licensing, and nrvram contents. See "Create the Acme Packet Boot Media" and "Restore the System from a USB Flash Drive."

If the system recovery requires hard disk replacement, execute the format-hard-disk command after the system is recovered to re-establish the system logging and user data storage areas.