weizhouapache commented on PR #7239: URL: https://github.com/apache/cloudstack/pull/7239#issuecomment-1846056272
@SadiJr @harikrishna-patnala @DaanHoogland I tried to reproduce the issue on veeam12 environment with some changes (see https://github.com/apache/cloudstack/pull/8241) However, the restore of backup succeeds in my testing - unmanage a running vm - import it to cloudstack got two VMs with same instance name ``` +-----+---------------+--------------------------------------+---------------+---------------+---------------------+---------------------+ | id | name | uuid | instance_name | display_name | created | removed | +-----+---------------+--------------------------------------+---------------+---------------+---------------------+---------------------+ | 162 | admin-001-001 | c13f4662-dd08-4f24-abd3-c1b581a3ecd2 | i-2-162-VM | admin-001-001 | 2023-12-01 08:22:55 | 2023-12-07 20:00:16 | | 225 | i-2-162-VM | a974a38d-5b9a-40d2-a0fb-feb80ef88762 | i-2-162-VM | NULL | 2023-12-07 20:01:01 | NULL | +-----+---------------+--------------------------------------+---------------+---------------+---------------------+---------------------+ 2 rows in set (0.00 sec) ``` - assign backup offering - create a backup - stop the vm, and restore the backup. I checked the description and code again, I think we should not fix an issue with veeam backup/restore by changing the processes of unmanage/manage VM. We should fix the issue in veeam plugin, if the issue can be reproduced. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
