Salta al contenuto principale

Remove Acronis Virtual Appliance

Thread needs solution

Hi,

When I try to remove or update an Acronis ESX Appliance from an ESX host the dialog box appears with the IP address of the VCentre that the ESX host is connected to and requests the user ID and password for vCentre as opposed to the user name and password for the host where the appliance is installed. My problem is, I only have rights to the ESX host, not to vCentre. Ideally I would change the IP address in the "remove agent" dialog box to the IP of the ESX host and enter the username and password for that host but the IP is greyed out and I can't change it.

Is there some way I can add\remove acronis agent virtual appliances directly on the ESX Host and not within the context of the wider vCenter environment?

Thanks

Paul

 

Allegato Dimensione
removeagent.png 76.75 KB
0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Messaggi: 22
Commenti: 3800

Hi Paul,

The IP address in the prompt on the screen shot corresponds the address of ESXi host/vCenter registered on appliance side. You can open the console of the appliance from vSphere client and configure the connection to desired ESXi host from appliance GUI. An alternative solution would be to open Acronis Backup management console (installed somewhere) -> go to "All machines with agents" list and remove appliance from there ("Delete from AMS"). After that you'll need to manually delete the appliance machine from vSphere client (right-click->Remove from disk). The "Appliance removal" option availbale in Acronis Backup does both of these actions, but cannot perform physical deletion (from vSphere) if the login/password is unknown - hence the prompt you see.

NOTE: we do NOT recommend connecting Agent for VMware to ESXi hosts directly if they are managed by vCenter - connection through vCenter is the proper way, since otherwise the VM migration and other vSphere-related activities may not be handled properly by Acronis Backup.

Thank you.