No space left ?

Hi,

The error is actually referring to free space left on virtual appliance side (on the 2nd 2GB disk), rather than to disk space on datastore or .tib archive. The possible reasons are:

1) Presence of /tmp/core file which consumed all the space
2) Too large /var/log/messages file

These files can be deleted via going to virtual appliance console (Ctrl+Shift+Alt+Space+F1, then Alt+F2) and issuing the following commands:

#rm -rf /tmp/core
#rm -rf /var/log/messages

The free space can be checked by the following command:

#df

Prior to doing so it would make sense to save these files from the virtual appliance via WinSCP (as described in http://kb.acronis.com/content/36100 in troubleshooting section) and send them to our support team for investigation, so that we can check what could be the root cause of the issue.

It can also be that there were too many files generated under /var/lib/Acronis/vmProtect/VMMS/Temp/ path (there are temporary files generated during file browsing inside the archives) and this folder contents may need to be deleted.

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

Hi Vasily,

you're right (as usual :)

No space left in virtual vmProtect appliance (see attachment).

But did you know why ? It seems to be a recurrent issue. Is it a bug ? does vmP need a crontab to purge ?
vmP Virtual disk size should it be expanded?

Thank you.

ps for temp:
# du -sh /var/lib/Acronis/vmProtect/VMMS/Temp/
72.0K /var/lib/Acronis/vmProtect/VMMS/Temp

Hi,

The problem here is that sometimes there is /tmp/core generated as the result of crash, however most of the 'core' files that we've got so far for investigation were all trunkated and it was impossible to investigate them, i.e. the core took up all the space, but still didn't finish (the issues found in the complete 'core' files have been all addressed in the released versions of vmProtect 8, so only the incomplete cores problems are left). To address this type of issue we will increase the size of the virtual appliance disk up to 4Gb in the 9th version of Acronis vmProtect. This will be enough for the maximum size of the /tmp/core file and we'll be able to investigate it in order to fix the root causes. The core file may be larger than the size of the disk especially in case the amount of memory assigned to appliance is greater than the default 1GB (since core is in fact a memory dump).

The other side of the issue is /var/log/messages size which may grow up due to some Linux issues which we've yet to reproduce or investigate thoroughly. What we have found that at some point the Linux kernel starts to spam messages into /var/log/messages file and does not stop until it fills the whole disk (usually takes around 30 minutes to fill it up). This might be related to the events happening in the environment, i.e. network changes/dropouts, though the actual cause is still unclear. To avoid the impact of this issue we will add the logs rotating mechanizm into the 9th version of vmProtect so that /var/log/messages file does not grow larger than 20-30MBs and therefore the issue will be gone.

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

Hi,

the backup is ok now :)

Do you think the Windows version of vmProtect is better than the appliance (no crash, no space issue) ?

Are there number of virtual machines or file size to the maximum recommended TIB appliance?
Is it possible to resize the virtual disk (using Gparted or Acronis Disk Director for example) to avoid this bug?

Do you know when vmProtect v9 will be available ?

thank you

Hi,

The Windows Agent has its own pros and cons, such as for example absence of hot-add backup method, dependancy on Windows infrastructure, however crashes may occur no matter whether you use appliance or Windows Agent. The space issue should not affect Windows Agent though.

One Acronis vmProtect agent (no matter appliance or Windows agent) officially supports up to 100 VMs and what concerns the maximum TIB size - there is no limitation which we have discovered until now (we had archives up to 3TB in size with no noticable performance impact). There is one issue related to the _number_ of recovery points inside the same archive (the size does not matter) where if deduplication is enabled then incremental backups into this archive will be slowed down when the number of recovery points exceeds 200-500 (the larger the number is - the greater performance impact is). This issue can be worked around by disabling deduplication in options and the normal fix will be available in vmProtect 9.

The virtual disk of Appliance can be resized: first increase the size of the virtual disk in VM (appliance) properties in vSphere client, then add CD-ROM device to appliance and boot it from Acronis Disk Director boot media. After that you will be able to increase the ext3 2GB partition via ADD. Not really convenient but still a workaround.

What concerns vmProtect 9 release, I'm unable to publish the exact dates, though I can say that we should be able to release it this year. I'd say "soon" (c) Blizzard :)

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

OK thank you for all informations !
I'm waiting for the vmProtect v9 :)

Same here. Got the same here. I just forwarded the logs to a different logging server.

Hello, we have problems running backup task on 1 of our virtuals servert (Ver. 11.7) we did a restart and when booting we got the following error:

No volumes group found

/etc/lvm/.cache.tmp: write error failed: no space left on device

I read that maybe my log folder are full, but, I do not know linux commands, anyone can give some light to resolve this?

Thank you very much!

Hi Eliu,

You can connect to a VA with the WinSCP tool and check the contents of 

/var/lib/Acronis/ 
/usr/lib/Acronis/ 

to find out which directories are flooded with logs and clean them up.

Thank you Ekaterina, I will try that.