Category Archives: vSphere 6

Getting STARTED with VMWARE INTEGRATED OPENSTACK (VIO) – PART 2

VMware Integrated OpenStack (VIO) is an OpenStack distribution that is built and tested by VMware. VIO is compliant with the OpenStack Foundation guidelines for an OpenStack distribution and is API-compatible for all OpenStack services running on enterprise level virtual infrastructure.VMware ensures platform stability by rigorous testing and ensuring interoperability. VIO leverages vSphere, NSX, and storage functionality as core of infrastructure. VMware places priority on packing OpenStack core projects in the most stable manner through relentless testing (functional and interoperability).

VMware Integrated OpenStack provides the following key features:
• Fastest deployment with simple installation using an OVA file
• Simplified operations through API and web interface
• Distributed Resource Scheduler (DRS) and Storage DRS for workload    rebalancing and datastore load balancing
• vSphere high availability (HA) to protect and automatically restart workloads
• In-house expertise and skillset with existing vSphere technology
• Runs on the proven VMware software-defined data center
• Production-ready container management that is natively integrated by using VMware capabilities.

• Advanced networking functionality through NSX 

• Integration with vRealize Operations Manager and vRealize Log Insight for greater performance and capacity management, Alerting and troubleshooting.  
• Trusted and single vendor for infrastructure and OpenStack
• Compliant with the OpenStack Foundation’s 2019.11 interoperability guideline

OpenStack Model

The OpenStack model is comprised of core projects and supplement projects. In addition to the core OpenStack projects, customer can choose supplement projects for additional services and functionality based on their requirements.

VMware Integrated OpenStack Components

VMware Integrated OpenStack (VIO) is made by two main building blocks, first the VIO Manager and second OpenStack components. VIO is packaged as an OVA file that contains the VIO Manager server and an Ubuntu Linux virtual machine to be used as the template for the different OpenStack components.

VMware Integrated OpenStack is designed to run over vSphere and NSX-T Data Center, leveraging existing virtualization functionality to provide security, stability, performance, and reliability.

Plug-in drivers are available in Nova for interaction with vCenter Server  and in Neutron to interact with NSX-T Data Center (or vSphere Distributed Switch). Glance and Cinder interact with storage through the vCenter Server system and the OpenStack plug-in driver.

VMware Integrated OpenStack and the VMware SDDC Integration 

VMware Integrated OpenStack (VIO) provides full-stack integration with VMware Software-Defined Data Center (SDDC), which provides customer to have one-stop-shop enterprise grade OpenStack solutions.

Stay tuned for VMware Integrated OpenStack (VIO) – PART 3, In Part 3 will discuss more on VMware Integrated OpenStack (VIO) Deployment !!

 

Why VMware Integrated OpenStack (VIO) – Part 1

Time to move out from comfort zone, explore and deep dive into OpenStack, Specially VMware Integrated OpenStack (VIO), vSphere with Kubernetes, VMware Tanzu Kubernetes Grid (TKG), and VMware Tanzu Kubernetes Grid Integrated (TKGI) (formerly known as VMware Enterprise PKS).

Let’s Start with VMware Integrated OpenStack (VIO)?

VMware Integrated OpenStack (VIO) is a VMware supported enterprise grade OpenStack distribution that makes it easy to run OpenStack cloud on top of VMware virtualization technologies. With VIO, customers can rapidly build production-grade private and public OpenStack clouds on top of VMware technologies, leveraging their existing VMware investment and expertise.

VMware Integrated OpenStack is ideal for many different use cases, including building a IaaS platform, providing standard, OpenStack API access to developers, leveraging edge computing and deploying NFV services on OpenStack.

VMware Integrated OpenStack (VIO) can be deployed and run on your existing vSphere, NSX-T, and vSAN and simplify operations and offering better performance and stability.

VMware Integrated OpenStack (VIO) Architecture

The VMware Integrated OpenStack (VIO) connects vSphere resources to the OpenStack Compute, Networking, Block Storage, Image Service, Identity Service, and Orchestration components.

VMware Integrated OpenStack is design and implemented as separate management and compute clusters. The management cluster contains OpenStack components and compute cluster runs tenant or application workloads.

VMware Integrated OpenStack (VIO) core components are :-

Nova (compute) – Compute clusters in vSphere are used as Nova compute nodes. Nova Provides a way to provision compute instances (aka virtual servers) in these clusters.

Neutron (networking) – Neutron allows you to create and attach network interface devices managed by OpenStack. Neutron provides networking functions by communicating with the NSX Manager (for
NSX-T Data Center deployment) or with vCenter Server (for VDS-only deployments).

Cinder (block storage) – Cinder designed to create and manage a service that provides persistent data storage to applications. Cinder executes block volume operations through the VMDK driver, causing the desired
volumes to be created in vSphere.

Glance (image service) – Glance enables users to discover, register, and retrieve virtual machine images through the Image service in a variety of locations, from simple file systems to object-storage systems  like OpenStack Object Storage. Glance images are stored and cached in a dedicated image service datastore when the virtual machines that use them are booted.

