What’s New in vSphere 6.5: vCenter Server

Today VMware announced vSphere 6.5, which is one of the most feature rich releases of vSphere in quite some time. The vCenter Server Appliance is taking charge in this release with several new features which we’ll cover in this blog article. For starters, the installer has gotten an overhaul with a new modern look and feel. Users of both Linux and Mac will also be ecstatic since the installer is now supported on those platforms along with Microsoft Windows. If that wasn’t enough, the vCenter Server Appliance now has features that are exclusive such as:

  • Migration
  • Improved Appliance Management
  • VMware Update Manager
  • Native High Availability
  • Built-in Backup / Restore

We’ll also cover general improvements to vCenter Server 6.5 including the vSphere Web Client and the fully supported HTML5-based vSphere Client.

Migration

Getting to the vCenter Server Appliance is no longer an issue as the installer has a built in Migration Tool. This Migration Tool has several improvements over the recently released vSphere 6.0 Update 2m release. Now, Windows vCenter Server 5.5 and 6.0 are supported. If you’re currently running a Windows vCenter Server 6.0, this is your chance to get to the vCenter Server Appliance using this Migration Tool. In vSphere 6.5 there is an improvement in the migration tool which allows for more granular selection of migrated data as follows:

  • Configuration
  • Configuration, events, and tasks
  • Configuration, events, tasks, and performance metrics

migrationVMware Update Manager (VUM) is now part of the vCenter Server Appliance. This will be huge for customers who have been waiting to migrate to the vCenter Server Appliance without managing a separate Windows server for VUM.  If you’ve already migrated to the vCenter Server Appliance 6.0 the upgrade process will migrate your VUM baselines and updates to the vCenter Server Appliance 6.5.  During the migration process the vCenter configuration, inventory, and alarm data is migrated by default.

Improved Appliance Management

Another exclusive feature of the vCenter Server Appliance 6.5 is the improved appliance management capabilities. The vCenter Server Appliance Management Interface continues its evolution and exposes additional health and configurations. This simple user interface now shows Network and Database statistics, disk space, and health in addition to CPU and memory statistics which reduces the reliance on using a command line interface for simple monitoring and operational tasks.

app-mgmtvCenter Server High Availability

vCenter Server 6.5 has a new native high availability solution that is available exclusively for the vCenter Server Appliance. This solution consists of Active, Passive, and Witness nodes which are cloned from the existing vCenter Server. Failover within the vCenter HA cluster can occur when an entire node is lost (host failure for example) or when certain key services fail. For the initial release of vCenter HA an RTO of about 5 minutes is expected but may vary slightly depending on load, size, and capabilities of the underlying hardware.

vchaBackup and Restore

New in vCenter Server 6.5 is built-in backup and restore for the vCenter Server Appliance. This new out-of-the-box functionality enables customers to backup vCenter Server and Platform Services Controller appliances directly from the VAMI or API, and also backs up both VUM and Auto Deploy running embedded with the appliance. The backup consists of a set of files that will be streamed to a storage device of the customer’s choosing using SCP, HTTP(s), or FTP(s) protocols. This backup fully supports vCenter Server Appliances with embedded and external Platform Services Controllers. The Restore workflow is launched from the same ISO from which the vCenter Server Appliance (or PSC) was originally deployed or upgraded.

vSphere Web Client

From a User Interface perspective, probably the most used UI is the vSphere Web Client. This interface continues to be based on the Adobe Flex platform and requires Adobe Flash to use. However, VMware has continued to identify areas for improvement that will help improve the user experience until it is retired. Through several outreach efforts over the past year we’ve identified some high-value areas where we think customers are looking most for improvements. This small list of high-impact improvements will help with the overall user experience with the vSphere Web Client while development continues with the HTML5-based vSphere Client:

  • Inventory tree is the default view
  • Home screen reorganized
  • Renamed “Manage” tab to “Configure”
  • Removed “Related Objects” tab
  • Performance improvements (VM Rollup at 5000 instead of 50 VMs)
  • Live refresh for power states, tasks, and more!

web-clientvSphere Client

