Sunday, 30 April 2017

VMware Cloud on AWS - Points to Remember

As we all know about the recent partnership between VMware and Amazon which brings us with VMware Cloud on AWS, there has been a lot of blogs / references,which are now official focussing towards Software Defined Data Center on Amazon Web Services

VMware Cloud on AWS – 10 Things we need to know



I was able to gather some key points from various sources which would be worth noticing for various environments, dedicated this article to link to the original post dedicated by me as Guest Blogger Vembu Technologies Blog which is a privately held, information technology company that specializes in developing software products inBackupDisaster Recovery and cloud storage domains.

Server / Storage / Network Virtualization with VMware

Last week I Got a chance to dedicate Guest Blog Post @ Vembu Technologies Blog which is a privately held, information technology company that specializes in developing software products in Backup, Disaster Recovery and cloud storage domains. Vembu’s products serve data center IT-Administrators in small and medium businesses managing VMware, Microsoft Hyper-V and Physical Server environments and was founded in 2002.

So thought of dedicating the blog post talking about the most important question which is asked from me when delivering various VMware Courses i.e the various Types of Virtualization, Dedicated this post to give a quick overview and providing the link Types Of Virtualization – Know the Difference to the original post dedicated at Vembu's Blog


VMware vSphere or Server Virtualization is something with which most of us are familiar and have been using the same in our environment for a very long time now, and I have also dedicated lots of blog posts mostly in Back to Basic Series talking about various feature set available to us in VMware vSphere, Here is the link if in case you missed it Back to Basics

Moreover Storage Virtualization with VMware vSAN was introduced by VMware with the release of VMware vSphere 5.5 and since then a lot of cool features has been added, I have dedicated couple of articles talking about VMware vSAN and also discussed about creating a vSAN Cluster in my Home Lab environment here are the links discussing about the same in case you missed it. VMware VSAN Overview & VMware VSAN is Up and Running Now @ Home Lab

Network Virtualization with VMware NSX we can remove the limits we have when working with VMware vSphere Networking, VMware NSX does that by using a different approach i.e VXLAN removing any trunking level dependency from the underlying Physical Network, I have dedicated couple of articles talking about NSX here are the links for your reference VMware NSX - Overview,Overview VMware NSX Distributed Firewall & An Insight to VMware NSX Layers

Tuesday, 25 April 2017

Back to Basics - Part 13 vCenter Server High Availability

In our last blog posts related to Back to Basics Series we discussed about Virtual Machine Files (Part1), Standard Switches (Part2), vCenter Server (Part 3),Templates (Part4) vApp (Part 5), Migration (Part 6),Cloning (Part 7), Host Profiles (Part 8), Virtual Volumes AKA VVOL's (Part 9) Fault Tolerance (Part10) ,Distributed Switches (Part 11) and Distributed Resource Scheduler Part 12 we also discussed about the various tasks related to building Home Lab Part1Part 2Part 3,Part 4 Part 5.

Dedicated this article to talk about an important feature that has been added in VMware vSphere 6.5 wherein the vCenter Server provides us the option to achieve high availability.



Image Source- VMware

vCenter Server high availability provides us protection against host and hardware failures and helps us to reduce the overall downtime required when patching the vCenter Server appliance which can be done using the <codeph>software-packages</codeph> utility available in the vCenter Server Appliance shell.

Before proceeding with the deployment of vCenter Server in High availability mode we need to ensure we are configuring the network well in advance for which we need to add a port group to each ESXi host, and add a virtual NIC to the vCenter Server Appliance.

When achieving the High Availability for vCenter Server each of the nodes plays an important part where in the active node runs the active vCenter Server appliance instance and communicates with other nodes over a dedicated HA network, passive node acts as a cloned copy of active node and becomes active in case of any failures detected for active node, the last node on our list is witness node which helps us to avoid any split brain scenarios.

During the configuration of High availability we get two options i.e Basic in which the vCenter HA wizard automatically creates and configures a second network adapter on the vCenter Server Appliance, clones the Active node, and configures the vCenter HA network, the next option which is advance option gives us more flexibility over basic option wherein we are responsible for adding a second NIC to the vCenter Server Appliance, cloning the Active node to the Passive and Witness nodes, and configuring the clones.


