Book Image

Learning Neo4j 3.x - Second Edition

By : Jerome Baton
Book Image

Learning Neo4j 3.x - Second Edition

By: Jerome Baton

Overview of this book

Neo4j is a graph database that allows traversing huge amounts of data with ease. This book aims at quickly getting you started with the popular graph database Neo4j. Starting with a brief introduction to graph theory, this book will show you the advantages of using graph databases along with data modeling techniques for graph databases. You'll gain practical hands-on experience with commonly used and lesser known features for updating graph store with Neo4j's Cypher query language. Furthermore, you'll also learn to create awesome procedures using APOC and extend Neo4j's functionality, enabling integration, algorithmic analysis, and other advanced spatial operation capabilities on data. Through the course of the book you will come across implementation examples on the latest updates in Neo4j, such as in-graph indexes, scaling, performance improvements, visualization, data refactoring techniques, security enhancements, and much more. By the end of the book, you'll have gained the skills to design and implement modern spatial applications, from graphing data to unraveling business capabilities with the help of real-world use cases.
Table of Contents (24 chapters)
Title Page
Credits
About the Authors
Acknowledgement
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface

Disaster recovery


Sometimes, servers fail to serve for so many possible reasons. If a read replica fails, so be it; replace it or add another one, it will get the data as it joins the cluster. If a core server fails, the cluster handles it too. The graph is recreated via the other cores. You can see it yourself:

  1. Stop a core server.
  2. Go through its folders, and remove data/databases and data/cluster-state.
  3. Restart it (the more data, the more time it will take).
  4. Watch the log file to see when it is ready.
  5. Go to its Neo4j browser.
  6. Be amazed.

This is so simple, it reminds me what a speaker said at a graph connect conference: "We do the hard things so you don't have to."

If all your core servers fail, first find the reason, for it is very unlikely on a real state-of-the-art deployment. If you want to roll your graph to the date of a previous backup, the steps are as follows:

  1. Stop all instances (core and replicas).
  2. Perform a backup restore on each instance (with the same backup file).
  3. Restart all instances...