You may want to star this request: http://code.google.com/p/googleappengine/issues/detail?id=776
On Oct 20, 1:25 pm, Tom <[EMAIL PROTECTED]> wrote: > A continuing concern on my part is how I am going to manage backups, > revisions, and integrity of the data behind my app. There are > numerous ways that the data can get corrupted (programming errors, > malicious users, etc.). With any complexity of objects and volume of > data, using bulk upload/download seems a bit awkward. There are > several issues logged already for this (eg. Issue > #59http://code.google.com/p/googleappengine/issues/detail?id=59). I'd > like to throw out some suggestions for consideration. > > Provide a mechanism to snapshot an app's datastore in its entirety, > keeping it on Google's servers. Commands to switch between versions > would then be provided (in header of app.yaml?). The additional > storage space could be counted against the limits currently provided > for an app. (I'd pay for backup!) > > Provide a mechanism to download the datastore in its entirety to a > local machine (as Issue #59 suggests). Count the bandwidth for such > an operation against the app's limits. Would there be a CPU hit as > well? The reciprocal upload method would of course be required. > (Database processing could then be done on non-Google server > machines.) > > Something simple but capable of giving an app owner peace of mind > would be most welcome! > > Thanks! > Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
