How to Backup and Restore or Migrate ERPM

Follow


Date: January 23, 2017
Revision: 2.5

Backup

First export the encryption key. The encryption key will be required to regain access to the stored passwords should restoration or migration of the management console be necessary. Go to SETTINGS | ENCRYPTION SETTINGS.



Click EXPORT and provide the exported encryption key with a name, then click "Open". This will save the encryption key at the chosen location.

Second, export the migration data sub-key. This is only necessary for version 4.83.5 and older versions of ERPM/RPM. If the migration data sub-key is not backed up, then when restoration of the program occurs, it will replay migration steps against the database which could lead to problems - which can be fixed - in the database. Problems will include jobs with bad information and users may gain more access to systems than they should have. Back up the following registry sub-key:

  • 32bit systems = HKLM\Software\Lieberman\{RPM | PWC}\MigrationData
  • 64bit systems = HKLM\Software\Wow6432node\Lieberman\{RPM | PWC}\MigrationData



The keys denote the migration steps taken against the current database to this point.

Alternatively, to exporting the encryption key and the migration data keys mentioned above, you may simply export the following registry key:

  • 32bit systems = HKLM\Software\Lieberman
  • 64bit systems = HKLM\Software\Wow6432node\Lieberman



Database:
Backup your SQL database that E/RPM uses. Your actual backup process for your database may vary. Typically using the SQL or Oracle administration tools, this consists of right-clicking on the database or file groups and choosing "backup".

SSH/Telnet Response Files:
Any additional XML repsonse files that have been created for E/RPM and their corresponding XSD files shold be backed up. These files are only present if you have added them. They are used for for SSH/Telnet targets.

Event Sinks:
These are integrations/notifications/alerts for E/RPM. If any have been configured, their XML files should also be backed up. These are located by default at: C:\ProgramData\Lieberman\GenericEventServer\Versio n 1.x\EventSinks\SystemEventSinks.

Help Desk Integrations:
ERPM/RPM can create integrations with BMC Remedy, HP Service Manager, or Microsoft Service Manager. The integration confguration files are located in sub-folders at: C:\ProgramData\Lieberman and have a name similar to LiebIntintegrationName. These folders and files only exist if the integration has been configured.

Restore

If the database requires restoration, please perform this step prior to restoring the application. Your restoration procedure may vary for a database. Typically, just choose to restore the database backup.

Next, restore the registry key collected during the intial backup. If the database is restored and the version of ERPM/RPM is restored without replacing the registry keys first, ERPM/RPM WILL re-perform migration steps on the database. This could lead to missing data, failed jobs, or worse.

For reference, the following registry keys are located at these locations:

  • 32bit systems = HKLM\Software\Lieberman\{RPM | PWC}\MigrationData
  • 64bit systems = HKLM\Software\Wow6432node\Lieberman\{RPM | PWC}\MigrationData



Under each key is a DWORD value called bStepCompleted if the steps were completed.
Important! During a restore, if reverting to a previous version of the database, delete the registry keys corresponding to that version. Simply discern the difference between the keys that should be present on the database version you are restoring, from the version you have presently installed.

Version 4.02:

  • {E0B8A4FC-36D5-4BC2-B972-BF2F89A4764A}



Version 4.50:

  • {E0B8A4FC-36D5-4BC2-B972-BF2F89A4764A}
  • {1D4ECE80-F295-441C-8EEE-074882D6A1B7}



Version 4.70 - version 4.83.0:

  • {E0B8A4FC-36D5-4BC2-B972-BF2F89A4764A}
  • {1D4ECE80-F295-441C-8EEE-074882D6A1B7}
  • {D628D50C-AA68-47E0-A8D6-446720BEC6FB}



Version 4.83.1:

  • {E0B8A4FC-36D5-4BC2-B972-BF2F89A4764A}
  • {1D4ECE80-F295-441C-8EEE-074882D6A1B7}
  • {D628D50C-AA68-47E0-A8D6-446720BEC6FB}
  • {9BB15F0C-1683-4FA1-8655-83C5E5BF360C}
  • {5222A2B4-BD00-4FF0-8A82-C65EDD656A78}
  • {A43841A4-3B35-4F14-9DC3-B39D8F601679}



Version 4.83.2:

  • {E0B8A4FC-36D5-4BC2-B972-BF2F89A4764A}
  • {1D4ECE80-F295-441C-8EEE-074882D6A1B7}
  • {D628D50C-AA68-47E0-A8D6-446720BEC6FB}
  • {9BB15F0C-1683-4FA1-8655-83C5E5BF360C}
  • {5222A2B4-BD00-4FF0-8A82-C65EDD656A78}
  • {A43841A4-3B35-4F14-9DC3-B39D8F601679}
  • {F9B373D3-1206-4287-A856-4F7674BED3B5}



