<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello,</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In testing fault tolerance/recovery procedures if the master storage domain is lost/removed, ovirt becomes pretty much unusable. You cannot add new storage as oVirt will not mount it, even if you can mount it manually to the host. If you
force remove the old failed storage domain via the engine database, you’re essentially screwed since it will fail to mount ANY new storage.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Is there some workaround for this so that if the original master storage domain becomes damaged, fails, goes offline etc that oVirt is not so dependent on this OR another storage can continue to be added?</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Right now, I have an oVirt datacenter with multiple networks, redundant nic’s etc that that is going to have to be completely removed, reconfigured and then set up from scratch again essentially due to the master storage domain issue.</p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
</div>
</body>
</html>