Home > Blogs > VMware vSphere Blog > Tag Archives: VMware

Tag Archives: VMware

One Cloud, Any Application – #VMW28days

Screen Shot 2015-02-09 at 4.11.51 PM

VMware Virtual SAN 6.0 – you heard all about it on February 2nd – you read all about it in our blog post on the vSphere Storage Blog.

 

Still want more?

 

Visit VMware’s One Cloud, Any Application site every day in February to learn more about our products and solutions including software-defined storage, Virtual SAN 6, and Virtual Volumes (VVOLs). With content for IT decision makers and practitioners alike, this site contains everything from technical documentation to infographics, whitepapers, and analyst insights.

 

Stop by today!

 

Also, this Thursday, February 12th, at 11am PST, we would like to invite you to join the software-defined storage CrowdChat! Here, you’ll be able to ask questions directly to VMware storage experts. RSVP today!

 

For more information about VMware Virtual SAN, follow us on Twitter at @VMwareVSAN and Facebook at facebook.com/vmwarevsan.

 

vSphere APIs for IO Filtering

I’ve been fortunate to have one of our super sharp product line managers, Alex Jauch (twitter @ajauch), spend some time explaining to me one of the new enabling technologies of vSphere 6.0: VAIO.  Let’s take a look at this really powerful capability and see what types of things it can enable and an overview of how it works.

VAIO stands for “vSphere APIs for IO Filtering”

This had for a time colloquially been known as “IO Filters”. Fundamentally, it is a means by which a VM can have its IO safely and securely filtered in accordance with a policy.

VAIO offers partners the ability to put their technology directly into the IO stream of a VM through a filter that intercepts data before it is committed to disk.

Why would I want to do that? What kinds of things can you do with an IO filter?

Well that’s up to our customers and our partners. VAIO is a filtering framework that will initially allow vendors to present capabilities for caching and replication to individual VMs. This will expand over time as partners come on board to write filters for the framework, so you can imagine where this can go for topics such as security, antivirus, encryption and other areas, as the framework matures. VAIO gives us the ability to do stuff to an IO stream in a safe and certified fashion, and manage the whole thing through profiles to ensure we get a view into the IO stream’s compliance with policy!

The VAIO program itself is for partners – the benefit is for consumers who want to do policy based management of their environment and pull in the value of our partner solutions directly into per-VM and indeed per-virtual disk storage management.

When partners create their solutions their data services are surfaced through the Storage Policy Based Management control plane, just like all the rest of our policy-driven storage offerings like Virtual SAN or Virtual Volumes.

Beyond that, because the data services operate at the VM virtual device level, they can also work with just about any type of storage device, again furthering the value of VSAN and VVOLs, and extending the use of these offerings through these additional data services.

How does it work?

The capabilities of a partner filter solution are registered with the VAIO framework, and are surfaced for user interaction in the SPBM Continue reading

SAP HANA Dynamic Tiering and the VMware Software Defined Data Center

The latest release of SAP HANA has brought the concepts of multi-temperature data and lifecycle management to a new level.  With SP09, SAP has addressed the size and cost constraints which may prohibit an all in memory solution. SAP HANA with the Dynamic Tiering (DT) option enables placement of the highest value “hot data” in the classic SAP HANA in-memory tables, and less frequently accessed “Warm Data” is placed or migrated to tables which reside on an SAP HANA Extended Storage Host (ES Host).

The data associated with the ES Host will reside on disk and not in-memory, however since data is stored using the same columnar paradigm as classic SAP HANA, performance is optimized for data processing.

SAP Business Warehouse Powered by HANA

The Dynamic Tiering option is Plug & Play for SAP Business Warehouse (BW) 7.4 SP8 Power By HANA. SAP BW provides full access to your data whether it resides in-memory data or on the extended host, access is transparent to the user, so no need to direct your queries to the SAP in-memory store or extended host store.

With the SAP HANA SP09 release BW Objects which can reside on the Extended Storage Host are the Write-Optimized Data Storage Objects and the Persistent Staging Area. Since these objects can comprise between 15% to 40% of the total database footprint, customers using DT in their landscapes can realize substantial savings by reducing the amount of RAM necessary to run SAP HANA. In addition the SAP HANA Extended Storage Hosts can be deployed on either Certified Servers or standard x86 commodity servers.

