Recently at Dell World, I was part of a conversation about what would be utopian disaster recovery and where we are today in the state of the industry. But where we are today is transforming, with a new name that encompasses many technologies. We are now using the term “data protection” (DP) to mean much more than just disaster recovery (DR), backup, business continuity (BC), replication, data loss prevention, and replication, but also the basic functions of confidentiality, such as encryption. The main goal of data protection is to provide a way to use your data as quickly as possible wherever it is needed and with minimal or no loss.
Articles Tagged with Zerto
In many cases, when we mention Data Protection for the Hybrid Cloud, we are usually talking about backing up to the cloud. The cloud becomes a repository of our backup images and in some cases those backup images can be launched within clouds that use the same technology. Being able to send data to the cloud is becoming table stakes for infrastructure as a service (IaaS) data protection. However, once we move outside the realm of IaaS to Platform or Software as a Service (PaaS or SaaS), data protection is hit or miss.
One aspect of SDDC that does not get a lot of attention is Data Protection, instead we are concentrating on SDN and automation. Yet, this leads me to Data Protection. There is a clear marriage between Data Protection and SDDC that needs to be added to any architecture. As with all things, we start with the architecture. Our SDDC architecture should also include data protection, but what data are we really protecting? Within SDDC there are three forms of data: tenant, configuration, and automation. Without one or the other, we may not be able to reload our SDDC during a disaster. What is required to get these three types of data, what really are these types of data? and how can we add data protection into SDDC cleanly?
A major aspect of virtualizing any business critical application is data protection which encompasses not only backup, but disaster recovery, and business continuity. It is imperative that our data be protected. While this is true of all workloads, it becomes a bigger concern when virtualizing business critical applications. Not only do we need backups, but we need to protect the business, which is where business continuity comes into play.
There have been quite a few new products announced in the last few months. Some I have received as briefings, others I have researched. These security and data protection products show the changing face of virtualization and cloud.
A typo report on twitter has lead me to a set of thoughts with respect to data. Where are your Datasores? What is a datasore? Unlike a Data Store which holds data, a datasore is a place where data becomes either painful to manage or protect. Or where the data exceeds your capability to handle it. A data sore should never happen, but with the explosion of data being moved, protected, managed, and mined we have exceeded certain limits of our existing set of tools. How do we find data sores and alleviate them? Does alleviating them require us to re-architect our entire data usage and storage mechanisms?