HP StorageWorks Storage Mirroring Recover User's Guide (T5437-96008, November 2009)

588 of 739
Replication sets
A replication set defines the data on a source machine that Storage Mirroring Recover
protects. Replication sets are defined by volumes, directories, files, or wild card
combinations. Creating multiple replication sets allows you to customize sets of data that
need to be protected. When working with data workloads, you need to define the
replication set data yourself. If you are protecting full-server, application, virtual, or
cluster workloads, the replication set is automatically defined for you.
When a replication set is created, a series of rules are defined that identify the volumes,
directories, files, and/or wild card combinations that will be replicated to the target. Each
rule includes:
● Path—The path including volume, drive, directory, file, and/or wild card
● Include—If the specified path is to be included in the files sent to the target
● Exclude—If the specified path is not to be included in the files sent to the target
● Recursive—If the rule should automatically be applied to the subdirectories of the
specified path
For example, a replication set rule might be volume\directory\* inc, rec
This specifies that all files contained in the volume\directory path are included in the
replication set. Because recursion is set, all files and subdirectories under
volume\directory are also included. A complete replication set becomes a list of
replication set rules.
Replication sets offer flexibility tailoring Storage Mirroring Recover to your environment.
For example, multiple replication sets can be created and saved for a source to define a
unique network configuration. There may be three replication sets - Critical Data, User
Data, and Offsite Data. Critical Data could be configured to replicate, in real-time, to an
onsite high-availability server. Offsite Data is replicated across a WAN and, therefore, is
configured to queue changes until a sufficient amount of data is changed to justify
transmission. At that point, the connection is made and stays active until all the data is
transmitted. User Data is not replicated throughout the day, but a nightly changed file
mirror copies only blocks of data that are different between the source and target server
prior to a nightly tape backup operation being run on the target server. Each of these
replication sets can be automated to transmit as needed, thus protecting your entire
environment.
● Creating a replication set
● Creating or modifying replication rules manually
● Modifying a replication set
● Renaming and copying a replication set