Compact CPG Query

[ag3parug]

Hi,

I am going to run a CPG compact task and am curious about some of the terminology used in the GUI menu. Can anyone enlighten me as to what the following mean:

SA Space
SD Space
USR Space (I assume this to mean user space as in that we are using for servers)

[kk2491]

Hi sir,

Please find the details below:

There are three types of logical disk:
1. User (USR) logical disks provide user storage space to fully provisioned virtual volumes.
2. Shared data (SD) logical disks provide the storage space for snapshots, virtual copies, thin provisioned virtual volumes
(TPVV) or thin duplicated virtual volumes (TDVV).
3. Shared administration (SA) logical disks provide the storage space for snapshot and TPVV/TDVV administration

I believe this is useful.

Correct me if I'm wrong.


Regards,
KK

[ag3parug]

Hi kk2491,

Thank you for your swift reply

You may be right - I reached out to another person I know who has a 3PAR array and they came back with the following -

SA - Snapshot Administration - space used to track snapshot/administration data
SD - Snapshot Data - space used by snapshots
USR - Space for all user data, he seemed to think regardless of whether it was a TPVV or FPVV

I'm interested to hear if anyone else concurs with either of these or has an entirely different understanding

[kk2491]

Ok..

Thats great..

One more, you can refer the below doc.

http://h20195.www2.hp.com/v2/GetPDF.asp ... 987ENW.pdf

This gives u better clarity hopefully.

Regards,
KK

[Architect]

On the ld naming scheme:
SA is the administration space of the CPG, storing the volumes metadata.
SD space is used for TPVVs as wel as snap space. Deduped volumes are a special kind of TPVV, called "TDVV". Data is indeed saved in LDs with an "SD" naming scheme as well.
Full fat VVs are usually using LDs with the same name as the VV, except when the full VVs are part of an AO-set. The AO movement process aggregates the Volumes data in "SB" LDs in that case. Anyway, confusingly, only this fat volume space is referenced as USR space. Probably a remnants from time tpvvs did not exist yet.

[ag3parug]

OK so if I understand things correctly the only data in the USR space would be thick provisioned volumes?

Normal thin provisioned volumes would be in the SD space and if I follow what you say volumes that are part of an AO configuration also exist within the SD space?

Sorry if I'm being a bit slow - all so new to me!

[Architect]

No worries, we've all been there and i'm happy to explain and help

Simplified:
thin volumes and snaps store data in SD-space.
thick volumes store data in USR-space.
this is regardless of using AO.

[ag3parug]

Fantastic - thanks all