Restoring IBM InfoSphere Information Server components

Use this procedure to restore components of IBM® InfoSphere® Information Server. You can restore the files, directories, and databases to recover from an event in which data was lost.

Before you begin

This task assumes that you are recovering InfoSphere Information Server on a system where InfoSphere Information Server was previously installed and that a good backup was previously performed. It also assumes that the host name of the computer is identical to that of the computer on which the backup was taken and that all components are being restored in the exact same location that they originally were in. If a different host name is used, the system is inoperable.

When you restore an installation, all of the same elements that were backed up must be restored before you start the InfoSphere Information Server and IBM WebSphere® Application Server services.

For more information about restoring Db2® databases, see Restore overview in the Db2 10.5 for Linux, UNIX, and Windows in the Knowledge Center. For other supported database systems, refer to your vendor documentation.

Procedure

  1. Disconnect all user sessions.
    Do not allow users to log in to the system at any point during the restore. Otherwise, it is possible that the restore might fail or users might lose data, which is overwritten when the metadata repository is restored.
  2. Stop the InfoSphere Information Server services and WebSphere Application Server services. For more information, see Administering IBM InfoSphere Information Server and IBM WebSphere Application Server services.
  3. If the microservices tier is installed, restore the microservices tier. Run the backup-restore-ugi.sh script to restore the microservices tier. See Backing up and restoring the Information Server microservices tier for more details. The microservices tier includes Enterprise Search, Watson Knowledge Catalog, and the Information Governance Catalog and Information Analyzer console.
  4. Stop the database instance of the metadata repository.
  5. Restore the metadata repository. For information about restoring a Db2 database, see the Restore overview in the Db2 10.5 for Linux, UNIX, and Windows in the Knowledge Center. For other supported database systems, refer to your vendor documentation.
  6. If IBM InfoSphere Information Analyzer was installed, restore the analysis database that is used by InfoSphere Information Analyzer.
  7. If you use the InfoSphere DataStage® and QualityStage® and have a backup of the operations database that is used for storing monitoring data that is displayed by the InfoSphere DataStage and QualityStage Operations Console, restore the operations database. Otherwise, you can re-create the operations database.
  8. If you use IBM InfoSphere QualityStage and have a backup of the Match Designer database that is used for refining or developing match specifications, restore it from backup. Otherwise, you can re-create the Match Designer database.
  9. If you use InfoSphere QualityStage Standardization Rules Designer and have a backup of the Standardization Rules Designer database that contains rule sets that are under revision or have changes that are not published, restore the Standardization Rules Designer database. Otherwise, if all the rule sets are published, you can re-create the Standardization Rules Designer database.
    Important: IBM InfoSphere QualityStage Standardization Rules Designer will not be supported after 31 December 2020. No replacement is planned.
  10. If you use InfoSphere DataStage and QualityStage and have a backup of the exceptions database that is used for storing exceptions that are generated by InfoSphere DataStage and QualityStage product components, restore the exceptions database. Otherwise, you can rerun your Exceptions stage jobs to generate new exception descriptors and their details.
  11. Restore the system elements that are listed in System elements and databases that require backing up.
  12. Restore the additional files that are listed in Additional files to back up.
  13. Restore external files or libraries that are used by IBM InfoSphere DataStage and InfoSphere QualityStage jobs.
    External files are data sets, file sets, sequential files, hashed files, and other similar files that run InfoSphere Information Server tasks, such as InfoSphere DataStage jobs. External libraries can be custom-written C++ functions that are called by the parallel engine.
  14. Restart the database instance of the metadata repository.
  15. Restart the microservices tier.
  16. Restart the InfoSphere Information Server services and WebSphere Application Server services. For more information, see Administering IBM InfoSphere Information Server and IBM WebSphere Application Server services.
  17. Disable maintenance mode if it was enabled.