Michael Cade is a Global Technologist for Veeam Software. Based in the UK, an IT Professional with over 14 years of industry experience with a key focus on Data Centre technologies including Virtualisation, Storage and Data Centre. Michael’s role at Veeam is to engage those new to availability technologies as well as those who are experts, speaking at events and sharing the Veeam vision and strategy of the company whilst providing feedback from the field into product management to shape the future success of Veeam Software.
Michael is very active around the social media sphere blogging and tweeting relevant technical content.
Michael is a member of several community programs including VMware vExpert, NetApp A-Team and Cisco Champions.
It’s safe to argue that, to date, the May 2018 implementation of the General Data Protection Regulation (GDPR) in the European Union, as well as the two-year ramp-up period that lead to the activation date, has elevated the status and industry press coverage of compliance-related issues more than any other data protection and compliance standard set by governing bodies. Veeam can help you stay compliant with ease.
Veeam offers a number of unique recovery processes for different scenarios and Veeam DataLabs Secure Restore is simply an optional enhancement included in many of these recovery processes. Let's explore what it brings to the table.
The end of general support for vSphere 5.5 was on September 19, 2018. There may be a number of questions for those customers that are still sitting on vSphere 5.5, like what version do I upgrade to? And what considerations do I need to make as part of the support upgrade path?
Today is End of General Support for vSphere 5.5! There have been lots of articles and walkthroughs on how to make that upgrade work for you, and how to get to a supported level of vSphere. But we wanted to touch on making sure your data is protected prior, during and after the upgrade events.
With the recent launch of Veeam Availability for Nutanix AHV, the third hypervisor to be supported by Veeam with an agentless approach, the most common question is around existing environments where the end user is required to keep an element of VMware or Hyper-V for existing workloads. This post will highlight how Veeam can be used to protect these multi-hypervisor environments.
In June 2017 we announced that we would be working on support for the Nutanix Acropolis Hypervisor (AHV) and shortly after in October we were able to show an alpha build of the code and demo what functionality would be arriving. Today we are excited and pleased to announce that our Hyper-Availability story is generally available for the entire Nutanix Enterprise Cloud platform, allowing us to protect all virtualized workloads – VMware vSphere, Microsoft Hyper-V and Nutanix AHV – in an application consistent state.
The ability to back up your data and recover is one thing, but let’s also consider the opportunity to leverage that backup data or even the ability to leverage the investment you made further with your production storage. Enabling other parts of your business to benefit from that data is even more important as we are in a world that is critically reliant on data. And that's where Veeam DataLabs step in.
We’ve covered how using a PowerShell script might come in handy for certain use cases. Now, let’s take the PowerShell script and show how it can be backed into your day-to-day Veeam Backup & Replication jobs.
Interested how you can use PowerShell to migrate your workloads to Microsoft Azure away from the on-premises configuration or create an isolated test and development environment? Let's explore a set of PowerShell scripts that will help you automate this routine.
Today Veeam announces Pure Storage as the next storage vendor to arrive onto this integration framework. With more and more businesses moving toward and adopting all-flash storage solutions that help those businesses to deliver more predictable performance across an ever more demanding business workload, it goes without saying that there is no requirement change for Always-On Availability. In fact, this increases the requirements around RTO and RPO SLAs.