Manual Backup Fails Across VMware Cloud Foundation Components.
Article ID: 452213
Updated On:
Products
Issue/Introduction
Manual Backup fails across VMware Cloud Foundation Components:
"Failed to create backups for VCF services runtime components 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'. Verify components are accessible and sufficient storage is available. Backup workflow failed for component: vcf-sddc-lcm".
To check the logs:
Login to one of the control pane via: vmware-system-user ID (Password would be obtained from deployed JSON file). Elevate the ID to root running command su -i
Once you logged in as root to control pane run below command to list the logs file for the backup task:
kubectl get pods -A | grep -iE "depot|lcm|fleet|backup"
copy the file with recent task and below command to view the backup logs:
Kubectl logs -n vcf-sddc-lcm <log file name>
Log snippet:
yyyy/mm/dd 05:39:12 NOTICE: sftp://svc_vcfbackup@domain-name@SFTP-server-IP-or-name:22//Backups/VCF_BACKUP/vcf/backups/xxxxxxxxxxxxxxxxxxxxxx/9.1.0.0200.25555874/vcf-sddc-lcm/06496737-fe94-4567-bcf8-27f8677995b6/9.1.0.0400.25570103/2026-08-17T05-35-45Z/: -- checksum is in use but the sourc
e and destination have no hashes in common; falling back to -- size-only
yyyy/mm/ddT05:39:13Z INFO - Creating a new backup manifest for this full backup.
yyyy/mm/ddT05:39:14Z INFO - Current backup manifest
"metadata": {
"id": "06496737-fe94-4567-bcf8-27f8677995b6",
"version": "9.1.0.0400.25570103",
"type": "vcf-sddc-lcm"
"name": "vcf-sddc-lcm"
"cluster_id": "xxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"cluster_version": "9.1.0.0200.25555874"
"encryption_passphrase_hash": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"files": []
2026-08-17T05:39:14Z INFO - Updated backup manifest
"metadata": {
"id": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"version": "9.1.0.0400.25570103",
"type": "vcf-sddc-lcm",
Environment
VMware Cloud Foundation (VCF) 9.1.
Cause
The Backup Service ID and directory configuration parameters specified during manual backup execution do not adhere to required VCF configuration standards.
Resolution
Review the current Backup Service ID and backup directory parameters against official VCF documentation requirements.
For example:
Service ID name: [email protected]
Directory path: /Backups/Path-location(Irrespective of SFTP OS: Windows or Linux). >> this would create the backup files in C drive of Windows
If you wish to have the backup files created in different directory(suppose D directory) then give the path as below:
/D:/Backups/<backup-absolute-path>
Update the Backup Service ID and directory configuration to align with proper naming and path standards.
Initiate the manual backup job and monitor the operation to confirm successful completion.
Additional Information
Note : Once you update the correct path and ID, it would take 10 to 15 mins to update and sync the update task.
Backup completion logs would look like below:
root@control-pane[ ~ ]# kubectl logs -n vcf-sddc-lcm <log-file name>
Executing on-demand WAL backup command in target pod
Master pod identified as vcf-sddc-lcm-db-0 is Running
Backup output: yyyy-mm-dd 05:37:37.429 - /scripts/postgres_backup.sh - I was called as: /scripts/postgres_backup. sh /home/postgres/pgdata/pgroot/data
yyyy-mm-dd 05:37:37.521 - /scripts/postgres_backup.sh - producing a new backup
INFO: yyyy-mm-dd 05:37:37.544393 Backup will be pushed to storage: default
INFO: yyyy-mm-dd 05:37:37.594903 Calling pg_start_backup()
INFO: yyyy-mm-dd 05:37:37.627452 Initializing the PG alive checker ( interval=1m0s) ...
INFO: yyyy-mm-dd 05:37:37.627481 Starting a new tar bundle
INFO: yyyy-mm-dd 05:37:37.627500 Walking ..
INFO:
yyyy-mm-dd 05:37:37.627637 Starting part 1
yyyy-mm-dd 05:37:37.855788 Packing ..
INFO: yyyy-mm-dd 05:37:37.856998 Finished writing part 1.
yyyy-mm-dd 05:37:38.066866 Starting part 2 ..
yyyy-mm-dd 05:37:38.066891 /global/pg_control
yyyy-mm-dd 05:37:38.067753 Finished writing part 2.
yyyy-mm-dd 05:37:38.067783 Calling pg_stop_backup()
yyyy-mm-dd 05:37:38.085855 Starting part 3 ...
yyyy-mm-dd 05:37:38.089958 backup_label
INFO: yyyy-mm-dd 05:37:38.089978 tablespace_map
INFO: yyyy-mm-dd 05:37:38.090019 Finished writing part 3.
INFO: yyyy-mm-dd 05:37:38.106232 Querying pg_database
INFO: yyyy-mm-dd 05:37:38.340762 Wrote backup with name base xxxxxxxxxxxxxxxxxxxxxxxx to storage default
Backup script completed successfully.
root@control-pane[ ~ ]#
root@control-pane[ ~ ]# kubectl logs -n vmsp-platform <log-file name>
yyyy-mm-ddT07:29:18Z INFO - Copy backup manifest to sftp:/D:/Backups/absolute-path/9.1.0.0200.25555874/vidb
/xxxxxxxxxxxxxxx/9.1.0.0100.25522734/yyyy-mm-ddT07-25-50Z
yyyy-mm-ddT07:29:19Z INFO - Successfully uploaded backup to sftp://[email protected]. [email protected]. 175/D: /absolute-path/9.1.0.0200.25555874/vidb/xxxxxxxxxxxxxxxxxxxxxxxxxx/9.1.0.0100.25522734/
yyyy-mm-ddT07-25-50Z/2026-08-17T07-25-50Z.base.tgz
yyyy-mm-dd 07:29:19 NOTICE: Config file "/root/.config/rclone/rclone.conf" not found - using defaults
yyyy-mm-ddT07:29:21Z INFO - Attempting to update output in secret multi-components-backup-xxxxxxxxxxxxxxxxxxxxxxxxxxxxx (resourceVersion: 29002677, attempt:
1/10)
yyyy-mm-ddT07:29:21Z INFO - Successfully updated output in secret multi-components-backup-xxxxxxxxxxxxxxxxxxxxxxxx
yyyy-mm-ddT07:29:21Z INFO - Backup has been completed successfully for component vidb.
yyyy-mm-ddT07:29:21Z INFO - Attempting to update messages in secret multi-components-backup-xxxxxxxxxxxxxxxxxxxx (resourceVersion: 29002886, attemp
t: 1/10)
yyyy-mm-ddT07:29:21Z INFO - Successfully updated messages in secret multi-components-backup-xxxxxxxxxxxxxxxxxxxxxxx
yyyy-mm-ddT07:29:21Z INFO - Hook values URL is not set, not setting hook output values
yyyy-mm-ddT07:29:21Z INFO - Updating backup state
configmap/vmsp-backup-state configured
yyyy-mm-ddT07:29:22Z INFO
- Backup state updated
yyyy-mm-ddT07:29:22Z INFO - Marking DB backup files as backed up
Feedback
