5.5 Backing up and restoring the configuration database It is a good practice to regularly back up the configuration database. The backup process is performed using a Tivoli Enterprise Portal client. The backup process does not interfere with the functioning of the configuration manager, nor does the Tivoli Enterprise Monitoring Server need to be disabled in order to execute the backup process. The backup begins only if there are no outstanding deferred database updates pending; the backup also waits until all database commits have completed. While the backup is running, it is possible to fetch records from the database as required by other transactions; however, any deferred database updates that are created while the backup is running will remain queued until the backup completes. This will not prevent other update transactions from running. The format of the backup file is platform-independent. Therefore, the backup process can be used to migrate the configuration data from one platform to another. If you use FTP to accomplish this, you must specify the ASCII format. Also, if you transfer a backup file to z/OS, define the LRECL of the receiving data as follows: RECFM=FB,LRECL=440,BLKSIZE=<some multiple of 440> There is only one procedure to back up the configuration database file regardless of the type of database (the product-provided Internal type or the DB2 Universal Database type) that your site uses for the configuration database. To back up the configuration database to a file: 1. Ensure that you are in update mode. The Configuration view opens. Chapter 5. Using OMEGAMON XE for Messaging to configure WebSphere MQ 193