The move command will first create the disk structure according to the
snapshots on the destination , then a 'qemui-mg convert' will be performed
for each snapshot.
On Wed, Jul 12, 2017 at 1:31 AM, Gianluca Cecchi
wrote:
> On Tue, Jul 11, 2017 at 3:14 PM, Gianluca Cecchi <
> gianluca.cec...@gmai
On Tue, Jul 11, 2017 at 3:14 PM, Gianluca Cecchi
wrote:
>
>
> On Tue, Jul 11, 2017 at 2:59 PM, Gianluca Cecchi <
> gianluca.cec...@gmail.com> wrote:
>
>> Hello,
>> I have a source oVirt environment with storage domain on FC
>> I have a destination oVirt environment with storage domain on iSCSI
>>
On Tue, Jul 11, 2017 at 3:33 PM, Elad Ben Aharon
wrote:
> Hi,
>
> I suggest another solution for you (which wasn't tested as a whole but
> much simpler in my opinion).
>
> On the source environment:
> - Create a local DC with a single local storage domain (let's call it
> sd1).
> - Deactivate an
Hi,
I suggest another solution for you (which wasn't tested as a whole but much
simpler in my opinion).
On the source environment:
- Create a local DC with a single local storage domain (let's call it sd1).
- Deactivate and detach the FC domain from the existing shared DC and
attach it to the lo
On Tue, Jul 11, 2017 at 2:59 PM, Gianluca Cecchi
wrote:
> Hello,
> I have a source oVirt environment with storage domain on FC
> I have a destination oVirt environment with storage domain on iSCSI
> The two environments can communicate only via the network of their
> respective hypervisors.
> The
Hello,
I have a source oVirt environment with storage domain on FC
I have a destination oVirt environment with storage domain on iSCSI
The two environments can communicate only via the network of their
respective hypervisors.
The source environment, in particular, is almost isolated and I cannot
at
6 matches
Mail list logo
