OK, I saw this but was duped by this (the first line):<div><br></div><div><span class="Apple-style-span" style="font-family: verdana, sans-serif; line-height: 16px; background-color: rgb(255, 255, 255); "><b>If your newly installed server has the same hostname as the former server</b></span><font class="Apple-style-span" face="verdana, sans-serif"><span class="Apple-style-span" style="line-height: 16px;"><br>
</span></font><div><br></div><div>I'll try to work through this document. The server is in a cloud environment and the way it was setup prevents it from having the same hostname. I can do this via hostnames, but I'll have to provision a new cluster.</div>
<div><br></div><div>Bryan</div><div><br><div class="gmail_quote">On Fri, Sep 16, 2011 at 4:02 PM, Vikas Gorur <span dir="ltr"><<a href="mailto:vikas@gluster.com">vikas@gluster.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>Brian,</div><div><br></div>Replace-brick is not what you need here. Replace-brick is designed to be used for a planned decommissioning of a node and migration of data from it to a new node. You can only use replace-brick when both the source and the target servers are up and running.<div>
<br></div><div>If you have a catastrophic failure where one of the servers gets its OS disk completely wiped, you need to do this:</div><div><br></div><div><a href="http://europe.gluster.org/community/documentation/index.php/Gluster_3.2:_Brick_Restoration_-_Replace_Crashed_Server" target="_blank">http://europe.gluster.org/community/documentation/index.php/Gluster_3.2:_Brick_Restoration_-_Replace_Crashed_Server</a></div>
<div><br></div><font color="#888888"><div><br clear="all"><div><br></div>-- <br><div>Vikas Gorur</div><div>Engineer - Gluster</div><div><br></div><br>
</div>
</font></blockquote></div><br></div></div>