Amazon Neptune
User Guide (API Version 2017-11-29)

Overview of Backing Up and Restoring a Neptune DB Cluster

In the following sections, you can find information about Neptune backups and how to restore your Neptune DB cluster using the AWS Management Console.

Fault Tolerance for a Neptune DB Cluster

A Neptune DB cluster is fault tolerant by design. The cluster volume spans multiple Availability Zones in a single AWS Region, and each Availability Zone contains a copy of the cluster volume data. This functionality means that your DB cluster can tolerate a failure of an Availability Zone without any loss of data and only a brief interruption of service.

If the primary instance in a DB cluster fails, Neptune automatically fails over to a new primary instance in one of two ways:

  • By promoting an existing Neptune Replica to the new primary instance

  • By creating a new primary instance

If the DB cluster has one or more Neptune Replicas, then a Neptune Replica is promoted to the primary instance during a failure event. A failure event results in a brief interruption, during which read and write operations fail with an exception. However, service is typically restored in less than 120 seconds, and often less than 60 seconds. To increase the availability of your DB cluster, we recommend that you create at least one or more Neptune Replicas in two or more different Availability Zones.

You can customize the order in which your Neptune Replicas are promoted to the primary instance after a failure by assigning each replica a priority. Priorities range from 0 for the highest priority to 15 for the lowest priority. If the primary instance fails, Neptune promotes the Neptune Replica with the highest priority to the new primary instance. You can modify the priority of a Neptune Replica at any time. Modifying the priority doesn't trigger a failover.

More than one Neptune Replica can share the same priority, resulting in promotion tiers. If two or more Neptune Replicas share the same priority, then Neptune promotes the replica that is largest in size. If two or more Neptune Replicas share the same priority and size, then Neptune promotes an arbitrary replica in the same promotion tier.

If the DB cluster doesn't contain any Neptune Replicas, then the primary instance is recreated during a failure event. A failure event results in an interruption during which read and write operations fail with an exception. Service is restored when the new primary instance is created, which typically takes less than 10 minutes. Promoting an Neptune Replica to the primary instance is much faster than creating a new primary instance.

Backups

Neptune backs up your cluster volume automatically and retains restore data for the length of the backup retention period. Neptune backups are continuous and incremental so you can quickly restore to any point within the backup retention period. No performance impact or interruption of database service occurs as backup data is being written. You can specify a backup retention period, from 1 to 35 days, when you create or modify a DB cluster.

If you want to retain a backup beyond the backup retention period, you can also take a snapshot of the data in your cluster volume. Storing snapshots incurs the standard storage charges for Neptune. For more information about Neptune storage pricing, see Amazon Neptune Pricing.

Because Neptune retains incremental restore data for the entire backup retention period, you only need to create a snapshot for data that you want to retain beyond the backup retention period. You can create a new DB cluster from the snapshot.

Note

  • For Amazon Neptune DB clusters, the default backup retention period is one day regardless of how the DB cluster is created.

  • You cannot disable automated backups on Neptune. The backup retention period for Neptune is managed by the DB cluster.

Backup Window

Automated backups occur daily during the preferred backup window. If the backup requires more time than allotted to the backup window, the backup continues after the window ends, until it finishes. The backup window can't overlap with the weekly maintenance window for the DB instance.

During the automatic backup window, storage I/O might be suspended briefly while the backup process initializes (typically under a few seconds). You might experience elevated latencies for a few minutes during backups for Multi-AZ deployments.

If you don't specify a preferred backup window when you create the DB instance, Neptune assigns a default 30-minute backup window. This window is selected at random from an eight-hour block of time per Region. The following table lists the time blocks for each region from which the default backups windows are assigned.

Region Time Block
US West (Oregon) Region 06:00–14:00 UTC
US East (Ohio) Region 03:00–11:00 UTC
US East (N. Virginia) Region 03:00–11:00 UTC
EU (Ireland) Region 22:00–06:00 UTC