Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1007158.1
Update Date:2009-04-15
Keywords:

Solution Type  Technical Instruction Sure

Solution  1007158.1 :   Validating Replication Set Modification for a Sun Storedge[TM] 6920  


Related Items
  • Sun Storage 6920 System
  •  
Related Categories
  • GCS>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays
  •  

PreviouslyPublishedAs
209862


Description
Validating Replication Set Modification for a Sun Storedge[TM] 6920

The purpose of this document is to provide basic steps for Remote Replication
Set(repset) modification for the 6920 array, via the Browser User Interface(BUI) or sscs Command Line Interface(CLI).

Content will be limited to a basic usage using the CLI or BUI interfaces
for modifying replication sets, and provide help with some usage failure scenarios for this activity. Content will be limited to:

  • Enable/Disable Autosync
  • Enable/Disable Snapshot of Secondary on Resume of Set
  • Enable/Disable Snapshot of Primary on Resume of Set
  • Change Mode between Sync and Async
  • Change Role between Primary and Secondary
  • Change Replication IO Priority
  • Change Async Sets will block IO or suspend the set on Queue Full conditions
  • Suspend a Set
  • Resume a Set
  • Change Queue full condition parameters

Consider reviewing some of the following documents if you are looking to perform actions beyond the scope of this document:

NOTE: Some operations apply only for the primary array, some only for the secondary array, and some for both. These will be annotated in BOLD.



Steps to Follow
Repsets, Autosyncs, Snapshots, & Arrays

A. Suspend a Repset

This is to be executed on the PRIMARY site

SSCS

sscs modify -c repset <repset_name>

EX:

sscs modify -c repset repset3/1

BUI

  1. Click on the Configuration Services or Common Array Manager Link.
  2. Click on the Replication Sets Tab or Menu Tree
  3. Click on the Repset name
  4. Click the Suspend button
  5. Click Normal in the pop-up
  • If you received an error, go to Step J

B. Resuming a Repset

This is to be executed on the PRIMARY site

SSCS

sscs modify -z repset <repset_name>

EX:

sscs modify -z repset repset3/1

BUI

  1. Click on the Configuration Services or Common Array Manager Link.
  2. Click on the Replication Sets Tab or Menu Tree
  3. Click on the Repset name
  4. Click the Resume button
  5. Click Normal in the pop-up
  • If you received an error, go to Step J

The following Procedures require that the set be in a state of Suspended

C. Enable Autosync

Autosync is an operation that automatically resumes a set
after a peer link failure.

SSCS

modify [-s|--auto-sync <enable|disable>] repset <repset_name>

EX:
sscs modify -s enable repset repset3/1

BUI

  1. Click on the Configuration Services or Common Array Manager Link.
  2. Click on the Replication Sets Tab or Menu Tree
  3. Click on the Repset name
  4. Check the Autosynchronize Box
  5. Click the Save button
  • If you received an error, go to Step J

D. Enable/Disable Taking a Snapshot of Secondary Volume, When the Primary Volume is Snapshotted

This does not depend on the replication set state. When a Primary volume has a snapshot taken, the secondary volume will take a snapshot at the same time, ensuring that both sides have the same point in time data. This requires
that the peer link be active.

This can be executed on either array, but only applies when the set role is secondary for that site. Snapshot for the Volume must be created manually. Reference document <Document: 1011356.1> : Validating Sun Storedge[TM] 6920 Snapshot Creation

SSCS

sscs modify [-x <enable|disable>] repset <repset_name>

EX:
sscs modify -x enable repset repset3/1

BUI

  1. Click on the Configuration Services or Common Array Manager Link.
  2. Click on the Replication Sets Tab or Menu Tree
  3. Click on the Repset name
  4. Check the Snap with Primary Box
  5. Click the Save button
  • If you received an error, go to Step J

E. Enable/Disable Taking a Snapshot of the Secondary Volume, when Set is Resumed

This can be executed on either array, but only applies when the set role is secondary for that site. Snapshot for the Volume must be created manually. Reference document <Document: 1011356.1> : Validating Sun Storedge[TM] 6920 Snapshot Creation

SSCS

modify [-p <enable|disable>] repset <repset_name>

EX:
sscs modify -p enable repset repset3/1

BUI

  1. Click on the Configuration Services or Common Array Manager Link.
  2. Click on the Replication Sets Tab or Menu Tree
  3. Click on the Repset name
  4. Check the Snap before Synchronization Box
  5. Click the Save button
  • If you received an error, go to Step J

F. Change Set Mode from Async to Sync

This can be executed on either array, but only applies when the set role is primary for that site.

SSCS

modify -m sync repset <repset_name>

EX:
sscs modify -m sync repset repset3/1

  1. Click on the Configuration Services or Common Array Manager Link.
  2. Click on the Replication Sets Tab or Menu Tree
  3. Click on the Repset name
  4. Click on the To Synchronous Mode button
  5. When the screen returns, click the Delete Queue button.
  • If you received an error, go to Step J

