Sun Storage 9970 System
 
Sun Storage 9910 System
 
Sun Storage 9960 System
 
Sun Storage 9980 System
 

GCS>Sun Microsystems>Storage - Disk>Datacenter Disk
 

This infodoc gives a preview of the terminology and procedures associated with the Sun StorEdge[TM] 9910 and Sun StorEdge[TM] 9960 disk arrays. The StorEdge 9960 consists of one DKC (disk control frame) and at least one DKU (disk unit). However the SE9960 can consist of up to 6 DKU's; 3 to the left of the DKC and 3 to the right of the DKC. In the SE9960 a DKU contains 8 HDU s (hard disk unit). The StorEdge 9910 is one physical cabinet with 4 HDU's in the back. One HDU can contain up to 12 HDD 's (hard disk drives). A B4 is made up of 4 HDUs , which means that a DKU in an SE9960 has two B4 s and an SE9910 contains one B4 . A parity group consists of exactly 4 HDDs, in the same slot numbers, spread across each HDU in the same B4. So and HDU can be a part of 11 parity groups if there is a spare disk in the HDU, or 12 parity groups if there is no spare disk.

To configure the new parity group , we must:

1. Choose a Raid Level

2. Select the Drive Size

3. Select the Emulation [different emulations give different size LDEV s (logical device) and are good for certain specific OS on the host]

4. Assign a CU (control unit) and starting LDEV ID [ Note: There can be total of 16 CU s in a StorEdge99x0, 256 maximum LDEV s per CU , therefore up to 4096 total LDEV s ]

5. Map a LUN [This LUN would be the one that you would see as the drive on your host]

Remember: You can not mix different size drives and different raid levels within the same parity group .

Now that we know that how we can create a LUN from an LDEV , we would like to attach multiple LDEV s to create a bigger LUN . We can do this with what we call LUSE, or L ogical U nit S ize E xpansion.

The following are the LUSE guidelines:

Another tool like LUSE is CVS , or C ustom V olume S ize. CVS may also be seen with the name VLVI (virtual logical volume image) or Virtual LUN .

When we assign an emulation type to a parity group we have no control over the size of an LDEV , so usually we are left with some unused disk space in our parity group. CVS process is used to claim unused space mentioned above. CVS creates smaller LDEV to be used in DCR (dedicated cache residency). DCR is a permanently configured part of cache during installation which is dedicated to an assigned LDEV. Remember: cache keeps the data in read/write process while shared memory keeps the info about where the data is in cache. The amount of storage determines the cache you need and the cache you need determines the shared memory you would need. On the same lines, the number of CUs you have determines the cache/shared memory you need.

The following are some CVS guidelines:

Now that we have desired amount of LUN s we want, how about backups. S hadowimage is for within the system copies and TrueCopy is for across systems copy. Shadowimage may also be seen with the name HMRCF . Truecopy may be seen with the name HRC .

The following are some shadowimage guidelines:

This solution has no attachment