IBM BS029ML Self Help Guide - Page 222
Backup strategy, Overview of the backup process
![]() |
View all IBM BS029ML manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 222 highlights
Backup strategy A complete and thoroughly tested backup and recovery procedure is essential for any production environment. WebSphere Portal Server is no different. You should develop complete disaster recovery strategies and approaches and test those procedures in a testing environment. Once verified, you should implement these same procedures in the WebSphere Portal Server production environment. This section does not detail a step-by-step process for backup. Rather, it provides insight into an approach for WebSphere Portal Server backup that you can implement into your existing disaster recovery procedures. Overview of the backup process The approach described in this section implements full system backups while maintaining 24x7 operations. The approach consists of stopping a percentage of the clustered nodes and then taking file system backups of the WebSphere Application Server and WebSphere Portal Sever root directories while the Portal nodes and node agents are stopped. The remaining clustered nodes continue to operate and maintain 24x7 operations. After the backups are complete on the first group of Portal nodes, those nodes are brought back online in the cluster, another group of nodes are stopped, and the process is repeated. We recommend making backups while the nodes are down to avoid incomplete backups because of open files while the backups are taking place. Note: Software tools may exist that allow complete backups to be made while files are open, but this section does not discuss these tools. If you wish to implement these types of tools, you can adjust the approach appropriately. The general outline of the approach is: Stop a group of Portal nodes in the cluster. Make a file system backup of the stopped nodes. Start the nodes. Stop another group of nodes in the cluster. Make a file system backup of the stopped nodes. Start the nodes. Repeat this process until all nodes have been stopped and file system backups are taken of each node. Stop the Deployment Manager node. Make a file system backup of the Deployment Manager node. Make a database backup of all the databases associated with WebSphere Portal. Restart the Deployment Manager. 208 IBM WebSphere Portal V6 Self Help Guide
![](/manual_guide/products/ibm-bs029ml-self-help-guide-6d3dd71/222.png)