Forum Discussion

Angel_Lopez_116's avatar
Angel_Lopez_116
Icon for Altostratus rankAltostratus
Nov 16, 2014

configuration backup script on viprion cluster

Hi there,

 

I have a vCMP Viprion cluster with two blades and several guests. Each guest spans across the two blades, so I got several VM for each guest in the cluster.

 

I want to use a config backup script that I've installed on /etc/cron.daily but my doubt is if I have to install the script on every VM or just it's OK to install it on one VM (the one that runs on the primary slot).

 

I guess I'd have to install it on one and all, but I'm not sure.

 

7 Replies

  • I want to use a config backup script that I've installed on /etc/cron.daily but my doubt is if I have to install the script on every VM or just it's OK to install it on one VM (the one that runs on the primary slot).

     

    i understand you have to run script on vcmp host (to backup host configuration) and all the guests (to backup guest configuration).

     

  • Yeah but if each guest has several VM (one per slot) do I have to run the script in one and all of the VM? If I do that I'll have several backups that are the same and I guess that detecting which slot is the primary and doing the backup in that VM only is maybe the way to follow, but I'm not sure on that. Thanks.

     

  • if each guest has several VM (one per slot) do I have to run the script in one and all of the VM?

     

    not sure if i understand your question correctly. what i understand is one backup (ucs) file per vcmp guest. it does not matter whether guest is in one or multiple slots.

     

  • 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!

    • nitass's avatar
      nitass
      Icon for Employee rankEmployee
      it seems you are backing up vm image (vdisk). what i was saying is to backup configuration file (ucs).
  • Hi nitass,

     

    I'm not trying to backup disk image for the VM, I perform a "tmsh save sys ucs".

     

    • nitass's avatar
      nitass
      Icon for Employee rankEmployee
      in that case, you need only one ucs for each guest. ucs contains all configuration no matter how many slots guest is running on.