Backup considerations for WebSphere Process Server
Mykyta_Kostovskyy 270000N0GT Comments (4) Visits (15828)
In this post I would like to share with you some important backup considerations that I highly recommended that you take into account when creating a backup policy and your backup mechanism.
So the most important difference between a plain WebSphere Application Server environment and a WebSphere Process Server environment is that with WebSphere Process Server you have permanently active data sources for the business process engine (BPC), general WebSphere Process Server data source (WPRCSDB), Common Event Infrastructure (CEIDB), and Messaging DB (MEDB). In environments, even with a low or middle load, you will still experience high database activity due to data persistence according to default quality of service policies.
So, as you can see from the above, it is not as simple as just making a backup of the files on the hard drive with the backupConfig.sh utility or just zipping the image or creating a disk image. The problem would be that when you take the backup of your files, your data source might have already moved ahead with data that is written in your current backup transaction logs or it could have changed due to the Dmgr configuration made a minute ago but not yet synchronized with the backup profile.
In order to do the backup right, please take the above crucial points into account. To make an appropriate backup policy suiting your business needs, the files and the database (in the best case) should be backed up at the same moment and on all the nodes at the same time. This could be done when everything is persisted and the system is inactive (for example during a maintenance cycle) or if you have a time frame to bring all the clusters down and make a backup of the data sources and files on the disk. So the perfect situation for data source backup would be when the all the environment data sources are inactive.
Most of the modern databases have capabilities to make online backups without a database outage in online (interactive mode), but please keep in mind that active messaging engine (ME) keeps a permanent exclusive lock on the SIB data store table. Also other tables might be effected depending on the database used and configuration setup (for example Security cred
On the other side from WebSphere Process Server runtime, the most important thing is to backup the data for configuration on the deployment manager and make sure that it is the most current version. The nodes are taki
Related blog post: Important backup consideration for Websphere Process Server V7