The database cloning process creates an exact copy of a
database to provide near-production data.
Tivoli® Storage FlashCopy® Manager uses
the FlashCopy or snapshot
function for database cloning. The following list identifies scenarios
when you might clone a database:
- To create a test system before you introduce, a new product release
or new functions into a production environment.
- To create an education system from a master training system. You
can reset the cloned database before you start a new course.
- To create a dedicated reporting system to offload the workload
away from the production environment.
Traditionally, the database
cloning process redirected a restore operation to create the clone.
This method has various disadvantages, including system downtime and
degraded system performance. Tivoli Storage FlashCopy Manager clones
a database by using the storage system FlashCopy or snapshot capabilities
to minimize the impact on the production database. A clone server or clone
system is required by Tivoli Storage FlashCopy Manager to
mount a cloned database.
The following figure shows how
Tivoli Storage FlashCopy Manager creates
and stores a cloned database on a clone server.
Figure 1. Tivoli Storage FlashCopy Manager and
database cloning