Forum Discussion

shahriar_sadm's avatar
7 years ago

Netbackup vmware policy best practice

Hi dear all, my vmware backup environment includes a vm backup host and about 20 esx host with about 700 virtual machines. Is it necessary to create one policy for each vm? If I use intelligent policy example for each host, maybe backup for 40 virtual machine will run together. Netbackup recommend 4 concurrent vm backup.
Generally whats the best practice and your suggestion for manage this number of vm and host.
Thanks
  • Hello,

    NetBackup recommends 4 concurrent backups - but per one datastore. This is set by Host Properties\Master\Resource Limit tab and supersedes other limits if they are higher.

    So for example, when in your case 40 VMs on 3 different datastores are picked up by an intelligent policy, there will be maximum of 12 VM backups running concurrently, if not restricted more by limits on other levels (storage unit, policy, etc.).

    Regards

     

  • Hello,

    NetBackup recommends 4 concurrent backups - but per one datastore. This is set by Host Properties\Master\Resource Limit tab and supersedes other limits if they are higher.

    So for example, when in your case 40 VMs on 3 different datastores are picked up by an intelligent policy, there will be maximum of 12 VM backups running concurrently, if not restricted more by limits on other levels (storage unit, policy, etc.).

    Regards

     

    • shahriar_sadm's avatar
      shahriar_sadm
      Level 6

      Thanks dears for reply,

      I still have a problem, imagine I create one policy per each esxserver, for every day one esx server and vms backup. what happend if one vm move between esx servers before next backup. esx1backup sundays and esx2 backup wedensdays. if vm1 will backup in sundays on esx1 and before wedensday move to esx2, vm1 has duplicate backups and if imagine reverse mybe no backup in a week! 

      Thanks 

      • AndreaBolongaro's avatar
        AndreaBolongaro
        Level 5

        shahriar_sadm,

        it depends on your environment, but generally it is not a good idea to have vmware policies fragmented per esx host.
        Please check this: NetBackup for VMware best practices

        If I understand correctly, you configured policies per ESX, so that when a vm moved from a esx to another it is backed up in another policy. A full is made when a vm is newly backuped up in a vmware policy.
        In order to  avoid switching of vms among policies, it is better using queries in VIP and Setting global limits on the use of VMware resources

        Hope it helps