Bug 765068 (GLUSTER-3336)

Summary:	Best practices for running geo-rep on multiple volumes
Product:	[Community] Gluster-Documentation	Reporter:	Vikas Gorur <vikas>
Component:	Other	Assignee:	Divya <divya>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-05-18 11:29:46 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Vikas Gorur 2011-08-04 18:40:43 UTC

This is in reference to the admin guide, section 9.5, best practices for geo-replication:

The section assumes that the user is working with only a single Gluster volume. It might be worthwhile to point out that if there are multiple volumes, the user can run geo-rep for them from different servers. It is only necessary that for a *given* volume all commands are run from the same server.

Comment 1 Divya 2012-05-18 11:29:46 UTC

We have mentioned "It is advisable to run the geo-replication commands in one of the bricks in the trusted storage pool". We have documented it clearly that one of the bricks in the trusted storage pool. Trust storage pool means multiple volumes.