Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Technical Instruction Sure Solution 1002513.1 : Sun StorageTek [TM] 6130/6140/6540: When taking a volume copy of a snapshot, all volumes must be owned by the same controller
PreviouslyPublishedAs 203491 Description The Volume Copy and Snapshot dataservices on the Sun StorageTek [TM] 6130/6140/6540 arrays can be used in combination, to create a standalone point-in-time clone of the original volume while still allowing full read/write access to the original volume (known as the "base" volume) This is achieved by :
Steps to Follow When taking a volume copy of a snapshot, then the base volume, the snapshot reserve volume, and the target volume for the volume copy must all be owned by the same array controller (either A or B). To prevent lun thrashing during the volume copy, the preferred controller for the base volume, the snapshot reserve volume and the target volume for the volume copy should also be set to be the same array controller. The current setting of the preferred and owning controller for the base volume and target volume can be seen in the management software GUI on the volume's "Volume Details" screen, for example : * Name: base-volume1 World Wide Name: 60:0A:0B:80:00:11:A9:80:00:00:0A:52:45:34:A6:12 Type: Standard .... Preferred Controller: B * Owning Controller: B The current setting of the preferred and owning controller for the reserve volume can be seen in the management software GUI on the snapshot's "Snapshot Details" screen, in the "Reserve Details" section, for example : * Name: reserve-volume1 Virtual Disk: 1 .... Preferred Controller: B * Owning Controller: B For advice on how to change the preferred and owning controller for any volume, see: Technical Instruction <Document: 1006464.1> Product Sun StorageTek 6540 Array Sun StorageTek 6140 Array Sun StorageTek 6130 Array Internal Comments For internal Sun use only. This document is result of escalation 1-19165982, where volumes used in a snapshot and volume copy combination were set to different preferred controllers, and so had different owning controllers. This resulted in the volume copy taking an extended time to run, during which many volume failovers were seen, and I/O performance to the base volume dropped to an unacceptably low level (2or 3 KB/s) 6130, 6140, 6540, volume copy, snapshot, controller, failover, preferred Previously Published As 87241 Change History Date: 2006-10-18 User Name: 31620 Action: Approved Comment: Verified Metadata - ok Verified Keywords - ok Verified still correct for audience - currently set to contract Audience left at contract as per FvF at http://kmo.central/howto/content/voyager-contributor-standards.html Checked review date - currently set to 2007-10-17 Checked for TM - ok as presented Publishing under the current publication rules of 18 Apr 2005: Version: 4 Attachments This solution has no attachment |
||||||||||||
|