CLIĬonnect to the 3PAR using your SSH client of choice. It is also possible to grow a VV using the management console GUI. To grow the virtual volume I used the growvv command while connected to the 3PAR CLI. The virtual volume in question was not part of a remote copy group, it exists purely for VMs that are to remain bound to a specific datacenter and never move between DCs. Array separates them out, and processes data in ASIC, and processes metadata/SCSI commands in Control processor.One of the virtual volumes used in a Microsoft Failover Cluster was almost full (~43MB space left) therefore we needed to grow the virtual volume (VV) to prevent downtime or should I say minimise as some VMs were already in a paused state due to insufficient disk space. To any host on a specific port: This is useful when the hosts (or WWNs) are not known prior to exportingĮach IO received has data and metadata such as SCSI control commands. This is a convenient way to export VVs to known hosts. To specific hosts: The VV is visible to the specified WWNs, regardless of which port(s) those WWNs appear on. Hosts can access VVs only after they have been exported as VLUNs. TDVVs are supported only on CPGs that use SSDs as a tier of storage. Thinly deduped VV (TDVV): Behave similarly to TPVV with the fundamental difference that TDVVs within the same CPG will share common pages of data. On creation, 256MB per node is allocated to a TPVV. Thinly Provisioned VV (TPVV): It has space for base volume allocated from the associated CPG, and snapshot space allocated from snapshot CPG if any. Uses SA LD.įully Provisioned VV (FPVV): It is a thick device with no snapshots.Ĭommonly Provisioned VV (CPVV): It is a thick device with snapshots. Snapshot admin space: Contains metadata for snapshots. The granularity of snapshot data mapping is 16KB pages. Snapshot data space: Contains modified data for a given snapshot. User Space: Contains data of the base VV. Snapshot volumes: As the name suggests, it is a snapshot volume and contains modified data for a given snapshot. Storage space (regions) to Virtual volumes (VV)from CPG’s logical disk pool.īase volumes: It is a fully provisioned virtual volume/TPVV/TDVV. Step size: Number of bytes that are stored contiguously on a single PDĮvery node creates LDs from the PDs it owns, thus chunklets from any given PD are owned by a single node with the partner node as the backup owner.Ĭommon Provisioning Groups (CPG) is a virtual pool of same typed LDs. Eg: a RAID5 LD with a row size of 2 and set size of 4 is effectively striped across 8 drives. Row size: Level of additional striping across more drives. Set size: Number of drives containing data. Snapshot Administration LD (SA LD) provide the storage space for metadata used for snapshot/TPVV/TDVV.ģPAR OS will automatically create LDs based upon parameters listed below:įor RAID5 (2 Multiple distributed Parity) Snapshot data LD (SD LD) provide the storage space for snapshots (or virtual copies), TPVV, TDVV. User LD (USR LD) provide user storage space to VVs. A single LD can have its multiple regions assigned to different servers. These regions are assigned to Virtual Volumes (VVs) which in turn are masked to the server. LD is further subdivided into 128MB regions. LD will consist of chunklets from same type of disk drives (either 7.5K/10k/15K/SSD etc). Depending upon RAID level specified, LDs are formed by striping across chunklets from number of physical drives across different enclosures. Raid functionality is implemented at Logical disks (LD) level. These spare chunklets are distributed across all drives. 3PAR OS reserves a certain number of chunklets as space chunklets depending on the sparing algorithm and system configuration. Physical disks (PD) are carved up in 1GB chunklets.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |