Backup and recovery of data files and databases is an essential operation for any business system, particularly for data and applications running in production environments. Create and follow a plan for backing up and recovering data on all tiers of your IBM
® Portal deployment.
Backup and recovery includes the WebSphere
Portal file system and databases. Your backup and recovery plan needs to address each deployment tier: complete system backup for catastrophic failures, backup of middleware such as WebSphere
Portal and IBM WebSphere
Application Server, and backup of individual applications running on the middleware. Backup and recovery can be performed on any or all of these tiers, depending on the needs of your portal deployment.
When you create a backup and recovery plan, consider these general questions:
- What procedure will you use to back up data?
- How often will you back up data?
- What are the trade-offs between online and offline backups?
- How does the scope of your portal deployment affect the backup and recovery strategy? For example, the number of users and the volume and importance of the data being stored and used in applications will affect your decisions about backup and recovery practices.
- Will you use IBM Tivoli® Storage Manager or other utility to back up the file system?
Backing up and recovering a WebSphere
Portal installation includes the WebSphere
Application Server runtime environment and all applications deployed on WebSphere
Portal. However, if applications use remote information sources outside of the WebSphere
Portal databases and the LDAP directory, you need to consider these remote sources and develop backup and recovery procedures as part of your comprehensive strategy.
Guidelines for clustered deploymentsParent topic: Administering
If IBM WebSphere
Portal is deployed in a clustered topology, both a primary node and additional nodes are running in a cluster. In this topology, there is no difference in database backup and restore because all cluster members use the same WebSphere
Portal databases. However, you need to consider some additional factors when backing up and recovering the file system in a clustered deployment.
Backing up files, databases, and the LDAP server(s)
Periodically run an automated backup procedure for the IBM WebSphere
Portal file system, databases, and LDAP server(s) using a backup and recovery utility of your choice. Remember to run the backup procedure before performing critical system-wide changes, such as upgrading to a new version of WebSphere
Portal or installing interim fixes and fix packs.
Restoring files, databases, and the LDAP server(s)
When necessary, restore the IBM WebSphere
Portal file system, databases, and LDAP server(s) that you have backed up.