This is a multi-part MIME message. --=_reb-r3E2C9F17-t5431F02A Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Hi I am trying to backup and restore the VM using the flow suggester at Features/Backup-Restore API Integration <http://www.ovirt.org/Features/Backup-Restore_API_Integration#VM_Backup.2FRestore_suggested_flows> When I tried to restore the VM using the following steps, _*Full Virtual Machine Restoration*_ 1. Create disks for restore 2. Attach the disks for restore to the virtual appliance (Restore the data to it) 3. Detach the disks from the virtual appliance. 4. Create a vm using the configuration that was saved as part of the backup flow - (added capabillity to oVirt as part of the Backup API) 5. Attach the restored disks to the created vm. I encountered following error at step 4. <fault> <reason>Operation Failed</reason> <detail>[Import VM failed - _*VM Id already exist in the system*_. Please remove the VM (RHEL_65_CL1_CLONE2) from the system first]</detail> </fault> I have not deleted/removed the backed up VM from the system. Is it expected behaviour? Should it not overwrite the existing VM or Create new VM with different VM Id, if the backup up VM exists? Thanks, Santosh ***************************Legal Disclaimer*************************** "This communication may contain confidential and privileged material for the sole use of the intended recipient. Any unauthorized review, use or distribution by others is strictly prohibited. If you have received the message by mistake, please advise the sender by reply email and delete the message. Thank you." ********************************************************************** --=_reb-r3E2C9F17-t5431F02A Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWw+DQogIDxoZWFkPg0KDQogICAgPG1ldGEgaHR0cC1lcXVpdj0iY29udGVudC10eXBl IiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KICA8L2hlYWQ+DQogIDxi b2R5IGJnY29sb3I9IiNGRkZGRkYiIHRleHQ9IiMwMDAwMDAiPg0KICAgIEhpIDxicj4NCiAg ICA8YnI+DQogICAgSSBhbSB0cnlpbmcgdG8gYmFja3VwIGFuZCByZXN0b3JlIHRoZSBWTSB1 c2luZyB0aGUgZmxvdyBzdWdnZXN0ZXINCiAgICBhdMKgwqAgPGENCmhyZWY9Imh0dHA6Ly93 d3cub3ZpcnQub3JnL0ZlYXR1cmVzL0JhY2t1cC1SZXN0b3JlX0FQSV9JbnRlZ3JhdGlvbiNW TV9CYWNrdXAuMkZSZXN0b3JlX3N1Z2dlc3RlZF9mbG93cyI+RmVhdHVyZXMvQmFja3VwLVJl c3RvcmUNCg0KICAgICAgQVBJIEludGVncmF0aW9uPC9hPjxicj4NCiAgICA8YnI+DQogICAg V2hlbiBJIHRyaWVkIHRvIHJlc3RvcmUgdGhlIFZNIHVzaW5nIHRoZSBmb2xsb3dpbmcgc3Rl cHMsPGJyPg0KICAgIDxicj4NCiAgICA8YnI+DQogICAgPHU+PGI+RnVsbCBWaXJ0dWFsIE1h Y2hpbmUgUmVzdG9yYXRpb248L2I+PC91Pjxicj4NCiAgICA8b2w+DQogICAgICA8bGk+Q3Jl YXRlIGRpc2tzIGZvciByZXN0b3JlPC9saT4NCiAgICAgIDxsaT5BdHRhY2ggdGhlIGRpc2tz IGZvciByZXN0b3JlIHRvIHRoZSB2aXJ0dWFsIGFwcGxpYW5jZSAoUmVzdG9yZQ0KICAgICAg ICB0aGUgZGF0YSB0byBpdCk8L2xpPg0KICAgICAgPGxpPkRldGFjaCB0aGUgZGlza3MgZnJv bSB0aGUgdmlydHVhbCBhcHBsaWFuY2UuPC9saT4NCiAgICAgIDxsaT5DcmVhdGUgYSB2bSB1 c2luZyB0aGUgY29uZmlndXJhdGlvbiB0aGF0IHdhcyBzYXZlZCBhcyBwYXJ0IG9mDQogICAg ICAgIHRoZSBiYWNrdXAgZmxvdyAtIChhZGRlZCBjYXBhYmlsbGl0eSB0byBvVmlydCBhcyBw YXJ0IG9mIHRoZQ0KICAgICAgICBCYWNrdXAgQVBJKTwvbGk+DQogICAgICA8bGk+QXR0YWNo IHRoZSByZXN0b3JlZCBkaXNrcyB0byB0aGUgY3JlYXRlZCB2bS48L2xpPg0KICAgIDwvb2w+ DQogICAgSSBlbmNvdW50ZXJlZCBmb2xsb3dpbmcgZXJyb3IgYXQgc3RlcCA0Ljxicj4NCiAg ICA8YnI+DQogICAgPGJsb2NrcXVvdGU+PGZvbnQgY29sb3I9IiNjYzAwMDAiPiZsdDtmYXVs dCZndDs8YnI+DQogICAgICAgIMKgwqDCoCAmbHQ7cmVhc29uJmd0O09wZXJhdGlvbiBGYWls ZWQmbHQ7L3JlYXNvbiZndDs8YnI+DQogICAgICAgIMKgwqDCoCAmbHQ7ZGV0YWlsJmd0O1tJ bXBvcnQgVk0gZmFpbGVkIC0gPHU+PGI+Vk0gSWQgYWxyZWFkeSBleGlzdA0KICAgICAgICAg ICAgaW4gdGhlIHN5c3RlbTwvYj48L3U+LiBQbGVhc2UgcmVtb3ZlIHRoZSBWTQ0KICAgICAg ICAoUkhFTF82NV9DTDFfQ0xPTkUyKSBmcm9tIHRoZSBzeXN0ZW0gZmlyc3RdJmx0Oy9kZXRh aWwmZ3Q7PGJyPg0KICAgICAgICAmbHQ7L2ZhdWx0Jmd0OzwvZm9udD48YnI+DQogICAgPC9i bG9ja3F1b3RlPg0KICAgIDxicj4NCiAgICBJIGhhdmUgbm90IGRlbGV0ZWQvcmVtb3ZlZCB0 aGUgYmFja2VkIHVwIFZNIGZyb20gdGhlIHN5c3RlbS48YnI+DQogICAgPGJyPg0KICAgIElz IGl0IGV4cGVjdGVkIGJlaGF2aW91cj8gPGJyPg0KICAgIFNob3VsZCBpdCBub3Qgb3Zlcndy aXRlIHRoZSBleGlzdGluZyBWTSBvciBDcmVhdGUgbmV3IFZNIHdpdGgNCiAgICBkaWZmZXJl bnQgVk0gSWQsIGlmIHRoZSBiYWNrdXAgdXAgVk0gZXhpc3RzPzxicj4NCiAgICA8YnI+DQog ICAgwqA8YnI+DQogICAgVGhhbmtzLCBTYW50b3NoDQogIDwvYm9keT4NCjwvaHRtbD4NCg0K DQo8cHJlPg0KDQoqKioqKioqKioqKioqKioqKioqKioqKioqKipMZWdhbCBEaXNjbGFpbWVy KioqKioqKioqKioqKioqKioqKioqKioqKioqDQoiVGhpcyBjb21tdW5pY2F0aW9uIG1heSBj b250YWluIGNvbmZpZGVudGlhbCBhbmQgcHJpdmlsZWdlZCBtYXRlcmlhbCBmb3IgdGhlDQpz b2xlIHVzZSBvZiB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LiBBbnkgdW5hdXRob3JpemVkIHJl dmlldywgdXNlIG9yIGRpc3RyaWJ1dGlvbg0KYnkgb3RoZXJzIGlzIHN0cmljdGx5IHByb2hp Yml0ZWQuIElmIHlvdSBoYXZlIHJlY2VpdmVkIHRoZSBtZXNzYWdlIGJ5IG1pc3Rha2UsDQpw bGVhc2UgYWR2aXNlIHRoZSBzZW5kZXIgYnkgcmVwbHkgZW1haWwgYW5kIGRlbGV0ZSB0aGUg bWVzc2FnZS4gVGhhbmsgeW91LiINCioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKio8L3ByZT4NCg== --=_reb-r3E2C9F17-t5431F02A--
If you still have the backed up VM in your system, the create from configuration operation should be blocked as you've encountered. Allon, what does the create VM from configuration checks? The existence of the VM name or the existence of its ID? ----- Original Message ----- From: "santosh" <sbahir@commvault.com> To: users@ovirt.org Sent: Monday, 6 October, 2014 4:28:06 AM Subject: [ovirt-users] Restoring backed up VM Hi I am trying to backup and restore the VM using the flow suggester at Features/Backup-Restore API Integration When I tried to restore the VM using the following steps, Full Virtual Machine Restoration 1. Create disks for restore 2. Attach the disks for restore to the virtual appliance (Restore the data to it) 3. Detach the disks from the virtual appliance. 4. Create a vm using the configuration that was saved as part of the backup flow - (added capabillity to oVirt as part of the Backup API) 5. Attach the restored disks to the created vm. I encountered following error at step 4. <fault> <reason>Operation Failed</reason> <detail>[Import VM failed - VM Id already exist in the system . Please remove the VM (RHEL_65_CL1_CLONE2) from the system first]</detail> </fault> I have not deleted/removed the backed up VM from the system. Is it expected behaviour? Should it not overwrite the existing VM or Create new VM with different VM Id, if the backup up VM exists? Thanks, Santosh ***************************Legal Disclaimer*************************** "This communication may contain confidential and privileged material for the sole use of the intended recipient. Any unauthorized review, use or distribution by others is strictly prohibited. If you have received the message by mistake, please advise the sender by reply email and delete the message. Thank you." ********************************************************************** _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Elad, the the VM from configuration checks the existence of the VM id. Probably RHEL_65_CL1_CLONE2 has the same id as the VM which is being imported. Regards, Maor ----- Original Message -----
From: "Elad Ben Aharon" <ebenahar@redhat.com> To: "santosh" <sbahir@commvault.com>, "Allon Mureinik" <amureini@redhat.com> Cc: users@ovirt.org Sent: Tuesday, October 7, 2014 9:08:42 AM Subject: Re: [ovirt-users] Restoring backed up VM
If you still have the backed up VM in your system, the create from configuration operation should be blocked as you've encountered. Allon, what does the create VM from configuration checks? The existence of the VM name or the existence of its ID?
----- Original Message ----- From: "santosh" <sbahir@commvault.com> To: users@ovirt.org Sent: Monday, 6 October, 2014 4:28:06 AM Subject: [ovirt-users] Restoring backed up VM
Hi
I am trying to backup and restore the VM using the flow suggester at Features/Backup-Restore API Integration
When I tried to restore the VM using the following steps,
Full Virtual Machine Restoration
1. Create disks for restore 2. Attach the disks for restore to the virtual appliance (Restore the data to it) 3. Detach the disks from the virtual appliance. 4. Create a vm using the configuration that was saved as part of the backup flow - (added capabillity to oVirt as part of the Backup API) 5. Attach the restored disks to the created vm.
I encountered following error at step 4.
<fault> <reason>Operation Failed</reason> <detail>[Import VM failed - VM Id already exist in the system . Please remove the VM (RHEL_65_CL1_CLONE2) from the system first]</detail> </fault>
I have not deleted/removed the backed up VM from the system.
Is it expected behaviour? Should it not overwrite the existing VM or Create new VM with different VM Id, if the backup up VM exists?
Thanks, Santosh ***************************Legal Disclaimer*************************** "This communication may contain confidential and privileged material for the sole use of the intended recipient. Any unauthorized review, use or distribution by others is strictly prohibited. If you have received the message by mistake, please advise the sender by reply email and delete the message. Thank you." **********************************************************************
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Allon, Elad: Yes, RHEL_65_CL1_CLONE2 has the same ID as the VM being restored. And error message also indicates that the conflict is occurring on the VM id. Thanks for the confirmation. Thanks, Santosh On 10/07/2014 03:59 AM, Maor Lipchuk wrote:
Elad, the the VM from configuration checks the existence of the VM id. Probably RHEL_65_CL1_CLONE2 has the same id as the VM which is being imported.
Regards, Maor
----- Original Message -----
From: "Elad Ben Aharon" <ebenahar@redhat.com> To: "santosh" <sbahir@commvault.com>, "Allon Mureinik" <amureini@redhat.com> Cc: users@ovirt.org Sent: Tuesday, October 7, 2014 9:08:42 AM Subject: Re: [ovirt-users] Restoring backed up VM
If you still have the backed up VM in your system, the create from configuration operation should be blocked as you've encountered. Allon, what does the create VM from configuration checks? The existence of the VM name or the existence of its ID?
----- Original Message ----- From: "santosh" <sbahir@commvault.com> To: users@ovirt.org Sent: Monday, 6 October, 2014 4:28:06 AM Subject: [ovirt-users] Restoring backed up VM
Hi
I am trying to backup and restore the VM using the flow suggester at Features/Backup-Restore API Integration
When I tried to restore the VM using the following steps,
Full Virtual Machine Restoration
1. Create disks for restore 2. Attach the disks for restore to the virtual appliance (Restore the data to it) 3. Detach the disks from the virtual appliance. 4. Create a vm using the configuration that was saved as part of the backup flow - (added capabillity to oVirt as part of the Backup API) 5. Attach the restored disks to the created vm.
I encountered following error at step 4.
<fault> <reason>Operation Failed</reason> <detail>[Import VM failed - VM Id already exist in the system . Please remove the VM (RHEL_65_CL1_CLONE2) from the system first]</detail> </fault>
I have not deleted/removed the backed up VM from the system.
Is it expected behaviour? Should it not overwrite the existing VM or Create new VM with different VM Id, if the backup up VM exists?
Thanks, Santosh ***************************Legal Disclaimer*************************** "This communication may contain confidential and privileged material for the sole use of the intended recipient. Any unauthorized review, use or distribution by others is strictly prohibited. If you have received the message by mistake, please advise the sender by reply email and delete the message. Thank you." **********************************************************************
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
***************************Legal Disclaimer*************************** "This communication may contain confidential and privileged material for the sole use of the intended recipient. Any unauthorized review, use or distribution by others is strictly prohibited. If you have received the message by mistake, please advise the sender by reply email and delete the message. Thank you." **********************************************************************
participants (3)
-
Elad Ben Aharon -
Maor Lipchuk -
santosh