Lets assume that I have a "properly" written AppEngine application (writes 
to the datastore are wrapped into transactions, tasks are put in the task 
queue and retried, etc) and I want to make a "consistent" backup (ie. I 
don't want half-committed transactions in the backup). The documentation 
[1] suggests disabling writes and running a backup from the datastore 
admin, which sounds sensible but fails because the backup map-reduce job 
itself needs to write to the datastore. Any other suggestions?

On a related note, the backup is just a dump in protobuff format. I can 
create a hacky python script to extract the data, but is there a 
recommended/supported way to transform it into something like JSON or CSV?

Attila

[1] 
https://cloud.google.com/datastore/docs/console/datastore-backing-up-restoring

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/2629485a-ccbc-4705-aeaa-5008964220f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  • [google-appengine]... Attila-Mihaly Balazs

Reply via email to