Restoring files, databases, and the LDAP server(s)Added by IBM | Edited by IBM on June 23, 2012 | Version 2 (Show original)
|When necessary, restore the IBM® WebSphere® Portal file system, databases, and LDAP server(s) that you have backed up.
When necessary, restore the IBM
® Portal file system, databases, and LDAP server(s) that you have backed up.
Before restoring 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, the configuration and data files might not be synchronized with the information in the databases.
- Remember that the file system backup for WebSphere Portal includes directories containing the configuration files.
- Consider whether you implemented separate databases for each database domain or multiple database domains using the same database. For example, if all database domains were implemented 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.
To restore the WebSphere
Portal file system, databases, and the LDAP server, follow these steps:
- Stop all servers.
- If applicable, stop all external HTTP servers.
- Stop all of the WebSphere Portal servers.
- Move the backed up files to their original location.
Refer to the documentation of the backup utility that you used for instructions on restoring files.
WARNING: Do not overwrite the existing AppServer, PortalServer, or wp_profile root directories with the backed up files because you risk corrupting the WebSphere Portal file system. You should first remove these old directories and then extract the backed up version in its place.
- Restore the WebSphere Portal databases:
Optional: If necessary, restore your LDAP server.
- For IBM DB2 Universal Database Enterprise Server Edition, refer to the DB2 Information Center.
- For other database servers, refer to that database server documentation for instructions.
Parent topic: Backup and restore
- For IBM Tivoli® Directory Server, refer to Tivoli Directory Server Information Center.
- For IBM Lotus® Domino®, refer to the Directory Services topics in the Lotus Domino Administrator Help.
- For other LDAP servers, refer to the product documentation for instructions.