volume replication to new server

View: New views
4 Messages — Rating Filter:   Alert me  

volume replication to new server

by Roger Mason :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello,

I'm a new user.  I have run a single server operation for a few weeks
and just added a second one.  Both systems were installed from CVS
source onto Gentoo linux boxes.

After adding the second machine I created a new volume on that is
replicated on both the SCM and second server.  The createvol_rep
command completed sucessfully and I then created a mountpoint for the
volume from one of my clients.  I tested successfully that the mounted
volume is writeable when either the SCM or second server is down.

Now I would like volumes created _before_ adding the second server to
be replicated to it.

Is this possible?  If so, how?

Thanks for any help.

Roger


Re: volume replication to new server

by Neil Horman-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wed, Nov 05, 2008 at 10:56:58AM -0330, Roger Mason wrote:

> Hello,
>
> I'm a new user.  I have run a single server operation for a few weeks
> and just added a second one.  Both systems were installed from CVS
> source onto Gentoo linux boxes.
>
> After adding the second machine I created a new volume on that is
> replicated on both the SCM and second server.  The createvol_rep
> command completed sucessfully and I then created a mountpoint for the
> volume from one of my clients.  I tested successfully that the mounted
> volume is writeable when either the SCM or second server is down.
>
> Now I would like volumes created _before_ adding the second server to
> be replicated to it.
>
> Is this possible?  If so, how?
>

I've been using coda for a few months now, and I've found that if you have a
volume that you want replicated to a newly added server, you can do so by
creating a new volume (either with volutil clone if you want at read-only
replica), or with volutil create if you want a read-write replica.  In the
latter case, however, after you create the replica, you will need to manually
edit the VRDB to make coda aware that the new volume is a replica of the
origional (see man vrdb for details).

Neil

> Thanks for any help.
>
> Roger
>
>

--
/***************************************************
 *Neil Horman
 *nhorman@...
 *gpg keyid: 1024D / 0x92A74FA1
 *http://pgp.mit.edu
 ***************************************************/


Re: volume replication to new server

by u+codalist-wk5r :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Roger,

On Wed, Nov 05, 2008 at 10:56:58AM -0330, Roger Mason wrote:
> Now I would like volumes created _before_ adding the second server to
> be replicated to it.
>
> Is this possible?  If so, how?

See http://coda.wikidev.net/Dynamically_add_replicated_server

I guess it contains all the necessary bits.

Regards,
Rune


Re: volume replication to new server

by Roger Mason :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello,

Neil Horman <nhorman@...> writes:

> On Wed, Nov 05, 2008 at 10:56:58AM -0330, Roger Mason wrote:

[blah blah]

>> Now I would like volumes created _before_ adding the second server to
>> be replicated to it.
>>
>> Is this possible?  If so, how?

> I've been using coda for a few months now, and I've found that if you have a
> volume that you want replicated to a newly added server, you can do so by
> creating a new volume (either with volutil clone if you want at read-only
> replica), or with volutil create if you want a read-write replica.  In the
> latter case, however, after you create the replica, you will need to manually
> edit the VRDB to make coda aware that the new volume is a replica of the
> origional (see man vrdb for details).

 u+codalist-wk5r@... writes:

> See http://coda.wikidev.net/Dynamically_add_replicated_server

> I guess it contains all the necessary bits.

Thank you both very much.  I followed the procedure given on the wiki
and it seems to have worked.

Regards,
Roger