------=_Part_42425213_176413900.1469542552035
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
I'd be happy to, but how/where do I do that?
Regards,
Logan
----- On Jul 25, 2016, at 2:56 PM, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote:
| Il 22/Lug/2016 17:10, "Logan Kuhn" < logank(a)wolfram.com > ha scritto:
| > Thank you!
| > That does do some interesting things, but doesn't appear to work.
|> I've added a new storage domain, merged the differences in the metadata file
|> back to the old one and powered it up. When I start up the nodes they endlessly
|> report: VDSM ovirt-reqa1 command failed: (-226, 'Unable to read resource
| > owners', 'Sanlock exception')
|> I tried reinstalling one of them and the error message continues. At least for
| > now I've restored the old config and the error is gone.
| > Regards,
| > Logan
| Logan, do you mind to write a testcase in
ovirt.org website for the disaster
| recovery test you are doing? Milan, if Logan write it, can you please review
| it?
| > ----- On Jul 22, 2016, at 3:06 AM, Milan Zamazal mzamazal(a)redhat.com wrote:
| > | Logan Kuhn < logank(a)wolfram.com > writes:
| > |> Am I correct in the assumption that importing a previously master data
domain
| > |> into a fresh engine without a current master domain is supported?
| > | It's supported only in case the master domain was previously correctly
| > | detached from the data center.
| > | In case of an unexpected complete disaster, when a fresh engine is
| > | installed and used, it's still possible to recover the master domain in
| > | theory. You must find `metadata' file in the master domain and edit it
| > | for the new engine. It's completely unsupported and it may or may not
| > | work. We don't have guidelines how to do it, but you may try to create
| > | a new master domain, then detach it and compare the two metadata files.
| > _______________________________________________
| > Users mailing list
| > Users(a)ovirt.org
| >
http://lists.ovirt.org/mailman/listinfo/users
------=_Part_42425213_176413900.1469542552035
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<html><body><div style="font-family: Arial; font-size: 12pt; color:
#000000"><div>I'd be happy to, but how/where do I do
that?</div><div><br></div><div
data-marker="__SIG_PRE__">Regards,<br>Logan</div><br><span
id="zwchr" data-marker="__DIVIDER__">----- On Jul 25, 2016, at 2:56
PM, Sandro Bonazzola &lt;sbonazzo(a)redhat.com&gt;
wrote:<br></span><div
data-marker="__QUOTED_TEXT__"><blockquote style="border-left:2px
solid
#1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><p
dir="ltr"></p>
<p dir="ltr">Il 22/Lug/2016 17:10, "Logan Kuhn" <<a
href="mailto:logank@wolfram.com"
target="_blank">logank(a)wolfram.com</a>&gt; ha scritto:<br>
><br>
> Thank you!<br>
><br>
> That does do some interesting things, but doesn't appear to work.<br>
><br>
> I've added a new storage domain, merged the differences in the metadata file
back to the old one and powered it up. When I start up the nodes they endlessly
report: VDSM ovirt-reqa1 command failed: (-226, 'Unable to read resource owners',
'Sanlock exception')<br>
><br>
> I tried reinstalling one of them and the error message continues. At
least for now I've restored the old config and the error is gone.<br>
><br>
> Regards,<br>
> Logan<br>
><br></p>
<p dir="ltr">Logan, do you mind to write a testcase in <a
href="http://ovirt.org" target="_blank">ovirt.org</a> website
for the disaster recovery test you are doing? Milan, if Logan write it, can you please
review it?<br><br><br></p>
<p dir="ltr">> ----- On Jul 22, 2016, at 3:06 AM, Milan Zamazal
<a href="mailto:mzamazal@redhat.com"
target="_blank">mzamazal(a)redhat.com</a> wrote:<br>
><br>
> | Logan Kuhn <<a href="mailto:logank@wolfram.com"
target="_blank">logank(a)wolfram.com</a>&gt; writes:<br>
> |<br>
> |> Am I correct in the assumption that importing a previously master data
domain<br>
> |> into a fresh engine without a current master domain is
supported?<br>
> |<br>
> | It's supported only in case the master domain was previously
correctly<br>
> | detached from the data center.<br>
> |<br>
> | In case of an unexpected complete disaster, when a fresh engine is<br>
> | installed and used, it's still possible to recover the master domain
in<br>
> | theory. You must find `metadata' file in the master domain and
edit it<br>
> | for the new engine. It's completely unsupported and it may or may
not<br>
> | work. We don't have guidelines how to do it, but you may try to
create<br>
> | a new master domain, then detach it and compare the two metadata
files.<br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@ovirt.org"
target="_blank">Users(a)ovirt.org</a><br>
> <a
href="http://lists.ovirt.org/mailman/listinfo/users"
target="_blank">http://lists.ovirt.org/mailman/listinfo/user...
------=_Part_42425213_176413900.1469542552035--