From 3661be2f43591bd76ff0eeb5aedb8e75b0cbfeb8 Mon Sep 17 00:00:00 2001
From: Kotresh HR <khiremat@redhat.com>
Date: Mon, 13 Apr 2015 11:56:35 +0530
Subject: doc/geo-rep: Doc changes w.r.t common shared gluster meta volume

BUG: 1217939
Change-Id: I0fbb03e809793030e614c40acc930a0579f88d52
Reviewed-on: http://review.gluster.org/10447
Signed-off-by: Kotresh HR <khiremat@redhat.com>
Reviewed-on: http://review.gluster.org/10555
Reviewed-by: Aravinda VK <avishwan@redhat.com>
Tested-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
---
 .../en-US/markdown/admin_distributed_geo_rep.md    | 31 ++++++++++++++++------
 1 file changed, 23 insertions(+), 8 deletions(-)

(limited to 'doc/admin-guide/en-US')

diff --git a/doc/admin-guide/en-US/markdown/admin_distributed_geo_rep.md b/doc/admin-guide/en-US/markdown/admin_distributed_geo_rep.md
index bc111255b4a..38c1f6725b8 100644
--- a/doc/admin-guide/en-US/markdown/admin_distributed_geo_rep.md
+++ b/doc/admin-guide/en-US/markdown/admin_distributed_geo_rep.md
@@ -113,16 +113,26 @@ To add multiple volumes per mountbroker user,
     /usr/libexec/glusterfs/set_geo_rep_pem_keys.sh <mountbroker_user> <master_volume> <slave_volume>
     ```
 
-### Configuring meta volume
-A gluster meta volume needs to be configured with geo-replication to
-better handle rename and other consistency issues in geo-replication during
-brick/node down scenarios when master volume is configured with EC(Erasure Code)/AFR.
+### Create and mount meta volume
+NOTE:
+___
+If shared meta volume is already created and mounted at '/var/run/gluster/shared_storage'
+as part of nfs or snapshot, please jump into section 'Configure meta volume with goe-replication'.
+___
+
+A 3-way replicated common gluster meta-volume should be configured and is shared
+by nfs, snapshot and geo-replication. The name of the meta-volume should be
+'gluster_shared_storage' and should be mounted at '/var/run/gluster/shared_storage/'.
+
+The meta volume needs to be configured with geo-replication to better handle
+rename and other consistency issues in geo-replication during brick/node down
+scenarios when master volume is configured with EC(Erasure Code)/AFR.
 Following are the steps to configure meta volume
 
 Create a 3 way replicated meta volume in the master cluster with all three bricks from different nodes as follows.
 
     ```sh
-    gluster volume create <meta_vol> replica 3 <host1>:<brick_path> <host2>:<brick_path> <host3>:<brick_path>
+    gluster volume create gluster_shared_storage replica 3 <host1>:<brick_path> <host2>:<brick_path> <host3>:<brick_path>
     ```
 
 Start the meta volume as follows.
@@ -131,12 +141,17 @@ Start the meta volume as follows.
     gluster volume start <meta_vol>
     ```
 
-Configure meta volume with geo-replication session as follows.
+Mount the meta volume as follows in all the master nodes.
+    ```sh
+    mount -t glusterfs <master_host>:gluster_shared_storage /var/run/gluster/shared_storage
+    ```
+
+###Configure meta volume with geo-replication session as follows.
 
     ```sh
-    gluster volume geo-replication <master_volume> <slave_host>::<slave_volume> config meta_volume <meta_vol>
+    gluster volume geo-replication <master_volume> <slave_host>::<slave_volume> config use_meta_volume true
     # If Mountbroker Setup,
-    gluster volume geo-replication <master_volume> <mountbroker_user>@<slave_host>::<slave_volume> config meta_volume <meta_vol>
+    gluster volume geo-replication <master_volume> <mountbroker_user>@<slave_host>::<slave_volume> config use_meta_volume true
     ```
 
 #### Starting a geo-rep session
-- 
cgit