Version 4.83.3:

  • {E0B8A4FC-36D5-4BC2-B972-BF2F89A4764A}
  • {1D4ECE80-F295-441C-8EEE-074882D6A1B7}
  • {D628D50C-AA68-47E0-A8D6-446720BEC6FB}
  • {9BB15F0C-1683-4FA1-8655-83C5E5BF360C}
  • {5222A2B4-BD00-4FF0-8A82-C65EDD656A78}
  • {A43841A4-3B35-4F14-9DC3-B39D8F601679}
  • {F9B373D3-1206-4287-A856-4F7674BED3B5}
  • {86F7ED28-3083-4CFC-BCF0-AB3F682196B3}



Version 4.83.4:

  • {E0B8A4FC-36D5-4BC2-B972-BF2F89A4764A}
  • {1D4ECE80-F295-441C-8EEE-074882D6A1B7}
  • {D628D50C-AA68-47E0-A8D6-446720BEC6FB}
  • {9BB15F0C-1683-4FA1-8655-83C5E5BF360C}
  • {5222A2B4-BD00-4FF0-8A82-C65EDD656A78}
  • {A43841A4-3B35-4F14-9DC3-B39D8F601679}
  • {F9B373D3-1206-4287-A856-4F7674BED3B5}
  • {86F7ED28-3083-4CFC-BCF0-AB3F682196B3}
  • {A7978993-AAAC-468b-A570-840541AB4512}



Version 4.83.5:

  • {E0B8A4FC-36D5-4BC2-B972-BF2F89A4764A}
  • {1D4ECE80-F295-441C-8EEE-074882D6A1B7}
  • {D628D50C-AA68-47E0-A8D6-446720BEC6FB}
  • {9BB15F0C-1683-4FA1-8655-83C5E5BF360C}
  • {5222A2B4-BD00-4FF0-8A82-C65EDD656A78}
  • {A43841A4-3B35-4F14-9DC3-B39D8F601679}
  • {F9B373D3-1206-4287-A856-4F7674BED3B5}
  • {86F7ED28-3083-4CFC-BCF0-AB3F682196B3}
  • {A7978993-AAAC-468b-A570-840541AB4512}
  • {9B675AD6-920A-4885-BFC6-EBE6DA549E2D}



Version 4.83.6 and later:
No longer uses the registry to handle DB migration checkpoints. If working with version 4.83.6 and later, it is only necessary to backup/restore the ERPM/RPM program database.

Restore

Once the database and registry keys are ready, re-install the application. This generally consists of clicking NEXT at all prompts in the installer and finally FINISH.

Second, reimport the registry keys. If you exported the Lieberman registry key mentioned above, simply re-import the registry key and launch the application.

If you only exported the encryption key and the MigrationData key rather than the Lieberman registry key then do the following:

  1. Import the DataMigration key
  2. Launch the program
  3. Follow the mini-setup wizard to reconnect to a database. Be sure to use the same DB schema configuration previously configured.
  4. When prompted, import the encryption key



Do not install the website at this point. Click OK to close the dialog.

Next, go to Help | Reister and input your registration key. If this is a new server and does not share the same NetBIOS name as the last server, you will need a new license key for the new server from Lieberman Software.



Once the database and the encryption key have been re-configured, you will need to redeploy the website. From the SETTINGS menu select MANAGE WEB APPLICATION | INSTALL WEB APPLICATION INSTANCE.



For version 4.81 and later, website settings are stored in the database. So simply re-importing the encryption key and reconnecting to the same database will be enough to re-deploy the website. For versions 4.80 and earlier, If you re-imported the encryption key only, you will need to reconfigure all of these settings. If you re-imported the registry key, all of these options will already be configured.

Click INSTALL WEB APPLICATION. Once the installation is complete, you may close the dialog.

Finally, restore the answer files, event sinks, and help desk integration configuration files to the same phsyical path as the original system. If they do not go to the same path, it will be necessary to manually edit existing password change jobs to point to the answer file's new locations and the event sink directory will have to be manually updated.

The restoration is now complete. Total time to complete, less than 5 minutes + database restoration.

Supplemental Information

Disaster Recovery and High Availability: Disaster Recovery, Security, and High Availability
Database Sizing: Database Sizing Requirements
Move Your Database: Move your database

Applies To

Random Password Manager (RPM)
Enterprise Random Password Manager (ERPM)

Was this article helpful?
0 out of 0 found this helpful

Comments

Powered by Zendesk