How to restore XKM from old installation

How to restore XKM from old installation

  1. Login to NonStop with the user that Owned your old XKM installation.
  2. Make sure the new XKM is not running.
    VOLUME $<XKM Volume>.XYGATEKM
    STATUS *, PROG *            <<< find the process ID of XKM
    STOP <XKM Process ID>
  3. Move a way\Rename the newly installed XKM
  4. Install a fresh XKM
  5. License the program as its instructed at the end of the installation.
    PLEASE DO NOT RUN THE KEYCOM
  6. FUP DUP the following files from your OLD XKM Backup to the new XKM Installation.
    Make sure to use the SOURCEDATE keyword in your FUP DUP Like the below example:
    FUP DUP $<backup volume>.<subvol>.ENCKEY,$<volume>.XYGATEKM.ENCKEY,SOURCEDATE,PURGE
    ENCKEY
    ENCKSET
    LOCIDS
    LOCMAPS
    MASTKEY
    SESSION
    KMACL
  1. After above files are restored to the new XKM installation, change the volume to XYGATEKM installation and  RUN KEYCOM
  2. Select 1 -> Control Key Server
  3. Select option 1 -> Start
  4. At this time you need to have those people who originally on the old XKM logged in and singed the Local Master key. They need to enter their credentials and the passkey.
  5. Select 5 -> Status        (To check if server is initialized and running.)

    • Related Articles

    • XMA How To Change Ownership On The Existing Installation

      The following methods are available to change the ownership of an XMA environment. Method #1 - Re-Install XMA Procedure: Refer to Chapter 1 " Installing XMA " in the XYGATE Merged Audit (XMA), User's Guide and Reference Manual Method #2 - ...

    • XTR: Change the owner of XTR installation.

      Step 1: Change the owner of non SQL files in the XTR installation Command; FUP GIVE <$vol>.<xygatetr>.* WHERE NOT SQL AND NOT OWNER = <new-owner>, <new-onwer> Step 2: Change the owner of SQL Catalogs in the XTR installation Command; SQLCI ALTER ...

    • XS1: MongoDB configuration steps for XS1 installation

      Summary: 1. create the user "xs1.admin" 2. create the db "XYGATE_SecurityOne" 3. create the collection "xma" 4. create the user "xs1.owner" with read/write access to the db XYGATE_SecurityOne 5. if needed, modify the mongod configuration file ...

    • XUA: LDAP and RSA installation Directory create failure for /rsa

      The error can be ignored if the RSA web service isn't going to be used. This is the last step the installation does before doing xua_finish_install (if 255,255) or asking to complete the installation by logging on as 255,255 and running a ...

    • XPQ: Workaround for INCORRECT OLD PASSWORD message (XPQ 3.40 and earlier versions)

      Add a UAGROUP to the top of the UAACL file similar to the following: UAGROUP PASSWORD-CHANGES-FOR-RSA-USERS DESCRIPTION "PASSWORD changes for RSA users using the XPQ PASSWORD program" FROM_USER $EVERYONE TO_USER $RSA-USERS REQUESTOR ...