Hi nitass,
But if I'm not wrong (I'm in my first steps of learning how works all this stuff of vCMP, VMs, guests...) a guest that runs in two slots will have two VM because we'll have a different disk image in each slot, and a different VM in each slot for this guest.
So if I have a custom backup script scheduled (I've copied the script to the cron.daily folder) and this scripts runs in each VM, currently I'm gonna make two backups, one for each VM running for this guest, and these two backups will be exactly the same.
I guess that my script maybe should better have some section to know if it's running on a vCMP guest and in this case just do the work in the primary VM (the one running on the primary slot) so I can avoid this duplicity (or more if I have more than two slots and VMs for this guest in each).
Something like this:
PLATFORM=`grep platform /PLATFORM | cut -d'=' -f2`
if [ "$PLATFORM" == "Z101" ]; then
PRIMARY_SLOT=`tmsh show sys cluster field-fmt | grep current-primary-slot-id | awk '{print $2}'`
if [ $PRIMARY_SLOT -eq `cat /SLOT` ]; then
BACKUP STUFF
fi
fi
I don't know how you guys manage guests backups on a vCMP infraestructure, I'm just triying to adapt my custom scripts to it.
Another way would be to schedule the backup script on the vCMP host instead of scheduling it on the guest, and execute the actual "backup stuff" just in the VM running on the primary slot from the host.
I don't know which approach is the best on these cases.
Thanks!