Topics | How To |
Change the State of Replication Pair
Configure Orphan File Processing
Perform Replication Prediction
Out Of Band Sync from the Replication Set
Out Of Band Sync from a Replication Pair
Replicate the Destination Data Back to the Source Computer
Before You Begin
Required Capability: Capabilities and Permitted Actions
To start Data Replication Activity:
Start, or Start Full Resync.
Before You Begin
Required Capability: Capabilities and Permitted Actions
To change the state of a Replication Pair:
Before You Begin
Required Capability: Capabilities and Permitted Actions
To configure orphan file processing for a Replication Set:
Before You Begin
Required Capability: Capabilities and Permitted Actions
To view the orphan files for a Replication Pair:
Each listed command should be run from a command line prompt, in the folder where the base package resides.
Before You Begin
Required Capability: Capabilities and Permitted Actions
All active Replication Pairs are automatically monitored from the time they are configured. To monitor an object not configured using CDR, you will need to add the path of the object to the list of monitored objects by executing this command.
Windows: predict -folder <full path and folder name>
Examples:
UNIX: cdrp -start
View the data for a monitored volume, folder, mount point, or file system by executing this command.
Windows: predict -getdata <full path and folder name>
If you specify a volume for this command, all monitored paths in this volume will be reported.
Examples:
Sample Output:
predict -getdata L:\
Vol Name: L:\
Folder \test1\
Monitored Interval From <time_stamp> to <time_stamp>
Monitored area Bytes Changed 00863744 Change in MB = 0.823730 MB
Folder \test\
Monitored Interval From <time_stamp> to <time_stamp>
Monitored area Bytes Changed 60018688 Change in MB = 57.238281 MB
UNIX: cdrp -q[uery] [[-c] <fname>]
Queries replication statistics for the file system that the specified file belongs to. If a file name is not provided, the program will enumerate all mounted watched file systems and will provide statistics for each of them. You may pass a "-c" option along with the file name. This will make the tool perform continuous queries -- refreshing the screen every several seconds.
Reset the data for a monitored volume, folder, mount point, or file system by executing this command.
Windows: predict -getdata <full path and folder name> -c
If you specify a volume for this command, the data for all monitored paths in this volume will be reset.
Examples:
UNIX: cdrp -r[eset] [<fname>]
Resets replication statistics for the file system that the specified file belongs to. If a file name is not provided, the program will reset replication statistics for all mounted, monitored file systems.
For objects not configured using CDR, stop monitoring by executing this command.
Windows: predict -remove <full path and folder name>
Examples:
UNIX: cdrp -stop
Before You Begin
Required Capability: Capabilities and Permitted Actions
To perform the Out Of Band Sync for a Replication Pair at Replication Set level:
Before you Begin
Required Capability: Capabilities and Permitted Actions
To perform the Out Of Band Sync for a Replication Pair:
Required Capability: Capabilities and Permitted Actions
To temporarily use the replica as the production data set:
Example:
There are three Replication Pairs:
E:\ => L:\E_drive
F:\ => L:\F_drive
N:\ => M:\N_drive
Query the USNs of the L: and M: volumes (the first two Replication Pairs use the same destination drive, L:, and will thus use the same USN) by typing the following commands:
Sample output:
CDRXHelp 1.0 - CDR External Base Line Helper Tool
Path:
L:\
USN: 0f4f5a68
Sample output:
CDRXHelp 1.0 - CDR External Base Line Helper Tool
Path:
M:\
USN: 0f4f6b46
Record both USNs for use later in this procedure.
When the original Source computer is operational again, proceed to the next section.
To replicate data back to the original Source computer:
Do not start the Replication Pair(s) yet.
Example:
Using the same example from Step 2, create three Replication
Pairs on the Destination computer:
L:\E_drive => E:\
L:\F_drive => F:\
M:\N_drive => N:\
Determine the Replication Pair ID(s) using the CDRXHelp.exe -cn <ClientName> -vm <InstanceName*> -pairs command:
<software_installation_path>\Base> CDRXHelp.exe -cn <ClientName> -vm <InstanceName*> -pairs
Sample output:
REPID PAIRID SrcPath
DestPath
91 177 L:\E_drive E:\
91 180 L:\F_drive F:\
92 183 M:\N_drive N:\
CDRXHelp.exe -setUSN -cn <ClientName> -vm <InstanceName*> -pID <PAIRID> -USN <some_USN> - sets a Replication Pair with a Pair ID <PAIRID> to a specific USN, <some_USN>.
If you miss this step your Replication Pair will have the default USN of 0 and when you start the Replication Pair, a Full Re-Sync will be performed. |
Example:
Using the same example from Steps 2 and 4, execute the following three commands:
<software_installation_path>\Base> CDRXHelp.exe
-setUSN
-cn <ClientName> -vm <InstanceName*> -pID 177 -USN 0f4f5a68
<software_installation_path>\Base> CDRXHelp.exe -setUSN
-cn <ClientName> -vm <InstanceName*> -pID 180 -USN 0f4f5a68
<software_installation_path>\Base> CDRXHelp.exe -setUSN
-cn <ClientName> -vm <InstanceName*> -pID 183 -USN 0f4f6b46
Sample output:
CDRXHelp 1.0 - CDR External Base Line Helper Tool
PairId: 177
Old JournalId: ffffffffffffffff
Old USN: ffffffffffffffff
New JournalId: 1c625d8d392c299
New USN: 0f4f5a68
When the Replication Set is deleted, any Recovery Points or Consistent Recovery Points that were created from the Destination will be deleted as well, which is necessary in order for SmartSync to succeed when you start replication on the original Source computer again. If you want to preserve the data in such Recovery Points, back them up before deleting the Replication Set. See Back up a Recovery Point. |
Do not start the Replication Pair(s) yet.
* InstanceName is the name used for a CDR instance (by default it is Instance001). If multiple instances of CDR are installed use the corresponding instance name, see Multi Instancing for more information.