Apply template to multiple backup specs simultaneously

Is it possible to apply a template to more than one backup spec?  I have created an exclude list and I have 300 backup specs.  Will I have to edit each spec one by one?  I have the specs grouped into groups but when I right click a group, there isn't an option to apply a template.

Thanks,

Randy

Parents
  • Hello Randy,

    Just a short one - checking with you if the replies you got are good/useful, and if yes, may I request you to click on ACCEPT AS SOLUTION, if you find it to be so this can be shared.

    Looking at what you posted - I agree with Sebastian - omniwl.pl is your option and you may want to consider it.

    I just have one comment - 300 backup specifications. How many are FILESYSTEM backups and INTEGRATION backups. This looks to be a lot.

    I guess you have a very big environment.

    RGds,

    Sherman (HPE DP Support)

Reply
  • Hello Randy,

    Just a short one - checking with you if the replies you got are good/useful, and if yes, may I request you to click on ACCEPT AS SOLUTION, if you find it to be so this can be shared.

    Looking at what you posted - I agree with Sebastian - omniwl.pl is your option and you may want to consider it.

    I just have one comment - 300 backup specifications. How many are FILESYSTEM backups and INTEGRATION backups. This looks to be a lot.

    I guess you have a very big environment.

    RGds,

    Sherman (HPE DP Support)

Children
  • Good morning Sherman,

    You asked a question that could start a whole new thread.  Yes, I have over 300 specs because I am a 15 year NetBackup veteran implementing Data Protector for the first time.  In my NetBackup world, I found it easier to create one backup policy per server/client.  I was at HP Discover last month and people looked at me like I was from another planet when I told them I had one spec per client.  I'm guessing this wasn't a good idea/plan?

  • Even in Netbackup having one Policy per Client is suicidal, I'm running several Domains myself and we never came to a point where that was slightly reasonable.

    For DataProtector I can recommend multiple Datalists, grouping similar Hosts, f.E. by Location, OS-Type, Application, Retention and so on. Since you can mix different Backup Selections like Hosts (All Local Drives) or Objects (like Folder or Volume) you can group by higher locics and are not a slave of Backup Selection.

    We for example have Groups for Exchange-Hostbackups, MSSQL-Hostbackups, SAP-Hostbackups, other Unix and other Windows Hosts. One such Group for each of our DataCenter-Locations. All Clients in those Groups also share the same Retention, important for good Media/Pool usage since DataProtector does not distinguish Retentions on Media. We do have a hand full of Single Client Datalists but those are usually special Backups with extraordinary Retention or Backup Selections.

  • Even in Netbackup having one Policy per Client is suicidal, I'm running several Domains myself and we never came to a point where that was slightly reasonable.

    For DataProtector I can recommend multiple Datalists, grouping similar Hosts, f.E. by Location, OS-Type, Application, Retention and so on. Since you can mix different Backup Selections like Hosts (All Local Drives) or Objects (like Folder or Volume) you can group by higher locics and are not a slave of Backup Selection.

    We for example have Groups for Exchange-Hostbackups, MSSQL-Hostbackups, SAP-Hostbackups, other Unix and other Windows Hosts. One such Group for each of our DataCenter-Locations. All Clients in those Groups also share the same Retention, important for good Media/Pool usage since DataProtector does not distinguish Retentions on Media. We do have a hand full of Single Client Datalists but those are usually special Backups with extraordinary Retention or Backup Selections.

  • Even in Netbackup having one Policy per Client is suicidal, I'm running several Domains myself and we never came to a point where that was slightly reasonable.

    For DataProtector I can recommend multiple Datalists, grouping similar Hosts, f.E. by Location, OS-Type, Application, Retention and so on. Since you can mix different Backup Selections like Hosts (All Local Drives) or Objects (like Folder or Volume) you can group by higher locics and are not a slave of Backup Selection.

    We for example have Groups for Exchange-Hostbackups, MSSQL-Hostbackups, SAP-Hostbackups, other Unix and other Windows Hosts. One such Group for each of our DataCenter-Locations. All Clients in those Groups also share the same Retention, important for good Media/Pool usage since DataProtector does not distinguish Retentions on Media. We do have a hand full of Single Client Datalists but those are usually special Backups with extraordinary Retention or Backup Selections.

  • Hello Randy,

    The part on "one backup specification per client" - it is possible and you are free to do it, based on your Enterprise Backup Solution requirements (and maybe even restrictions).

    But if we look things as a whole, YES - we can improve it or maybe have a more streamlined configuration.

    What svollrat have suggested is a good one and you might want to consider his example.

    Rgds,

    Sherman