Skip to main content

Will there be a fix to KB23121

Thread needs solution

link to kb: https://kb.acronis.com/content/23121

hi,

for us vcenter integration is one of the key features in acronis. all backup plans build up on the vc infrastructure. if vcenter integration fails backups can fail.

having the need to delete the "corrupted" registry key every once in a while is inaccaptable.

when will there be a fix to superseed the workaround?

ps: if you start seeing inactive vms check your vcenter integration. if that fails you have been corrupted by acrons ;-) (see above link for help)

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi,

Most of the root causes of Acronis Management Server (AMS) database corruption which lead to such vCenter integration problem are fixed in the recent updates for Acronis Backup Advanced 11.5 (Update 6) and the remaining ones should be addressed in the upcoming new update (to be released in the next several weeks).

Note that vCenter integration functionality itself is not responsible for backup - you can deploy a virtual appliance(s) or Windows Agent(s) for VMware and connect it to vCenter without enabling integration. "vCenter Integration" is responsible only for viewing the vCenter folders in AMS GUI + automatic deployment of virtual appliances (which is usually not required). The core backup + VM binding functionality (automatic distribution of VMs among backup agents) as well as support for vMotion is available without "vCenter Integration".

Thank you.

--

Best regards,

Vasily

Acronis Virtualization Program Manager

Hi Vasily,

i would say yes and no to your answer. yes to the fact that you can deploy esx appliance without having the vcenter integration. no to your statement that vcenter integration isn't responsible for backup. it is definitly. you need the integration when you setup folder structure on vcenter and put vms in different folders. the backup plans have been setup to fetch the vms in the different folder in order to have diefferent backup tasks for different types of vms. this cannot be handled with the appliance only as vms get vmotioned to different esx servers.

to sum up without vcenter integration i wouldn't have a single backup.

vcenter integration crashes each time you restart vcenter server appliance. this is very annoying. 

----------------------------------------------------------------------------------------
Error
----------------------------------------------------------------------------------------
Failed to obtain information about the vCenter integration.
----------------------------------------------------------------------------------------
Details:
    Code: 14.712.838(0x00E08006)
<u>LineInfo:</u> 0xA20120E20D7DA150;

    Module: virtual_center_addon_vs_43994
    Message: Failed to enumerate the registered VMware vCenters.

    Code: 16.285.699(0x00F88003)
<u>LineInfo:</u> 0x88F44F36DA889CD4;

    Module: management_server_vs_43994
    Message: The specified entry does not exist: '37966F27-0D6A-4261-027A-76F8B45D3BD3'.

----------------------------------------------------------------------------------------
 

Support doenst seem to have any clue why this issue happens. i need someone who can cross check this beavior.

1. vcenter 6 appliance

2. run neccessary service as the default asn and asm user

3. mssql database with sql authentication

4. enable vcenter integration

5. restart ams service

6. check if vcenter integration works

 

 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi,

Can you please send me your support case ID in a private message, so that I can check and followup with our support team?

P.S. We've just released an update for Acronis Backup 11.5 with multiple fixes included (including fixes for AMS-related problems), so it makes sense to update to this new build before continuing the troubleshooting. This update is called Acronis Backup 11.7, but technically it's the same code base.

Thank you.

--

Best regards,

Vasily

Acronis Virtualization Program Manager