Skip to content

Virtual Library Posts

EMC DD – Error: Failed to call RPC function ‘DDBoostFcWriteFile’: Failed to open file ‘

To resolved this issue in version 12 follow this procedure:

1) Download the fix  and unzip it to a temporary location.
2) When possible, stop the Veeam Installer service
3) Then go to this location: C:\Windows\Veeam\Backup
4) Rename the VeeamDeploymentDll.dll to VeeamDeploymentDll.dll.orig
5) Copy the DLL from this fix you unzipped to the same location (C:\Windows\Veeam\Backup)
6) Repeat steps 4 and 5 for the additional locations below as needed (some paths may not exist on all managed servers, replace in all that do):

C:\Program Files (x86)\Veeam\Backup Transport\GuestInteraction\VSS\Packages

C:\Program Files\Common Files\Veeam\Backup and Replication\Mount Service\Packages

C:\Program Files\Veeam\Backup and Replication\Backup Catalog

C:\Program Files\Veeam\Backup and Replication\Backup\Packages

C:\Program Files\Veeam\Backup and Replication\Enterprise Manager

C:\Program Files\Veeam\Veeam Distribution Service\Packages

7) Start the Veeam Installer Service
8) Retry the backups


Veeam – Issue after patch to version

After installing the patch we got this issue when open the console “could not create unique index “backups_tem_id_idx” checking the logs we can found this.

[23.08.2023 10:54:36.982] <21> Error        could not create unique index “backups_temp_id_idx” (Veeam.Backup.Common.CPsqlException)
[23.08.2023 10:54:36.982] <21> Error        [CExceptionHandlingDBAccessorDecorator]
[23.08.2023 10:54:36.982] <21> Error        —————————————————————-
[23.08.2023 10:54:36.982] <21> Error        Stored procedure execution failed:
[23.08.2023 10:54:36.982] <21> Error        —————————————————————-
[23.08.2023 10:56:27.923] <01> Error        Backup service has failed.

This is a known issue and Veeam provide the hotfix. Please download the hotfix from here and follow the next steps:

1. Make sure your build version is P20230718

2. Make sure no Jobs or Restores are running.

3. Run veeam_backup_12.0.0.1420_PrivateFix_TF550096.exe as Admin

Powershell command to Identify the Virtual Machine with CDROM Connect

Keeping CDROMs plugged into Virtual Machines can inhibit DRS/vMotion from working well for these Virtual Machines, as such it is best practice to remove CDROMs when not needed, so follow the commands to identify them.

List all Virtual Machine with CDROM connect:

Get-VM | Get-CDDrive | Where {$_.extensiondata.connectable.connected -eq $true} | Select Parent

Disconnect all CDROM from all Virtual Machine

Get-VM | Get-CDDrive | Where {$_.extensiondata.connectable.connected -eq $true} | Set-CDDrive -NoMedia -confirm:$false

Failed to enter namespaces maintenance mode due to Error com.vmware.vapi errors.unauthenticated

You can’t put your host in maintenance due to this error “Failed to enter namespaces maintenance mode due to Error com.vmware.vapi errors.unauthenticated

It’s time to check if you have a certificate expired, login to VCSA over ssh and execute this command:
for store in $(/usr/lib/vmware-vmafd/bin/vecs-cli store list | grep -v TRUSTED_ROOT_CRLS); do echo “[*] Store :” $store; /usr/lib/vmware-vmafd/bin/vecs-cli entry list –store $store –text | grep -ie “Alias” -ie “Not After”;done;

The WCP certificate are expired

[*] Store : wcp
Alias : wcp
Not After : Jan 10 11:48:31 2023 GMT

To renew the certificate execute this command /usr/lib/vmware-vmca/bin/certificate-manager with option 6 “Replace Solution user certificates with VMCA certificates”

Error Installing the VMtools with error vc_runtimeminimum_x86.msi

When we try to update the VMtools we got an installation package vc_runtimeminimum_x86.msi’ error appears, to correct this problem you must follow the following steps.

Run regedit.exe as administrator
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products
Perform a search for the string {2E72FA1F-BADB-4337-B8AE-F7C17EC47D1D}
You should find the path being referenced in one of the subkeys (see attached example)
Delete the key {2E72FA1F-BADB-4337-B8AE-F7C17EC47D1D}. 


vCenter 7u2x – ERROR: Full backup not allowed during VM snapshot

Unable to backup on version 7u2a, checking the logs from /var/log/vmware/applmgmt/backup.log is:

[VTSDBBackup:PID-117743] [] INFO: Starting the VTSDB backup
[VTSDBBackup:PID-117743] [] INFO: Download Postgres initialize files: /storage/vtsdb/vtsdbdata/health_status_worker.conf,/storage/vtsdb/vtsdbdata/postgresql.conf,/storage/vtsdb/vtsdbdata/,/storage/vtsdb/vtsdbdata/,/storage/vtsdb/vtsdbdata/pg_hba.conf,/storage/vtsdb/vtsdbdata/current_logfiles,/storage/vtsdb/vtsdbdata/pg_ident.conf
[] INFO: Download Postgres initialize files: storage/vtsdb/vtsdbdata/health_status_worker.conf,storage/vtsdb/vtsdbdata/postgresql.conf,storage/vtsdb/vtsdbdata/,storage/vtsdb/vtsdbdata/,storage/vtsdb/vtsdbdata/pg_hba.conf,storage/vtsdb/vtsdbdata/current_logfiles,storage/vtsdb/vtsdbdata/pg_ident.conf
[] INFO: tarCmd = [‘/usr/bin/tar’, ‘-cz’, ‘-C’, ‘/’, ‘–ignore-failed-read’, ‘–no-recursion’, ‘–warning’, ‘no-file-ignored’, ‘storage/vtsdb/vtsdbdata/health_status_worker.conf’, ‘storage/vtsdb/vtsdbdata/postgresql.conf’, ‘storage/vtsdb/vtsdbdata/’, ‘storage/vtsdb/vtsdbdata/’, ‘storage/vtsdb/vtsdbdata/pg_hba.conf’, ‘storage/vtsdb/vtsdbdata/current_logfiles’, ‘storage/vtsdb/vtsdbdata/pg_ident.conf’]
[] ERROR: Encounter error during backup VCDB.
Traceback (most recent call last):
File “/usr/lib/applmgmt/backup_restore/py/vmware/appliance/backup_restore/components/”, line 1936, in BackupVCDB
raise Exception(‘Full backup not allowed during VM snapshot’)
Exception: Full backup not allowed during VM snapshot
2022-12-14T09:44:23.79 [20221214-094419-20395099] [VCDBBackup:PID-117740] [] ERROR: Full backup not allowed during VM snapshot

This is generally caused by an interruption to the backup, or a restore from backup, leaving a flag file in place.

Remove or rename /etc/vmware/backupMarker.txt and re-run the backup.

How to enable Hardware-Assisted Virtualization with PCI Passthrough Devices

Since the upgrade to version ESXi 6.7 U1 and newer, it’s impossible to enable Hardware-Assisted Virtualization with PCI Passthrough Devices by GUI and it’s not supported by VMware, but it’s possible to enable by editing the VMX file.

Follow the procedure:

1- Shutdown the VM

2- Add this configuration

  • vhv.allowPassthru=”TRUE”
  • vhv.enable=”TRUE”

3- Power On the VM