SAP HANA Native Use Cases

The number of software ISVs and developers choosing SAP HANA as their native database is quite impressive. Whether SAP HANA is being used for Data Marts, Enterprise Data Warehouses, or for custom applications, Dynamic Tiering presents interesting opportunities to make these use cases more robust. It’s important to adhere to the SAP HANA Node to ES Host ratios when using HANA as the native database. When the HANA in-memory database is 64GB to 512GB in size, the Extended Storage Host resident data can be 4 times the size of the HANA in-memory database. Below is a sizing summary:

SAP   HANA In-Memory Data

Extended   Storage Host Data Ratio

64GB – 512 GB

1:4

>512 GB to <2TB

1:8

>2TB

Unlimited

 

Deploying SAP HANA In The VMware Software-Defined Datacenter

SAP HANA Extended Storage Host is fully supported by SAP to runs on VMware vSphere. It’s interesting to note that SAP does not allow the deployment of a SAP HANA Worker Node and the Extended Storage option on the same physical server. In addition when deploying SAP HANA with DT in the physical world, SAP provides the following guidance:

“The distance between HANA hosts and Extended Storage hosts should be as short as possible to avoid performance impact on distributed INSERTs, UPDATEs, or Queries. Ideally, ES hosts should be placed inside the same rack as the HANA hosts.”

VMware can actually go one better. In the VMware Software Defined Datacenter both the SAP HANA Worker Node virtual machine and the Extended Storage Host virtual machine can be consolidated on a single physical vSphere Host which is a supported SAP configuration. This avoids the performance impact on distributed INSERTs, UPDATEs, or Queries which SAP mentions in the physical world. This is a clear benefit, by consolidating these virtual machines customers can better utilize server resources and increase their ROI. Also the consolidation and co-location of SAP HANA Nodes onto a single vSphere Host may reduce the internode communication latency associated with multi host deployments in a physical SAP Dynamic Tiering landscape.

SAP HANA Dynamic Tiering with VMware HA and Workload Management

For customers who choose to use the Dynamic Tiering option, SAP HANA System Replication is not available in SP09. However as with SAP HANA single node scale up deployments, the Extended Storage Host can be protected against hardware and or OS outages with VMware High Availability (HA). Enabling VMware HA allows the ES Host to be restarted on any vSphere hosts within the vSphere cluster without the need for a dedicated standby server. Also vMotion can be used to perform workload management or zero downtime maintenance by live migrating the ES Host to another server. Since the ES Host can run on both certified and standard x86 hardware, Distributed Resource Scheduler (DRS) can be set to atomically migrate virtual machines to other vSphere hosts within the cluster in order to maximize performance and availability.

SAP has devised a brilliant multi-temperature strategy to manage the data lifecycle of their customer’s SAP HANA landscapes. When deploying SAP HANA with Dynamic Tiering our joint customers can extend and virtualize their SAP HANA databases beyond the 1TB vSphere 5.5 monster VM limitation. I will be discussing these topics in-depth, as well as techniques to simplify and accelerate SAP HANA deployments in the VMware Software Defined Data Center at VMware Partner Exchange 2015 in my session entitled; “Leveraging SAP HANA Dynamic Tiering Strategy and Concepts in The VMware Software Defined Data Center”

Storage and Availability at Partner Exchange 2015

VMware’s 2015 Partner Exchange is now just about one week away, and it’s shaping up to be a great one!

In storage and availability we’ll have a lot to talk about across the board: Some sessions will offer deeper examinations of our current products, others will give you a great exploration of some of the newer things VMware has to showcase.

I’ve made a list of some of the sessions put on by those of us in the storage and availability product team; it’s a good cross section from product marketing, product managers, and technical marketing people such as myself.  Outside of the engineers who actually write the code, these are the people closest to the products you use, so sign up and hear something new.  There are also sessions from our highly experienced field sales and technical teams — the experts at understanding how these products address customer requirements and explaining their value to our customers.

I’m personally doing a technical session with my colleague Rawlinson on Virtual SAN (STO4275) and looking forward to it quite a bit.

