Difference between revisions of "Disaster Recovery (DR)"
Jump to navigation
Jump to search
↑ https://medium.com/velotio-perspectives/the-ultimate-guide-to-disaster-recovery-for-your-kubernetes-clusters-94143fcc8c1e
Tags: Mobile web edit, Mobile edit |
|||
| Line 3: | Line 3: | ||
| − | [[Kubernetes]]: One way to deal with master failure is to set up multi-master Kubernetes cluster, but even that does not allow you to completely eliminate the Kubernetes etcd backup and restore, and it is still possible that you may accidentally destroy data on the HA environment. <ref>https://medium.com/velotio-perspectives/the-ultimate-guide-to-disaster-recovery-for-your-kubernetes-clusters-94143fcc8c1e</ref> | + | [[Kubernetes]]: One way to deal with master failure is to set up multi-master Kubernetes cluster, but even that does not allow you to completely eliminate the Kubernetes etcd backup and restore, and it is still possible that you may accidentally destroy data on the [[HA]] environment. <ref>https://medium.com/velotio-perspectives/the-ultimate-guide-to-disaster-recovery-for-your-kubernetes-clusters-94143fcc8c1e</ref> |
Revision as of 16:04, 23 February 2020
Kubernetes: One way to deal with master failure is to set up multi-master Kubernetes cluster, but even that does not allow you to completely eliminate the Kubernetes etcd backup and restore, and it is still possible that you may accidentally destroy data on the HA environment. [1]
See also
- Backups: Data corruption, Business continuity planning, Bacula, Commvault, NetBackup, Veeam, Storage Lifecycle Policy (SLP), TeamCity backup, Backup docker containers, HP Data Protector, Unitrends, Acronis, Veeam Backup & Replication, Disaster Recovery (DR), Point-in-time recovery, RTO, RPO, PITR, Rewind
Advertising:
