Skip to main content

Error Backing up a VM

Thread needs solution
Beginner
Posts: 2
Comments: 1

I'm not able to backup a virtual machine included in an activites with other 6 VM's.
I get everytime the same error:

70 Errore 24/10/11 08:29:44 Impossibile eseguire l'operazione con archivio 'avfs:/smb?//vci-nas1/VMPBackup/ServerVCI_2011_10_21_02_00_07_955D.TIB'. Errore: 'Internal error: number of backed up sectors differs from counted'.
Informazioni aggiuntive:
--------------------
Codice errore: 1
Modulo: 7
LineInfo: a5695862aaf8e6b9
Campi:
Messaggio: Impossibile eseguire l'operazione con archivio 'avfs:/smb?//vci-nas1/VMPBackup/ServerVCI_2011_10_21_02_00_07_955D.TIB'. Errore: 'Internal error: number of backed up sectors differs from counted'.
--------------------

All the other VM's are backed up correctly.
This VM has nothing different form the others: same datastore, same number of cpu's, same OS.
Please can you help me solve it.
Many thanks

Edika

0 Users found this helpful
Forum Hero
Posts: 613
Comments: 8747

sorry, ignore - misread your post when answering.

Forum Star
Posts: 88
Comments: 4769

Hello all,

Thank you for your posts.

Edika, let me help you with this issue please. It is caused by an issue in the product which will be fixed in Update 1. In the meantime please use the solution from this KB article.

Let me know if you need additional assistance please.

Thank you.

Beginner
Posts: 2
Comments: 1

Hello Anton,

I've read the article, and disabled the CBD.
Without this option the backup is really slow and also this is a key feature of the product, when you think this issue will be fixed?
As I'm evaluating vmProtect, Veeeam and vReplicator, I have to take a decision in max 1 month.
vmProtect looks good and was my first choice before I discovered this problem.
Hope the fix came out soon.

Edika

OT: I've also send an email to the support but no reply after 3 days. Customer support is very important for these kind of product...

Forum Star
Posts: 88
Comments: 4769

Hello Edika,

Thank you for the follow-up.

We do not have the exact release date for Update 1 I am afraid, I am sorry for any inconvenience this issue may be causing you.

I found your case in our support system and it will be taken care of very soon. Our response time for e-mail cases for trial versions is 3 business days, you can always contact our Chat support as well. You can check additional support options here.

If you need any additional help please let me know, I will be happy to assist you.

Thank you.

Beginner
Posts: 0
Comments: 6

Hello,

i have this issue too.
We use VM-Protect 9 to backup 5 VM's.
3 Jobs are working fine but the other 2 are failing every time.

Months ago all Jobs were working fine....

I just created all 5 Jobs new, but result is the same.
I also created snapshots in VSphere by hand. No problem.
Updating VM-Protect 9 to latest Build didnt solve the problem.

I dont know how to go further:
Here is the Log:

##################################################################
Task 'Web-PROD' fehlgeschlagen: 'Erstellen eines Backups fehlgeschlagen.
Zusätzliche Info:
--------------------
Fehlercode: 3
Module: 435
Zeileninfo: 555b5abba0950340
Felder:
Nachricht: Erstellen eines Backups fehlgeschlagen.
--------------------
Fehlercode: 32786
Module: 114
Zeileninfo: 28314c961de7d337
Felder:
Nachricht: Vorbereitung auf das Backup fehlgeschlagen.
--------------------
Fehlercode: 353
Module: 149
Zeileninfo: a71592046cb2c5f6
Felder:
Nachricht: Backup der Gruppe fehlgeschlagen.
--------------------
Fehlercode: 2
Module: 218
Zeileninfo: 338a407ad20e0987
Felder:
Nachricht: Fehler während Ausführung der Backup- und Recovery-Engine aufgetreten.
--------------------
Fehlercode: 1080
Module: 1
Zeileninfo: b43e776571144dee
Felder:
Nachricht: Endgültiges Ausführen des Aktionsergebnisses ist fehlgeschlagen.
--------------------
Fehlercode: 1
Module: 7
Zeileninfo: a5695862aaf8e6e4
Felder:
Nachricht: Durchführung der Aktion mit dem Archiv 'avfs:/smb?//192.168.12.2/Backup%20-%20CMS/Web-Prod.TIB' fehlgeschlagen. Fehler: 'Internal error: number of backed up sectors differs from counted'.
--------------------'.

####################################################################

Kindly Regards

TobWee

 

Edit1:

I also tryed this solution:
https://kb.acronis.com/content/25536
It also didnt solve the problem.

Acronis Program Manager
Posts: 22
Comments: 3743

Hi,

The 'Internal error: number of backed up sectors differs from counted' is a very low level one and it indicates issues with particular backup archive structure. You mentioned that you tried to re-create the backup plans, but have you tried to create new _archives_ (when selecting Where to backup)? The next step is to localize the issue: take one VM which produces the problem and create a separate plan for it, saving it into _new_ archive into separate folder. If the problem is still reproduced, then try to disable "deduplication" option in the backup task settings and again re-create the archive. Another possible cause is broken CBT record on the specific VM, which can be workarounded by disabling CBT option in the backup plan settings (or via resetting CBT on the VM). Also you can try changing the archive format from default "Single file" to "Multiple files" - it is possible when you create a new backup plan.

