Copy one AuraDB Instance to another

If you need to copy or clone your existing AuraDBinstance to another (for example, when doing a production refresh for development or staging), you have a couple of options.

1. Clone to another AuraDB Instance (Unavailable in the Free Tier as the instance limit is 1)

   • New AuraDB Instance

   • Existing AuraDB Instance

2. Manually export and import the data

Clone to another AuraDB Instance:

• Click the ellipsis in the desired source AuraDB Instance on the Aura console page.
  
• Clone:
  
  

• Clone to a new AuraDB Instance

  1. Click Clone to New and then AuraDB
     Note: Aura Enterprise users could select just Clone to New
  2. Please select the destination AuraDB Instance's size (ensuring it is at least as large as the source instance)
  3. Enter the name and select the destination Aura DB Instance's region. This does not need to be in the same region as your existing Aura DB Instance
  4. Check I understand and click Clone Instance.
     Note: The cost shown in the below screenshot is just an indicative example and should not be considered for actual estimates. The actual cost would vary depending on your Aura DB Instance's size and usage.
     
  5. The next screen will display the new AuraDB Instance's credentials. Please save them in a secured location and then click Continue.
  6. The new AuraDB Instance will be created and available in your Aura console.
  7. The new AuraDB Instance will go through stages like Setting up your database, Overwriting and Loading. The time taken for these steps to complete depends on multiple factors like the amount of data, including indexes and constraints, the capacity of the destination AuraDB Instance, etc.
     
     
  8. When all the steps are completed, the AuraDB Instance will show a Running state and is now ready to be used.

• Clone to an existing AuraDB Instance:

Caution: Cloning into an existing AuraDB Instance will replace all data. Please take a snapshot and export it if you want to keep the current data.

1. Click Clone to Existing and then AuraDB.
   Note: Aura Enterprise users could select just Clone to Existing
2. In the next screen, select the destination AuraDB Instance (ensuring it is at least as large as the source AuraDB Instance)from the drop-down and rename it if required:
3. Check I Understand and click Clone if you wish to proceed.
   
4. The destination AuraDB Instace will go through a few stages like Overwriting and Loading.
   The time taken for these steps to complete depends on multiple factors like the amount of data, including indexes and constraints, the capacity of the destination AuraDB Instance, etc.
   
   
5. When all the steps are completed, the AuraDB Instance will show a Running state and is now ready to be used.
   Note: The credentials to connect to the destination AuraDB Instance will be the same as earlier and would not be affected by the clone operation.

Manually export and import the data

• Follow the steps in the knowledge base article for exporting your data.
• Once you have downloaded the dump file you can proceed to import.

Create a new AuraDB Instance

• On the main Aura console page, choose Create an Instance
• Select the size of your new AuraDB Instance (ensuring it is at least as large as the original one) and the region you want it deployed in.
• This does not need to be in the same region as your existing AuraDB Instance.
  
• As always, copy the password that is displayed for future use. Let the creation complete before moving to the next step. 

Import to the AuraDB Instance just created

• The final step will be to import your data.
  Note: the AuraDB Instance being copied to will be overwritten in this step, so be certain you are working with the right one.
• If the dump file is smaller than 4GB you can do this in the Aura console otherwise please use the command line tool push-to-cloud. Please see the article for using push-to-cloud for more details.
• Open your new AuraDB Instance and click the Import Data tab. Then click the Choose file button to navigate to the location of the graph.db.dump file saved in the first step.
  
• You'll be prompted to confirm you want to overwrite all of the existing data; click Upload to continue. 

Wait for the import to complete

We recommend getting a coffee, tea, or other favourite beverage at this step. It will take anywhere from a few minutes for a small amount of data, to potentially an hour or more if you have an exceptionally large amount of data and a slow internet connection, for the import to finish. 

That's it, you now have a second copy of your AuraDB Instance to make use of. As always, use the blue button at the bottom of this page to contact us with any questions.