Lastly, don’t be shy to come say hello after the sessions.  We love to hear your thoughts, if we’ve got time between activities…

Continue reading

vCenter Server 5.5 Update 1b released

Today VMware released an update to its virtualization management solution, vCenter Server. The update brings several fixes as documented in the release notes which can be reviewed in full here.

The new versions are as follows:

  • vCenter Server 5.5 Update 1b | 12 JUN 2014 | Build 1891313
  • vCenter Server 5.5 Update 1b Installation Package | 12 JUN 2014 | Build 1891310
  • vCenter Server Appliance 5.5 Update 1b | 12 JUN 2014 | Build 1891314
    downloaded now from vmware.com

Continue reading

Which vCenter Server platform should I use – Appliance or Windows?

One of the most repetitive questions that I get asked is which version of vCenter Server should I be using. This obviously is based on the decision between using the vCenter Server appliance (VCSA) introduced with vSphere 5.0 or the trusted and proven vCenter Server on Windows.

whichplatform

It has been general knowledge that the vCenter Server appliance, since its introduction has lacked features to that of its Windows counterpart. With vSphere 5.5 the vCenter Server appliance has come a long way, it supports all solutions that integrate with vCenter Server (vCD, vCOPs, SRM, VUM etc) but is it production ready? I can confidently say yes but will it meet your requirements?
Continue reading

Getting ready to upgrade production to vCenter Server 5.5? Make sure you’re using the correct deployment option

Over the last few months, many customers have been testing and familiarizing themselves with vSphere 5.5 however deployment into a production environment is usually stalled until the availability of the first update or service pack. As we are nearing the typical time frame of when such an update or service pack may become available, I wanted to share some findings that may affect your deployment selection of vCenter Single Sign-On when deploying or upgrading to vCenter Server 5.5

During the installation of vCenter Single Sign-On server you are asked on the deployment option of the vCenter Single Sign-On instance. Below is the intended use case for each deployment option.

SSO#0

Continue reading

Now Available – VMware vSphere Mobile Watchlist

VMware vSphere Mobile Watchlist allows you to monitor the virtual machines you care about in your vSphere infrastructure remotely on your phone. Discover diagnostic information about any alerts on your VMs using VMware Knowledge Base Articles and the web. Remediate problems from your phone by using power operations or delegate the problem to someone on your team back at the datacenter.
IMPORTANT NOTE: A VMware vSphere installation (5.0 and above) is required to use VMware vSphere Mobile Watchlist. Access to your vSphere infrastructure may need a secure access method like VPN. Contact your IT department for further assistance.

   

Continue reading

Virtual SAN VM Density Contest Results!

Dear vSphere Blog Readers,

Please join me in congratulating our VM Density contest winners – The Miami VMUG Team:

  • Alex Correa, Systems Engineer – Espirito Santo Bank
  • Tony Santiago, Lead Infrastructure Engineer – Venturian Group
  • Bruno Ferreira, Technical Advisor – FedEx

The Miami VMUG team was able to power on 2,248 VMs on a 3-node Virtual SAN cluster!VMDenistyWinnersVMDenistyWinners2

Continue reading

When to Centralize vCenter Single Sign-On Server 5.5

While VMware highly recommends the deployment of all vCenter Server components into a single virtual machine (excluding the vCenter Server database), large enterprise customers running multiple vCenter Server instances within a single physical location can simplify the vCenter Single Sign-On architecture and management by reducing the footprint and required resources and specify a dedicated vCenter Single Sign-On environment for all local resources in each physical location.

For vSphere 5.5 the VMware recommendation is to centralize vCenter Single Sign-On when you have 8 or more vCenter Server instances in a given location (this is a soft recommendation).

Centralized vCenter Single Sign-On Architecture


Figure 1: A Centralized vCenter Single Sign-On Server environment

There can be increased risk when centralizing a vCenter Single Sign-On server (to why it is not recommended for smaller environments) due to the increased number of components affected if the vCenter Single-Sign-On server was to become unavailable, in short all vCenter Server components of all vCenter Servers registered will incur authentication loss (when compared to  just the single vCenter Server instance when installed locally) and so availability of the vCenter Single Sign-On centralized server(s) is highly recommended. Continue reading