For this implementation, a user-case might be like this: Say the Neo4j DB goes down in 1 or more nodes, or I might suspect that important data has been corrupted/modified or deleted, or if I suspect someone in the organization purposely changed the data and I want to track the user down using the backups. With one of those scenarios in mind, I would be able to go back, using today's date, 5 days ago at 3:46 pm (8/23/14), and even after that go forward (8/25/14 at 2:29 am) and have all possible changes applied to my disposition.
I don't know either how EBS snapshots work, but if those snapshots can only ensure the data is clean when the DB is down, there it wouldn't work for me since the DB I have is running in a production environment Responding to your question Michael, basically what I want to achieve is have all data and transactions performed during a period of time available for me to use, in a more resource/time efficient way. Performing full backups every minute would consume ton of storage and ton of computing power. Current incremental backups overwrite the transaction logs, therefore losing the track of transactions applied up to that point. I personally think it would make sense to add these modifications/features -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
