Vmprotect 9. cannot run backupjob. Disk full (its not)

Hi,

Typically such error is thrown from the share side, i.e. vmProtect asamba module gets this error when trying to write new data into the existing archive. It has grown pretty huge in your case. Have you set up any retention rules for the backups (automatic clean up)? I'd first of all tried removing some old recovery points from several VMs in View->Recovery Points and then re-tried to back up in order to verify whether the problem is really related to the size of the backup data. After that please contact our support team for assistance with the results of this check which would let us localize the issue.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Hi Vasily.

I tried to delete some recoverypoints in the backupjob. After a few minutes it told me the following.

Code: 27066484 (0x019D0074)
Line: 836463A653DED97A
Message: An error has occurred while executing command 'delete_slices'.
============

Code: 27066476 (0x019D006C)
Line: 3ACC6A274197F3A2
Message: A VELight Archive Browse Manager error has occurred.
============

Code: 28311564 (0x01B0000C)
Line: DA004EF1034B82A
Message: Failed to delete one or more backups.
============

Code: 10551415 (0x00A10077)
Line: 6EF4BE227EFF5580
Message: Failed to delete recovery points.
============

Code: 10551364 (0x00A10044)
Line: 266FAA7C48E31604
Message: Failed to delete the backups. Location login administrator
============

Code: 4195005 (0x004002BD)
Line: 97E50E642849A355
Message: The RemovePoints function error: Failed to remove backups.
============

Code: 458773 (0x00070015)
Line: 9D2DE1F088CBC4ED
Message: Disk is full.
============

Code: 262148 (0x00040004)
Line: 1F40BC5F43E9AE30
Message: The disk is full.

Yes it is a very large file. We have 180 days retention. We have that long retention because we need long retention (didnt think there were any limitations in size). I think maybe we should split the file in half but that doesnt change the fact that acronis seems to have problems handling large backupfiles. We still have about 4TB free on the backupdestination which is a windows server 2008 r2. We are not intressted in wiping all backupdata we have. Kind of defeats the point of backup if we have to delete it all and start from the beginning.
We have no problem storing other files on the same destination so i think it is vmprotect that is having problems. But i guess i will have to open a supportcase.

Hi,

I have consulted with our experts regarding the issue and such symptoms lead us to conclusion that the problem is related to the underlying NAS device which doesn't seem to handle files larger than 8TB (there is no such limitation in our code from what we have checked). This is also proven by the fact that even manual deletion of recovery points doesn't work (since the deletion process requires writing into the archive). Still you can recover from this archive as it requires only read access to the file and it should work properly.

Are there any logs on the NAS which can be checked after reproducing the problem? Likely they would contain some evidences.

As a workaround you can split the backup task into 2-3 smaller ones which will be backing up less number of VMs (for example 3-4 instead of 10) into separate archives on the NAS. This would let you comply with your retention policy and at the same time keep the archives under the 8TB limit.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Hi!

The backup destination is not a nas i is a IBM server with internal disk running Windows Server 2008 R2. The disk is formatted as NTFS (GPT) so it is far from 16TB which is the max file size for NTFS. There is no error in the windows server. Have you had other customers that have had over 8TB in a single TIB?
I guess i will have to split the jobs into smaller ones to keep the size down.

Hi,

Thank you for the clarifications, it makes sense. The problem here is that the "Disk is full" error may be thrown by our code in different situations (which do not necessarily mean outage of capacity), when the data cannot be written into the archive, so we have to kind of guess the reason. For proper investigation we'll need to insert additional breakpoints into the code which means that there will be a custom build required (and for starting this process it's better to contact our support team).

Also to answer your question: so far I've seen only 4TB archive maximum. You are the first to have such huge one (at least the first one to report any problems) :)

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Hi!

I've made some additional research and it looks like the problem is related to Linux used on Acronis vmProtect appliance side. By default we use x32 bit kernel which has limitations on the size of the files it can handle (it is close to 8TB), so using a x64 bit kernel should help to resolve the problem. I will send you a private message with the link to this custom build in the next several minutes (luckily I have it by hand created for different case). You can upgrade your existing appliance to this build and try to run the existing backup task (which backs up to that huge archive) to see how it goes. Please let me know the result in any case.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Hi Vasily!

Superb. I have now upgraded the appliance to the version you sent me. I will se how the job goes tonight and i will get back to you regardless of success or failure.
After this hopefully works i will try break down the job into smaller portions to avoid the file to get so large.
Best regards
Björn

Hi Again Vasily!

Just wanted to let you know that the backup has been running like it should all weekend without a problem.
Thank you so much for the help. We will now try to split up the jobs. But now i know that we can use the large file and the retention that we want without throwing half a year of backups away.

Thank you again and have a good day
Best regards
Björn

Hi Björn,

Thank you for the confirmation! I'm really glad we could help :)

P.S. In future versions we will be using x64bit Linux kernel by default so this should not be a problem.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Hi.

It looks like i'm another customer with the same issue, my tib file from a single server with 30 days retention time got to 7.99GB and now stops with disk full error.

I'm using the latest backup for vmware 9.2.10535.

The backup file is stored on a win 2012 server with ntfs formatted, the partition is 19TB and has more than 3TB free space.

How to get the 64bit appliance to allow bigger tib files?

Thanks in advance

Hi Markus,

The x64 bit appliance requires a new build to be created. The build I've sent before in this thread (in 2014) was based on an old version (internal ID: TTASK-8980), so for you a new one needs to be created. To start this process please submit a support ticket to our support team with reference to this thread.

Thank you.

--

Best regards,

Vasily

Acronis Virtualization Program Manager

Thanks Vasily for great support. Will do a support ticket as recommended by you.

Really hope that version 10 will have 64bit kernel by default and also other improvements like direct attached storage larger than 2TB. Looking forward to Version 10...  :-D

Hi,

we have the same issue. We're running latest Appliance version. Backup-Destination QNAP Nas with 12 TB.

Filesize: 8TB

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

Fehlercode: 4

Module: 4

Zeileninfo: 1f40bc5f43e9ae30

Felder:

Nachricht: Datenträger ist voll.

--------------------'.

Is there already a new x64 build available  for download?

Best regards

Norman

You'll need to request an installer image by support and reference to the comment of Vasily.

Hope the version 10 will be 64bit by default and also the ability to mount direct attached storage larger 2 TB.

Best Regards

Hi,

I'm now uploading the Acronis Backup for VMware build with x64 kernel-based appliance inside (#10558) to the following FTP:

Pick up the locale you need (there are 4 languages uploaded) and feel free to use it.

The next version which we're working on contains x64 kernel by default and we won't use x32 versions any more (only for specific cases).

Thank you.

--

Best regards,

Vasily

Acronis Virtualization Program Manager

Hi Vasily,

We use, Acronis Backup for VMware (former vmProtect 9) Upgrade from 6/7/8 standart. We have the same problem.

One virtual machine size 8.5 TB.  The backup destination is Windows Server 2008 R2. The disk is formatted as NTFS (GPT).

Thank you.
Best regards.

Hi! 

Thank you for your posting! Are you using the latest available build? How much free space is available in the target location? Please attach the log files from the failing operation. 

Here is an updated link to the build 10558 with x64 kernel-based appliance inside