> -----Original Message-----
> From: vdsm-devel-boun...@lists.fedorahosted.org [mailto:vdsm-devel-
> boun...@lists.fedorahosted.org] On Behalf Of Itamar Heim
> Sent: Friday, February 17, 2012 5:13 PM
> To: ??????
> Cc: us...@ovirt.org; email@example.com
> Subject: Re: [vdsm] [Users] Restoring Virtual Machines
> On 02/17/2012 11:51 AM, ?????? wrote:
> > Can I use the "data of storage domain", created in the old ovirt to
> > import
> > virtual machines in a new ovirt?
> > It is possible to convert the "data of storage domain" in "export
> > domain"
> > manually? To mount it as a "Export domain" in a new overt
No, it's impossible. The export domain has specific layout (similar to
layout of master domain)
that contains for example VM's ovf files.
In theory you can 'hijack' master domain, but the flow is very complicated
and not recommended.
> cc-ing vdsm-devel on how to change the metadata of the SD to make it an
> export domain, instead of a data domain (which is pretty arbitrary iirc).
> > -----Original Message-----
> > From: Itamar Heim [mailto:ih...@redhat.com]
> > Sent: Thursday, February 16, 2012 4:36 AM
> > To: ??????
> > Cc: us...@ovirt.org
> > Subject: Re: [Users] Restoring Virtual Machines
> > On 02/15/2012 11:43 AM, ?????? wrote:
> >> hi, in the process of testing ovirt some questions:
> >> 1. If you are upgrading ovirt we erased the database postgress,
> >> whether it is possible to restore the list of virtual machines without
> >> having to restore the database from the dump? Take a virtual machine
> >> working on the nodes.
> > not easily right now.
> > easiest (other than restore) would probably be to make the storage
> > domain
> > into an export domain, and import from it in the new engine.
> >> 2. Is it possible to manage virtual machines through the cli?
> > yes.
> >> 3. Is it possible to arrange a backup of virtual machines without
> >> interruption of its performance?
> > I don't think there is a simple answer to this question.
> > can you explain what is the exact concern?
> > thanks,
> > Itamar
> vdsm-devel mailing list
vdsm-devel mailing list