docs: add ec2 BR (#1058)

Co-authored-by: Yiran <cuiyiran3@gmail.com> Co-authored-by: Jeremyhi <jiachun_feng@proton.me>
GreptimeTeam · Jul 16, 2024 · 5d2b8b5 · 5d2b8b5
1 parent 80b8082
commit 5d2b8b5
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 0 deletions.
diff --git a/docs/nightly/en/user-guide/operations/disaster-recovery/overview.md b/docs/nightly/en/user-guide/operations/disaster-recovery/overview.md
@@ -58,6 +58,8 @@ If the Standalone is running on the local disk for WAL and data, then:
 * RPO: depends on backup frequency.
 * RTO: doesn't make sense in standalone mode, mostly depends on the size of the data to be restored, your failure response time, and the operational infrastructure.
 
+A good start is to deploy GreptimeDB Standalone into an IaaS platform that has a backup and recovery solution. For example, Amazon EC2 with EBS volumes provides a comprehensive [Backup and Recovery solution](https://docs.aws.amazon.com/prescriptive-guidance/latest/backup-recovery/backup-recovery-ec2-ebs.html).
+
 But if running the Standalone with remote WAL and object storage, there is a better DR solution:
 ![DR-Standalone](/DR-Standalone.png)
 

diff --git a/docs/nightly/zh/user-guide/operations/disaster-recovery/overview.md b/docs/nightly/zh/user-guide/operations/disaster-recovery/overview.md
@@ -66,6 +66,8 @@ GreptimeDB 将数据存储在对象存储（如 [AWS S3](https://docs.aws.amazon
 * RPO：取决于备份频率。
 * RTO：在 Standalone 没有意义，主要取决于要恢复的数据大小、故障响应时间和操作基础设施。
 
+选择将 GreptimeDB Standalone 部署到具有备份和恢复解决方案的 IaaS 平台中是一个很好的开始，例如亚马逊 EC2（结合 EBS 卷）提供了全面的[备份和恢复解决方案](https://docs.aws.amazon.com/zh_cn/prescriptive-guidance/latest/backup-recovery/backup-recovery-ec2-ebs.html)。
+
 但是如果使用远程 WAL 和对象存储运行 Standalone，有一个更好的 DR 解决方案：
 
 ![DR-Standalone](/DR-Standalone.png)