Veeam CDP IO Filter upgrade fails on vCenter 9.1 with iofiltermanager transition failed error

Products

• VMware vCenter Server

Issue/Introduction

After upgrading VMware vCenter Server to version 9.1, attempting to update the Veeam CDP replication IO filter from version 12.3.20 to version 13 fails.

A task in vCenter displays the following error: "a general system error occurred: iofiltermanager transition failed for iofilter ids: vee_bootbank_veecdp_12.3.20-1oem.8800.1.0.20613240 Location 'http://VEEAMSERVERFQDN:33035/dapi/bundle/8.0.0/12.3.20/" is not a valid file."

Environment

VMware vCenter Server 9.1
Veeam CDP

Cause

The vib_url column in the legacy vCenter vpx_cluster_iofilters database table contains an incomplete URL path (ending in a directory rather than the expected .zip file). Because this table is referenced during the transition to vSphere Lifecycle Manager (vLCM) single image management, the invalid URL breaks the IO filter conversion and update process.

Resolution

1. Take an offline snapshot or file-based backup of the vCenter Server.

2. Connect to the vCenter Server Appliance (vCSA) via SSH and access the vPostgres database: /opt/vmware/vpostgres/current/bin/psql -U postgres VCDB.

3. Remove the invalid IO filter entry from the database for the affected cluster using the following command (replace cluster-ID with the actual ID of the affected cluster): delete from vpx_cluster_iofilters where cluster_id = 'cluster-ID';

4. Disconnect from the database and exit the SSH session.

5. Push the IO filter again from the Veeam server; the installation will now successfully bypass the failed conversion process and utilize the vSphere 9.1 single image architecture.