Restoring files, databases, and the LDAP server(s)
When necessary, restore the IBM® WebSphere® Portal file system, databases, and LDAP server or servers that you backed up.
Before you begin
Before you restore WebSphere Portal databases, remember to adhere
to the following principles:
- Whenever you restore WebSphere Portal databases, you must restore the databases for all of the nonshared database domains to ensure consistency: Release, LikeMinds, Java™ Content Repository (JCR), and Feedback are the nonshared database domains.
- Restoring the databases of the shareable database domains is optional and might not be required when you do not want to lose recent user and community information: Customization and Community are the shareable database domains.
- Whenever you restore the WebSphere Portal databases, you must also restore the configuration and data files that were archived when the backup image was taken.
- Be sure that your database restoration rolls forward to the point when you performed the file system backup for the WebSphere Portal deployment. If you fail to do this step, the configuration and data files might not be synchronized with the information in the databases.
- The file system backup for WebSphere Portal includes directories that contain the configuration files.
- Consider whether you implemented separate databases for each database domain or multiple database domains by using the same database. For example, if all database domains were implemented by using a single WebSphere Portal database, then restoring this database restores the contents of all domains.
- If you are using IBM DB2 Universal Database™ Enterprise Server Edition, you should understand the basics of DB2® data backup.
- If you are using a different database management system (DBMS), refer to the DBMS documentation for backup instructions.