![]() Getting back to Datos IO and Rubrik, what does this mean for these acquisitions and the industry in general? First, I think there’s a PR angle to this. With shared backup metadata, restoring in multiple locations no longer becomes a problem. Many vendors (Rubrik and Cohesity included) offer cloud support, either as a repository or as a location to run a virtual appliance. All of the backup data hits the cloud and so restores would be managed from there. Where does the backup take place? If I need to restore from a historical backup that was “on-prem”, do I have the access, network bandwidth and connectivity to do that?Ĭompanies like Druva are meeting that challenge by being cloud-centric. ![]() Imagine my application has run “on-prem” for many days or weeks and then gets moved to the public cloud. Public cloud represents another challenge. This isn’t what replication is intended for. Yes, it’s possible to create database replicas, but backup systems effectively create many backup images over time. The ability to replicate and shard data provides resiliency, but not protection against data corruption. HybridĪs we move to a hybrid and multi-cloud world, how will backup change? Already NoSQL and eventually consistent databases like MongoDB represent a challenge for data protection. Instead, systems are replaced over time, with some lasting many decades. Enterprise deployments rarely sweep the floor as new technology is deployed. In larger enterprises, it’s more likely that there’s “one of everything” installed. However, these systems typically have a greater heritage and so offer support for a wider set of platforms. Many “legacy” backup platforms still operate as single servers plus disk shelves, although some do offer higher availability.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |