I seem to have come across this issue quite often recently, where Veeam reports “File is locked by running session (Name of Current Job)” I have found that more often than not, the issue is caused when a job is stopped incorrectly, for example the Veeam server is rebooted during a backup job. In this exampleRead More.
This issue started after I deleted a few .vib files from the backup repository in an effort to free up space on the repository for backup jobs. We are using Veeam 8. In viewing the backup job for that particular VM group, it now fail showing the following error message (screen shot embedded). It looks like the backup job tries to process then failed because it cannot find the .vib file that was created on 8/22/2015 because that .vib file I removed it from the repository. What should I do now to fix this problem?
You can uninstall third-party VIBs or VMware VIBs from your ESXi host.
VMware partners prepare third-party VIBs to provide management agents or asynchronously released drivers.
Install vCLI or deploy the vSphere Management Assistant (vMA) virtual machine. See Getting Started with vSphere Command-Line Interfaces. For troubleshooting, run esxcli commands in the ESXi Shell.
- If the removal requires a reboot, and if the host belongs to a VMware HA cluster, disable HA for the host.
- Determine whether the update requires the host to be in maintenance mode or to be rebooted. If necessary, place the host in maintenance mode.See Determine Whether an Update Requires the Host to Be in Maintenance Mode or to Be Rebooted. See Place a Host in Maintenance Mode.
- Install vCLI or deploy the vSphere Management Assistant (vMA) virtual machine. See Getting Started with vSphere Command-Line Interfaces. For troubleshooting, run esxcli commands in the ESXi Shell.
Procedure
- Power off each virtual machines running on the ESXi host. To shut down the guest operating system and then power off the virtual machinevmware-cmd --server=server_namepath_to_vm stop softTo force the power off operationvmware-cmd --server=server_namepath_to_vm stop hardAlternatively, to avoid powering off virtual machines, you can migrate them to another host. See the topic Migrating Virtual Machines in the vCenter Server and Host Management documentation.
- Place the host in maintenance mode. vicfg-hostops --server=server_name --operation enter
- If necessary, shut down or migrate virtual machines.
- Determine which VIBs are installed on the host.
- Remove the VIB.esxcli --server=server_name software vib remove --vibname=nameSpecify one or more VIBs to remove in one of the following forms:
- name
- name:version
- vendor:name
- vendor:name:version
For example, the command to remove a VIB specified by vendor, name and version would take this form:Note:The remove command supports several more options. See the vSphere Command-Line Interface Reference.