HP OpenView Storage Mirroring User Guide (360226-002, May 2004)

6 - 2
Connection Options
When establishing a connection, you must specify the machines that are involved with the connection, what data is being
protected and where that data is going, as well as configuring how this connection will perform.
! Source Server—You must specify the Storage Mirroring source machine that contains the replication set that is going
to be transmitted to the Storage Mirroring target.
! Replication Set—At least one replication set must exist on the source before establishing a connection. You must
specify the replication set that will be connected to the target machine.
! Target Server—You must specify which Storage Mirroring target will maintain the copy of the source data. You can
specify a machine name, IP address, or virtual IP address.
! Route—This is an optional setting allowing you to specify the IP address on the target the data will be transmitted
through. You should only change this setting if you want to select a different route for Storage Mirroring traffic. On a
machine with more than one NIC, this increases the flexibility of configuring Storage Mirroring activity. For example, you
can separate regular network traffic and Storage Mirroring traffic on a machine.
! Mappings—You must specify the location on the target where the replicated data will reside. Storage Mirroring offers
two predefined locations as well as a custom option that allows you to create your own path.
! One-to-One—In cases where only one source is replicated to each target, it is often easier to maintain the identical
volume/directory structure on the source and target. Additionally, if the target will stand-in for the source during
failover where users will be accessing data directly on the target (versus restoring data to the source for user access
or accessing data through shares or exports), this configuration is generally used.
The one-to-one option in the Management Console and the
map exact switch used with the connect command
in the Text Client map each source volume to the same structure on the target. For example, c:\data and
d:\files on the source would be replicated to c:\data and d:\files, respectively, on the target.
! All-to-One—In cases where more than one source is replicated to a single target server, it may be necessary to
store the data from each source in a separate directory on the same volume. If separate target locations are not
defined for each source, there is a potential that replicated data could be overwritten and corrupted. Replicating each
source to its own directory structure also simplifies the restore process.
The all-to-one option in the Management Console and the
map base switch used with the connect command in
the Text Client, map each source volume to a single target volume.
The predefined path is
\source_name\repset_name\ volume_name. For example, the default path for the
replication set rule c:\data is \source_name\ replication_set_name\c.
! Custom Location—If the predefined options do not store the data in a location that is appropriate for your
network operations, you can specify your own custom location where the replicated files will be sent.
! Start Mirror on Connection—Mirroring can be initiated immediately when the connection is established. If mirroring
is not configured to start automatically, you must start it manually after the connection is established or set a schedule
to start it later.
NOTE: The same replication set can be connected to multiple target machines.
NOTE: If you are using Windows 200x, your mapping selection can be critical.
! If you are mirroring and replicating dynamic volumes or mount points, your location on the target must
be able to accommodate the amount of data that you are replicating.
! If you are mirroring and replicating sparse files and your location on the target is a non-NTFS 5 volume,
the amount of disk space available must be equal to or greater than the entire size of the sparse file. If
you are mirroring and replicating to an NTFS 5 volume, the amount of disk space available must be
equal to or greater than the on-disc size of the sparse file.
! If you are mirroring and replicating multiple mount points, your directory mapping must not create a
cycle or loop. For example, if you have the
c: volume mounted at d:\c and the d: volume mounted at
c:\d, this is a circular configuration. If you create and connect a replication set for either c:\d or
d:\c, there will be a circular configuration and mirroring will never complete.
WARNING: Data integrity cannot be guaranteed without a mirror being performed. This option is recommended for
the initial connection.