是否建议将实体从一个应用程序复制到另一个应用程序以备份数据?

发布于 2024-12-28 20:21:04 字数 390 浏览 1 评论 0原文

我指的是此处解释的数据存储区管理工具:http://code.google。 com/appengine/docs/adminconsole/datastoreadmin.html

本地备份的一种方法是使用bulkloader.py,但我更喜欢这种解决方案,因为您的数据保留在 Google 的云中,并且可以轻松地从云中传输应用程序到另一个使用管理控制台中的按钮逐个实体。考虑拥有两个应用程序,一个我可以每周手动备份,另一个实际为用户服务。备份应用程序可能会产生一些存储成本,但总体成本会很小,因为除非备份需要,否则不会使用前端/后端实例......

I'm referring tothe datastore admin tool explained here: http://code.google.com/appengine/docs/adminconsole/datastoreadmin.html

One way of backing up locally is by using bulkloader.py, but I'm liking this solution better as your data stays in Google's cloud and can be easily transferred from one app to the other using a button in the admin console on an entity by entity basis. thinking of having two apps, one that i can manually back up to every week, and another that actually serves users. The backup app might incur some storage costs but overall costs would be minimal as no front/backend instances would be used except as needed for the backups...

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

黑寡妇 2025-01-04 20:21:04

我当然不建议将一个 GAE 应用程序的数据备份到另一个应用程序。对我来说,备份有几个原因:

  1. 为了防止 Google 发生灾难性中断。
  2. 防止您的编程错误导致重大数据丢失。
  3. 防止您的 Google 帐户被撤销。

备份到另一个 GAE 应用程序对这些方面的作用相对较小。

  1. 如果您使用高复制数据存储区,那么您已经将您的数据分布在 Google 的云中,因此再次这样做似乎是多余的 - 但不是从高可用性的意义上来说。 Google 丢失您数据的唯一方式是发生灾难性灾难,在这种情况下,您的两个应用程序都可能处于危险之中。
  2. 如果您在本地备份数据,则可以存储历史快照。然而,如果您只是备份到另一个应用程序,则不会存储历史数据,因此您几乎无法防止程序员错误,除非您在错误发生和准备进行下一次备份之间捕获它。
  3. 如果 Google 无论出于何种原因终止了您的帐户,您都会丢失应用程序和所有数据。

最终,通过备份到另一个 GAE,您仍然可以将所有鸡蛋放在一个篮子里。您刚刚划分了您的篮子。如果您的数据非常重要,需要在应用程序外部进行备份,那么在本地或完全备份到另一个提供商也非常重要。无论如何,这就是我的意见。

Backing up one GAE app's data to another app is certainly not recommended by me. To me, there are a handful of reasons to backup:

  1. To safeguard against a catastrophic outage on Google's part.
  2. To safeguard against a programming error on your part that results in significant data loss.
  3. To safeguard against your Google account being revoked.

Backing up to another GAE app does relatively little on each of these.

  1. If you use the High Replication datastore, you're already distributing your data all across Google's cloud, so doing that again just seems redundant -- but not in the high availability sense of the word. The only way Google is going to lose your data is through some catastrophic disaster, in which case both of your apps may be in peril.
  2. If you backup your data locally, you can store historic snapshots. Whereas if you're simply backing up to another app, you aren't storing historic data, so you have little protection against programmer error unless you catch it in between the time the error happens and when you're going to do your next backup.
  3. In the event that Google, for whatever reason, kills your account, you lose both apps and all your data.

Ultimately, by backing up to another GAE, you still have all your eggs in one basket. You've just partitioned your basket. If your data is important enough to be backed up outside of your app, it's important enough to backup locally or to another provider entirely. That's my opinion anyway.

情深如许 2025-01-04 20:21:04

我们定期将数据备份到另一个应用程序以用作我们的开发环境,但正如其他人指出的那样,这并不能真正保护您的数据免受重大应用程序引擎灾难的影响(尽管这种情况不太可能......)。

我发现的用于灾难恢复的归档数据的最佳解决方案是使用 google 提供的 python 脚本将其拉到 EC2 或本地磁盘上。

We backup our data periodically to another application to use as our development environment, but as others pointed out that's not really protecting your data against a major appengine catastrophe (as unlikely as this is...).

The best solution I've found for archiving data for disaster recovery is to pull it down using the python scripts google provides either onto EC2 or local disk.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文