Keystone (identity management) – Authentication and authorization in OpenStack are managed by Keystone.

Heat (orchestration) – Heat provides orchestration service to orchestrate composite cloud applications through an OpenStack API call.

Ceilometer (telemetry) – Telemetry collect data on the utilization of the physical and virtual resources comprising deployed clouds, persist these data for subsequent retrieval and analysis, and trigger actions when defined criteria are met.

VMware also provides simplified OpenStack operations with vRealize Operations Manager (vROps) integrations for performance monitoring, capacity planning and troubleshooting. And vRealize Log Insight (vRLI) for diagnostics across OpenStack service logs.

Stay tuned for VMware Integrated OpenStack (VIO) – PART 2 !!

 

vCenter Architecture Changes in vSphere 6.0 and Deploying VCSA 6.0 – Part 3

This is Part 3 of vCenter Architecture Changes in vSphere 6.0 and Deploying vCenter 6. In vCenter Architecture Changes in vSphere 6.0 and Deploying vCenter 6 – Part 1. We have discussed vCenter Architecture Changes in vSphere 6.0vCenter Deployment Modes and how to install Windows-based vCenter Server with an Embedded Platform Services Controller.

In vCenter Architecture Changes in vSphere 6.0 and Deploying VCSA 6 – Part 2 we have discussed how to deploy VCSA 6.0 with an Embedded Platform Services Controller.

Here in vCenter Architecture Changes in vSphere 6.0 and Deploying VCSA 6.0 – Part 3 we’ll discuss how to deploy VCSA 6.0 with an External Platform Services Controller.

To deploy vCenter Server 6.0 with an External Platform Services Controller, We need to deploy PSC (Platform Services Controller) first and then Install vCenter Server. So let’s start and deploy  PSC (Platform Services Controller).

External PSC (Platform Services Controller) deployment using VCSA 6.0 :- 

1. Login to any Windows Server and Copy/Mount the ISO image to start the deployment.

2. We can start VCSA deployment by Double-Clicking ‘vcsa-setup.html’ file. If you have not installed VMware-ClientIntegrationPlugin-6.0 on this server need to install VMware-ClientIntegrationPlugin-6.0 before starting the deployment of VCSA 6.0.

vc10

3. Click ‘Install’ to start the vCenter Server Appliance 6.0 deployment..

evc1

4. On the ‘End User Licence Agreement’ window select ‘Accept the License Agreement’ and Click Next

evc2

5. On the ‘Connect to the target Server’ window, Enter the ESXi host Name or IP address on which want to deploy the PSC (Platform Services Controller) Appliance. Enter root password of the ESXi host and Click ‘Next’

Note:- Make Sure ‘Lock down mode is Disabled’ on the ESXi host and NTP is configured and there is time synchronization between ESXi host and the NTP server.

evc3

6. On the ‘Certificate Warning’ Window click ‘YES’ to accept and continue with deployment.

evc4

7. On the ‘Set up Virtual Machine’ window Enter the Appliance Name and root password for the Appliance and Click ‘Next’

evc5

8. On the ‘Select deployment type’ window select ‘Install Platform Services Controller’ under External Platform Services Controller and click ‘Next’

vc16

9. On the ‘Set up Single Sign-On (SSO)’ window select ‘Create a new SSO domain’, Enter SSO Administrator password, SSO Domain Name and SSO site Name and Click ‘Next’

vc17

10. On the ‘Select Appliance Size’ window click ‘Next’ to continue,

Note :- There is no option to select PSC appliance size, this will deploy an external Platform Services Controller VM with 2 vCPU and 2GB of memory and requires 30 GB of disk space.

vc18

11. On the ‘Select datastore’ window select the datastore to store the PSC  (we can Enable Thin Disk Mode by checking the Enable This Disk Mode check box, but for production recommendation is to           deploy ‘Thick Disk Mode’) and click ‘Next’

vc19

12. On the ‘Network Settings’ Window Enter the PSC appliance IP address, PSC Name, Subnet Mask, Network Gateway, DNS Server, and NTP server settings and Click ‘Next’

vc20_1

13. On the ‘Ready to Complete’ window Review the settings and Click ‘Finish’ to start the deployment . vc21_1

14. It will take 15-20 Minutes to download and deploy appliance, configure machine, and complete setup.

vc22

vc23

vc23_1

15. Here we go ‘Installation of Platform Services Controller completed successfully’. You can see on below screen that now we are ready to Run installer to install ‘vCenter Server’ and connect to this Platform Services Controller by using 192.168.201.131.

vc23_2

We have deployed PSC (Platform Services Controller) and now need to Run the Installer again to Install vCenter Server deployment:-

External vCenter Server deployment using VCSA 6.0 :-

1. Again start VCSA deployment by Double-Clicking ‘vcsa-setup.html’ file.

vc10

2. Click ‘Install’ to start the vCenter Server Appliance 6.0 deployment.

