The Blog

While many organizations feel adequately protected, many security suites, including some of the most popular ones, do not effectively protect against these strains of ransomware.

Today I was looking forward to sitting down and working more on Zerto DR into Azure. I had my schedule (and more importantly my mind) clear and ready to go. I woke up checked email, shuttled the kiddos off to school and grabbed a bite. Everything was ready! Wrong!

I’m not suggesting demos are bad, just that you shouldn’t become mesmerized by a slick demo. This is particularly important when it comes to Backup and DR to the cloud.

Imagine if every time you swapped out an old server you had to keep the old server sitting around and powered up for the next 5 to 7 years. Ridiculous right, but that’s what many organizations do with their legacy backups.

One of the most powerful tools in the marketing arsenal is the check box. Does your solution do this? Absolutely, there’s the check box right there! Compare our solution to our competitors? See that, we have way more check boxes.

One of the biggest problems for businesses today is an absence of or gaps in business continuity. Business continuity allows business to continue operating during and after a disaster. A business continuity plan (BCP) is comprised of policies and procedures to help fulfill that goal.

One of the most common barriers to Docker adoption for production deployments is a misconception around data persistence, or lack thereof. While it is true that if you remove a Docker container it’s destroyed and the data is lost but that doesn’t have to be the case.

I recently attended the Netapp Insight conference in Las Vegas. There were a lot of great speakers and sessions but for my money, the best one was Best Practices and Deep Dive for VMware with SolidFire. The presenter for this session was Andy Banta, his title was Storage Janitor.

While working on another project I ran into an issue running the Cloud/VMware modules for Ansible. No mater what I did it appeared broken. Newer module features required a newer version of Ansible. But I was being denied, stuck at 1.8 and no amount of apt foo seemed to resolve the issue.