From fd2a2e862c905c3f6a9b50d777c7f8e9f659dce6 Mon Sep 17 00:00:00 2001 From: Akash Jain Date: Thu, 1 Oct 2020 18:59:30 +0530 Subject: [PATCH] docs: add documentation for clone backend --- wiki/content/slash-graphql/admin/clone.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 wiki/content/slash-graphql/admin/clone.md diff --git a/wiki/content/slash-graphql/admin/clone.md b/wiki/content/slash-graphql/admin/clone.md new file mode 100644 index 00000000000..c44f0c6e736 --- /dev/null +++ b/wiki/content/slash-graphql/admin/clone.md @@ -0,0 +1,17 @@ ++++ +title = "Cloning Backend" +[menu.main] + parent = "slash-graphql-admin" + weight = 7 ++++ + +Cloning a backend allows making a copy of an existing backend. The clone will be created with all the data and schema of the original backend present at the time of cloning. The clone will have its own endpoint and will be independent of the original backend once it is created. Any further changes in either backends will not reflect in the other. Currently, a clone can only be created in the same zone as that of the original backend. + +In order to clone your backend, click on the `Clone Backend` button under the [Settings](https://slash.dgraph.io/_/settings) tab in the dashboard's sidebar. + +You can also clone using the [Slash GraphQL CLI](https://www.npmjs.com/package/slash-graphql) as a two step process. + +1. Create a new backend. +2. Restore data into the new backend from the original backend. + +You can also perform the restore operation on an existing backend if you have an unused backend or want to resuse an existing endpoint. But note that the restore operation will drop all the existing data along with schema on the current backedn and replace it with the original backend's data and schema.