Exporting SRM Configuration data fails with the error - Unable to generate file. ManagedObjectReference: type = VirtualMachine, value = vm-xxxx, serverGuid = a4397fe4-xxxx-40ad-xxxx-2adb7433863a is not part of the request.
VMware Live Site Recovery Manager 9.x
VMware Site Recovery Manager 8.x
VMware vSphere Replication 8.x
VMware vSphere Replication 9.x
The export process is failing because it cannot access information related to a specific virtual machine due to permission issues, a missing VM, or inconsistencies in the vCenter inventory related to this VM.
1. Ensure the user account performing the export has sufficient permissions to access the specified virtual machine within the vCenter inventory.
2. Get the Managed Object ID of the VM:
Connect to vCenter mob page https://<vcenter-server-IP-or-FQDN>/mob > content -> group-d1 (Datacenters) -> (SDDC-Datacenter) -> choose the link for the corresponding WorkloadDatastore based on the cluster location of the VM.
3. Verify that the VM is not contained in SRM Database and is not protected by SRM.
4. Verify if the VM "vm-XXXXX" actually exists in the vCenter inventory, if it's deleted & remove it from the SRM configuration.
Steps to take a srmdb dump
1. Stop the SRM service
[ ~ ]# systemctl status srm-server.service
[ ~ ]# systemctl stop srm-server.service
2. Dump the database to a text file
[ /opt/vmware/vpostgres/current/bin ]# ./pg_dump -U srmdb > /tmp/srmdb.txt
3. Start the SRM service
[ ~ ]# systemctl restart srm-server.service
Steps to collect VC vpx_vm table from vCenter's.
1. SSH to vCenter.
2. Run "/opt/vmware/vpostgres/current/bin/psql -d VCDB -U postgres" to connect to VC DB.
3. Run "\COPY (select * from vpx_vm) to '/root/vpx_vm.txt';" to collect vpx_vm table.
Validate if the VM "vm-XXXXX" exists in inventory
Export Site Recovery Manager Configuration Data Through the User Interface