Restoring a Server Backup File

Complete the procedure in this section to restore data from a backup file, or from an archive file.

Note the following when restoring data or archives:

·         Data can be restored only when the server is stopped.

·         Both servers must be stopped in an HA configuration. The backup can be restored to either server.

·         In Release 1.2.0 and higher, data can be restored to a server with a different high-availability (HA) configuration. For example, data from a standalone server can be restored to a server in HA mode.

·         Backup files include the ICPAM configuration and other data.

·         Archive files include only historical events that were removed from the database using the Archive function. You can view historical events recovered from an archive file using Reports, but they cannot be viewed in the Events and Alarms module. See Archiving the Historical Events Database for more information.

·         If an archive from release 1.2.0 or earlier is restored, you will automatically be redirected to the Events configuration page of the ICPAM Server Administration utility. Use this page to enter the required setting to prune and archive old events. See the Archiving Historical Events for information and instructions. You cannot start the server or perform other activities until the event archiving is successfully configured.

Procedure:

To restore the data from a backup or archive file, do the following:

Step 1            Verify that you have the correct backup file from either the Active or Standby server.

See Backing up the ICPAM Database.

Step 2            Stop the Standby server, if installed.

Note   •  For redundant HA configurations, ensure that both the Active and Standby servers are stopped (in Down state). Restoring a backup while either of the servers is up will result in unexpected behavior.
     If you are upgrading or reinstalling the server software, the Standby server should already be in the Down state.

a.  Log on to the Standby ICPAM appliance.

b. Select Monitoring and then select Status.

c.  In the Admin State Entry, click Stop.

d. Verify that the Admin State is Down.

server_monitoring_2_admin_state_down.jpg

 

Step 3            Stop the Active server.

Note    •  For redundant HA configurations, ensure that both the Active and Standby servers are Down (Admin State). Restoring a backup while either of the servers is up will result in unexpected behavior.
       If you are upgrading or reinstalling the server software, the Standby server should already be in the Down state.

a.  Log on to the Active ICPAM appliance.

b. Select Monitoring and then select Status.

c.  In the Admin State Entry, click Stop.

d. Verify that the Admin State is Down.

Step 4            On the Active server, select the Setup tab, and then select Restore.

server_setup_restore.png

 

Step 5            Enter and re-enter the password for the backup file. This is the password entered when the backup file was created, as described in Backing up the ICPAM Database.

Step 6            Click Browse to locate and select the .zip backup file.

For example: bak-02102011-1141001.3.0_0.3.25.cpam-supermicro-116

Step 7            If the file is an archive file, select the Is Archived File check box.

See Archiving the Historical Events Database for more information.

Step 8            Click Restore and wait for the restore process to complete.

Step 9            Wait for the server to automatically restart.

             A pop-up message appears informing you that the Web administrator utility is restarting.

             If the ICPAM Server Administration utility disconnects, a browser error message may be shown. Wait approximately five minutes for the server to restart, and then refresh your browser to log in again.

Step 10         If restoring a backup from Release 1.2.0 or earlier to Release 1.3.0 or higher, you must enter the event pruning and archive settings.

Note     If you are upgrading from release 1.3.0 or higher, skip to Step 11.

·         Pruned Events are removed from the main database table and placed in a separate database, allowing you to reduce the size of the main database date while keeping them accessible on the ICPAM system. Pruned events are not visible in Events & Alarms, but are included in reports. Pruned events are also included in system backups.

·         Archived events are removed from all ICPAM database tables and copied to a compressed file. The file includes a password-protected SQL script, and can be run on an offline database to view the purged events. Archived events are not visible in the Events & Alarms listings or Reports, and are not included in system backups.

Tip            These settings are only required if restoring a backup from Release 1.2.0 or earlier. After the restore is complete, you can make additional changes. See the Archiving Historical Events for more information.

server_setup_event.png

 

a.  Select the Pruning tab (Figure A-6), and enter the following settings:

        Live Events Window (days)—Enter a value between 0 and 500 (inclusive). This is the number of days of events that will be available on live view. All the events older than the specified days will be removed at the pruning schedule time. For example, enter 30 to keep events in the live view for 30 days. After midnight on day 30, the events are subject to pruning and archiving (depending on the schedule defined in the following steps).

  Note        To ensure that events are regularly pruned, we recommend entering 60 days or less in the Live Events Window field. Entering a value greater than 60 can cause an excessive number of event entries to accumulate in the main database and negatively impact system performance.
  
          The number is rounded to midnight of the last day.

        Schedule—define the time and frequency when events should pruned.

o       Date—To schedule pruning for one day per month, select Date and then select a day of the month. For example: 15.

o       Weekday—To schedule pruning once per week, select Weekday and then select a day of the week. For example: Tuesday.

o       Daily—To run pruning every day, select Daily.

o       Time—Enter the time in 24 hour format (hh:mm:ss). For example, to run pruning at 2 p.m., enter 14:00:00. To run pruning at 1 a.m., enter 01:00:00.

server_setup_event_archive.png

 

b. Select the Archive tab and enter the following settings:

Tip             The archive settings are required during the initial setup. After a successful restore, you can disable auto-archiving if necessary. See the Archiving Historical Events.

        Enter and re-enter the administrator Password. This password is used to restore the archive file (similar to backup files).

        Historic Events Window (days)—Enter the number of days that events will be available for reports. After the minimum number of days the events will be archived to a compressed file. For example, enter 30 to keep events in the live view for 30 days. After midnight on day 30, the events are subject to archiving (depending on the schedule defined in the following steps).

        Enter a Schedule when the historic events will be removed from the pruned database and placed into a compressed archive file (archived files are listed above the entry fields).

o       Date—To schedule archiving for one day per month, select Date and then select a day of the month. For example: 15.

o       Weekday—To schedule archiving once per week, select Weekday and then select a day of the week. For example: Tuesday.

o       Daily—To run archiving every day, select Daily.

o       Time—Enter the time in 24 hour format (hh:mm:ss). For example, to run archiving at 2 p.m., enter 14:00:00. To run archiving at 1 a.m., enter 01:00:00.

        (Optional) Select Copy to remote server to automatically copy the archived event files to a remote FTP or SFTP location.

Note      Only the three most recent archive files are saved. If you do not save the archive file manually or by copying it to a remote server, then the oldest file will be permanently deleted when the fourth file is created.

        FTP: for standard File Transfer Protocol servers.

        SFTP: for secure file transfers using the Secure File Transfer Protocol (also known as the SSH File Transfer Protocol).

        Address—the IP address or hostname of the remote server.

        Username—the username required to log in to the server.

        Password—the login password for the remote server.

        Path—the directory path where the compressed archive will be copied. The path must exist on the remote server. If the directory is not available, the archive will fail.

c.  Select Next to apply the settings and continue.

Step 11         Verify that the Active server is up.

a.  Log on to the Active ICPAM appliance.

b. Select the Monitoring tab and then select Status, as shown below.

c.  Verify the following:

            The Admin State is Up.

            The Server Mode is Active.

server_monitoring_2.jpg

Step 12         If the Status is Down, click Start to manually restart the server and then verify that the Admin State is Up.

Step 13  Restart the Standby server, if installed.

a.  Log on to the Standby ICPAM appliance.

b. Select the Commands tab, and then select Start Server.

c.  Select the Monitoring tab and then select Status.

d. Verify the following:

o      The Admin State is Up.

o      The Server Mode is Standby.

 

See also:

Backing Up and Restoring Data