Reading Time: < 1 minute

After the announcemens at the VMworld US 2012, VMware has announce new products versions for the Q4 2012:

  • vCloud Connector 5.1
    • Basic Edition (free)
    • Advanced Edition (that include also interesting feature to move VMs and keep in sync)
  • vCloud Automation Center 5.1 (formerly Dynamic Ops)
  • vCenter Operations Management Suite 5.6
  • vFabric Application Director 5.0
  • vFabric Application Performance Manager 5.0

The main thems where related to the IT innovation, where 84% of global executives believe innovation is extremely important to their growth strategies, but 94% are unsatisfied with their innovation performance!

The VMware’s approach to cloud application management is based on move towards cloud and use of modern application frameworks and methodologies according with this schema:

Reading Time: 2 minutes

After few months after the Veeam Backup & Replication v6.1 announce (one year after the v6.0 announce), today Veeam has announced the new release of their products.

Backup & Replication v6.5

New support matrix for recent virtualization products:

continue reading…

Reading Time: < 1 minute

My speech of today vBrownbag Tech Talks is:

  • Tuesday 11:15 – 11:30Challenges for Virtualizing Small Business

To follow the talk:

Reading Time: 2 minutes

In some previous posts I’ve described the Dell KACE product family, included the Dell KACE – K1000 and KACE – K2000 products.

As I’ve written, one of the limit of the K1000 was the lack of (official) support for mobile device. This limit will be filled soon (estimation release data is Oct 9, 2012) with a new product:

Single-step secure setup that gets you up-and-running in minutes continue reading…

Reading Time: 5 minutes

In the previous post I’ve described the challenge in the SMB segment and some possible scenarios. And how is VMware addressing this challenge?

One of the news of the last VMworld, was the attention of the SMB segment with several sessions specific for it, group discussions, business cases and so on. But it’s not limited to VMworld, the attention is growing due to the challenge of fit in the the SMB requirements (that in most cases are quite similar to the enterprise requirements!) and the constrains (where usually are limited budget and limited IT stuff) and apply at this period of financial chrysis.

VMware has also a web page dedicated for the datacenter solutions specific for SMB (and also a blog area and a specific section for ROBO), where the entry level are the vSphere Essential bundles. More interesting is a document (VMware vSphere SMB Solutions Brief) with several interesting information and suggestion, and also with this possible schema:

Suite and bundles

As you can see, most of the VMware’s virtualization solutions for SMB are around the Essential+ bundle (or the specific version designed for ROBO scenarios).

But isn’t the only option: the new Acceleration Kit Standard is now cheaper (considering that it’s only for 6 sockets, but it will include a vCenter Server Standard instance) and there is also a specific bundle of Acceleration Kit Standard with Operations Management (good for MB segment or for the main office in a ROBO scenario).

About the new features included in Essential Plus bundle, there are also (from 5.1 version):

New features specific of the Standard edition (that include also new features of Essential+):

  • vShield Zones
  • Fault Tolerance
  • Storage vMotion

VSA 5.1

As described in a previous post, VSA can provide same benefit a shared storage (VMware HA, vMotion, …) with a smaller cost.

Compared to an entry level enterprise storage (like Dell MD3xxx or HP P2000 series, with a completely redundant solutions) you can remove the storage costs (considering also that some software features may require additional fee), but of course you have to spend on more disks (considering the replication, but you have to consider that sometimes the storage’s disks cost more that servers’s disks) and on good RAID controllers.

This solution could be great on small environment and in ROBO scenarios (in this case vSphere Replication could be use to handle the VM DR) considering that one instance is already included in each vSphere bundle (except the Essential one).

For more information see: New Features of the vSphere Storage Appliance version 5.1.

VMware Go Pro

Go Pro makes simple to deploy and extend virtualization, and to manage and protect your infrastructure, and it is specifically designed to help small and midsize businesses begin or extend virtualization efforts.

It improve the protection, scalability and reliability of your IT infrastructure with VMware Go Pro, a cloud-based virtualization and IT management solution built specifically for small and midsize businesses.Seems that on Q1 2013, it may include also a VM backup solution!

There is also an active promotion: every purchase of an Essentials Kit includes Go Pro (30 VM coverage) for cloud-based patch management.

VMware vCenter Protect

This product help to get centralized patch management and asset inventory for Windows and third party applications for both virtual and physical machines with vCenter Protect Standard. Add centralized antivirus, power management, and ITScripts with vCenter Protect Advanced. Reduce cost and complexity with an integrated approach to IT security and compliance.

Good for large enviroment, it could be useful also for MB segment as described on VMworld Reflection for Small-Midsize Businesses blog post.

Zimbra

This could be a good example of a SaaS solution (for private or public cloud). Also the availability of different clients for different devices (and also a web client) can help in a migration to new device scenarios.

Pricing

There are some interesting aspects in the new price list of the vSphere 5.1 suite.

Firts, without the vSphere 5 vRAM Entitlement you can push more on a scale-in (or vertical scaling) on hosts to reduce their number. This could be interesting in the MB segment, considering also the new servers (see, for example, a Dell PowerEdge R720) that have great expandibility, both on memory, card, but also on disks (if you plan to use shared storage).

For more information see the page: Compare VMware vSphere Pricing.

Virtualization vs. Cloud?

VMware has several solutions for the virtualization approach in the SMB. Of course there is also the free Hypervisor solution or the Essential bundle that could be a really first step (I think that, for very low budget, a two nodes single socket solution without shared storage and with a replication+backup software could be a good entry point).

But what about the cloud solutions? Exept the Go Pro solution, actually VMware doesn’t have an SMB version of vCloud Director to build private or hybrid cloud, but you can use the vCloud Connector to build a simplified version of an hybrid cloud.

