vSphere 6.5

In this post, I will be installing and configuring vSphere Data Protection 6.1.8 in vCenter 6.5 Environment

first, login into the vCenter 6.5 web client (flash) and Deploy the ova template and select the VDP.ova file to deploy.

select_vdp_ova_file

ova_template_install_01

ova_template_install_02

ova_template_install_03

ova_template_install_04

ova_template_install_05 — Select the Storage (Datastore) you want to deploy this appliance in and click Next

ova_template_install_06 — Select the Network where you want to Deploy this appliance and click Next

ova_template_install_07 — Provide the Network details such as DNS servers, IP address, Subnet mask, the default gateway of the appliance and click Next

Check all the information entered and click finish for the VM to be deployed in the environment.

Once the appliance is deployed, power in ON

configure_vdp_01

Once the appliance is powered on, go to the web browser to https://Appliance_IP_Address_or_FQDN:8543/vdp-configure to start the configuration of VDP

configure_vdp_02 — In the Web UI, login as root and the default password is *changeme ,* login into the web UI and change the root password

configure_vdp_03

configure_vdp_04 — Check the Network settings as these settings will be automatically populated from the values you set while deploying the appliance

configure_vdp_05

configure_vdp_06 — Provide a new root password for the VDP appliance

vdp_vcenter_registration_01 — Once you enter the details of the External PSC under SSO FQDN you can hit ‘Test Connection’

vdp_vcenter_registration_02

configure_vdp_07 — We now create new storage as this is the first VDP appliance being deployed

configure_vdp_08

configure_vdp_09

configure_vdp_10

configure_vdp_11 — Click Yes to start the configuration

configure_vdp_12 — Once the process completes, the appliance will restart and you can get into the main Web UI

vdp_main_page

vdp_main_UI_vCenter_Home — This is the UI you see when you login into the vCenter Web Client and click on VDP menu item

Looks like VMware finally got around to have a public statement on the release of vSphere 6.5 and here are some of its main NEW features

vCenter Server Appliance

vCenter server appliance now has integrated Update Manager
vCenter server appliance now has its native High Availability
vCenter server appliance has better appliance management
vCenter server appliance now has native Backup/Restore

HTML-5 based vSphere web client

Security

VM-level disk encryption capability designed to protect against unauthorized access to data. (This is done using the vSphere storage policy framework)
Encrypted vMotion capability
vSphere 6.5 adds a secure boot to the hypervisor to protect both the hypervisor and guest operating system
Enhanced audit-quality logging capability to provide more information about user actions like who did what, when and where if you need to investigate your environment

Host Resource management

Enhanced Host profiles (updated graphical editor that is part of the vSphere Web Client now has an easy-to-use search function in addition to a new ability to mark individual configuration elements as favorites for quick access, Administrators now have the means to create a hierarchy of host profiles by taking advantage of the new ability to copy settings from one profile to one or many others)
Auto Deploy (Easier to manage in vSphere 6.5 with the introduction of a full-featured graphical interface. Administrators no longer need to use PowerCLI to create and manage deploy rules or custom ESXi images)
Proactive HA ( Proactive HA will detect hardware conditions of a host and allow you to evacuate the VMs before the issue causes an outage. Working in conjunction with participating hardware vendors, vCenter will plug into the hardware monitoring solution to receive the health status of the monitored components such as fans, memory, and power supplies. vSphere can then be configured to respond according to the failure)
vSphere HA Orchestrated Restart (vSphere 6.5 now allows creating dependency chains using VM-to-VM rules. These dependency rules are enforced if when vSphere HA is used to restart VMs from failed hosts. This is great for multi-tier applications that do not recover successfully unless they are restarted in a particular order. A common example to this is a database, app, and web server)
Additional Restart priority levels in HA (vSphere 6.5 adds two additional restart priority levels named Highest and Lowest providing five total. This provides even greater control when planning the recovery of virtual machines managed by vSphere HA)
Simplified vSphere HA Admission Control ( First major change is that the administrator simply needs to define the number of host failures to tolerate (FTT). Once the numbers of hosts are configured, vSphere HA will automatically calculate a percentage of resources to set aside by applying the “Percentage of Cluster Resources” admission control policy. As hosts are added or removed from the cluster, the percentage will be automatically recalculated, Additionally, the vSphere Web Client will issue a warning if vSphere HA detects a host failure would cause a reduction in VM performance based on the actual resource consumption, not only based on the configured reservations)
Fault Tolerance (FT) (vSphere 6.5 FT has more integration with DRS which will help make better placement decisions by ranking the hosts based on the available network bandwidth as well as recommending which datastore to place the secondary vmdk files, FT networks can now be configured to use multiple NICs to increase the overall bandwidth available for FT logging traffic)
DRS Advanced options (VM Distribution, Memory Metric for Load Balancing, CPU over-commitment have their own check boxes in DRS)
Network-Aware DRS (DRS now considers network utilization, DRS observes the Tx and Rx rates of the connected physical uplinks and avoids placing VMs on hosts that are greater than 80% utilized. DRS will not reactively balance the hosts solely based on network utilization, rather, it will use network utilization as an additional check to determine whether the currently selected host is suitable for the VM)