Hi Del,

yes I have taken a look and it is a nice feature. We would prefer that the
exclusion and inclusion of VMs be policy and rule based though.

Regards,

Hans Chr.

On Tue, Feb 21, 2017 at 12:58 PM, Del Hoobler <hoobler AT us.ibm DOT com> wrote:

> Hi Hans Chr.
>
> Have you looked at the tagging support?
>
>
> https://www.ibm.com/support/knowledgecenter/SSERB6_8.1.0/
> ve.user/t_ve_dpext_cfg_bup_policy.html
>
> It was specifically added to enable you to avoid these types of issues.
>
>
> Del
>
> ----------------------------------------------------
>
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 02/21/2017
> 03:57:02 AM:
>
> > From: Hans Christian Riksheim <bullhcr AT GMAIL DOT COM>
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Date: 02/21/2017 03:57 AM
> > Subject: DOMAIN.vmfull on multiple lines in dsm.opt
> > Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> >
> > Really two questions.
> >
> > We have a lot of exceptions where VMs are not to be backed up and the
> > DOMAIN.vmfull statement is becoming unpractically long:
> >
> > domain.vmfull vmhostcluster=X,Y;-vm=abc*,*def,ghi* (times 100)
> >
> > Any possibility to have that statement span separate lines or some other
> > measure to increase readability?
> >
> > Second question is about case sensitivity. In previous versions
> > DOMAIN.VMFULL was not case sensitive but now it is. Unfortunately we
> have
> > no control of how the VMware guys name their vms so how do we exclude a
> vm
> > like
> >
> > VMNAME
> >
> > and cover all variations Vmname, vmNAME and so on?
> >
> > Regards,
> >
> > Hans Chr.
> >
>