Follow Us

Cool Social Media Sharing Touch Me Widget by Beautiful Blogger Widgets

Translate

Total Pageviews

Monday, 22 August 2016

Error "Cannot complete the requested operation: Resource not found" when creating the business group

When i was creating the business group in vRA i was getting this error message "Cannot complete the requested operation: Resource not found". I was scratching my head to know that what could be the reason of this error then finally i was able to find out the solution of this issue and Solution is "Do not create vRA Business group with name that contain spaces"

VMware vCloud Director - 5.6, 8.0, 8.10 Confiuguration Maximums

Thursday, 18 August 2016

VMware Lifecycle Product Matrix

Comparison of Hypervisor Based Replication solutions

I got this features comparison document between different hypervisor based replication solutions. Although i am not the publisher of this document so all credit goes to the Zerto team who created it. As i am unable to find out the proper link that i can share with everyone but anyone can download it from here.

VMware SRM 6.x Editions

SRM is DR Automation tool from VMware. From the licensing point of Site Recovery Manager can be purchased either as a standalone product or as part of VMware vCloud Suite® Enterprise Edition. As a standalone product, Site Recovery Manager is available in two editions, Standard and Enterprise. Both editions can only be licensed “per protected virtual machine.” A “protected virtual machine” is defined as a VM that is part of an SRM protection group, regardless of the state of the VM. Site Recovery Manager Enterprise Edition can also be purchased as part of vCloud Suite Enterprise Edition. In this case, Site Recovery Manager is licensed per “per protected processor.” Let's discuss what's the difference in between these two editions?


Monday, 15 August 2016

What is VIO (VMware Integrated Openstack)?

VMware Integrated OpenStack is a VMware supported OpenStack distribution (distro) that makes it easier for IT to run a production-grade OpenStack-based deployment on top of their existing VMware infrastructure. Building on their existing expertise, VMware administrators can foster innovation and agility by providing their developers with simple vendor-neutral OpenStack APIs on top of VMware’s best-of-breed SoftwareDefined Data Center (SDDC) infrastructure. Key administration capabilities, including install, upgrade, troubleshooting, and cost-visibility are provided via deep integration with already familiar VMware management tools, enabling fast time to innovation and lower total cost of ownership.
Image thanks to VMware
Benefits:-
• OpenStack Powered Platform Certified (DefCore 2015.04)
• Enterprise Grade OpenStack Cloud
• No OpenStack PhD Required
• Simplified OpenStack Operations
• Single Vendor Support
• Free for all VMware vSphere® Enterprise Plus customers, including vSphere with Operations Management™ Enterprise Plus and vCloud Suite® customers

NSX and VIO Interoperability:-

 
VSAN and VIO Interoperability:-


Refer this for Interoperability Matrix:-
http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php

For more info:-
https://www.vmware.com/files/pdf/openstack/VMware-Integrated-OpenStack-Datasheet.pdf

Monday, 8 August 2016

Roles assigned to Configurationadmin account in vRA7

A configuration admin user is created and a configuration catalog item is created in the default tenant. The configuration admin is granted the following rights:
Approval Administrator
Catalog Administrator
IaaS Administrator
Infrastructure Architect
Tenant Administrator
XaaS Architect

Rollback vRA Minimal and Distributed Installations

vRA has two types of installation:-
1. Minimal Installation
2. Distributed Installation

If installation is failed then follow the procedure given below for the rollback

A system administrator must manually remove some files and revert the database to completely uninstall a failed vRealize Automation IaaS installation.


1

If the following components are present, uninstall them with the Windows uninstaller.

vRealize Automation Agents
vRealize Automation DEM-Worker
vRealize Automation DEM-Orchestrator
vRealize Automation Server
vRealize Automation WAPI

Note
If you see the following message, restart the machine and then follow the steps in this procedure: Error opening installation log file. Verify that the specified log file location exists and it is writable

Note
If the Windows system has been reverted or you have uninstalled IaaS, you must run the iisreset command before you reinstall vRealize AutomationIaaS.
2

Revert your database to the state it was in before the installation was started. The method you use depends on the original database installation mode.
3

In IIS (Internet Information Services Manager) select Default Web Site (or your custom site) and click Bindings. Remove the https binding (defaults to 443).
4

Check that the Applications Repository, vRealize Automation and WAPI have been deleted and that the application pools RepositoryAppPool, vCACAppPool, WapiAppPool have also been deleted.

The installation is completely removed.

A system administrator must manually remove some files and revert the database to completely uninstall a failed IaaS installation.

1

If the following components are present, uninstall them with the Windows uninstaller.

vRealize Automation Server
vRealize Automation WAPI

Note
If you see the following message, restart the machine and then follow this procedure: Error opening installation log file. Verify that the specified log file location exists and it is writable.

Note
If the Windows system has been reverted or you have uninstalled IaaS, you must run the iisreset command before you reinstall vRealize AutomationIaaS.
2

Revert your database to the state it was in before the installation was started. The method you use depends on the original database installation mode.
3

