log for any errors Configuring metrics and alerts for Neo4j is addressed in

Log for any errors configuring metrics and alerts for

This preview shows page 20 - 22 out of 26 pages.

After the awslogs service is started, check the /var/log/awslogs.log for any errors. Configuring metrics and alerts for Neo4j is addressed in this Neo4j knowledge base article 5 . Online Backup Neo4j can be backed up while it continues to serve user traffic (called “online” backup). Neo4j offers two backup options: full or incremental. These strategies can be combined to provide the best mix of safety and efficiency. Depending on the risk profile of the system, a typical strategy might be to have daily full backups and hourly incremental backups, or weekly full backups with daily incremental backups. As the name suggests, a full backup will clone an entire database. These are the characteristics of a full backup: Copies database store files. Does not take locks. Replays transactions run after backup started until end of store file copy. At the end of a full backup, there is a consistent database image on disk. This backup file can be safely stored away, and recovering to this backup is as simple as copying the database files back into the Neo4j data directory (typically <Neo4j home>/data/graph.db ).
Image of page 20
Amazon Web Services – Running Neo4j Graph Databases on AWS Page 17 After the backup has been created, the recommendation is for the backup to be copied from the EC2 instance that ran the process into stable, long-term storage. Amazon S3 provides a range of suitable archive storage platforms depending on your needs. The backup can be copied to Amazon S3 directly, or you can achieve the same level of durability by using an EBS snapshot, which is stored in Amazon S3 automatically. Amazon EBS is a network-shared storage service that can be mounted from any EC2 instance. Amazon EBS provides persistent block-level storage volumes that are automatically replicated within their Availability Zones to protect from component failure, offering high availability and durability. A snapshot can be created from an EBS volume, which not only provides the ability to restore data in the future, but also provides the ability to mount that volume to another EC2 instance. This process can greatly decrease the time that it takes to add an additional Neo4j node to the cluster. A side benefit of EBS snapshots is that they are persisted to Amazon S3, which means that they are protected for long-term durability. Volumes can be created from snapshots in any Availability Zone in the Region, and snapshots can also be copied across Regions to provide an even greater level of durability. Amazon S3 provides three tiers of storage optimized for cost versus frequency of access. Amazon also provides lifecycle policies that can automatically transition objects from Amazon S3 Standard to Amazon S3 Infrequent Access and AWS Glacier (for long-term archive) after a specific amount of time has elapsed. Lifecycle policies streamline the archival and cost-saving process so that you don’t have to manually transition objects or pay increased storage fees for cold data. In addition to simplifying storage maintenance, Amazon S3 also supports versioning, which can help organize redundant backups based on timestamp.
Image of page 21
Image of page 22

You've reached the end of your free preview.

Want to read all 26 pages?

  • Spring '16
  • Databases, Neo4j, Amazon Web Services, AWS, Amazon Elastic Compute Cloud

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

Stuck? We have tutors online 24/7 who can help you get unstuck.
A+ icon
Ask Expert Tutors You can ask You can ask You can ask (will expire )
Answers in as fast as 15 minutes