Also, for some specific scenarios (like the CoIT case), a “public-like” approach could be a solution, considering that the VSSP program can change the entire (software) infrastructure cost in a “pay per use” model, with the advantages of including also several enterprise products.

Reading Time: 7 minutes

The challenge!

SMB segment could be a (big) challenge due to the following reasons:

  • Requirements: in most cases are the same of the enterprise segment. For example the required availability and SLA are really close and may imply similar solutions to achieve it.
  • Constraints: are really different and in most cases very strictly. For example budget, but also the IT staff and skills.
  • Evolution: and SMB may have big trend in evolution (or involution).

Note that also in SMB, disaster recovery, business continuity, availability and security aspects have still to be considered.

This kind of market remain still interesting, considering the number of the companies and also the fact that 60% of them are still on physical environment. According to a research (Forrester Business Continuity And Disaster Recovery Are Top IT Priorities For 2010 And 2011), for the SMB the top priorities are business continuity and disaster recovery (BC/DR), at the first place, and consolidation of the IT, at the second place.

continue reading…

Reading Time: 5 minutes

VSA (VMware vSphere/Virtual Storage Appliance) is a solution, introduced in version 1.0 with vSphere 5.0, to transform local storage in shared storage. Basically a VA on each node use a local datastore to export it via NFS. But most important is also make a replication to another node.

I’ve already talk about it in a VCP exam objective (VSA 1.0 questions are part of VCP5 exam), but honestly the VSA 1.0 had several disadvantages:

  • Cost: from my point of was too high (expecially for the position of this kind of solution).
  • Disks usage: is first release was necessary a local RAID1+0, so your storage space was reduced to 25% (considering also the replication). To be honest on January 23rd, 2012, VMware lifted this restriction and allow now support both RAID 5 (single parity disk) and RAID 6 (dual parity disks) configurations. Also the cluster storage capacity cannot be resized after deployment.
  • vCenter Server dependency: that made difficult to have a virtual vCenter on the VSA.
  • Storage limits per host: max 6 TB with 3 TB disks or max 9TB with with 2 TB disks.
  • Scalability: is limited to a maximum of 3 nodes (and of course a minimum of 2).

With the new version, that has been renamed in VSA 5.1, most of those limits has been removed or changed. But scalability still remain the same!

Note that VSA 5.1 can run both on vSphere 5.0 and 5.1 and also supports the single sign-on (SSO) functionality found in vSphere 5.1.

Cost

Finally VSA has been included in each vSphere 5.1 bundle (but only one instance), except the Essential one. So you can have it at no extra cost!

Disks usage

VSA 5.1 now supports the online increasing of storage capacity of a VSA cluster. For existing customers (VSA 1.0) there are 3 possibilities:
  • Convert RAID 10 to RAID 5/6.
  • Add more disks, destroy the current RAID and recreate new RAID.
  • Add more disks and create new RAID, keeping the data

Any unused storage on the local VMFS datastores can now be reclaimed via a new ‘Increase Storage’ option in the UI.

Storage limits

VSA 5.1 maximum with 3 TB drives:

  • 8 disks of up to 3TB capacity in a RAID 6 configuration (no hot spare)
  • 18TB usable by the VMFS-5 file system per host
  • Across three hosts, a total business usable storage of 27TB

VSA 5.1 maximum with 2 TB drives:

  • 12 local disks of up to 2TB in a RAID 6 configuration (no hot spare)
  • 16 external disks of up to 2TB in a RAID 6 configuration (with hot spare)
  • VMware supports maximum VMFS-5 size of 24TB per host in VSA 5.1
  • Across three hosts, total business-usable storage of 36TB

vCenter Server dependency

Now vCenter Server can run directly on the VSA 5.1 cluster, where it can be installed on local storage (one part), then the VSA needs to be configured (on remaining local storage), then SvMotion can be used (if licensed) to move the vCenter VM to the VSA cluster. Additionally, the local storage (where vCenter lived before the move) can be used by leveraging the new Resize function, which is available through UI.

Remote Office/Branch Office (ROBO) Support

VSA 5.1 now enables multiple VSA clusters to be managed by a single remote vCenter Server instance. The vCenter Server instance can also reside on a different subnet from the VSA cluster (limit in VSA 1.0). Each VSA storage cluster is located in its own unique datacenter object in the vCenter Server inventory.

The two-node VSA storage configuration uses a special “VSA Cluster Service,” which typically runs on the vCenter Server instance. It performs like a cluster member and is used as a tiebreaker to ensure that there still would be a majority of members in the cluster if one ESXi host/VSA member were to fail. The new designed tiebreaker for two-node configurations still can run as a vCenter Service in VSA 5.1. However, in a two-node ROBO deployment, the vCenter Server instance managing VSA is now remote. This means that the VSA tiebreaker code must be locally located at the branch office and not on the central vCenter Server instance.

In VSA 5.1, the tiebreaker code can be installed at the branch office. The administrator provides details on the location of tiebreaker code during VSA deployment, and the VSA installer validates these settings. The tiebreaker is simply a set of Java Archive (JAR) files. The JAR is a way of distributing a Java program, along with all its libraries. VMware provides installers to run the JAR file on a user-supplied platform, either Windows or Linux. The administrator is responsible for configuring the platform, including installing the base operating system (OS). The installer then introduces and sets up the tiebreaker code. VMware provides installation documentation for all the platforms that support running the tiebreaker code.

Finally there are also specific functions to remote install and upgrade VSA.

More information

© 2025-2011 vInfrastructure Blog | Disclaimer & Copyright