Salta al contenuto principale

Backup "Completed with warnings"

Thread needs solution

Hallo,

at the moment we are using Acronis Backup 12.5 for backing up virtual machines. However, for one virtual machine, the backup will always be completed with "Completed with warnings".

Hier are error messages:

 

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

Windows-Fehler: (0x8000FFFF) Schwerwiegender Fehler
Modul: 83
Erhalten der Objekt-Eigenschaft{0,choice,0< '{0}'} fehlgeschlagen.
Zusätzliche Informationen:
------------------------
Fehlercode: 116
Modul: 83
Zeileninfo: 0xBA3FDB9882F23569
Felder: {"$module":"hv_srv_vsa64_11010"}
Nachricht: Erhalten der Objekt-Eigenschaft{0,choice,0< '{0}'} fehlgeschlagen.
------------------------
Fehlercode: 1012
Modul: 20
Zeileninfo: 0xC523D9A02D03D55C
Felder: {"Query":"SELECT * FROM Win32_OptionalFeature WHERE InstallState=1 and Name='Microsoft-Hyper-V'","$module":"hv_srv_vsa64_11010"}
Nachricht: WMI 'ExecQuery' fehlgeschlagen.
------------------------
Fehlercode: 65520
Modul: 0
Zeileninfo: 0xBD28FDBD64EDB8FB
Felder: {"code":"2147549183","$module":"hv_srv_vsa64_11010"}
Nachricht: Schwerwiegender Fehler
 
-----------------------------------------------------------------------------------------------------------------------

 

Why is that?

The host is running Windows Server 2019 with Hyper-V. Other virtual machines on this host can be backed up without any problems.

The virtual server that shows the error message is a 2012 R2 (no AD, Exchange or SQL). The same error occurred also on a 2008 R2.

 

Thank you!

Benjamin

 

Edit: I translated the text to English.

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Messaggi: 0
Commenti: 2016

Hello Benjamin!

I should note that Hyper-V in Windows Server 2019 will be fully supported in Acronis Backup 12.5 Update 4.

https://www.acronis.com/en-us/support/documentation/AcronisBackup_12.5/#37871.html

As for now, please check whether the machine name, hdd names or folder names where this VM is located contain any special character (&, $ etc.). 

As a workaround, you can also install Agent for Windows on the machine where the backup fails.

 

 

Thanks for your answer!

Then I´ll wait for this Update und then check again.

 

Greetings,

Benjamin

Same problem here with Server 2019 as HyperV and two virtual machines(one DC and one rds Server).

Windows-Fehler: (0x8000FFFF) Schwerwiegender Fehler

Erhalten der Objekt-Eigenschaft{0,choice,0< '{0}'} fehlgeschlagen.
Zusätzliche Informationen:
------------------------
Fehlercode: 116
Modul: 83
Zeileninfo: 0xBA3FDB9882F23569
Felder: {"$module":"hv_srv_vsa64_11010"}
Nachricht: Erhalten der Objekt-Eigenschaft{0,choice,0< '{0}'} fehlgeschlagen.
------------------------
Fehlercode: 1012
Modul: 20
Zeileninfo: 0xC523D9A02D03D55C
Felder: {"$module":"hv_srv_vsa64_11010","Query":"SELECT * FROM Win32_OptionalFeature WHERE InstallState=1 and Name='Microsoft-Hyper-V'"}
Nachricht: WMI 'ExecQuery' fehlgeschlagen.
------------------------
Fehlercode: 65520
Modul: 0
Zeileninfo: 0xBD28FDBD64EDB8FB
Felder: {"$module":"hv_srv_vsa64_11010","code":"2147549183"}
Nachricht: Schwerwiegender Fehler
 
Kind regards,
 
Marc
 
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Messaggi: 0
Commenti: 2016

Hello Alexander,

welcome to Acronis forums!

As I noted above, Hyper-V in Windows Server 2019 will be fully supported in Acronis Backup 12.5 Update 4 that we expect to be released (but can't guarantee it) in approximately 1,5-2 months. 

Hi,

to add:

I found out that if you change the setting for "Limit the number of concurrent backups" to "1" under the backup plan, the error will no longer occur.

In German: Ich habe herausgefunden, dass wenn man unter dem Backup-Plan die Einstellung für "Die Anzahl gleichzeitig ausgeführter Backups begrenzen" auf 1 setzt, der Fehler bei uns nicht mehr auftritt.

 

Maybe it will help you too, Alexander.

 

Greetings,

Benjamin

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Messaggi: 0
Commenti: 2016

Hello Benjamin,

thanks for sharing this clarification.

Here is this path in English UI:

Backup Options -> Scheduling -> Limit the number of simultaneously running backups by