dont-boo-hoo-broken-vmware-snapshots-better-vmware-monitoring-solution

VMware snapshots can be seen as point in time copies (or little pictures) of a virtual machine’s disk file and the configuration the time they are created. Snapshots preserve the disk files content so that they can be reverted back to in the event that something goes wrong with the virtual machine. Snapshots are extremely helpful when upgrading or patching applications and servers, making it possible for the VMware admin to restore a machine when things go awry. 

When Good Snapshots Go Bad

Broken VMware snapshots

Snapshots are like little pictures of your virtual machines that you can revert to if something goes wrong with the VM. Unfortunately, if the snapshots go bad, there aren’t any snapshots of the snapshots, so you’re kind of stuck with lots of snapshots in memory but no way to restore your VMs or find the bad snapshots.

Sometimes, snapshots themselves go bad, meaning they aren’t any good for restoring the virtual machine that they are supposed to represent. Snapshots can become broken or invalid by any number of actions, most of which are completely outside the control of the system administrator. 

For example, certain backup software can cause a snapshot to be created and deleted. Also, VMware can choke up, causing an invalid snapshot that is hard to detect. 

These hard to find snapshots hide, taking up lots of memory for no good purpose at all. 

More Snapshots Means More Invalid Snapshots 

Usually, the more snapshots you’ve got, the larger the number of invalid or broken snapshots is. It’s not an uncommon problem at all, especially when working with VMware’s integrated vCenter Snapshots. In fact, more than 80 percent of all VMware vSphere environments are infected by broken and invalid snapshots. Many times, these bad snapshots are not able to be detected by VMware itself. 

A single delta file can get as large as the original VMDK, consuming many terabytes of your storage space. As everyone knows, storage is not cheap, and taking up storage needlessly is a big no no. 

When VMware Can’t Find Bad Snapshots for You

Snapwatcher inconsistent VM Snapshots

Snapwatcher can find those hidden snapshots and fix them or delete them, so that you can regain all of that valuable storage space.

Fortunately, there is a solution for finding, identifying, and deleting these bad snapshots so that you can free up memory and improve the operating environment for VMware. Opvizor, an US company, has developed a free solution so that VMware administrators can find and exterminate those bad snapshots. The product is called Snapwatcher.

One customer was able to reclaim close to 20 terabytes of storage space over time using the Snapwatcher tool. That’s a lot of memory to be eaten up with useless snapshots!

Get the Snapwatcher tool.

Snapwatcher by Opvizor Finds and Fixes Bad Snapshots 

Snapwatcher shows an overview of all of the snapshots in your vSphere environment. The software highlights the biggest snapshots, and sorts the snapshots (like broken VMware snapshots) by name, host, and virtual machine. In the work history section, you can tell how many snapshots have been fixed or corrected, along with how much storage space was recovered during the process. 

You can even establish your own rules for determining the conditions under which Snapwatcher will highlight the snapshots.

Let’s see how this works in real practice. Say a certain usage within a specific data store has been reached or that a particular snapshot reaches a certain predetermined size. The right snapshot can be highlighted, making it much easier on the VMware administrator. 

You no longer have to be tied down watching what your snapshots are up to. You can get all of the information you need to know quickly and easily within the Snapwatcher interface. When something does go wrong or gets broken, you can fix it simply and quickly with the Snapwatcher tool.

Problems Addressed by the Snapwatcher Product

Get VM snapshot problems addressed

It’s kind of like having a crew of little fix it guys hiding in your systems. Only it’s not quite that creepy, and the little guys don’t ask for overtime or file workers’ comp claims.

Snapwatcher can correct a number of problems, including any inconsistencies between the VMware snapshot manager and the actual snapshots, the most snapshot failures related to lock, and the ability to detect the MAC of a host and remotely unlock the file from the locking host. The fixing methods are built directly into Snapwatcher, making the admin’s job as easy as it can be. 

 Snapwatcher is even capable of determining when the backup software is still running so that it can make sure that not all of the lock files will be unlocked. One Snapwatcher user was able to recover a whopping 16 terabytes that were taken up by invalid and inconsistent snapshots!

Get Snapwatcher Today

You can sign up for Snapwatcher for free and get started freeing up valuable storage space in your VMware environment right now!

CNIL
Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud
PERFORMANCE MONITORING, LOG ANALYSIS, LICENSE COMPLIANCE!

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

Goal:

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.).

Implementation:

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

Goal:

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.

Implementation:

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

Goal:

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, …)


Implementation:

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

Goal:

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.

Implementation:

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

Goal:

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.

Implementation:

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.