how-to-detect-95-of-your-broken-snapshots

81% of VMware vSphere environments are losing precious disk space to broken or invalid snapshots.

  We want to change that.

About 4 weeks ago we launched our beta version of Snapwatcher to help alleviate virtual machine administrators from having to constantly hunt and firefight broken snapshots to preserve disk space. Snapwatcher is the first automated solution that constantly monitors all snapshots across the whole VMware vCenter system to detect and fix any old, broken or invalid snapshots. It comes with a powerful but simple dashboard where you can manage hundreds of snapshots in one place. Whenever Snapwatcher removes or repairs a broken snapshot, you’ll get a progress report to see how much memory you’re saving.

We had seen from our own experience and our customers’ that broken snapshots were a huge pain point, but we’re very pleased with the reception of our beta launch. In less than 2 weeks we had over 700 beta testers download the free version of Snapwatcher.

Snapwatcher Enterprise Edition - Never miss Broken Snapshots

Our beta users gave us great feedback and insights, and helped us discover a few more scenarios which cause broken snapshots to occur. We’ve since added additional workflows to repair these specific types of broken snapshots, and now Snapwatcher can now detect all types of normal and bad snapshots and fix 95 out of 100 broken snapshots. Our beta testers also request that Snapwatcher be able to ignore certain VMs and their snapshots. These features will be available in the paid version of Snapwatcher.

We’re excited to announce that we’re launching a commercial version of Snapwatcher 2.0 on March 24th for only $499 per user. Snapwatcher 2.0 will track and log snapshot deletion and repair tasks executed over time, giving users a history of all their snapshots and remediation activities. Snapwatcher 2.0 also offers enhanced fixing of inconsistent or broken snapshots, detection of running backups, and more.

We’re still continuing to offer a free edition of Snapwatcher with some new improvements, but it will be limited to read-only functions like snapshot detection and size reporting.

You can find and purchase the commercial version of Snapwatcher at http://try.opvizor.com/snapwatcherent.

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.