/var/log/vmware/vcf/domainmanager/domainmanager.log
YYYY:MM:DDTHH:MIN:SEC #### ERROR [vcf_dm,####,##] [c.v.v.c.f.p.n.a.ConfigureNsxtBackupScheduleAction,dm-exec-458] Error while configuring backup schedule for NSX Manager - <NSX MANAGER FQDN>com.vmware.vapi.std.errors.InvalidRequest: InvalidRequest (com.vmware.vapi.std.errors.invalid_request) (statusCode:400) => { messages = [], data = => {error_message=Restore error: Error while fetching fingerprint of fileserver <SDDC MANAGER FQDN> at port 22, httpStatus=BAD_REQUEST, error_code=29259, module_name=backup-restore}, errorType = INVALID_REQUEST
/var/log/vmware/vcf/operationsmanager/operationsmanager.log
YYYY:MM:DDTHH:MIN:SEC #### INFO [vcf_om,####,##] [c.v.e.s.c.services.InventoryUtil,om-scheduler-2] Provided server name '<SDDC MANAGER FQDN>' matches the IP or hostname of SDDC manager VM: true DEBUG [vcf_om,YYYY:MM:DDTHH:MIN:SEC ########,##] [c.v.v.b.s.BackupConfigurationServiceImpl,om-scheduler-2] The credentials are empty for the entity type SDDC_MANAGER and credential type BACKUP_PASSPHRASE
VCF 9
When SDDC Manager is deployed in a "reuse existing appliance" scenario, VCF automatically looks up the SDDC Manager's hostname from vCenter's VM inventory rather than from what is passed as input, and vCenter reported the short name for that VM, which is what got stored.
This is a known issue affecting VCF Installation on an existing fleet instance. Broadcom Engineering is working towards the fix release.
Workaround steps are available to overcome the issue and proceed with VCF installation successfully. The steps involve certain SDDC database table edits, as such, suggest to open a Support Request with Broadcom by referencing this article in the subject section of a new Support Case.