When attempting to run a cron job to export VMware Site Recovery Manager (SRM) configurations, the export files are not created. While manual exports via the Site Recovery UI work as expected, the automated script fails when executed through crontab -e.
Checking the impex.log file reveals the following error:
2026-02-18 14:31:25,579 [srm-reactive-thread-12] ERROR com.vmware.vim.sso.client.impl.SoapBindingImpl - SOAP faultcom.sun.xml.ws.fault. ServerSOAP FaultException: Client received SOAP Fault from server: Invalid credentials
Product: VMware Live Recovery 9.x (formerly SRM)
Component: Import/Export Tool (Impex)
The issue occurs because the export.sh script contains legacy Site UUIDs that no longer match the environment. This typically happens if the SRM appliances have been unregistered and re-registered.
While re-registration is a standard recovery step, it generates new UUIDs for the SRM nodes. The manually configured export.sh script does not automatically update these values, causing authentication to fail with "Invalid credentials" when the script attempts to log in to vCenter using the stale IDs.
You must update the site UUIDs within the export.sh script on both SRM nodes to match the current environment.
Log in to the SRM appliance via SSH.
Back up the existing script:
cp /opt/vmware/impex/bin/export.sh /opt/vmware/impex/bin/export.sh.bak
Open the file for editing:
vi /opt/vmware/impex/bin/export.sh
Update the -g (local site ID) and -r (remote site ID) flags with the current UUIDs. This needs to be performed on both SRM appliances .
Save the file and test the script manually by running:
./opt/vmware/impex/bin/export.sh
Verify the cron job (crontab -l) is set to the correct path:
0 * * * * /usr/bin/sudo /bin/bash /opt/vmware/impex/bin/export.sh
SRM server GUID can be found in, just an example list of files
a. SRM vmware-dr.log
b. /opt/vmware/dr-rest/lib/dr-rest-api.properties
c . /opt/vmware/dr-client/conf/serviceAccount