Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vCSA Backup failed with "ERROR: Timeout! Failed to complete in 72000 seconds" (74737)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 15595Language:
English

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

Examining the backup.log file at /var/log/vmware/applmgmt

We can see the following highlighted entries

2019-09-02T01:09:49.553 [VCDBBackup:PID-36378] INFO: Executing command: /opt/vmware/vpostgres/current/bin/psql -U postgres -p 5432 -t -c "select pg_is_in_backup();".

2019-09-02T01:09:49.579 [VCDBBackup:PID-36378] INFO: Postgres on-line backup already finished. Skip stopping backup operation

2019-09-02T01:09:49.579 [VCDBBackup:PID-36378] INFO: Successfully cleaned up for VCDB backup.

2019-09-02T21:01:08.368 [MainProcess:PID-36035] ERROR: Timeout! Failed to complete in 72000 seconds

2019-09-02T21:01:08.369 [MainProcess:PID-36035] ERROR: BackupManager encountered an exception: Timeout! Failed to complete in 72000 seconds.

2019-09-02T21:01:08.371 [MainProcess:PID-36035] INFO: Cleaning up the backup job.

2019-09-02T21:01:08.371 [MainProcess:PID-36035] INFO: Cleaning up all running backup child processes.

2019-09-02T21:01:08.432 [MainProcess:PID-36035] INFO: Cleaning up all sizeFiles.

2019-09-02T21:01:08.433 [MainProcess:PID-36035] INFO: Cleaning up Lotus.

2019-09-02T21:01:08.433 [MainProcess:PID-36035] INFO: Successfully completed Lotus cleanup.

2019-09-02T21:01:08.433 [MainProcess:PID-36035] INFO: Cleaning up ComponentScripts.

2019-09-02T21:01:08.433 [MainProcess:PID-36035] INFO: Cleaning up ConfigFiles.

2019-09-02T21:01:08.433 [MainProcess:PID-36035] INFO: Cleaning up StatsMonitorDB.

2019-09-02T21:01:08.433 [MainProcess:PID-36035] INFO: Cleaning up VCDB.

2019-09-02T21:01:08.434 [MainProcess:PID-36035] INFO: Finishing full database backup

2019-09-02T21:01:08.434 [MainProcess:PID-36035] INFO: Retrieving postgres server listening port

2019-09-02T21:01:08.434 [MainProcess:PID-36035] INFO: Executing command: netstat -plnt.

2019-09-02T21:01:08.508 [MainProcess:PID-36035] INFO: Canceling running pg_start_backup() process.

2019-09-02T21:01:08.509 [MainProcess:PID-36035] INFO: Executing command: ['/opt/vmware/vpostgres/current/bin/psql', '-U', 'postgres', '-p', '5432', '-At', '-c', "SELECT pg_cancel_backend(pid) FROM pg_stat_activity WHERE pid <> pg_backend_pid()  and query ~ '^select\\ pg_xlogfile_name\\(pg_start_backup\\(.*\\)\\)\\;' "].

2019-09-02T21:01:08.540 [MainProcess:PID-36035] INFO: No pg_start_backup() process is running.

2019-09-02T21:01:08.541 [MainProcess:PID-36035] INFO: Checking whether Postgres online backup still in progress

2019-09-02T21:01:08.541 [MainProcess:PID-36035] INFO: Executing command: /opt/vmware/vpostgres/current/bin/psql -U postgres -p 5432 -t -c "select pg_is_in_backup();".

2019-09-02T21:01:08.570 [MainProcess:PID-36035] INFO: Postgres on-line backup already finished. Skip stopping backup operation

2019-09-02T21:01:08.571 [MainProcess:PID-36035] INFO: Successfully cleaned up for VCDB backup.

2019-09-02T21:01:08.571 [MainProcess:PID-36035] INFO: Cleaning up failed backup files.

2019-09-02T21:01:08.728 [MainProcess:PID-36035] INFO: Cleaned up the backup job.

2019-09-02T21:01:09.537 [MainProcess:PID-36035] INFO: Event com.vmware.applmgmt.backup.job.failed.event successfully posted to http://localhost:8085/sdk

2019-09-02T21:01:09.548 [MainProcess:PID-36035] INFO: Backup job failed.

Examining carefully the log, isolating the processes related to ComponentScriptsBackup

# grep -i "ComponentScriptsBackup" backup.log

a) vum component backup starts and finishes successfully

2019-09-02T01:01:08.334 [ComponentScriptsBackup:PID-36375] INFO: Starting backup component: vum

2019-09-02T01:01:08.343 [ComponentScriptsBackup:PID-36375] INFO: Execute vum script: /etc/vmware/backup/component-scripts/vum/backup_restore.py --startBackup

2019-09-02T01:01:08.370 [ComponentScriptsBackup:PID-36375] INFO: Dispatching stream.

2019-09-02T01:01:09.316 [ComponentScriptsBackup:PID-36375] INFO: Component vum backup successful.

b) imagebuilder component starts and finishes successfully

2019-09-02T01:01:09.317 [ComponentScriptsBackup:PID-36375] INFO: Starting backup component: imagebuilder

2019-09-02T01:01:09.317 [ComponentScriptsBackup:PID-36375] INFO: Execute imagebuilder script: /etc/vmware/backup/component-scripts/imagebuilder/backup_restore.py --startBackup

2019-09-02T01:01:09.334 [ComponentScriptsBackup:PID-36375] INFO: Dispatching stream.

2019-09-02T01:01:10.633 [ComponentScriptsBackup:PID-36375] INFO: Component imagebuilder backup successful.

c) imagebuilder component starts but there's not a line with INFO: Component rdb backup successful

2019-09-02T01:01:10.637 [ComponentScriptsBackup:PID-36375] INFO: Starting backup component: rbd

2019-09-02T01:01:10.637 [ComponentScriptsBackup:PID-36375] INFO: Execute rbd script: /etc/vmware/backup/component-scripts/rbd/rbd-backup-restore --startBackup

2019-09-02T01:01:10.643 [ComponentScriptsBackup:PID-36375] INFO: Dispatching stream.

--> Missing a line with INFO: Component rdb backup successful

Cause

This indicates that the rdb database backup has not completed. The reason is because that database is constantly being updated. Frequent changes or other thread/processes that modify it can cause a running backup to restart. If the restarts happen frequently enough, it may never complete and the backup of the VCSA times out.

Resolution

It will be fixed in vSphere 6.7 P01 release

Workaround

There are two possible workarounds

a) If autodeploy service is used, stopping autodeploy service before performing the backup

Note: Stopping autodeploy during the backup aims to prevent the backup from restarting. Note that vCenter may not PXE-boot hosts when autodeploy is stopped

# service-control --stop vmware-rbd-watchdog
Once that the backup finishes, the service can be restarted
# service-control --start vmware-rbd-watchdog

To disable autodeploy and make it persistent across reboots, by turning off the automatic startup of the service on reboot
# /usr/lib/vmware-vmon/vmon-cli --update rbd --starttype MANUAL

b) Skipping rdb backup
Note that with this second workaround autodeploy related information will not be present in the backup
# mv /etc/vmware/backup/manifests/rbd.json /etc/vmware/backup/manifests/rbd.json_bak

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
/dev/sdc の容量不足が原因で vRealize Operations Manager 8.0 へのアップグレードが失敗する (75327)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere

Related Versions:

VMware vSphere 6.7.x

Take Our Survey

Support Assistant