Table of Contents
Protectier TS7650G best practice with v7000 - v5000
v5000 - v7000 design
Create only two storage pools (also known as managed disk groups), where one is used for metadata and the other is used for user data. Creating more pools causes the storage system cache to be segmented among all pools. By having only two pools, you optimize the storage subsystem cache allocation.
Use the sequential virtualization type for each MDisk rather than striped virtualization. Because of the nature of ProtecTIER file system architecture and workload, sequential virtualization shows better performance than striped.
Important: Always use RAID 6 in combination with Serial Advanced Technology Attachment (SATA) or near-line serial-attached SCSI (NL-SAS) drives.
LUN management: Starting with ProtecTIER Version 3.2, the management of LUNs greater than 8 terabytes (TB) is improved. When ProtecTIER V3.2 and later works with LUNs greater than 8 TB, it splits them in to logical volumes of smaller size. Therefore, you can work with LUNs greater than 8 TB, but there is no benefit in performance in completing this action.
Meta Data
Use balanced RAID 10 groups for metadata MDisks (use a layout according to your planning requirements) with at least 4+4 members.
Create a single pool for metadata that contains all the metadata MDisks. Specify an extent size default of 256 MB for each metadata volume created. For each metadata MDisk, create a single metadata (MD) volume to accommodate the full size of each metadata MDisk, by using the sequential virtualization type. Quorum volume: The 1 gigabyte (GB) MD quorum volume can be created on any metadata MDisk.
User Data
Use RAID for data protection and performance. The RAID type depends on the disk category, but is usually RAID 5 or RAID 6. Do not share the user data pool with the metadata pool. Create a single pool for user data that contains all the user data MDisks. Specify an extent size default of 256 MB for each user data volume that is created. For each user data MDisk, create a single user data (UD) VDisk/volume to accommodate the full size of each user data MDisk by using the sequential virtualization type. The size of UD volumes must be consistent. All UD volumes should be the same size.
# mkmdiskgrp -ext 256 -warning 100% -name UD_pool # mkmdiskgrp -ext 256 -warning 100% -name MD_pool # svctask mkarray -drive 28:27:26:25 -level raid5 -sparegoal 0 -strip 128 UD_pool # svctask mkarray -drive 8:6:5:10 -level raid10 -sparegoal 0 -strip 128 MD_pool # svctask mkvdisk -name UDvol1 -mdiskgrp UD_pool -iogrp io_grp0 -mdisk mdisk7 -size 1284864 -unit mb -vtype seq # svctask mkvdisk -name UDvol3 -mdiskgrp UD_pool -iogrp io_grp0 -mdisk mdisk8 -size 1286144 -unit mb -vtype seq
