VMware vSphere Data Protection (VDP) Advanced is able to perform true application-consistent backup and recovery of tier-1 applications – specifically, Microsoft SQL Server, Exchange, and SharePoint. This functionality is enabled by the VDP Advanced application agents for these applications. With these agents, administrators can back up and restore individual databases, enable multiple backup streams, truncate database logs, and restore individual Exchange mailboxes. Up until now, these agents were only supported for applications running in virtual machines. I am happy to report that it is now possible to offer the same level of data protection for these applications running on PHYSICAL servers! I repeat – VDP Advanced can now backup and restore SQL Server, Exchange, and SharePoint running on physical servers. Keep reading for more details…
The VMware Mobile Knowledge Portal iOS and Android app has recently been updated. It sports a great new look and feel and makes finding the information you need even easier by grouping it by area in our SDDC vision.
With the upcoming release of Virtual SAN, I want to take the opportunity to demonstrate some of the interoperability capabilities of Virtual SAN with other products and solutions.
I will start the series by showcasing Virtual SAN’s interoperability with OpenStack. This demonstration is based on the vSphere OpenStack Virtual Appliance (VOVA) and Virtual SAN. This demonstration showcases the integration capabilities between a VMware Virtual SAN and the OpenStack framework by deploying a single instance of vSphere OpenStack Virtual Appliance (VOVA) as the OpenStack cloud controller onto a Virtual SAN enabled vSphere 5.5 Cluster and deploying OpenStack based virtual machines or instances onto the Virtual SAN shared and distributed storage resource.
OpenStack environment running on vSphere can take advantage of the only hypervisor-converged solution in the industry and leverage the simplified management, operational model and technologies:
- Hybrid disk solution – flash based devices (SSD) and magnetic disks (HDD).
- High performance and distributed RAID architecture.
- Built-in application availability (if required for legacy applications).
- Storage Policy Based Management framework.
- Dynamic storage scalable capabilities (scale up and scale out).
Virtual SAN can also be considered in the context of quality of service (QoS) because VM Storage Policies can be use to define the level of performance, availability, and capacity required on a per–virtual machine or instance basis.
For future updates, be sure to following me on Twitter: @PunchingClouds
I been involved in many vCenter Heartbeat conversations since joining Technical Marketing, one question that always comes up is around licensing for vCenter Heartbeat and vCenter Server itself.
When I joined the Technical Marketing team last September I was tasked with vCenter Availability and Scalability along with providing coverage for all things vCenter and SSO.
Since that time I’ve branched out and am also covering Resource Management (more on this coming soon!) and also features in the Enterprise Plus SKU. I’m really excited about this as to this day one of my favorite and I feel underused features is the vSphere Distributed Switch, or VDS.
Deploying the Hyperic Agent(s)
You only need to do this on VMs with applications you want to protect. For additional guidance on these steps and details for how to install multiple agents simultaneously see: Getting Started with vFabric Hyperic 5.7 starting at pages 53 & 25
VMware’s conservative guidance about overcommitting your pCPU:vCPU ratio for Monster virtual machines is simple – don’t do it.
You have probably heard the terms “Big Data” and “Hadoop” mentioned somewhere in the industry lately – they are both very popular subjects of discussion at the moment. This blog gives you an introduction to the core technology and explains some of the contributions that VMware continues to make to the Hadoop world.
In Part 1 we installed the Hyperic and App HA vApps. Now we are going to setup App HA in vCenter and install the Hyperic agent on the vCenter server so that all of our pieces are communicating properly with each other.
Setting up App HA - additional details on this are available in the vSphere App HA Installation Guide starting on page 15
- From the Inventory menu in the vSphere web client, navigate to Administration > vSphere App HA
- Click the Settings tab
- Type the following parameters: Hyperic Server IP address/hostname, port (unless you changed this it would be the default: 7443), username (hqadmin) & password
- Click Apply
I recently installed App HA in my lab and found some of the documentation unclear and at times hard to follow. I’m going to work with our Tech Pubs group to improve it. In the meantime I wanted to share what I learned to help make your installation easier.
First, pay attention to the pre-reqs!
- Have DRS enabled on the cluster where you will be deploying the App HA appliance
- Enable “VM and Application Monitoring” in your cluster HA settings
- Create an IP Pool for the subnet(s) where you will install the Hyperic vApp
- Have 3 static IP addresses ready for the App HA appliance, vFabric Hyperic Server & vFabric Hyperic Server DB
- If you’ll want to use the email notification feature, make sure to configure email settings in vCenter
With those out of the way we are ready to get started. Here are the steps we are going to complete. I’ve broken this out into multiple posts to make navigating it easier.