There are a few best practices when implementing a 3PAR into a vSphere environment. One of these is the creation of a custom PSP-rule. With this set, all 3PAR volumes are automatically configured according to best practices when they get mounted. In this post I will show ways to create this rule.
This post includes a lot of detailed information of HP 3PAR storage. Most of the stuff is also true for the new 8000 series. But this post is no introduction to 3PAR. You should know 3PAR terminology to get useful information out of this post.
- Multisite-Cluster always syncs synchronously.
- Gateway connection handles the control traffic
- Windows systems are connected to the node that holds the data. This because of the DSM driver.
- For VMware this feature is available for SanIQ >= 12.5 with necessary patch installed for vSphere 5.5 and later.
- Advantage of Multisite Cluster is that Gateway is always on local site.
- To be able to failover after a complete site failure at least nRAID-10 is necessary.
- Cluster Swap
- Create a new cluster using new nodes
- Present the new VIP to existing hosts
- Start Cluster Swap in CMC
- P4000 replicates data from existing cluster to new cluster
- after completing, traffic from hosts just accessing new cluster
- Adding new nodes to existing cluster
- Add new node to cluster, wait to complete re-striping
- Remove old node from cluster
- repeat until ever node is replaced
- When adding a new node, it is optimally the same as already used nodes in the cluster. Otherwise the used capacity of the new node will just be as the capacity of existing nodes.
- Queue size
- Acceptable queue size of disk is 2.
- Acceptable queue size of node = (number disks) * 2
- Acceptable queue size of cluster = (number disks) * (number of nodes) * 2
- When there is a high write rate in cluster presenting storage to Oracle database, check archiving protocol data when there is a very high write density.
With November 2015 public CAs do not issue new certificates that uses internal names or reserved IP addresses in
subjectAltName or in
commonName. Furthermore such certificates will be revoked on October 1st, 2016.
Internal names are hostnames that do not end with an Top Level Domain ending (.com, .de, …). For example: .local, .internal. Also NetBIOS names without any domain extension are affected.