This post is about two cool and powerful products: VMware vRealize Operations Manger (vROPs) and HPE Primers/3PAR and how to combine them. This post includes current versions of both. Good and a bad news about costs: Bad first: vROPs free for a short period of time as trial. Good one: HPE Plug-In is free! Version 3.7 of HPE Storage Plug-ins for VMware is the first […]
A new – and badly documented – feature in StoreServ Management Console 3.6 is Topology Insights. Sounds first like the probably known Maps. But Topology View shows an end-to-end view: VM <–> VMDK <–> Datastore <–> Host <–> Virtual Volume <–> System. Enriched with performance-information! This short post is about this feature and how to get it.
Normally when using a self-signed certificate you get a warning. It is also normal to accept the certificate to continue your task. These days I wanted to register a 3PAR system as storage provider in vCenter. Because of a certification error, this could not be accomplished. In this post I describe how to solve – at least my – problem.
Recently I had a strange behavior when creating 3PAR snapshots in Veeam Backup&Replication after a site-failover (Peer-Persistence) occurred. Snapshot-jobs stop with error, backup-jobs using 3PAR integrated snapshots jobs are still running because they failed over to NBD. Snapshot-jobs were configured using secondary 3PAR for snapshots too – see more information here. Management console showed the following error for snapshot-jobs: VM VM name does not meet […]
Recently I had problems to connect a 3PAR system to a quorum appliance. Quorum is needed in a Peer Persistence configuration. The system had a connection to the quorum. After HPE support did replace a node, connection could not be established any more. Command showcropy -qw shows error “below min safe num QAs” and other errors talking about QAs. In SSMC quorum was stated as […]
Recently I upgraded a new 3PAR from 3.2.2 MU6 to 3.3.1 MU3. Even during the upgrade I could use me putty to run commands in 3PAR console. After the upgrade process activated 3.3.1 MU3, no putty session could be established any more. When trying to connect, the error appears: Network error: Software caused connection abort It turned out this is because no older TLS version […]
When initialize a new 3PAR, depending on your protection level, at least the size of one disk per disk-type will be reserved as spare. Also when you add disks to a running system, spare-chunklets are created. This is done by admithw. For example when you initialize a system containing 2 SSDs for adaptive flash cache (AFC) the size of one SSD is reserved for spare. […]
FC AFA (all flash array) 3PAR systems show quite a good latency on reads and writes. When operating an iSCSI AFA 3PAR it could happen that the systems show a rather high write latency on ESXi hosts. In this post you can read how to fix this.
In a 3PAR Peer Persistence configuration volumes are synchronously replicated between two 3PAR arrays. For each volume one array acts as primary or source array. This array exports the volume for read/write. The other array acts as secondary or target for replication. For performance reasons it could be an advantage when backup reads data from target array. This is easily possible with Veeam B&R 9.5.
In a 3PAR system it is best practice that setsize defined in CPG is a divisor of the number of disks in the CPG. The setsize defines basically the size of a sub-RAID within the CPG. For example a setsize of 8 in a RAID 5 means a sub-RAID uses 7 data and one parity disk.