The issue with appcfg.py exporting is that you need to write an Exporter class per entity, etc, etc. It's prone to errors not to mention that it's a fair amount of work.
Any professional web endeavor requires contingency plans to recover data in case there is an app error that incorrectly deletes, modifies data. With the exporter thing, you have to write a lot of code, have to export everything since you can't export entities added or updated since last export. Also the data goes out of app engine, so recovery will take a long time. A real solution is to have a backup service to take snapshots and keep them in app engine world. I would bet that this is something that people will be willing to pay for since day one. The critical component of any web app is the data, so please prioritize backup/ recovery feature. I see something related to this as the last item in the road map. I honestly can't believe that an alerting system for exception (which can be implemented with a couple of lines of code in the application) can be possibly more important that backup / recovery mechanism. http://code.google.com/appengine/docs/roadmap.html On Jul 30, 8:31 pm, "Nick Johnson (Google)" <nick.john...@google.com> wrote: > Hi johnP, > > GAEBAR is certainly one option. The other option is to use the bulk > exporting functionality of appcfg.py. Or, you can roll your own using > remote_api. > > -Nick Johnson > > > > On Thu, Jul 30, 2009 at 7:24 PM, johnP<j...@thinkwave.com> wrote: > > > Thanks - those links to ways of recovering source-code. > > > What I'm interested in is hearing Google's recommendation on backing > > up and restoring data. GAEBAR is an option, I know. Is the official > > advice from Google to use it? > > > Backing up and restoring of data seems to be a significant-enough > > issue to warrant some sort of official guidance:) > > > johnP > > > On Jul 30, 10:14 am, Holger <w...@arcor.de> wrote: > >> You may be interested in this > >> threadhttp://groups.google.de/group/google-appengine/browse_thread/thread/e... > > >> Could just use the zipme script to implement some download capability > >> in case your own source got > >> lost.http://www.manatlan.com/blog/zipme___download_sources_of_your_gae_web... > > >> Rename zipme (in app.yaml as well as in script) to something else and > >> use strong passwords to minimize the risk being hacked. > > >> On Jul 30, 6:37 pm, johnP <j...@thinkwave.com> wrote: > > >> > Does Google provide any best-practices for implementing a backup > >> > process? > > >> > Thanks! > > >> > johnP > > >> > On Jul 30, 2:37 am, "Nick Johnson (Google)" <nick.john...@google.com> > >> > wrote: > > >> > > Hi, > > >> > > It's up to you to take backups of your data. We take regular backups > >> > > of the > >> > > datastore, but we're unable to restore individual users' data. > > >> > > -Nick Johnson > > >> > > On Thu, Jul 30, 2009 at 5:22 AM, DiveIntoGAE <taogf1...@gmail.com> > >> > > wrote: > > >> > > > If I delete some important datas by mistake, how can I recover > >> > > > them? > > >> > > -- > >> > > Nick Johnson, Developer Programs Engineer, App Engine > > -- > Nick Johnson, Developer Programs Engineer, App Engine --~--~---------~--~----~------------~-------~--~----~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
