Sun Storage 6920 System
 

GCS>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays
 

Content will be limited to a basic usage using the CLI or BUI interfaces
for creating snapshots, and provide help with some usage failure scenarios
for this activity. Consider reviewing some of the following documents if you
are looking to perform actions beyond the scope of this document:

• Best Practices for the Sun StorEdge 6920 System, Version 3.0.1
• Sun StorEdge 6920 System CLI Quick Reference Guide, Release 3.0
•  <Document: 1009915.1> Troubleshooting Sun StorEdge[TM] 6920 Configuration Problems
• Sun StorEdge 6920 System Administration Guide For the Browser Interface Management Software, Release 3.0

A. Start by Planning

Snapshot layout and planning mostly follows the same procedure as for volume creation. Reference document <Document: 1009979.1> Validating Sun StorEdge[TM] 6920 Volume Creation

In addition refer to Best Practices for the Sun StorEdge 6920 System, Version 3.0.1 - chapter 5 - Working with Snapshots 819-7320-10

and, depending upon the intended use,reference Sun StorEdge? Data Snapshot Software With Oracle Databases Usage Guide

The considerations for volumes are mostly common to snapshots, but in addition the following considerations are unique to Snapshots :

• Space for the Snapshot reserve
• The predicted quantity of snapshots
• The percentage of the parent volume that will change during the life of the snapshot.

If the choice of values is not known, then refer to related documents.

B. Basic Usage Using Browser or SSCS interfaces

SSCS

To create a snapshot on a volume that has no reserve space assigned.

sscs snapshot [-S TestDomain] -v <volume> -C <Num of Snaps> -L <update usage> volume <new_snap_volume>

No message returned usually indicates that the operation was successful, but it
it wise to check that the object was created as expected, Reference <Document: 1004359.1> Validating Sun Storedge[TM] 6920 Snapshot Details and State

Example CLI:

sscs snapshot -S TestDomain -v r5vol2 -C 2 -L average volume r5vol2_snap0

To create a snap on a volume that has already an assigned Reserve, the following command can
be used:

sscs snapshot -v <source_volume> volume <new_snap_volume>

Example

./sscs snapshot -v vol4 volume vol4-snap6

GUI

To create a snapshot on a volume that has no reserve space assigned.

Note: We do not consider mapping initiators part of basic snapshot creation.

1. Click on the Configuration Services or Common Array Manager(3.2.0.38) Link.
2. Click on the Volume Tab or Volume Menu Tree to see the 'Volume Summary'
3. Select volume to take a snapshot of by clicking on the volume name
4. Click on blue Snapshot button on the volume details page
5. New window will pop up (might need to enable popups in browser), enter volume name by which new snapshot will be known, and click on blue next button.
6. Enter Snapshot attributes: Allocate Reserve From Storage Pool, Number of Snapshots, Write Activity, Volume/Snapshot Policy
7. Click Next twice(skips initiator screen)
8. Click on Finish to take the snapshot at this point.

To create a snap on a volume that has already an assigned Reserve, the following sequence can be used:

1. Click on the Configuration Services or Common Array Manager(3.2.0.38) Link.
2. Click on the Volume Tab or Volume Menu Tree to see the 'Volume Summary'
3. Select volume to take a snapshot of by clicking on the volume name
4. Click on blue Snapshot button on the volume details page
5. New window will pop up (might need to enable popups in browser), enter volume name by which new snapshot will be known, and click on blue next button.
6. Enter Snapshot attributes: Number of Snapshots and Write Activity
7. Click Next twice(skips initiator selection screen)
8. Click on Finish to take the snapshot at this point.

• If you received a failure notification, continue to Step C.
• If you received a success notification, you have validated that volume creation is complete.

C. Creation failure

The creation of a snapshot can fail for several reasons:

Message:
The maximum number of snapshots for this volume has been exceeded.; operation failed.

Action:
Only 8 snap's can be associated with a volume at a time. While there can be up to 32 enumerated snaps, only 8 can be associated. Best Practices for the Sun StorEdge 6920 System, Version 3.0.1 Page 76|

Message:
The create operation failed.; operation failed.

Action:
The syntax is right, but one or more of the parameters is outside the operational bounds

Message:
The maximum number of snapshots for this volume has been exceeded.; operation failed

Action:
Only 8 snap's can be associated with a volume at a time. While there can be up to 32 enumerated snaps, only 8 can be associated. Best Practices for the Sun StorEdge 6920 System, Version 3.0.1 Page 76|

Message:
No snapshot reserve pool configured

Action:
Use a command to assign a snapshot reserve and take a snap. See Step B.

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

D. Data Collection

• Answers to Questions in Step A.
• 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 input and selections for the new volume wizard in the BUI
• The following sscs output:

sscs list sdomain
sscs list volume
sscs list pool
sscs list pool <pool name> (needed for sizing issues)
sscs list vdisk

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

E. Validate that services are running properly on the SP

Reference document <Document: 1007129.1> Validating Services on a Sun StorEdge 6920 Service Processor

F. Perform health check of array

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

G. Escalate

Provide the following:

• Description of what is not being displayed properly


• Results of Step E.


• Results of Step F.


• Location of everything in Step D
  

This solution has no attachment