cancel
Showing results for 
Search instead for 
Did you mean: 

Error in some VMware backups snapshots - (4275) Unable to consolidate Virtual Machine Disks

andrich2016
Level 4

We are running a Netbackup Server 8.2 and two virtual machines presents  (4275) Unable to consolidate Virtual Machine Disks  error daily. 

Is this a Netbackup or a VMware issue?

The VMware version is 6.7.

 

1 ACCEPTED SOLUTION

Accepted Solutions

andrich2016
Level 4

Hello everybody

Thanks for all contributions.

The case was solved using this vwmare kb:

https://kb.vmware.com/s/article/84475

a- It could be vpxa-worker ----> this can be fixed by restart vpxa agent using the below commands:

# /etc/init.d/vpxa stop

# /etc/init.d/vpxa start

b- It could be hostd or hostd-profiler ---> this can be fixed by restarting hostd agent using the below commands:

# /etc/init.d/hostd stop

# /etc/init.d/hostd start

 

View solution in original post

5 REPLIES 5

quebek
Moderator
Moderator
   VIP    Certified

Hello

This is VMWARE related issue - ask your VM admins to deal with it.

Hamza_H
Moderator
Moderator
   VIP   

Hello,

Well, regarding the error, it says that the consolidation fails, which is in general because there are some snapshot locks somewhere, sometimes, there are "stuck" lock files on the backups host under /tmp/vmware-root/ or C:\Windows\TEMP\vmware-SYSTEM , make sure there is no lock file there for the specific VM, if yes, delete them and re-run your backup..

digging into logs may, for example vxms at high verbosity, help you identify which file is causing the problem.

 

Here is a veritas technote : https://www.veritas.com/support/en_US/article.100034022

 

**edited: added Windows path for lock files and veritas technote**

Dollypee
Moderator
Moderator
   VIP    Certified

Hi @andrich2016 ,

In addition to @Hamza_H comment, also verified there are no stale snapshots. you can verify this by right clicking affected VM, point to snapshot manager and ensure there not stuck snapshots showing. 

Let us know the outcome of your troubleshooting. Thanks

Krutons
Moderator
Moderator
   VIP   

I've seen where VM's are still locked even when there are no stale snapshots sitting in /tmp/vmware-root/ and there are no hung processes on the backup host as well. It's only a happened a few times but I needed to reboot the backup host.

andrich2016
Level 4

Hello everybody

Thanks for all contributions.

The case was solved using this vwmare kb:

https://kb.vmware.com/s/article/84475

a- It could be vpxa-worker ----> this can be fixed by restart vpxa agent using the below commands:

# /etc/init.d/vpxa stop

# /etc/init.d/vpxa start

b- It could be hostd or hostd-profiler ---> this can be fixed by restarting hostd agent using the below commands:

# /etc/init.d/hostd stop

# /etc/init.d/hostd start