What needs to be considered when sizing a solution which will utilize HP 3PAR Snapshots?
A.
Additional host ports will be required
B.
Snapshots need to be written at 64k blocks
C.
Backend IOs will increase
D.
To ensure performance, additional system cache is used.
Explanation:
Module 4 page 82 mentions this specifically
Full and thin VVs are supported in sizes from 1 GB to 16 TB in 1 GB increments. Volume sets on HP 3PAR StoreServ systems allow up to 999 virtual volumes with the same characteristics to be created with only a few mouse clicks. Name and size are the minimum information required to create a virtual volume.
Volume templates with predefined characteristics allow the quick creation of similar VVs. The maximum number of Base VVs (Full or Thin provisioned) is 4096 on any HP 3PAR StoreServ.
The combined maximum number of volumes = number of Base volumes + Virtual Copies (snapshots) + Full Copies is 8192 the 7000 and 12288 on the 10000.
The maximum number of VLUNs per host is 16383, the maximum per system is 32768. The maximum number of CPGs per system is 2048. The maximum number of volumes per CPG is 8192 on the 7000 and 12288 on the 10000.
Volumes can be converted from full to thin and from thin to full provisioning without I/O interruption from within the Management Console or the CLI. In conjunction with Windows Server 2012, HP 3PAR StoreServ supports Offload Data Transfer (ODX) on Hyper-V 3.x.
CPGs with exactly the same characteristics but a different name can exist on a single system allowing you to group and easily identify volumes created for a particular workgroup in a company. Reporting tools like HP 3PAR System Reporter can summarize space usage per CPG for chargeback.
A solution using snapshots increases back-end I/O.
0
0