Piszki Lab | EN

My case study in the clouds…

Veeam Backup – Consolidation is needed (unable access file since it is locked)

| 2 Comments

We recently bought a Veeam Availability Suite v8 Enterprise edition, we absolutely love this solution, it is simple and effective. In the era of applications written in Java positively distinguished by low demand for resources and speed. In Veeam Backup, on our View environment, deduplication ratio achieved x3,7 (for “thick” machines intended for developers). We are also holders of extensive private cloud based on vCloud Director, the ability to safely perform a backup of the environment is very important to us (and this functionality has Veeam Backup).

veeam4

Recently after a few backups noticed (thanks to Veeam ONE) that several machines managed by vCloud Director shows “Virtual machine disks consolidation is needed”. Unfortunately attempt to make drive consolidation ends following messages (An error occurred while consolidating disks: msg.snapshot.error-DISKLOCKED, An error occurred while consolidating disks: msg.fileio.lock.):

veeam1

veeam2

Checking the machines themselves no results (no locked files), led me to solve this KB and early experience with VMware Data Protection (where the same error). Both solutions, Veeam and VDP, use the same method. VM drives assemble to the Veeam machine directly, create a snapshot and copy the data. If any of these processes is interrupted (eg. A network error), the backup fails with the error and the drive is not “unmounted” from the Veeam machine. You can check this very easily in the settings of the backup server:

veeam3

All crossed the disks are the remnants of failed backups. Just delete them to drive consolidation was completed correctly.

veeam5

Interestingly, in our case, all the backups with vCloud Director vApp completed correctly! Veeam Backup has not reported a single error associated with this task.

Rate this article:
[Total: 1    Average: 4/5]

Author: Piotr Pisz

Computer always, since I got a Commodore 64 at the end of primary school, through his beloved Amiga and Linux infinite number of consoles, until today, fully virtual day. Since 2001, Unix/Linux Systems Administrator, for seven years a faithful companion and protector of Solaris system, until his sad end. In the year 2011 came in the depths of virtualization, then smoothly ascended into the clouds and continues there today. Professionally working as Systems Architect in the Polish Security Printing Works.

2 Comments

  1. I recently had this error and looking at the interwebs there seemed like a million solutions some of which were rather drastic.

    I actually fixed rather easily by creating a new VM snapshot, then deleted it and was then able to consolidate the disks again.

    Hopefully this may work for you.

    • Hello Julian,
      You’re right, there are plenty of solutions.
      Once I had the same thing in the case of Avamar and take snapshot helped.
      In the case of VDP and Veeam helped unmounting drives (for me).

      Regards,
      Piotr

Leave a Reply

Required fields are marked *.


.

Enjoyed the post? Support Piszki Lab | EN, click on the AD! :-)

.