Is the backup licensing model about to change? While I was at VMworld in San Francisco, I really took notice of all the different Recovery-as-a-Service (RaaS) options were available and believe this service has really reached it maturity. The amount of options and services available seems to have really taken a solid leap forward in the last few years. Most all the companies follow the same type of licensing model in that the software is licensed by the number of agents that are deployed in the environment, the number of hosts or the amount of data being backed up. Most all the companies except for one particular company I talked to.
The next generation of data protection is not just about backup or replication into and out of the cloud, but about inexpensive recovery directly into a cloud in a hypervisor agnostic manner. Recovery is the key to backup and while we spend many hours ensuring that our backups happen in a timely manner, we spend very little time testing those backups and ensuring that recovery can happen at any time for any workload, not just those that are mission critical. Next generation data protection must also be extremely simple to use, setup, and configure. Is your data protection tool a next generation tool or lost in the past somewhere?
VMworld 2013 is upon us and one of our tasks is to figure out which vendor’s booths to go see. With over 230 booths to choose from this is a daunting task. If you are interested in finding creative new solutions to your management, monitoring, deployment, security, data protection, and desktop management problems, this list will help you.
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.
In a recent set of announcements the make virtualization backup and data protection companies have announced support for tape. Tape has always been supported indirectly by virtualization backup companies such as Veeam, Quantum, and PhD Virtual as well as directly by Symantec, HP, CommVault, etc. It is interesting to note that there is a convergence on tape support using two distinct methods. The first is to add support for tape libraries directly into their products: Veeam. The second is to add tape support by better integration with their existing product suite: Quantum. Even so, we know that tape still reigns for storing of large amounts of data. We just cannot seem to be rid of it nor do I think we ever will.
Data Protection and patch management of virtual desktops, while not a sexy topic, is one that should happen on a regular basis within any organization implementing or working to implement virtual desktops. Recently, we have been testing virtual desktop software and there is a huge difference between patching and protecting data in a small number of instances and 1000s of instances. There are scale considerations as well as ease of use for file level and system recovery as well as issues with patching virtual desktops (not to mention other security issues).
There is a dilemma for all tenants of a public or private cloud: Scope. For the tenant, they want everything to be in scope. For the Cloud Service Provider (CSP) they want to limit scope to the bare minimum. What does it mean for a Cloud to be ‘PCI Compliant’ and why is this a requirement for some tenants. The real issue, is what is in scope for PCI-DSS while your data is in the cloud and how can you as the tenant meet those requirements.
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?