background image
<< Example of a Site Configuration | Storage systems and SAN switches >>
<< Example of a Site Configuration | Storage systems and SAN switches >>

Preinstallation Checklist

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preinstallation Task Flow
Remote Mirroring of an Oracle Database Using Data Replicator Software
2-3
Preinstallation Task Flow
For the RVM Solution to work, you first must set up the environment for Remote Volume
Mirroring. Create a Synchronous Write Mode as described on page
3-10
, and then proceed
with the following steps:
·
Create a Snapshot volume for each of the mirrored volumes. The default 20 percent
repository size should be adequate for the RVM Solution.
·
Create a volume copy for each of the mirrored volumes. The volume copy must be the
same size or larger than the mirrored volumes. Keep the naming syntax clear and easy
to interpret.
·
Map each of the volume copies to the remote host. Leave snapshots and secondary
mirrored volumes unmapped.
Preinstallation Checklist
Make sure the following equipment, tools, and software are available before installing
Remote Volume Mirroring.
Component
Description
Servers
Document the following items regarding the servers:
·
Vendor
·
Product and model number
·
Name, location, IP address, and
applications supported
·
Operating system version, patch level,
and configurations
·
Amount of memory
·
I/O slot loading
·
Internal disk and external disk use
·
Logical unit numbers (LUNs) used
·
Use of volume managers,
virtualizers, and replication software
·
Backup vendor, product, method,
and scheduling
·
Server optimization
·
Storage area network (SAN)
·
Will this server be upgraded or
replaced in the near future?
Host bus adapters
(HBAs)
Document the following items regarding the HBAs:
·
Vendor
·
Product and model number
·
Technical interface specifications
·
Firmware level
·
Software driver level
·
Configuration
·
1-Gb, 2-Gb, or 4-Gb capability
·
Zoning
·
WWN