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
↑ https://aws.amazon.com/blogs/database/cross-region-disaster-recovery-of-amazon-rds-for-sql-server/
| Line 12: | Line 12: | ||
* [[Amazon Regions]] | * [[Amazon Regions]] | ||
* [[CloudEndure]] | * [[CloudEndure]] | ||
| + | * [[Cross-Region disaster recovery of Amazon RDS for SQL Server]] <ref>https://aws.amazon.com/blogs/database/cross-region-disaster-recovery-of-amazon-rds-for-sql-server/</ref> | ||
== See also == | == See also == | ||
Revision as of 15:17, 14 July 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
- Cross-Region disaster recovery of Amazon RDS for SQL Server [2]
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:
