BrainBlog for Kasten by Jason Bloomberg
What are the differences between Kubernetes data protection and the more traditional data protection offerings, even though such products deal with virtualization and cloud scenarios as well as traditional on-premises data protection?
Here are five salient differences between such products — differences that go beyond data protection, highlighting some of the fundamental strengths of cloud native computing generally.
Difference No. 1: Data Protection Centering on Metadata vs. Data Protection Centering on Data
At the heart of data protection lies backup and restore functionality. There is more to data protection than these two capabilities, but without backup and restore, there is no protection whatsoever.
In traditional environments, which for the purposes of this article include virtualization and cloud as well as various on-premises environments, backup and restore are focused on persistent data and the storage that contains it.
Kubernetes data protection, in contrast, focuses on metadata as well as the underlying data.
Kubernetes is essentially a declarative, configuration-based container orchestration platform. Providing data protection to those configurations and other metadata, including resource definitions, Helm charts and other files is central to the Kubernetes data protection challenge.
Read the entire BrainBlog here.
