13.1.2.2. Procedure – Restoring a MS database backup

The following steps describe how to restore an earlier MS database.

Warning

Restoring an earlier database will delete the current database, including the configuration of every host, as well as any certificates stored in the PKI system. Any modification and configuration change performed since the backup was created will be lost.

  1. Copy the database backup archive file to the MS host.

  2. As root, issue the /usr/share/MS/MS-restore.sh <backup-file-to-restore> command.

  3. Follow the on-screen instructions of the script. When the restoring process fails, the usr/sbin/MS-integrity can fix the database backup archive file. To accomplish this, complete the following steps.

    1. Create a temporary working directory

      mkdir /tmp/vms-backup

    2. Unpack the archive file

      tar -zxf <backup-file-to-restore> -C /tmp/vms-backup

    3. Try to recover the database

      /usr/sbin/vms-integrity -r -d /tmp/vms-backup

    4. Check the recovered database

      /usr/sbin/vms-integrity -d /tmp/vms-backup

    5. Pack the database

      tar -C /tmp/vms-backup -czf <fixed-backup-file> .

    6. Delete the working directory

      rm -rf /tmp/vms-backup

  4. Login to MS using MC. If you have reinstalled MS, use the username and password you have provided during the reinstallation.

  5. If the restored database has to be upgraded, MC displays a list of the components to be upgraded. Click Convert.

  6. Select PKI > Distribute Certificates. Note that key distribution will fail on every host except on the MS host. This is normal.

  7. Upload the configuration of the MS host.

  8. Restart at least the Management Server component on the MS host. This will terminate your MC session.

  9. Relogin with MC and check your restored configuration.

  10. Upload and restart any component as needed. You may also need to redistribute the certificates.

Previous Up Next
 Home