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.0, 9.0.2.2
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. Identify the Virtual Machine Name: Correlate the Managed Object ID (vm-XXXXXX) from error message from Export SRM Configuration wizard with the human-readable VM name using the vCenter Managed Object Browser (MOB).
Example: https://<vCenter_FQDN>/mob/?moid=vm-243562
3. Confirm VM presence in SRM DB:
- Connect using ssh to SRM appliance
- cd /opt/vmware/srm/dbtool
- Run the command "python SrmDbTool.py query VM_name"
4. If the VM name begins with vCLS-*, implement the workaround detailed in Broadcom KB 316514 to put the cluster into "Retreat Mode."
5. If the above symptoms and issue matches, please contact Broadcom Support for further assistance.
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