Automated backup (Veeam) fails to backup the "ESXI Configuration Backup" as the actual backup files is not in the Scratch Config location after a few minutes
search cancel

Automated backup (Veeam) fails to backup the "ESXI Configuration Backup" as the actual backup files is not in the Scratch Config location after a few minutes

book

Article ID: 400043

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

The vim-cmd creates a new folder with a UID as name in /scratch/downloads, then exports the current host config to /scratch/downloads as configBundle-<hostname>.tgz and then presents it under a specific URL to be downloaded via the browser, get or curl command.

Environment

VMware vSphere ESXi 7.x

Resolution

This is a normal behavior but to store the file permanently, would need to copy it to a different location.

For Example: Create a script with the below steps and it to create the config backup:

# vim-cmd hostsvc/firmware/sync_config
# vim-cmd hostsvc/firmware/backup_config
# find /scratch/downloads/ -name \*.tgz -exec cp {} /vmfs/volumes/<datastore>/<folder>/configBundle-$(hostname)_$(date +'%Y%m%d_%H%M%S').tgz \;

Additional Information

Aside from the above step there are NO other option or any way to "make the file stay for an extra few minutes" as it is impossible to reroute the resulting .tgz archive to a different location.