Sunday, 16 April 2017

Active Directory Integration - Nakivo Backup and Replication v7

We have already dedicated couple of articles related to Nakivo Backup and Replication v6.1 wherein we have seen the architectural components and also talked about new features available in Nakivo Backup and Replication v6.1 here is a link for your quick reference Demystifying Nakivo Backup and Replication v6.1

We also discussed about Backup/Recovery of Active Directory Objects with Nakivo Backup and Replication v6.1 in case you missed it here is the link for your quick reference Backup/Recover Active Directory Objects with Nakivo

Apart from testing the backup and recovery related functionalities using Nakivo Backup and Replication v6.1 we also had a detailed discussion on Replicating Virtual Machines here is the link for your reference Replicate VM's with Nakivo Backup & Replication

We also talked about working with Nakivo Backup and replication appliance and what's new withNakivo Backup and replication 6.2 which was announced by NAKIVO on october 13th 2016 which help us by providing backupreplication, and recovery of paid EC2 instances sold through AWS Marketplace we also discussed about What's New - Nakivo Backup and Replication v7 Part 1 wherein we have seen some highlights about Hyper-v support which has been added for Hyper-v 2016 and 2012 with Nakivo v7.

In Our last article related to Nakivo Backup and Replication series we discussed about 

It's time to test out one of the feature that we discussed in our last posts, the feature which I will be talking about is Active Directory Integration this is one of the important feature we look forward too,when it comes to production environment, with NAKIVO Backup & Replication we can easily integrate Microsoft Active Directory and map Active Directory groups to NAKIVO Backup & Replication user roles, which will allow domain users to log in to NAKVIO Backup & Replication using their domain credentials.
When it comes to integration the steps are pretty straightforward wherein I created a test user Backup Admin in Active Directory and added this user to a group Backupusers.
Login to Nakivo backup and Replication console as an administrator and look for the options of User Accounts and edit the properties of the same.
The AD integration option is disabled by default we can enable the option by specifying domain name and the name of the group that belongs to our active directory and click test integration.
Test Integration option will ask to specify the details including domain user login and the credentials, once the test is successful we can log out as an administrator and login as the AD user.

Try Nakivo Backup and Replication v7 

Tuesday, 4 April 2017

Cannot run upgrade scripts on ESXi Host

Recently was given some tasks to upgrade few ESXi boxes (UCS-B200-M3) running with ESXi 5.0 update 3, to ESXi 5.5 Update 2 . As part of the process migrated some Monster Virtual Machines to neighbor ESXi boxes and put the host in the maintenance mode which made DRS to kick in and migrate remaining Virtual Machines to other host in the cluster.

Second thing on the list was to create a baseline and attached the baseline to the ESXi host, and proceed with remediation, initially it looked as if the host is being remediated properly until it was 92 percent completed and I saw the status of the host was still showing as ESXi5.0 Update 2, so thought of checking the tasks and events and was able to see something error. “Cannot run upgrade scripts on the Host”.

As part of initial troubleshooting I searched for KB article 2007163 which talks about the same issue so started following the steps in Kb article to locate the log files and any error in the log files, as suggested in the Kb article.

After connecting to my ESXi box using putty was not able to find any entries similar to below in the /var/log/vua.log file, :

OSError: [Errno 39] Directory not empty: /bootbank/state.XXXXXXX (where XXXXXXX is a number)

However was able to see some strange error messages “This Application is Not using Quick Exit ()” The Exit code will be set to 0.@ bora/vim/lib/vmacore/main/service.cpp

So started search for some more references to troubleshoot this issue and was able to find some references which talks about the FDM agent uninstallation and then remediating ESXi hosts.

Followed below steps to further troubleshoot this issue by uninstalling the FDM agent, as suggested in KB article 2012323 and then rebooting the ESXi host, Remediating and Exit the maintenance mode.

1 # cp /opt/vmware/uninstallers/VMware-fdm-uninstall.sh /tmp
2 # chmod +x /tmp/VMware-fdm-uninstall.sh
3 # /tmp/VMware-fdm-uninstall.sh

** Configuration shown above worked in my environment kindly raise a support request if you are also facing similar issue and unable to resolve with the help of KB articles