Thank you.

Beginner
Posts: 0
Comments: 6

Hello Vasily,

thank you for your fast answer !

I created a new task, a new plan and also a new folder to safe the tib (so it created a new archive).

I already tryed it without the CBT-Option, the result was exactly the same.
The backup task tooks 19 hours für the 1.054TB machine and about 3 days for the 6TB machine.

So now i will try it with disabling the deduplication and if this will not solve the problem i try it with "create multiple archives".

So i started the backup task without deduplication and i saw something in vsphere:

Task:
Reconfiguring the virtual machine "Acronis Appliance"
Status:
The given Harddisk-Delta-Format "redoLogFormat" is not supportet

 

I havent seen this until now.

Regards TobWee

 

 

 

 

Acronis Program Manager
Posts: 22
Comments: 3743

Hi,

The last message can be given if the backup is performed in hotadd mode and the appliance tries to attach the backedup disks to itself, while the disks cannot be attached because appliance is running on the datastore which doesn't support this format of delta files as are supported on the datastore where the backed up VM resides. In other words likely something has changed in your infrastructure for these huge VMs which is now causing the problem. The general recommendation is to deploy appliance to the same datastore where the backedup VMs reside - thus eliminating the possibility of such problems.

Thank you.

Beginner
Posts: 0
Comments: 6

Hi,

In this infrastructur we have 7 Datastores and 1 Acronis Appliance.
Your right the 3 running backups comes from the VM's which are on the same Datastore like the Acronis Appliance.

The type of the Datastores is all the same (VMFS5).
So i should provide 1 Acronis Appliance on all Datastores ?
What should i do if the VM's use more than 1 Datastore ?

Ydo you think this is the problem in our case ?

Regards

TobWee

Acronis Program Manager
Posts: 22
Comments: 3743

Hi,

In general it is sufficient to deploy one appliance to the largest datastore - it should be good for other machines backup as well. So if you deploy appliance to that largest datastore, the 3 VMs which are backed up properly will continue to be backed up fine, and the 2 problematic machines should also be good.

I'd first of all tried to validate the concept by deploying a separate appliance to the largest datastore and tried to back up one of the problematic VMs using it.

Thank you.

Beginner
Posts: 0
Comments: 6

Hi,

thank you very much !
Actually the appliance is hosted on the second largest datastore.
I will try to fix it with deploying a new one on the largest datastore.

Regards

TobWee

Beginner
Posts: 0
Comments: 6

Good morning Vasily,

i deployed a new backup appliance in the largest datastore (this is the datastore for one of the problematic machines).

So i configured 2 tasks, one of the problematic vm's and one of the well backed up vm's.

I have exactly the same problem.
Even this time i saw the problem:
###########################################
Task:
Reconfiguring the virtual machine "Acronis Appliance"
Status:
The given Harddisk-Delta-Format "redoLogFormat" is not supportet
###########################################

The task failed with the same errorcodes.
 

Could there be other possibilities which are causing this error ?

Regards TobWee

Acronis Program Manager
Posts: 22
Comments: 3743

Hi,

The error is thrown from VMware when the backed up disks are tried to be attached to appliance because the disks delta format is changed depending on the disk size (see format differences here) and this format is not supported by appliance machine which results in the error:

https://www.vmware.com/support/developer/converter-sdk/conv55_apireference/vim.fault.DeltaDiskFormatNotSupported.html

 

I'm afraid that without looking at your specific environment and checking the config of both appliance and the backed up VMs it's quite hard to guess the reason for the failure. I can only suggest to try updating the virtual appliance virtual hardware from vSphere client and re-trying the operation. If this doesn't help then the only option would be to contact our support team and continue the investigation.

Thank you.

Beginner
Posts: 0
Comments: 6

Hi Vasilly,

i ´thought the changing of the deltaformat is only for the older ESXi Versions.
We use V.5.5.

Unfortuanately our supportcontract ends last year.
Maybe there is a Disk-limit for the acronis appliance V9 ?

Regards

TobWee

Acronis Program Manager
Posts: 22
Comments: 3743

Hi,

There is no such limit imposed by appliance itself - it may be caused in VM version of the appliance machine in vSphere, which is why I suggested to upgrade the virtual appliance hardware (power off appliance->upgrade virtual hardware->power on). It may help but if not then I'm afraid without support assistance it would be hardly possible to get to the bottom of the issue.

The "brute force" workaround would be to use Windows Agent instead of appliance to perform backups - in this case there will be network block device (NBD) mode used instead of HotAdd (where attaching disks to appliances is required), so the backup should be possible using this approach. It can be then further expanded to Direct SAN Access mode, if your datastores are backed up iSCSI/FC SAN. See details here.

Thank you.