Released in March, vSphere 6 is another step in the direction toward a fully software-defined data center. In this environment, all of the infrastructure layers will be virtualized, and the virtual machine is the centerpiece of all the action. Policy will direct all of the provision, monitoring, and management tasks. The importance of any given application will dictate the amount of resources it is allotted and exactly how the SLA will be maintained, no matter what happens in terms of hardware and/or software failures. vSphere 6 is a small step for VMware, and a huge step for the software-defined data center. What will storage administrators get out of this new product?

All New for vSphere 6: VVOLs

VMware performance

VMware got the community exited about the concept of Virtual Volumes, aka VVOLs, way back in 2011 at VMworld, but the concept only came to fruition with this release of vSphere. At the same time, various storage vendors also announced support of VVOL within their own products, so it was a timely rollout for all. A simple way to visualize what VVOLs empower the provision, monitoring, and management of application storage at the machine level. VVOLs eliminate the mismatch of architecture between the storage and the virtual machine, empowering the admin to deliver precise, policy-based access to a virtual machine. Better yet, the resources can be redistributed as needed as application requirements change.

vSphere 6 Features Improvements to Replication

vSphere 6 makes full synchronizations more efficient for specific storage arrays by making it possible for vSphere to communicate with Replication in order to get storage allocation info and to reduce traffic on the network. It’s now much easier to distribute resources using Storage vMotion and DRS without having to violate RPOs to recover a virtual machine. (Note: Replication is not a part of VDP 6.0, which has a completely separate replication engine.)

vSphere 6 Features Improvements in Security & Data Protection

VMware performance

Data protection and security also got major enhancements with version 6. VMware released VMWare Data Protection Advanced (VDP-A) with the previous version, but the latest version combines VDP and VDP-A functionality. This version supports external proxies, and are able to be deployed in other vSphwere clusters. As many as 24 concurrent streams of backups are possible using external proxies, and it supports Red Hat Enterprise Linux Logical Volume Manager as well as Ext4 file systems. It’s free to those who use Essentials Plus Kit 6.0, vSphere with Operations Management 6.0, and vCloud Suite 6.0.

vSphere 6 Features Improvements in VSAN

Aside from VVOLs, VSLAN (Virtual SAN) just might be the most important improvements in vSphere 6. Both of these features allow the storage administrator to abstract and pool storage and services in order to provision, monitor, and manage storage based on policies and at the virtual machine level. Along with VSLAN, version 6 also features improvements in snapshots, clones, and the ability to create as many as 32 snapshots or clones for each virtual machine. This amounts to 16K in snapshots or clones for each cluster. There are also improvements in power and rack failures and added support for blade infrastructures.

Are you looking for superior VMware performance monitoring tools to go along with the improvements and enhancements to vSphere 6? Sign up for Snapwatcher today.

Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials


Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).


immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance


Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.


While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace


No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data


IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.


immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence


CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.


As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.