vc11

3. On the ‘End User Licence Agreement’ window select ‘Accept the License Agreement’ and Click Next

vc12

4. On the ‘Connect to the target Server’ window, Enter the ESXi host Name or IP address on which want to deploy the vCenter Server Appliance. Enter root password of the ESXi host and Click ‘Next’

Note:- Make Sure ‘Lock down mode is Disabled’ on the ESXi host and NTP is configured and there is time synchronization between ESXi host and the NTP server.

evc3

5. On the ‘Certificate Warning’ Window click ‘YES’ to accept and continue with deployment.

evc4

6. On the ‘Setup Virtual Machine’ window Enter the vCenter server Virtual Machine Name and root password for the Appliance and Click ‘Next’

evc5

7. On the ‘Select deployment type’ window select ‘Install vCenter Server (Requires External Platform Services Controller’ under External Platform Services Controller and click ‘Next’

evc6

8. On the ‘Configure Single Sign-On (SSO)’ window Enter Platform Services Controller FQDN or IP Address, Enter SSO Administrator password and Click ‘Next’

evc7

9. on the ‘Select Appliance Size’ window select the Appliance size Tiny, Small, Medium and Large depending on the number of ESXi Hosts and VMs this vCenter Server will be Managing and Click ‘Next’

evc8

10. On the ‘Select datastore’ window select the datastore to store the VM configuration files and all of the Virtual Disks.  (we can Enable Thin Disk Mode by checking the Enable This Disk Mode check box, but for production recommendation is to deploy ‘Thick Disk Mode’) and click ‘Next’

evc9

11. On the ‘Configure Database’ window select the desired database type and click ‘Next’

Note :- vCenter Server Appliance can use either embedded PostgreSQL database, which is recommended, or an external database include Oracle Database 11g and Oracle Database 12c. Unlike Windows                     support for PostgreSQL, vCenter Server Appliance supports up to 1,000 hosts or 10,000 virtual machines at full vCenter Server scale. External database support is being deprecated; this is the last                          release that supports the use of an external database with vCenter Server Appliance.

evc10

12. On the ‘Network Settings’ Window Enter the vCenter Server appliance IP address, vCenter Server Name, Subnet Mask, Gateway, DNS Server, and NTP server settings and Click ‘Next’

evc11

13. On the ‘Ready to Complete’ window Review the settings and Click ‘Finish’ to start the deployment.

evc12

14.  It will take 15-20 Minutes to download and deploy appliance, configure machine, and complete setup.

evc13

evc14

15. Here we go ‘Installation of vCenter Server completed successfully’. You can see on below screen that Installation Completed and ready to use.  Start using vSphere web client :- https://192.168.201.132/vsphere-client as SSO administrator (administrator@vsphere.local)

evc15

16. We can connect to ESXi host directly using VI Client and see both VMs (Platform Services Controller and vCenter Server) are up and running and ready to use.evc16That’s it for now Stay tuned for next topic 🙂

Until then Share & Spread The Knowledge !!!!

vCenter Architecture Changes in vSphere 6.0 and Deploying VCSA 6.0 – Part 2

In my last blog vCenter Architecture Changes in vSphere 6.0 and Deploying vCenter 6 – Part 1  We have discussed about Architectural changes in vSphere 6.0. Also we have discussed vCenter Deployment Modes (vCenter Server with an Embedded Platform Services Controller and vCenter Server with an External Platform Services Controller). We have discussed how to install Windows-based vCenter Server with an Embedded Platform Services Controller.

In this vCenter Architecture Changes in vSphere 6.0 and Deploying VCSA 6 – Part 2 will discuss how to deploy VCSA 6.0 with an Embedded Platform Services Controller.

VCSA 6.0 deployment :-

1. Download the VCSA installer from VMware website and Copy/Mount the ISO image to any Windows PC to start the deployment.

vc102. Before starting VCSA deployment we need to Install VMware client integration plug-in.

vc13. Best part is that VMware-Client Integration Plugin is part of VCSA installer, Browse the VCSA folder and Double Click VMware-ClientIntegrationPlugin-6.0.0 to start the installation.

vc24. It is pretty simple Windows Installation process. Just follow the screen to complete the VMware-Client Integration Plugin Installation.vc35. On the ‘Welcome to the Installation wizard for the VMware Client Integration Plug-in 6.0.0’ window click ‘Next’

vc46. On the ‘End-User License Agreement’ window ‘Accept the License Agreement’ and Click ‘Next’

vc5

7. On the ‘Destination Folder’ Window change the folder if required or click ‘Next’vc6

8. On the ‘Ready to Install the Plug-in’ window click ‘Install’ to start the Installation.

vc7

9. it will take 1-2 minutes to finish the installation.

vc8

10. Here we go ‘Installation Completed’ Click ‘Finish’ to close the window.

vc9

11. Once we have Finished VMware Client Integration Plug-in installation, We can start VCSA deployment by Double-Clicking ‘vcsa-setup.html’ file.

vc10  12. Click ‘Install’ to start the Deployment.

vc11

13. ‘Accept the License Agreement’ and Click ‘Next’

vc12

14. On the ‘Connect to the target Server’ window, Enter the ESXi host Name or IP address on which want to deploy the vCenter Server Appliance. Enter root password of the ESXi host and Click ‘Next’

Note:- Make Sure ‘lock down mode is Disabled’ on the ESXi host and NTP is configured and there is time synchronization between ESXi host and the NTP server.

vc13

15. On the ‘Certificate Warning’ Window click ‘YES’ to accept and continue with deployment.

vc14

16. On the ‘Setup Virtual Machine’ window Enter the VM name and root password for the Appliance and Click ‘Next’

vc15_1

17. On the ‘Select deployment type’ window select ‘ Install vCenter Server with an Embedded Platform Services Controller’ under Embedded Platform Services Controller and click ‘Next’

VCE1

18. On the ‘Set up Single Sign-On’ window select ‘Create a new SSO domain’, Enter SSO Administrator password, SSO Domain Name and SSO site name and Click ‘Next’

VCE2

19. On the ‘Select Appliance Size’ window select the appliance size as per size of the Infrastructure going to be managed by the vCenter Server, for the demo purpose i am choosing here ‘Tiny (Up to 10 hosts,             100 VMs)’. You can see that this will deploy a tiny VM configured with 2 vCPUs and 8 GB of Memory and requires 120 GB of disk size.

VCE3

20.  On the ‘Select datastore’ window select the datastore to store the vCenter Server (we can Enable Thin Disk Mode by checking the Enable This Disk Mode check box, but for production recommendation is to           deploy ‘Thick Disk Mode’) and click ‘Next’

vce4

21. On the ‘Configure Database’ window select the desired database type and click ‘Next’

vCenter Server Appliance can use either embedded PostgreSQL database, which is recommended, or an external database include Oracle Database 11g and Oracle Database 12c. Unlike Windows support           for PostgreSQL, vCenter Server Appliance supports up to 1,000 hosts or 10,000 virtual machines at full vCenter Server scale. External database support is being deprecated; this is the last release that                   supports the use of an external database with vCenter Server Appliance.

vce5

22. On the ‘Network Settings’ Window Enter the vCenter Server appliance IP address, Subnet Mask, Gateway, DNS Server, and NTP server settings and Click ‘Next’

VCE6

23. On the ‘Ready to Complete’ window Review the settings and Click ‘Finish’ to start the deployment

vce7

24. It will take several minutes to finish the deployment.

vc22

vc23

25.  Here we go Installation of vCenter Server is successfully completed and ready for use. We can access vSphere Web Client using https://<IP address>/vsphere-client and login as SSO Administrator                credentials.

vce10

26. That’s it. We can connect to vCenter Server and start using and configuring.

VCE11

That’s it 🙂 We have discussed in this part 2 how to deploy VCSA 6.0 with an Embedded Platform Services Controller. In the next part vCenter Architecture Changes in vSphere 6.0 and Deploying VCSA 6.0 – Part 3, Will discuss how to deploy VCSA 6.0 with an External Platform Services Controller. Until then please stay tuned and Keep Spreading the knowledge 🙂

 

vCenter Architecture Changes in vSphere 6.0 and Deploying vCenter 6 – Part 1

Here in this post will discuss about the vCenter Server architecture changes from vSphere 5.5 to vSphere 6. Will also discuss different use cases and Deploying vCenter Server 6 with Installable Windows-based and Deploying vCenter Server 6 with VCSA.

Firstly let me brief about VMware vCenter Server 5.5 components, there are multiple individual components are used to deliver the vCenter Server management solution.

  1. vCenter Single Sign-On
  2. vSphere Web Client
  3. vCenter Inventory Service
  4. vCenter Server

When deploying a vCenter server there are 2 deployment processes Simple Install and Custom Install. 

Simple Install :- The simple install is a deployment option that deploys vCenter Server with its default options selected to a single physical or virtual machine. The simple install install all four components of vCenter Server (vCenter Single Sign-On, vSphere Web Client, vCenter Inventory Service, and the vCenter Server instance) on a single windows Server. This is ideal for small customer.

There are several limitations with the simple installer:-

When you choose Simple install it will install in default location with no option to change the destination folder. Many customers prefer to install their applications to a volume other than the system volume.

Simple install provides only the vCenter Single Sign-On deployment option of “vCenter Single Sign-On for your first vCenter Server.” Therefore it cannot be used for additional vCenter servers.pic1Custom Install :- The custom install gives you option to install each individual component independently on same or different servers. Because each component is being installed individually, so it is important that components are installed in the following order:

1. vCenter Single Sign-On

2. vSphere Web Client  ( Not compulsory can be installed later)

3. vCenter Inventory Service

4. vCenter Server

pic2With the release of vSphere 6.0, vCenter Server installation and configuration has been simplified dramatically. The installation of vCenter now consists of only two components instead of 4 components in vSphere 5.5. and provide all services for the virtual datacenter:

  • Platform Services Controller vSphere 6.0 introduces a new component called the Platform Services Controller (PSC). Now no need to install all these components individually. We choose to install Platform Services Controller (PSC) and all the services included in Platform Services Controller will be installed:
    • vCenter Single Sign-On
    • License Service
    • Lookup Service
    • VMware Directory Service
    • VMware Certificate Authority
  • vCenter Services Same way when we install vCenter Services it will install group of services includes:
    • vCenter Server
    • vSphere Web Client
    • vCenter Inventory Service
    • vSphere Auto Deploy
    • vSphere ESXi Dump Collector
    • vSphere Syslog Collector (Microsoft Windows)/VMware Syslog Service (Appliance)

vCenter Deployment Modes:- 

There are two basic architectures that can be used when deploying vSphere 6.0 :-

1. Install vCenter Server with an Embedded Platform Services Controller vCenter Server with an Embedded Platform Services Controller mode installs all services on the same virtual machine or physical server as vCenter Server. It will install PSC components first followed by vCenter Server Services.  This mode is ideal for small environments.     pic32. Install vCenter Server with an External Platform Services Controller vCenter Server with an External Platform Services Controller mode installs the platform services on a system that is separate from where vCenter services are installed. Installing the platform services is a prerequisite for installing vCenterThis mode is ideal for larger environments, where there are multiple vCenter servers.

pic4There will be several use cases depending on business requirement to deploy vCenter Server either with an Embedded Platform Services Controller or with an External Platform Services Controller .Here are List of recommended use cases for VMware vSphere 6.0 deployment. You can also find out here  :- http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2108548pic5pic6vCenter Server comes not only as an installable Windows-based application but also as a SUSE Linux-based Virtual appliance. Will you use Windows-based or Virtual appliance? There are advantages and disadvantages to each approach. I am not going to discuss what to use here.

Here Will discuss both approach, How to install Windows-based vCenter Server and How to deploy VCSA (VMware vCenter Server Virtual Appliance) with Embedded and External PSC.

Install Windows-based vCenter Server 6 with an Embedded Platform Services Controller:-

  • To install Windows-based vCenter Server we need to have a Windows Server ready.
  • Server must be a member of a domain.
  • Make a new account in Active Directory for the vCenter Server before the deployment and assign required permission on the host where you want to install vCenter Server.
  • Enter a DNS entry for the Server.

Now we are ready to start vCenter Server installation.

1. Login to the Windows Server with Service account and copy/mount the installer VMware-VIMSetup-all-6.0.0-2800571.iso

2. Browse the location of the Installer and double click the Autorun to start the VMware vCenter Installer.pic73. VMware vCenter Installer will start. Select ‘vCenter Server for Windows’ under VMware vCenter Server and Click ‘Install’.

VC24. VMware vCenter Server installation will start and Click ‘Next’ on ‘Welcome to the VMware vCenter Server 6.0. Installer’

VC45. Click the ‘I accept the terms of the license agreement’ box and then click ‘Next’

VC56. Here we are installing vCenter with an Embedded Platform Services Controller, So click ‘vCenter Server and Embedded Platform Services Controller’ and then click ‘Next’. VC67. Enter the ‘System Name’ on the ‘System Network Name’ window and then click ‘Next’. In the most cases it will auto select FQDN of the server on which we are installing vCenter Server.

VC78. On the ‘vCenter Single Sign-On Configuration’ page enter the ‘Domain Name’ (By default it will be vsphere.local), ‘Enter SSO Administrator Password’ and ‘Site Name’ and then click ‘Next’

p39. On the ‘vCenter Server Service Account’ page select ‘Specify a user Service account’ enter password for the Service account and then click ‘Next’. If you have logged in as Service Account it will auto take the account name in ‘Account user name’

VC910. Choose the ‘Database Settings’ and then click ‘Next’. In production environment it is always recommended to ‘use an external database’

VC1011.  On the ‘Configure Ports’ page normally select default ports but if required you can change the port numbers as per and click ‘Next’

VC1112. On the ‘Destination Directory’ page change the location if required or click ‘Next’

VC1213. On the ‘Ready to Install’ page review the settings and click ‘Install’ to start the ‘Installation Process…’

p714. It will take several minutes to install ‘vCenter Server Platform Services Controller and vCenter Server services. Wait for Installation to finish.

VC12-115. Installation in Progress….

VC1616. Here we go ‘Setup Completed’ and vCenter Server has been successfully Installed. Click ‘Finish’ to complete the Installation.

VC17

Will discuss Deploying a new vCenter 6 with VCSA (Embedded and External) in Next Part… So stay tuned  🙂

SHARE & SPREAD THE KNOWLEDGE!!

 

Backing up and Restoring the vCenter Server 6.0 with vSphere Data Protection 6 – Part 1

Few days ago wrote blog about how to Back up and Restore the vCenter Server 6.0 embedded vPostgres database. I am extending same topic and will discuss here how to Back Up and Restore vCenter Server using  vSphere Data Protection.

One of the most critical aspects to any network, not only virtualized Infrastructure, is a solid backup strategy and VMware offers its own backup tool, VMware Data Protection to back up and restore a virtual machine (VM) that contains vCenter Server, a vCenter Server Appliance, or a Platform Services Controller.

vSphere Data Protection (VDP) is a robust, simple to deploy, disk‐based backup and recovery solution that is powered by EMC. VDP is fully integrated with the VMware vCenter Server and enables centralized and efficient management of backup jobs while storing backups in deduplicated destination storage locations.

The VMware vSphere Web Client interface is used to select, schedule, configure, and manage backups and recoveries of virtual machines.

VDP Provides fast and efficient data protection for all of your virtual machines, even those powered off or migrated between vSphere hosts.

VDP Reduces the cost of backing up virtual machines and minimizes the backup window by using Change Block Tracking (CBT) and VMware virtual machine snapshots.

VDP Allows easy backups without the need for third‐party agents installed in each virtual machine. To take a full image backup of vCenter Server or any VMs using vSphere Data Protection (VDP), minimum requirements is that VM must have VMware Tools installed and running and VM must use a fully qualified domain name (FQDN) with correct DNS resolution, or must be configured with a static IP address.

The main purpose of this blog is that, vSphere Data Protection to restore a VM that contains vCenter Server instance directly on the ESXi host that is running the vSphere Data Protection Appliance when the vCenter Server service becomes unavailable or when you cannot access the vSphere Data Protection user interface by using the vSphere Web Client.

One VDP Appliance supports Up to 400 Virtual Machines and one vCenter Server can support Up to 20 VDP appliances.

VDP supports Image-level Backup and Restore, VMDK Backup and Restore, and Guest‐level backups for Microsoft SQL Servers, Exchange Servers, and Share Point Servers. With guest‐level backups, client agents (VMware VDP for SQL Server Client, VMware VDP for Exchange Server Client, or VMware VDP for SharePoint Server Client) are installed on the SQL Server, Exchange Server, or SharePoint Server in the same manner that backup agents are typically installed on physical servers.

vSphere Data Protection Architecture

VDP can be deployed to any storage supported by vSphere e.g. VMFS, NFS, and VSAN datastores. Management of VDP is performed by using the vSphere Web Client.

VDP0I’ll only discuss here how to deploy VDP, Initial Configuration of VDP, Scheduled Backup of vCenter Server VM and How to restore direct-to ESXi host when vCenter Server becomes unavailable or when the user cannot access the vSphere Data Protection user interface by using the vSphere Web Client.

vSphere Data Protection (VDP) installation

1. Connect the vCenter Server using vSphere Web Client: https://vcenter6.vcix.nv:9443/vsphere-client/ with Administrative privileges.

VDP12. Go to Home –> Hosts and Clusters –> Right Click the Cluster/ESXi Host and choose Deploy OVF Template.VDP2

3. It will open up Deploy OVF Template window. If you are deploying OVF first time it will ask to install the VMware Client Integration Plug‐in. Click on the Download the Client Integration Plug‐in to download, make sure you have Internet access or Download on machine has Internet Access and Install on the machine from you want to Deploy OVF.VDP3

4. Once you Click on the Download the Client Integration Plug‐in, it will ask you to save. Click Save File.VDP4

5. Once Download finished double click to start Client Integration Plug‐in Installation.VDP5

6. It is very Simple and Straight forward, Just follow the screen to finish the Installation.VDP6

VDP7

VDP8

VDP9


VDP12
7. Once Client Integration Plug‐in Installation finished. Connect the vCenter Server using vSphere Web Client –> Home –> Hosts and Clusters –> Right Click the Cluster/ESXi Host and choose Deploy OVF Template.VDP13

8. It Will open up Deploy OVF Template Window, Select Local File and Click Browse to Navigate to the location of the VDP Appliance .ova file. Confirm that you select the appropriate file for the datastore and Click OK. Click Next to validate the .OVA file.VDP14

VDP159. It will validate the OVA file. Review the template details and click NextVDP16

10. On the Accept EULAs screen, read the license agreement (If you want 😉 and click Accept, and then click NextVDP17

11. On the Select name and folder screen, Enter VDP Appliance Name and Select folder or datacenter where you want to deploy the VDP Appliance, and then click NextVDP18

12. On the Select Storage screen, select the virtual disk format and select the Datastore to store VDP Appliance. Click Next.VDP19

13. On the Setup networks screen, select the Network Port Group for the VDP Appliance and click Next.VDP20

14. In the Customize template screen, Enter Default Gateway, DNS, Network 1 IP Address of VDP, and Network 1 Netmask/Subnet Mask. Click Next.

NOTE :- The VDP Appliance does not support DHCP.  A static IP address is required.VDP21

15. On the Ready to complete screen, confirm that all of the deployment options are correct. Check Power on after deployment box and click Finish.VDP22

16. It will take some time to Deploy OVF Template. You can monitor progress in Recent Tasks. VDP23

17. Once Deployment Completed, you can see the VDP VM under Host and Cluster, And on the Virtual Machine Summary for VDP.VDP24

18. vCenter deploys the VDP Appliance and boots into the install mode. VDP25

==================================================

VDP has been deployed and now ready for Initial Configuration.

Initial Configuration

1. Open Web Browser and type https://vdp6.vcix.nv:8543/vdp-configure/ to access the VDP console. Username is root and Default password – changeme.VDP26

2. The VDP Welcome screen appears, Click Next to start configuring VDP.VDP27

3. Next Screen is to configure Network Settings for VDP Appliance. Enter IP Address, Subnet Mask, Gateway, DNS IP address, Name and Domain name of VDP and Click Next.VDP28

4. On the Time Zone screen, Select the time zone for the VDP Appliance and Click Next.VDP29

5. On the VDP Credentials screen, Enter password for Root account and Click Next.VDP30

6. On the vCenter Registration screen, Enter vCenter Server User Name, Enter Password for User, Enter vCenter Server User Name you want to register VDP with and Click Test Connection to test connection with entered vCenter Server.VDP31

7. Click Ok on connection status box and Click Next.VDP32

8. Next is Create Storage Page, Select the type and Capacity for VDP and Click Next.VDP33

9. On the Device Allocation Page, Select Storage Provision type and Select the Datastore for VDP and Number of Disks. And Click Next.VDP34

10. On the CPU and Memory Page Select No of Virtual CPUs and Memory and Click Next.VDP35

11. On the Product Improvement Page, Select Enable Customer Experience Improvement Program if you want or leave that Uncheck and Click Next.VDP36

12. On the Ready to Complete page, Select the Run Perform Analysis and Restart Appliance if Successful check box and Click Next to Start the configuration of VDP as per provided details.VDP37

13. Click OK on the Warning dialog box and Wait for configuration to finish.VDP38

14. You can see on below screen it has started configuration of VDP.VDP39

15. Once Configuration done, On the Complete page click Restart Appliance to Finish the configuration and start the VDP Appliance.VDP40

16. As you can see we can Monitor in Resent Tasks.VDP41

17. Once VDP Appliance reloaded. You can Log in with root account with changed password. VDP42

That’s It. Deployment of VDP Appliance and Initial Configuration of appliance has been completed. In the Backing up and Restoring the vCenter Server 6.0 with vSphere Data Protection 6 – Part 2 will discuss how to Take Backup of VM and How to perform Emergency Restore of vCenter Server in the absence vCenter Server.

Thank You 🙂 Keep Learning and Keep Sharing !!

 

Geo-Location Based Traffic Management with F5 BIG-IP for VMware Products (PoC)

Great Blog written By Spas Kaloferov, Solutions Architect member of Professional Services Engineering (PSE) for the Software-Defined Datacenter (SDDC) – a part of the Global Technical & Professional Solutions (GTPS) team.

Excellent one, Must read. Please click below link to read full use case:-

Geo-Location Based Traffic Management with F5 BIG-IP for VMware Products (PoC)

This is great design use case for Local Load Balancing with Local Traffic Manager (LTM) and Geo-Location load balancing with Global Traffic Manager (GTM).

 Thank You 🙂

Backing up and Restoring the vCenter Server 6.0 embedded vPostgres database

Currently i am working to design VMware Infrastructure on vSphere 6.0 for one of the customer. This is small infra with 5-6 hosts and expected growth is 10-20% in next 3-4 years. So as per requirement decided that vCenter management server will be deployed as virtual machine running in vCenter Server with an Embedded Platform Services Controller and bundled PostgreSQL database will be used as PostgreSQL database with vSphere 6.0 can support up to 20 hosts and 200 virtual machines which is full filling our requirement for next 4-5 years.

We had Design review meeting last week and question came up from customer can we backup bundled PostgreSQL database? If yes how can we Backup and Restore vCenter Server bundled PostgreSQL database.

So wanted to share with all and hope this will be useful for many.

Back Up the Embedded vCenter Server Database:-

1. Log in to vCenter Server with administrative privilege, I have logged in as Service Account used for vCenter Server.

2. Browse C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx\ folder, If you changed the default installation location it will be different for you.  B1

3. Locate the vcdb.properties file in the C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx\ and open the file in a text editor.B3

4. In the vcdb.properties file, locate the password of the vc database user and record it as we need it while will take backup.B4

5. Download the Windows back up and restore package windows_backup_restore.zip attached to KB article (2091961) and unzip it on the host machine.B5

6. After unzip you can see that are 2 python scripts, One for Backup and another for Restore.B6

7. Once download and unzip done, we are good to go to run the command to take Backup of the database.

8. Before taking the Backup just wanted to show my current inventory setup, just for the record.B7

9. Open command prompt and navigate to C:\Program Files\VMware\vCenter Server\python directory to run the backup_win.py script.

C:\Program Files\VMware\vCenter Server\python> python.exe “c:\vCenter Server\backup_win.py” -p “enter password we have recorded in step 4”  -f “c:\vcdb_backup_02july2015.bak”B8

10. When the backup completes, you can see a message that the Backup completed successfully.

11. Now backup of vCenter database has been taken, So let me modify/delete inventories entry and then will restore to get those back. As you can see in below screenshot i have deleted Cluster and Datacenter entries.B9

Restore the vCenter Server vPostgres Database:-

1. Log in to vCenter Server with administrative privilege, I have logged in as Service Account used for vCenter Server.

2. Stop the vCenter Server Service and VMware Content Library service. When you stop vCenter server service it will stop all other services dependent on vCenter Server.R1

R23. Locate the vcdb.properties file in the C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx\ and open the file in a text editor. Locate the password of the vc database user and record it as we need it while Restore the database.

4. Open Command prompt and Run restore script to Restore the database from last backup.

C:\Program Files\VMware\vCenter Server\python> python.exe “c:\vCenter Server\restore_win.py” -p “enter password we have recorded in step 3”  -f “c:\vcdb_backup_02july2015.bak”R4

R55. When the Restore completes, you can see a message that the Restore completed successfully.

6. Start the VMware Content Library service and vCenter Server Service and all other related services.

7. Connect to vCenter Server Web Client to check the status.R6

That’s All 🙂 We have done with how to Backup and Restore the vCenter Server 6.0 embedded vPostgres database. Thank you 🙂

———————————————————————————————

Reference VMware KB to Download the Windows back up and restore package/script:- http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2091961

VMware VCP6-DCV Certification is available now!!

Here is the most awaited VCP6-DCV certification has been announced by VMware.

VCP6-DCV Logo

VMware Certified Professional 6 – Data Center Virtualization (VCP6-DCV) exam will Validate your ability/skills required to install, configure, administer and scale a vSphere virtualized data center on VMware vSphere 6.

For existing VCP5-DCV certified, course is recommended but not required. You can directly go for VCP6-DCV Beta exam (VMware Certified Professional 6 – Data Center Virtualization Beta Exam)

To Know more about Beta exam Click Here. And to request for Exam Authorization Click Here.

 

Version 6 Certification Roadmap:-

 

EXAM RoadMap

Good time to upgrade yourself .. Good Luck !!!!!

VMware Certification Upgrade / Migration Path from v5 to v6

VMware has announced the new Upgrade / Migration Path from v5 to v6, Here is the latest paths how we can Upgrade / Migrate from version 5 to New Version 6. Biggest news is that do not need to go through the New training to upgrade to v6.

Upgrading from VCP5 to VCP6: Only one exam is required. There is no course attendance required (but it is recommended to go through to know the New product better). There is Name changes from previous version, here is new Name:-

VCP-DCV = Data Center Virtualization
VCP-DTM = Desktop & Mobility (Previously VCP-DT = Desktop)
VCP-CMA = Cloud Management & Automation (Previously VCP-Cloud)
VCP-NV = Network Virtualization

  • There are five VCP6 migration options across the four technology tracks: Data Center Virtualization (DCV), Desktop and Mobility (DTM), Cloud Management and Automation (CMA), and Network Virtulization (NV):
  • VCP6: Data Center Virtualization Exam (exam number: 2V0-621) – Beta yet to be released.
  • VCP6: Data Center Virtualization Delta Exam (exam number: 2V0-621D) – Beta yet to be released.
  • VCP6: Desktop & Mobility Exam (exam number: 2V0-651) – Yet to be released.
  • VCP6: Cloud Management and Automation Exam (exam number: 2V0-631) – Yet to be released.
  • VCP6: Network Virtualization Exam (exam number: 2V0-641) – Yet to be released.

If you hold one of the following v6 certifications it will be automatically upgraded to the equivalent new VCP6 certification:

  • VCP6-Cloud = VCP6-Cloud Management and Automation
  • VCP6-Desktop = VCP6-Desktop and Mobility
  • VCP-Network Virtualization = VCP6–Network Virtualization

Upgrading to VCIX6: VCIX6 contains two exams: Design & Administration similar for all three tracks: DCV, DTM, CMA.

If you hold either a VCAP Administration or Design certification, you will need to take the other of what you do not have in VCIX6 exam.  For example if you hold VCAP5-DCD, you will need to take VCIX6 administration exam and if you hold VCAP5-DCA then you would only need to take the VCIX6 Data Center Design exam to earn your VCIX6-DCV/VCIX6-DCD certifications.

For existing dual VCAP5, You can choose to take either VCIX6 exam; Design or Administration.

For existing VCIX-NV, You will be upgraded automatically to VCIX6-NV.

Upgrading to VCDX6: If you hold a VCDX5, Only required to take VCIX6 design exam in the corresponding solution track.

Thank You!