From bf863d3d976fa7e0938791dae4c9147c961ec164 Mon Sep 17 00:00:00 2001 From: aman1403 <170030039@iitdh.ac.in> Date: Fri, 11 Sep 2020 18:40:32 +0530 Subject: [PATCH] Add rfc8040 urls for docs/getting-started-guide/persistence_and_backup.rst Signed-off-by: aman1403 <170030039@iitdh.ac.in> Change-Id: I8f1d2b6a0d1d09adff14d6221b2ab90dde98aef7 --- docs/getting-started-guide/persistence_and_backup.rst | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/getting-started-guide/persistence_and_backup.rst b/docs/getting-started-guide/persistence_and_backup.rst index f4245c43b..1e147d522 100644 --- a/docs/getting-started-guide/persistence_and_backup.rst +++ b/docs/getting-started-guide/persistence_and_backup.rst @@ -38,6 +38,10 @@ node, taking only the file name as a parameter:: POST /restconf/operations/cluster-admin:backup-datastore + or + + POST /rests/operations/cluster-admin:backup-datastore + RPC input JSON:: { @@ -65,4 +69,4 @@ process will delete it after a successful restore. The backup is node independent, so when restoring a 3 node cluster, it is best to restore it on each node for consistency. For example, if restoring on one node only, it can happen that the other two empty nodes form a majority and -the cluster comes up with no data. \ No newline at end of file +the cluster comes up with no data. -- 2.36.6