Update VCSA 6.5 with selected version

When you currently try to update your vCenter Service Appliance (VCSA) 6.5 in Virtual Appliance Management Interface (VAMI) (Port 5480) your only suggestion is Update 2. A new feature of VCSA 6.7 is the ability to select the update you want to install. In 6.5 the latest update will be installed when using default repository.

vSphere 6.5 U2 is a very uncommon update-version. First, there are not just fixes and updates in U2 but also new features (see here) that are also available in vSphere 6.7. Second, U2 gets available after 6.7, so it is not possible to upgrade 6.5 U2 to 6.7 GA. Therefore updating to U2 should be well considered.

What are your options to stay within a Update version respectively select your update version?

Continue reading “Update VCSA 6.5 with selected version”

Advertisements
Update VCSA 6.5 with selected version

vROps – Intelligent Workload Placement

There is not very much information out there for the new feature Intelligent Workload Placement in vROps 6.1 and its improvements in 6.2. In this post there are some information that should help to understand what this feature does.

Continue reading “vROps – Intelligent Workload Placement”

vROps – Intelligent Workload Placement

Some basic stuff about HP P4000

Multisite Cluster

  • 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.

Migrate Data

  • 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

General information

  • 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.
Some basic stuff about HP P4000