Databases Reference
In-Depth Information
In the following example a backup operation takes place. As you can see—the first
run shows the amount of CPU consumed by the regular backup operation against
the time that operation takes to complete. On the second run, the duration has been
configured so that the workload against the database is minimized. The backup
operation takes longer, but the advantage of it is the reduced performance impact.
This can be seen in the example below:
Regular backup:
RMAN> BACKUP DATABASE;
Backup duration and throttling:
RMAN> BACKUP
2> DURATION 0:10
3> MINIMIZE LOAD
4> DATABASE;
Database cloning
Cloning a test or development environment after the backup has been taken from the
production environment is a very good opportunity to test if the backup will serve
its purpose. This is not the only time when a database clone is required, there are
several other scenarios, such as providing a fresh environment for developers and
pre-production environments, manually setting up a disaster recovery site, upgrade
preparation, and performance and stress testing, to name just a few.
Search WWH ::
Custom Search