With vSphere 6.5 I’m excited to say that we have a fully supported version of the HTML5-based vSphere Client that will run alongside the vSphere Web Client. The vSphere Client is built right into vCenter Server 6.5 (both Windows and Appliance) and is enabled by default. While the vSphere Client doesn’t yet have full feature parity the team have prioritized many of the day to day tasks of administrators and continue to seek feedback on what’s missing that will enable customers to use it full time. The vSphere Web Client will continue to be accessible via “http://<vcenter_fqdn>/vsphere-client” while the vSphere Client will be reachable via “http://<vcenter_fqdn>/ui”. VMware will also be periodically updating the vSphere Client outside of the normal vCenter Server release cycle. To make sure it is easy and simple for customers to stay up to date the vSphere Client will be able to be updated without any effects to the rest of vCenter Server.

Now let’s take a look at some of the benefits to the new vSphere Client:

  • Clean, consistent UI built on VMware’s new Clarity UI standards (to be adopted across our portfolio)
  • Built on HTML5 so it is truly a cross-browser and cross-platform application
  • No browser plugins to install/manage
  • Integrated into vCenter Server for 6.5 and fully supported
  • Fully supports Enhanced Linked Mode
  • Users of the Fling have been extremely positive about its performance

h5-client

 

 

 

Source –  https://blogs.vmware.com/vsphere/2016/10/whats-new-in-vsphere-6-5-vcenter-server.html

 

 

 

Advertisements

Unable to re-configure replication for some VM’s

A few weeks ago I run into the problem where I have performed recovery of some virtual machines. After performing recovery deleted the VMs from the recovery site. But it wasn’t deleted from VR database

– Attempt to reconfigure replication from the primary site failed with the following error ”

Unable to configure replication for the virtual machine because the group cannot be created. Another virtual machine  has same instance UUID  already exists on protection site.

I did some workaround and didn’t find the solution. So after logged a complaint in Vmware support , here is the solution :

Setep-1  Took a backup of VR databases on both the sites. Following are the steps:

cd /opt/vmware/vpostgres/9.3/bin

./psql -U vrmsdb
Setep-2 – Took a snapshot of the appliances.

Step-3– Run this SQL Query on the primary site appliance. Zero rows retrieved.

SELECT a.group_movalue AS “PRIMARY GID”, b.name AS “virtual_machine Name”, ‘https://&#8217; || c.address || ‘:8043/mob/?moid=’ || a.group_movalue || ‘&vmodl=1’ AS “Link to Paste” FROM primaryvirtualmachineentity a, virtualmachineentity b, localserverentity c WHERE a.movalue = b.movalue ORDER BY name;

Step-4–   From SSH session to DR site replication appliance, cd to navigate to this directory:
cd /opt/vmware/vpostgres/9.3/bin

Step-5 Run this command to access the embedded database:

./psql -U vrmsdb

Step-5 Run this query on the remote VRMS to get the GID of the orphaned job and generate a URL to review it using the MOB:

SELECT a.group_movalue AS “SECONDARY GID”, b.name AS “VM Name”, ‘https://&#8217; || c.address || ‘:8043/mob/?moid=’ || a.group_movalue || ‘&vmodl=1’ AS “Link to Paste” FROM secondaryvirtualmachineentity a, virtualmachineentity b, localserverentity c WHERE a.movalue = b.movalue ORDER BY name;

Step-6– Copy the MOB URL you acquired from the database and paste in to your browser.

Step-7– Select the destroy method and click Invoke Method to remove the VRMS database entry related to the problematic replication job.

The orphaned job no longer exists in the VR UI and you can configure replication for the affected virtual machine as normal.

Affinity rules

An affinity rule is a setting that establishes a relationship between two or more VMware virtual machines (VMs) and hosts.

Affinity rules and anti-affinity rules tell the vSphere hypervisor platform to keep virtual entities together or separated. The rules, which can be applied as either required or preferred, help reduce traffic across networks and keep the virtual workload balanced on available hosts. If two virtual machines communicate frequently and should share a host, the VMware admin can create a VM-VM affinity rule to keep them together. Conversely, if two resource-hungry VMs would tax a host, an anti-affinity rule will keep those VMs from sharing a host. you can configure them using DRS.

Affinity rules and anti-affinity rules can be applied between VMs and hosts as well, and a VM can be subject to VM-VM affinity rules and VM-Host affinity rules at the same time. Affinity and anti-affinity rules in a vSphere environment can conflict with one another. For example, two VMs with an anti-affinity relationship may both be linked to a third VM via an affinity rule, but they cannot share a host. Optional affinity rule violation alarms can alert administrators to these events.