Sun StorEdge[TM] Availability Suite: Remote Mirror: Best Practice for Performing Full Mirror Sync Over a Highly Latent Network (Doc ID 1001958.1)

Last updated on JUNE 12, 2017

Applies to:

Sun Storage Availability Suite - Version: 3.0 and later   [Release: 3.0 and later ]
Sun Storage Network Data Replicator (SNDR) - Version: 3.0.1 and later    [Release: 3.0 and later]
All Platforms

Goal

This document was designed to supplement the Administration Guide for
Availability Suite Remote Mirror Software(aka SNDR). The guide states that
under circumstances where network latency causes the full sync time
for a set or group of sets to be unmanageably large, to perform a backup
to tape of the Primary device and ship it to the secondary site for a restore.


Note that there is more than one reason that a full sync is required. This document is designed to take this into account. For those instances where the full sync is the result of failure or other issues, it is up to the user to identify the sets. If this is in question, contact Support for help.

 

The document is broken into two parts. The first part details this procedure through the use of the Point In Time Copy (aka Instant Image) software. The second part details the procedure without PiTC. Oracle recommends that the first procedure be used on systems that are in production, as it is the most reliable way to ensure data consistency. This document provides more details, ensuring that data integrity is maintained. The document uses magnetic tape as an example of removable media. This is not a media limitation. If you have other media that may be accessed through a raw utility for reads and writes, and meets the physical size requirements, it may be used instead of magnetic tape.


Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms