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
| Line 9: | Line 9: | ||
* [[BCDR]] | * [[BCDR]] | ||
* [[Veeam Backup & Replication]] | * [[Veeam Backup & Replication]] | ||
| − | * [[Zerto]] | + | * [[Zerto]] disaster recovery software for virtualized and cloud infrastructures. |
* [[Amazon Regions]] | * [[Amazon Regions]] | ||
* [[CloudEndure]] | * [[CloudEndure]] | ||
Revision as of 14:49, 20 June 2022
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]
Related terms
- BCDR
- Veeam Backup & Replication
- Zerto disaster recovery software for virtualized and cloud infrastructures.
- Amazon Regions
- CloudEndure
See also
- Disaster Recovery (DR), RTO, RPO
- Disaster Recovery, BCP, Cross-region, RTO, RPO, AWS Elastic Disaster Recovery (
aws drs) - BC, BCP, BCDR
- 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:
