On 10/01/2013 06:39 PM, Christian Kolquist wrote:yes, importing an existing data domain is a high priority for us for next version as the issue was raised several times by community users.
We have a NFS storage cluster (Isilon) for the domain.
The main question: is there a way to bring in an existing storage domain
to a new engine without exporting it then importing it? This would be
good for not just upgrades but also disaster recovery as well.
for 3.3, there a few options (the first one is the cleanest)
1. "save the export part"
- stop using the domain in 3.1
- change its meta data to that of an export domain
- import it as an existing export domain to 3.3
- import the VMs
2. "re-create the VMs / import disks"
- stop using the domain in 3.1
- create a new (empty) domain in 3.3
- move all disks to the new domain (assuming you create the new nfs
export in a way allowing you to move, not copy, from the old export)
- use the register disk api to add all disks
- create VMs and associate the disks to them
yes, this one requires to document first which disk is for which VM.
i think someone scripted something around this option.
if your disks have snapshots, this may become too complex.
3. re-create the VMs and override their disks.
this was suggested several times in the past, but if you have snapshots, not relevant.
------------------------------__------------------------------__---<mailto:iheim@redhat.com>> wrote:
On 09/30/2013 04:55 PM, Christian Kolquist wrote:
So, after many frustrating weekends of trying to upgrade ovirt
from 3.1,
I have come to the conclustion that it would just be best to
export all
of our VM's and Import them once I have redone the entire
installation
with FC19 and ovirt 3.3. Is there a way to export the entire domain
easily? Or to bring the entire domain into a new install of the
engine?
Exporting a single VM takes a very long while. It would take a
couple
of days to export all of our VM's (33 total vm's using 1.017 TB
of data)
and then reimport them using the normal means of exporting the
machines
off then on to the export domain, load the new engine server
then import
them all back in.
Any tips or tricks would be welcome.
do you have a single data domain in the DC?
is it nfs or something else?
Christian
FYI, I ran into just about every single bug that people had when
upgrading from 3.1 to 3.2 and a few more. I can't spend any
more time
troubleshooting the upgrade process. If we can't do the
export->import
easily or migrate the current storage domain we will probably
have to
get rid of ovirt and move to another solution.
This email, along with any attachments, is confidential. If you
believe you received this message in error, please contact the
sender immediately and delete all copies of the message.
Thank you.
_________________________________________________
Users mailing list
Users@ovirt.org <mailto:Users@ovirt.org>
http://lists.ovirt.org/__mailman/listinfo/users
<http://lists.ovirt.org/mailman/listinfo/users>
---------------------------------------------------------------
This email, along with any attachments, is confidential. If you
believe you received this message in error, please contact the
sender immediately and delete all copies of the message.
Thank you.
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users