Today's technology-driven businesses rely on digital devices and systems for much of their day-to-day operational needs. For this reason, every corporation should have a disaster recovery procedure in place that covers hardware, software and critical data necessary for businesses to function.
Contingency plans don't have to be complicated. However, to be effective, recovery procedures should be:
This article explains how to back up and restore the critical statistics data and configuration settings of your ipMonitor 8 installation. Following the guidelines detailed here will allow you effectively prepare for and recover from a failure that could cause your ipMonitor installation to become unavailable.
We recommend saving the PDF version of this document to an easily accessible location and storing these guidelines alongside any other disaster recovery procedures your company maintains.
|Click the PDF icon to open a printable PDF version of this tutorial. It includes all the information found here, including images from the ipMonitor software, diagrams, and links to additional resources.|
The primary objective of this disaster recovery plan is to enable a corporation to get ipMonitor up and running again in the shortest amount of time, with the least amount of effort. To properly implement this recovery procedure, you will require the following:
1. Your company's Account and Password information for the ipMonitor Support Portal.
Access to the ipMonitor Support Portal (located at https://support.ipmonitor.com) will provide you with:
2. A recent *.ipm8backup file from your ipMonitor 8 installation.
ipMonitor 8 includes the ability to archive your configuration settings on a regular basis using the Recurring Internal Maintenance feature. Specifying an Encryption Credential will allow the archiving process to include the usernames and passwords stored in the ipMonitor Credentials Database.
|This is the only method that can be used to back up and restore the ipMonitor 8 Credentials Database. Credential information cannot be exported using the Export Settings feature.|
Since manually repopulating every existing Credential with its username and password can be a time consuming process, archiving your Credentials data is highly recommended.
Note: The instructions outlined in this article assume that an Encryption Credential has been used to store your Credentials data.
3. The password for the Encryption Credential.
If you specified an Encryption Credential when archiving your configuration settings, you will need the password in order to retrieve the Credential information from ipMonitor's Credentials Database.
4. The username and password information of the Windows Account assigned to the ipMonitorSrv Service.
This information is only necessary if the ipMonitorSrv Service is configured to run under an account other than the default Local System Account.
5. The username and password information for any Local Machine Windows Accounts impersonated by Credentials assigned to Monitors or Alerts.
Since the ipMonitor Credentials Database will refer to local Windows accounts once restored, these accounts will need to be recreated on the server where ipMonitor 8 will reside.
6. A recent backup of the following sub-directories located in the ipMonitor installation directory:
* You will only need to back up the indicated Legacy directories if:
Backing up your ipMonitor installation on a regular basis is an essential part of protecting your data. Fully archiving your accumulated statistics and configuration settings is a two step process:
Ensure the Archive ipMonitor Configuration option within the Recurring Internal Maintenance Schedule feature is enabled and has an Encryption Credential assigned.
To do so, proceed with the following:
With the above settings in place, at approximately 12:15 AM every day the Recurring Internal Maintenance Schedule will back up the installation's complete configuration settings to a single encrypted file.
By default, the backup file will be created in the .\ipMonitor8\backup\ directory.
Incorporate the pertinent sub-directories of the ipMonitor 8 installation folder into your corporate backup strategy as frequently as it allows. The following sub-directories should be backed up at regular intervals:
* You will only need to back up the indicated Legacy directories if:
To recover your ipMonitor installation, you will require all the resources outlined in the section of this document titled ipMonitor Disaster Recovery Requirements. Fully restoring your ipMonitor 8 installation is a four-step process.
For this step of the recovery process, you will require your company's Account and Password information in order to log in to the ipMonitor Support Portal.
|Ensure you download the ipMonitor 8 Backup-Restore Utility.
If you download the ipMonitor 7.x Backup-Restore Utility instead, you will not be able to restore your installation's resources to any version of ipMonitor other than 7.x.
The ipMonitor 8 Configuration Program is used to configure key operating parameters for the ipMonitor Monitoring Service (ipMonitorSrv). After you install ipMonitor, the Configuration Program will automatically launch in "First Run" mode:
The Emergency Licensing tool is provided as a Customer Service courtesy to assist with cases of hardware failure or similar issues that render customers unable to properly Park the ipMonitor license. Once you've run through the ipMonitor Configuration Program, proceed with the following:
|Emergency Licenses are valid for a period of 7 days. This length of time allows you to resolve your hardware or system issues in order to apply a new, permanent License to your installation.
Immediately after the Emergency License is generated, the ipMonitor Technical Support department is notified of its existence. Although you will automatically be entered into the Technical Support queue, we strongly encourage you to proactively contact ipMonitor Technical support to begin the full License restoration process.
Technical support is available during regular business hours, 9am to 5pm Eastern Time, Monday through Friday, except holidays.
Restoring your ipMonitor configuration settings and statistics data is the last step in fully recovering your failed installation:
|• \internal\mib_base.bxml||* If a custom SNMP MIB Database has previously been installed|
|• \wwwroot\rpticons\||* To retain any custom Report Icons saved to ipMonitor|
|• \wwwroot\saved\||* If Reports have been saved to this default location|
|• \wwwroot\stats\override.css||* To retain any CSS changes made to the Live Report screens|
|• \wwwroot\cfg\override.css||* To retain any CSS changes made to the Configuration screens|
|If the password provided during the restore process was incorrect, Credentials will no longer be associated with the original Administrator Account(s) that created them when restored. As a result, they will be considered "Orphaned". This is a security precaution.
To solve this issue, either run the Backup and Restore Utility again and provide another password, or reinitialize the Credentials manually.
To learn more about reinitializing Orphaned Credentials, refer to section of the Administrator's Guide titled The Credentials Manager.
The recovery process may result in additional ipMonitor configuration components that may not be necessary for your installation. These components can be quickly and easily removed from your configuration.
If the Administrator Account you added when restoring your installation is unnecessary, remove it by following the instructions outlined below:
The ipMonitor 8 Configuration Program automatically creates two Configurable Reports and a Report Publisher for the default system Monitors. If the two Reports and the Publisher are not needed, proceed with the following instructions to remove them:
The ipMonitor 8 Configuration Program also creates a default Alerting Profile. If this Profile is not used, proceed with the following to remove it:
For information on other features and concepts related to those discussed in this article, refer to the following ipMonitor resources:
Last Updated: December 22, 2006 | What did you think of this topic?