In IIS (Internet Information Services Manager) select the Default Web Site (or your custom site) and click Bindings. Remove the https binding (defaults to 443).
4

Check that the Applications Repository, vCAC and WAPI have been deleted and that the application pools RepositoryAppPool, vCACAppPool, WapiAppPool have also been deleted.


Roll Back Failure Points
Failure Point
Action
Installing Manager Service
If present, uninstall vCloud Automation Center Server.
Installing DEM-Orchestrator
If present, uninstall the DEM Orchestrator .
Installing DEM-Worker
If present, uninstall all DEM Workers
Installing an Agent
If present, uninstall all vRealize Automation agents.
Source:-

Monday, 25 July 2016

vSphere 6 Lockdown Modes

As with vSphere 6 there are two types lockdown modes:- Normal and strict lockdown modes. So what is the difference in these lockdown modes. Checkout this Excellent VMware Blog Article by Mike Foley https://blogs.vmware.com/vsphere/2015/03/vsphere-6-0-lockdown-modes.html


Saturday, 23 July 2016

Extrasphere: how to perform storage/host vmotion without vCenter

Credit of all the great work goes to Extrasphere App developers. I am sharing their video here. If you want to watch it you can directly watch it at youtube and link is https://www.youtube.com/watch?v=o3yio4QjPy0

 

Tuesday, 19 July 2016

vSphere 6 Fault Tolerance(FT)

FT is one of feature in HA Cluster that provides zero downtime, but due to its limitations till vSphere 5.5 the use cases for this was also limited. But with vSphere 6 a lot of changes have been made in this  feature to overcome from its limitations.


Why one should use FT?
  • Continuous Availability with zero downtime and zero data loss.
  • Transparent to Guest OS
  • It does not depend on Guest OS and Application
  • Instantaneous failover from Primary to Secondary VM in case of ESXi Host Failure.

Enhancements in vSphere 6 FT
  • Supports for Up to 4 vCPUs and 64 GB RAM
  • Supports vMotion of both Primary and Secondary VM
  • Supports backup of FT VMs by using VADP like EMC, HP etc.
  • Replaced "Record and Replay" with Fast Check-Pointing
  • Supports thin, thick eager-zeroed and thick lazy zeroed
  • Separate File Copies for Primary and Secondary VMs like .vmx, .vmdk etc. and both can be on difference datastores. 
Use Cases of FT?
  • Applications that needs to available all the times
  • Custom Applications those do not have their own HA Solution
  • Custom Application those do have their HA Solution but that is too much complicated to configure
  • On-Demand FT
Requirements for FT?
  • Intel Sandy Bridge or Later (Avoton is not supported)
  • AMD Bulldozer or later
  • 10 Gbps FT logging network
Limits?

  • The maximum number of vCPUs aggregated across all fault tolerant VMs on a host. vCPUs from both Primary VMs and Secondary VMs count toward this limit. The default value is 8.
  • The maximum number of fault tolerant VMs allowed on a host in the cluster. Both Primary VMs and Secondary VMs count toward this limit. The default value is 4.
Shared Files in vSphere 6 FT?
FT has shared files:-
.shared.vmft = Prevents UUID Change.Which is found on a shared datastore, is the vSphere Fault Tolerance metadata file and contains the primary and secondary instance UUIDs and the primary and secondary vmx paths.
.ftgeneration = Is for split-brain condition. This attempt succeeds if the virtual machines remain running on the isolated or partitioned host and that host lost access to the virtual machines’ datastores when it became isolated or partitioned. A split-brain condition exists because there are two instances of the virtual machine. The .ftgeneration file ensures that only one instance of the virtual machine can read from or write to the virtual machine's virtual disks.

Licensing? 
Number of vCPUs supported by single FT enabled VM is limited by level of licensing
  • vSphere Standard or Enterprise Edition = Max. 2 vCPUs
  • vSphere Enterprise Plus = Max. 4 vCPUS
Features Not Supported for FT VMs?

When configuring your cluster, you should be aware that not all vSphere features can interoperate with Fault Tolerance.  
The following vSphere features are not supported for fault tolerant virtual machines.
  • Storage vMotion. You cannot invoke Storage vMotion for virtual machines with Fault Tolerance turned on. To migrate the storage, you should temporarily turn off Fault Tolerance, and perform the storage vMotion action. When this is complete, you can turn Fault Tolerance back on. 
  • Linked clones. You cannot use Fault Tolerance on a virtual machine that is a linked clone, nor can you create a linked clone from an FT-enabled virtual machine.
  • VM Component Protection (VMCP). If your cluster has VMCP enabled, overrides are created for fault tolerant virtual machines that turn this feature off.
  • Virtual Volume datastores.
  • Storage-based policy management.
  • I/O Filters
  • Snapshots. Snapshots must be removed or committed before Fault Tolerance can be enabled on a virtual machine. In addition, it is not possible to take snapshots of virtual machines on which Fault Tolerance is enabled.