Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

Share this Page URL
Help

Chapter 5: Administrator scenarios > Managing stacked projects - Pg. 207

Example 5-12 Accept the warning message to replace the database SQL2539W Warning! Restoring to an existing database that is the same asthe backup image database. The database files will be deleted. Do you want to continue ? (y/n) Repeat the same process for other databases. After restoring the database, synchronization is mandatory to synchronize the images in the Virtual Center with those in the Tivoli Service Automation Manager. Synchronization steps are described in "Synchronizing with the current status" on page 202. Recovery scenario Our experience tells us that the best approach to recover a system following a disaster is the sum of the two solutions described: "Virtual Center solution for backing up a software stack" on page 201 and "Periodic backup using DB2" on page 205. Take an image backup after an important change in your environment, such as after applying a FixPack, after changing hardware or any other upgrade in the cloud. This will prevent you from having to return to the previous state in case of a disaster. Configure your system to take a daily database backup of your cloud. You can configure DB2 to take daily backup and set DB2 to save the transactions log. In case of a disaster, follow these steps to restore your cloud: 1. "Restoring the software stack images using the Virtual Center" on page 202 2. "Restoring a DB2 backup" on page 206 3. "Synchronizing with the current status" on page 202 5.3 Managing stacked projects The problem of stacked projects concerns wrong entries in a data model. It can be resolved using new functions in the Reliability, Availability and Serviceability (RAS) feature introduced in Tivoli Service Automation Manager 7.2.2. Chapter 5. Administrator scenarios 207