I wish vmware would just come out and say. "That backing up the Service Console is not really needed". It is best practice to just do a new install. As my "bosses" just want a backup client on the esx host service console. Which I do not think is needed and is extra work and if the backup client wants to go south it will bring the host down with it.
I have this script. It backs up the config files of ESX host as well as the guest configs. But not the vmdk files of the guest itself. (and I don't want them).
What does any body think about this script I created??
script
This should be a cron job. Run as root.
#!/bin/bash
nameh=$(hostname)
cd /root/
vm-support -q
mv esx-*.tgz /vmfs/volumes/SANVol1/bh/$nameh.tgz
rm vm-support* -fr
rm old_cores -fr
You can leave the file on the san or use the script below to copy to your vcenter server.
C:\Program Files\VMware\VMware VI Remote CLI\Perl\apps\general>fileaccess.pl --operation get --filetype datastore --remotepath "bh/server.example.com.tgz" --datastorename SANvol1 --datacentername TEST --localpath "c:/server.example.com.tgz" --username vmscript --password 0bmij
mccann.jim@gmail.com
PS. Backup of the guest is done either via VCB or backup client installed in the guest.
PSS. Also the one reason I made this script was for missing Disk Descriptor File and going to a backup system to just get 1 file is a pain. Just have the tar file on your vcenter server. Open up the tar find your guest DDF and cut and paste or copy over it and get that guest back online. Plus it has all kinds of other good stuff in it.
