ADSM-L

Re: [ADSM-L] DOMAIN.vmfull on multiple lines in dsm.opt

2017-02-21 18:46:43
Subject: Re: [ADSM-L] DOMAIN.vmfull on multiple lines in dsm.opt
From: "Harris, Steven" <steven.harris AT BTFINANCIALGROUP DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 21 Feb 2017 23:44:05 +0000
Del

 I can't speak for anyone else, but I can't go to 8.1 because of the vCenter 6 
dependency.

Regards

Steve

Steven Harris
TSM Admin/Consultant
Canberra Australia

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Del Hoobler
Sent: Wednesday, 22 February 2017 6:19 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] DOMAIN.vmfull on multiple lines in dsm.opt

Hi Hans Chr.,

I am not sure I fully understand. Technically, you no longer need to use 
the options file if you use the new V8.1 features (tagging) with vSphere 
6. 

Why can't you use these new features? What is missing that you need?



Del

----------------------------------------------------


"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 02/21/2017 
08:18:26 AM:

> From: Hans Christian Riksheim <bullhcr AT GMAIL DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 02/21/2017 08:18 AM
> Subject: Re: DOMAIN.vmfull on multiple lines in dsm.opt
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 
> 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.
> > >
> >
> 

This message and any attachment is confidential and may be privileged or 
otherwise protected from disclosure. You should immediately delete the message 
if you are not the intended recipient. If you have received this email by 
mistake please delete it from your system; you should not copy the message or 
disclose its content to anyone. 

This electronic communication may contain general financial product advice but 
should not be relied upon or construed as a recommendation of any financial 
product. The information has been prepared without taking into account your 
objectives, financial situation or needs. You should consider the Product 
Disclosure Statement relating to the financial product and consult your 
financial adviser before making a decision about whether to acquire, hold or 
dispose of a financial product. 

For further details on the financial product please go to http://www.bt.com.au 

Past performance is not a reliable indicator of future performance.

<Prev in Thread] Current Thread [Next in Thread>