Sun Microsystems 3 manual Choosing the Resynchronization Type Update or Full

Page 25

Choosing the Resynchronization Type: Update or Full

Tip – If a synchronization initiated by the sndradm -mor

sndradm -m-rcommands is interrupted, use the sndradm -m-uupdate command to complete the synchronization. Use /usr/opt/SUNWscm/sbin/scmadm -Sto view the synchronization progress.

An update resynchronization applies changes that occurred at the primary data to the secondary site during the time replication was suspended. The primary site can also be updated from the secondary, if desired.

Afull synchronization is a complete disk-to-disk copy. This operation is the most time consuming of the synchronization operations. A full synchronization is only done when the Sun SNDR software volume set is:

Initially established

Damaged due to a disaster

Data integrity is questions

If the integrity of the Sun SNDR software volume data is questioned, then the only way to get the volume back into a synchronized set is to perform a full volume copy.

The Sun SNDR software volume set data might be in question if, for example, there was a double disk failure on a RAID 5 set or if the Sun SNDR software is shutdown manually and writes occurred to either the primary or secondary volumes without scoreboarding being active. The full copy can either be performed from the primary to the secondary or if appropriate, from the secondary to the primary.

Choosing Automatic or Manual Resynchronization

The Sun SNDR software provides a choice of automatic or manual resynchronization after a disaster. Automatic resynchronization is discouraged if the interruption is the warning of a larger rolling disaster. It is best to maintain the secondary site in a dated but consistent state, rather than risk a disastrous interruption that leaves the secondary inconsistent and difficult to recover from. The autosynchronization option is disabled by default for this reason.

See also “Using The Sun SNDR and Sun StorEdge Instant Image Software” on page 16. Before you start a resynchronization operation, ensure that you have an appropriate Instant Image software point-in-time copy of the Sun SNDR software target volume.

Chapter 2 Configuration Considerations 15

Image 25
Contents Sun StorEdge Network Data Replicator Configuration Guide Please Recycle Contents Page Before You Read This Book PrefaceDocumentation Conventions Using Unix CommandsRelated Documentation Shell PromptsApplication Title Part Number Ordering Sun Documentation Accessing Sun Documentation OnlineSun Welcomes Your Comments Page Sun Sndr Software Description OverviewPage TCP/IP Connection Hardware Components Supported Hardware and SoftwareNetwork Multipathing Architecture ApplicationsSdbc Volumes Eligible for Replication Configuration ConsiderationsChoosing Volume Level Protection Bitmap Volumes for Scoreboard LogsATM Link Advantages Choosing a Connection Medium to Link My SitesLink Security Configuring Redundant Links Between SitesChoosing Between Synchronous and Asynchronous Replication Configuring The Sun Sndr Software for Mutual Replication When To Suspend Replication to the Secondary SiteSync Order-Dependent Writes and Volume Set GroupingRecovering the Primary or Secondary Site Recovery ConsiderationsFailing Over to the Secondary Site Choosing the Resynchronization Type Update or Full Using The Sun Sndr and Sun StorEdge Instant Image Software Sun Sndr Software and Sun StorEdge Fast Write Cache Software Dev/rdsk/c0t0d0s9 One-to-Many and Multihop Volume SetsUsing The Sun Sndr Software in a Firewall Environment
Related manuals
Manual 368 pages 47.9 Kb