Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Log & Event Manager (LEM) > Disaster Recovery Planning in LEM

Disaster Recovery Planning in LEM

Created by Tim Rush, last modified by Melanie Boyd on Oct 24, 2017

Views: 22 Votes: 0 Revisions: 4

Overview

This document describes how to plan or test the disaster recoverability of LEM.

Sometimes an auditor demands to validate the ability to either restore the database (in part or whole).

Environment

  • All LEM deployments

Steps

Procedure to restore the database

Notes: 

  • Read through entire procedure before following each step.
  • An auditor could require proof that you can recover data, or ability to restore beyond the 'required' 6 months direct online access to logs.
  • Procedure will not impact the current running LEM, which is collecting and reporting events/alerts.
  • Procedure assumes database backup is available from a network share (archiveconfig).
  • Procedure assumes a single LEM appliance deployment. (Contact support if LEM is a multi-server deployment.)

 

  1. Access the Solarwinds customer portal to download an 'evaluation LEM'. You want to download the same LEM version as your current online running LEM. An evaluation LEM is the same image, just not licensed for production, so functionality will stop 30 days after deployment..
  2. Deploy the new LEM as outlined in the Quick Start Guide, except you will not be installing the license.
    http://www.solarwinds.com/documentat...StartGuide.pdf
  3. Notes about the default LEM deployment (this is only for testing and running reports):
    • sets (reserves) 8GB of RAM  --> does not need to match the production LEM
    • sets (reserves) 2-CPU's at 2.0Ghz  --> does not need to match the production LEM
    • VM will reserve 250GB of storage space  --> only need to size for what is restored

      depends upon the amount of the database to be restored (number of partitions)

    • sets the default hostname as "swi-lem"  -->  verify unique name, different from production LEM. use CMC 'hostname' command to change.
    • sets the LEM to obtain DHCP address  -->  use CMC 'netconfig' command to change.
    • sets "password" as the default CMC user password  -->  use CMC 'password' command to change.

      change size/RAM/CPU while shutdown, reboot the LEM (from CMC/putty) after making network changes

  4. The QuickStart Guide has you open a browser to access the LEM, and install the license. Do not do this part.

    When the first event comes into the LEM, LEM will create the the database.

  5. Although you can run the "import" command from the CMC/SSH access, avoid doing this.

    This will put this test LEM online with the same hostname and IP address as the production LEM.

    The "import" command is used to recover configurations on the production LEM that were accidentally deleted or changed.

  6. Verify that you have access to the backups on a network share.
  7. Contact Solarwinds support to perform either the actual restore of the database.

Procedure to recover the entire LEM

Notes: 

  • Read through entire procedure before following each step.
  • Procedure assumes the production LEM is offline or missing from the network or virtual environment.
  • Procedure assumes the database backup is available from a network share (archiveconfig).
  • Procedure assumes the configuration backup is available from a network share (backupconfig).

 

  1. Very important: Access the Solarwinds customer portal to download the same LEM version as the production LEM.
  2. Deploy the new LEM as outlined in the Quick Start Guide.

    http://www.solarwinds.com/documentat...StartGuide.pdf

  3. Before starting up this 'new' replacement LEM, be sure to set the resources to be reserved, just like the production LEM.
    • reserve the same amount of RAM  --> somewhere between 8 to 256GB of RAM
    • reserve the same number of CPU (at 2.0Ghz)  --> somewhere between 2 to 16 CPU (core/processors)
    • increase the VMware (or Hyper-V)   -->  restoring the entire database
  4. After starting the LEM, contact Solarwinds support (or Customer Service) to have the license reset.
  5. Open a browser to the LEM, and install the license per the Quick Start.

    (Browser access is available on ports 8443 and 8080. Once the 2 step activation is performed, which includes running the "activate" command under CMC/SSH access, port 8080 will be blocked. Port 8080 can be re-opened by using the "togglehttp" command.)

  6. Open a Vsphere-console (or putty/SSH to LEM), enter the "appliance" menu, enter the "import" command, and point to the network share where the configuration backups reside (backupconfig command configurations). Then reboot the LEM from the CMC user access.
  7. Although you can run the "import" command from the CMC/SSH access, avoid doing this. This will put this test LEM online with the same hostname and IP address as the production LEM. The "import" command is used to recover configurations on the production LEM that were accidentally deleted or changed.
  8. Reboot the LEM from the CMC command.
  9. Verify that you have access to the database backups on a network share.
  10. Contact SolarWinds support to perform the actual restore of the database.

 

 

Last modified

Tags

Classifications

Public