On Friday, March 1, 2013 3:55:16 AM UTC-6, Lasse Westh-Nielsen wrote:
Although a full backup allows for continued operations on the target instance --- it required? Can I configure neo4j to NOT apply any updates that occurred AFTER the backup command had been issued?
Lasse,
Do you have to stop the instance before copying the graph.db directory?
Is there a problem with simply copying the graph.db directory while the
instance is still running?
But I am wondering what your use case is?
I am trying to make a hot backup of both a
mysql database and a neo4j database that are tightly coupled. It tricky
because updates to one may ultimately result in updates to the other
... it is easy to make backups that are out of sync and I am trying to
guarantee they are in sync.
Although a full backup does not require any locking ... is it possible to invoke a database-wide lock? If so, how?
I don't believe so. You could do it from your application, require all queries to lock a particular node?
Do you mean to lock each and every node on a node basis? Basically, iterate over every node and lock it?