February 2019 – DTechinspiration

Here are some of the key highlights of this release:

Hyper-V Failover Cluster Support for Backup & Recovery

This version provides Backup and Recovery for the VMs residing in Hyper-V Failover Cluster. Even if the VMs running on Hyper-V cluster move from one host to another, the backups will continue to run without any interruption.

Shared VHDX Backup

Also, Vembu now extends its backup support to shared VHDX of Hyper-V.

Hyper-V Checksum Based Incremental

Vembu leverages CBT for performing incremental backups. With v4.0, Vembu brings in Checksum based incremental method to ensure that you have a seamless backup experience, even if the CBT happens to fail in some rare cases.

Credential Manager

The all-new credential manager will ease the management of hosts, VMs and physical machines. You don’t have to enter the credentials every time you need to backup a machine.

Let’s take a look at some of the enhancements made in this release:

1. Along with the added VMs, the disks that are newly added can also be backed up in the next successive incremental.

2. You can get a separate report for your Quick VM Recovery operations, which includes details like

VM Name

Recovery point

Start and end time

Target hypervisor

Status of recovery

3. While performing Live Recovery to VMware, you will be getting an option to configure specifications of the virtual hardware like

Socket & Core Counts

Memory

Hard disk provision type

Network adapter

4. Reconnection attempts will be made to continue the data transfer if a VMware or Hyper-V VM backup jobs get interrupted due to network failure

5. A new set of APIs has been released to give detailed reports on storage utilization like the size of the VM, storage space utilized by a backup job, compression rate etc.

Here is download link: Vembu

I ran into an issue and looking for help from VMWare and the first question from VMware is “What is the version of product” and i was in impression that it will expire next month. But when i checked it was already expired.

I am talking about:

1. vCenter Server 5.1

2. ESXi 5.1.0 3070626

3. Update Manager 5.1

4. SRM 5.1

5. Dell EqualLogic SAN (SRA 2.2)

6. VROPS 6.1

Note: Here is the link which is showing EOL or VMware Lifecycle Product Matrix.

Now the First recommendation is to upgrade to supported version.

Before Upgrading to supported version we have to check VMware compatibility matrix. As you can see we are running multiple VMware product and they are inter related and we have to update them in a sequence.

1. First Open the Update sequence for vSphere 6.0 and its compatible VMware products.

vCenter

vRA

VCM

ITBM

vRAS

vCD

VCNS

NSX

View

vCenter

vRO

VUM

vROPs/

VDP

vRealize

VIN

vCC

vRLI

BDE

SRM

ESXi

VMware

vShield/

vShield

View

SSO

Manager

Controllers

Composer

Connection

Server

vCOPs

Hyperic

Tools

NSX

App/

Endpoint/

Agent /

External

Server

Edge

NSX LFw

NSX

Client

Guest

IDS

Seq.

10*

Chart Credit: VMware

2. After identifying the sequence need to check VMware Product Interoperability Matrices. (Link)

3. Here is the Chart which we used to upgrade our environment.

Product	Current Version	Goal	Description

VMware vCenter Server	5.1.0 3070521	Appliance – 6.5	Current version
NSX for vSphere
VSAN
VMware vCenter Update Manager	5.1.0	Appliance – 6.5	Current Version
VMware ESX/ESXi	5.1.0 3070522	6.5	Two stage
SRM	5.1.2
SRA	2.2		Dell Equallogic PS Series SRA
vROPS	6.4.0

Product	Current Version	1	2	3	4	5	6	7	8	9	10	Result	Goal
vCloud Director
VMware vCenter Server	5.1.0 3070521	5.5 U3	6.0.0 U2 – External PSC	Need to do SRM Testing	6.0.0 U2a ->6.0.0 U3	6.5						6.5	Y
VMware vCenter Update Manager	5.1.0	5.5 U3	6.0.0 U2	Need to do SRM Testing	6.0.0 U2	6.5						6.5	Y
VMware ESX/ESXi	5.1.0 3070522	5.5 U3	6.0.0 U2	Need to do SRM Testing	6.0.0 U2	6.5						6.5	Y
VMWare SRM	5.1.2	5.5.1	6.0 V	Need to do SRM Testing	6.1.1	6.5						6.5	Y
Vmware SRA	2.2	2.2			2.3	2.3						2.3	Y
vROPs	6.4.0	6.6										6.6	Y