Veritas Disk Group Configuration Guidelines:-
1) Use multiple Disk Groups—preferably a minimum of four; place the DATA, REDO, TEMP, UNDO, and FRA archive logs in different (separate) Veritas Disk Groups
2) Optimally, use RAID 1 for tier 1 storage
3) Configure Disk Groups so that each contains LUNs of the same size and performance characteristics
Distribute Veritas Disk Group members over as many spindles as is practical for the site’s configuration and operational needs
Data Striping and Load Balancing:-
1) Veritas software level striping: layout=stripe ncols=10 stripeunit=128k
2) Storage-level striping further parallelizes the individual I/O requests within storage
3) Using the storage RAID protection, the amount of I/O traffic (host to storage) is reduced
4) EMC PowerPath should be used for load balancing and path failover
5) Use of metavolumes is optional
a) There is an upper limit on the number of LUNs that a host can address—typically ranging from 256 to 1,024 per HBA.
Volume Configuration with Veritas (Hypervolumes):
1) Created 5 Veritas Disk Groups
2) Five Disk Groups are used because this number provides better granularity for performance planning
3) The use of five Disk Groups also provides increased flexibility when planning for the utilization of EMC replication technology within the context of an enterprise-scale workload
4) Having five Disk Groups permits the placement of data onto different storage tiers if desired
| Hypervolume | Purpose | Size |
| 1 | DATA | 32 GB |
| 2 | REDO | 400 MB |
| 3 | DATA | 32 GB |
| 4 | FRA | 30 GB |
| 5 | TEMP | 10 GB |
| 6 | FRA | 30 GB |
Average Disk Utilization for Raid 1 should be below 150 IOPS per disk and should not go above 200 IOPS per disk as per below configuration.
-- 80 physical disks (40 mirrored pairs)
-- 240 devices visible to Veritas
Posts
