Table of Contents
Advertisement
Asynchronous Replication
Communicating with a Partner Host, page 5-2
•
Create a Pairing, page 5-7
•
Asynchronous Replication (hereafter referred to as Async Replication) is an optional and separately
licensed feature. It provides a permission-based mechanism to create a duplicate version of a LUN on a
device attached to a partner host.
Cisco uses block-level Async Replication and incorporates an Async snapshot feature to capture a
point-in-time state that allows applications to continue writing their data. These features help to prevent
damage from failures or disasters that may occur in one location and improves the ability to recover a
copy of the data in another location.
Note
Before you use the Asynchronous (Async) Replication feature, make sure that you do not use the
•
LUN or Snapshot "Snapdiff1_xyz" as the name (where 'xyz' is either the Source or Target, LUN, or
Snapshot name) because the user data might get deleted during the replication process.
•
When using the Async Replication feature, both the Source and the Target must be LUNS, except
for the Windows Pairing type where the Destination is a Windows file.
•
The Source and Target LUNs must be the same size and must be 2TB or less.
•
Use "Create New Pairings" to add a new partner host. A LUN must be present before a pairing can
be created.
•
The Cisco UCS Invicta Scaling System uses the standard remote shell facility, ssh, to send the public
key. Use "Public Key" to display this key. The key must be copied and pasted into the
authorized_keys list. See section - Communicating with the Partner Host
Use "Windows Installer" to obtain an installation package for software required for Windows use of
•
Async Replication.
The first replication that is performed on a pairing is always a FULL replication. Subsequent
•
replications reflect the delta changes, except where an "Update Partner" operation is performed. In
that case, the next replication is a FULL replication.
When updating a partner host, a full replication is triggered.
•
We do not recommend using Destination entities in Read-Write mode as this poses a risk to the
•
accuracy of the data replication and may corrupt data recovery.
Cisco UCS Invicta Scaling System Administration and Configuration Guide, Version 5.0.1.1a
5
C H A P T E R
5-1
Advertisement
Table of Contents
