Oracle Database migration to a remote Data Protector cell--Best practices

3
Environment Configuration
The environment used for our testing contains two Data Protector cells, (cell 1 and cell 2), each on a
different location (data center A and data center B).
Each cell has its own cell Manager and one Oracle Database server:
Cell 1 (data center A):
• Ita017:
– (HP-UX) Data Protector cell Manager in cell1.
– Oracle Server 10.2.0.3
– Recovery Catalog RCVCAT.
• Ita022:
– (HP-UX) Oracle Server running 10.2.0.3.
– Oracle Database DB10g.
– Data Protector File Library.
Cell 2 (data center B):
• hpu016:
– (HP-UX) Data Protector cell Manager in cell2.
– Oracle Server 10.2.0.3
– Recovery Catalog RCAT
• hpu015
– (HP-UX) Oracle Server running 10.2.0.3
– Data Protector Jukebox.
Note:
hpu015 will host the target database DB10g after the migration.
Originally, only the Oracle Server software is installed on the server.
For the purpose of the testing, we need a database on hpu016 were we
can import the source Recovery Catalog. We could use either an empty
database or an existing Recovery Catalog. If we use an existing Recovery
Catalog, then the source RCVCAT should be imported under a different
user schema than the RCAT owner.
On hpu015 we use a Jukebox to be able to import the media from the File
Library. See the Media export/import section for more information
The distance and network connection between both data centers plays only a role in case we decide to
copy the media from the file library over the network link. While it maybe feasible for small databases,
it is not an option for larger ones. In such cases, the media should be shipped to the target data center.