VMware Cloud Director 10.5.1.1
This issue caused by the NFS share used from Cloud Director no longer available.
To apply the following workaround to help recovering Cloud Director:
1) To use a new NFS server and create the NFS share with same name and IP addressed used previously.
2) To mount the new NFS share on the Cloud Director cells. See Cloud Director requirements when using NFS for the transfer server storage
3) To create the following folders:
appliance-nodes
gosc
cells
2) To copy the response.properties
file from the primary node in the data/transfer folder:
cd /opt/vmware/vcloud-director/etc
cp response.properties /opt/vmware/vcloud-director/data/transfer/response.properties
3) To change the ownership of the folders and file with the command:
chown vcloud:vcloud appliance-nodes
chown vcloud:vcloud cells
chown vcloud:vcloud gosc
chown vcloud:vcloud response.properties
4) To change the permission on the appliance-nodes
folder to allow the appliance to resync:
chmod 750 appliance-nodes
5) To execute the appliance resync on the primary node and on each of the standby nodes with the command:
systemctl restart appliance-sync.timer
We highly recommend that you keep copies of the Cloud Director database backup on different location from the NFS server. This will make sure that if the above does not work, you will still have the ability to recreate the Cloud Director Environment and restore it from the backup.