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).
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?
The public cloud reality is much different than the hype. You only get from the public cloud what you bring to it. You need to bring your own security, performance monitoring, knowledge, and expertise.
I would like to thank Mike Laverick for reporting this typo and spurring thoughts on datasores. 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.
It is possible to get data protection for your virtual and cloud environments for free today, but there are are often limits. Trialware as it is called provides just enough of a taste for the data protection tool to convince you to buy the versions with more capabilities. However, for the SMB, the free versions may be good enough.