X-Git-Url: https://git.opendaylight.org/gerrit/gitweb?a=blobdiff_plain;f=docs%2Fgetting-started-guide%2Fpersistence_and_backup.rst;h=1e147d522dd85d7acddeee6e57619fb25f36b251;hb=HEAD;hp=f4245c43be4dd13646982ac29951975abe52921d;hpb=5b2c913d9ec62350fd28bd5b793dafea084d0335;p=docs.git

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.