G. Change Set Mode from Sync to Async

This can be executed on either array, but only applies when the set role is primary for that site.

SSCS

modify -m async -q <queue volume pool> -u [block|suspend] -k [# blocks in queue for queue full] -t [# IOs in queue for queue full] repset <repset_name>

EX:

sscs modify -m async -q my-async-queue-pool -u block -k 0 -t 0 repset myprimaryvol/1

  1. Click on the Configuration Services or Common Array Manager Link.
  2. Click on the Replication Sets Tab or Menu Tree
  3. Click on the Repset name
  4. Click on the To Asynchronous Mode button
  5. Specify the Queue size(defaults to 10% of local volume in set)
  6. Specify the number of blocks to dictate a Queue Full condition(defaults to 0)
  7. Specify the number of IOs to dictate a Queue Full condition(defaults to 0)
  8. Specify whether to block new IOs or suspend the set on a queue full condition.
  9. Click Next
  10. Specify The Pool for the Queue
  11. Click Finish

Note: Specifying the blocks and IO's on queue as zero(0), allows the full size of the queue volume, to be used. If a queue full condition is hit, the repset will either block new IO's or place the set automatically into a Suspend state.

  • If you received an error, go to Step J

H. Changing the Set Role for the local array

This can be executed on either array, and needs to be changed on BOTH arrays, prior to resuming the set.

SSCS

modify [-r <primary|secondary>] repset <repset_name>

EX:
sscs modify -r primary repset repset3/1

BUI

  1. Click on the Configuration Services or Common Array Manager Link.
  2. Click on the Replication Sets Tab or Menu Tree
  3. Click on the Repset name
  4. Change the Role dropdown to Primary or Secondary
  5. Click the Save button

I. Change Replication Priority

This can be executed on either array, but only applies when the set role is primary for that site.

SSCS

modify [-R <low|medium|high>] repset <repset_name>

EX:

sscs modify -R high repset repset3/1

BUI

  1. Click on the Configuration Services or Common Array Manager Link.
  2. Click on the Replication Sets Tab or Menu Tree
  3. Click on the Repset name
  4. Change the Role dropdown to Primary or Secondary
  5. Click the Save button
  • If you received an error, go to Step J

J. Creation Failure.

Please review the following table for a failure message and corresponding action. Please follow the action that describes your symptom.

BUI

Message:
An error occurred. Please contact your system administrator

Action:
Please go to Step K.

SSCS

Message:
<pool_name>: The resource was not found.

Action:
Make sure the pool exists and the name is correct(sscs list pool)

Message:
<domain>: The resource was not found.

Action:
Check the spelling of the domain name, and make sure it exists(sscs list sdomain)

Message:
Error: The operation failed.

Action:
Please go to Step K.

If a message is not listed, or an action above did not work, go to Step K.

K. Data Collection

Please collect the following information:

  • 6920 Solution Extract, Reference document <Document: 1003756.1> : How to collect an extractor from a Sun StorEdge[TM] 6920 (2.x and 3.x)
  • The message given by SSCS or BUI(screen capture if possible)
  • The command used, if by SSCS
  • The following sscs output:

sscs list sdomain
sscs list volume <volume name>
sscs list pool
sscs list pool <pool name> (needed for queue)
sscs list vdisk
sscs list repset
sscs list repset <repset>
sscs list fcport
sscs list fcport <fcport of peer link>
sscs list etherport
sscs list etherport <etherport>

Once this information is collected, please contact Sun Support



Product
Sun StorageTek 6920 System
Sun StorageTek 6920 Maintenance Update 2
Sun StorageTek 6920 Maintenance Update 1

Internal Comments
Validate command and perform health check of array

This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the “Document Feedback” alias(es) listed below:

storage-os-disk-mid-domain@sun.com



Sun Support



L. Validate command provided


Validate command provided against examples in the Sun StorEdge 6920 System CLI Quick Reference Guide, Release 3.0.

Ensure that options are valid based on the usage available in reference guide.



M.
error occurred


If the customer reports:



An error occurred. Please contact your system administrator


OR



Error: The operation failed.


Validate the services on the Service Processor. Reference <Document: 1007129.1>  



N. Perform health check of array


Reference <Document: 1005447.1> : Sun StorEdge[TM] 6920 Health Checklist



O. Escalate


Provide the following:



  • Description of what is not being displayed properly

  • Results of Step L.

  • Results of Step M.

  • Results of Step N.

  • Location of everything in Step K

The Knowledge Queue for this article is KNO-STO-MIDRANGE_DISK.

modify, configure, remote replication, replication sets, 6920, rename, normalized, audited
Previously Published As
90756

Change History
Date: 2007-09-28
User Name: 7058
Action: Approved
Comment: OK to publish.
Version: 3
Date: 2007-09-26
User Name: 7058
Action: Accept
Comment:
Version: 0


Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback