Re: DOMAIN.vmfull on multiple lines in dsm.opt

[Harris, Steven]

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@VM.MARIST.EDU] On Behalf Of Del 
Hoobler
Sent: Wednesday, 22 February 2017 6:19 AM
To: ADSM-L@VM.MARIST.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"  wrote on 02/21/2017 
08:18:26 AM:

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

Re: rebinding of objects

[Del Hoobler]

HI Michael,

Yes, it will rebind them if you are using the same NODENAME.

If you want multiple COPY type backups with different policies,
you will need to use a different NODENAME.


Del



"ADSM: Dist Stor Manager"  wrote on 02/21/2017 
08:05:37 AM:

> From: Michael Prix 
> To: ADSM-L@VM.MARIST.EDU
> Date: 02/21/2017 08:06 AM
> Subject: rebinding of objects
> Sent by: "ADSM: Dist Stor Manager" 
> 
> Hello,
> 
> I'm well aware of the rebinding of objects in case of an incremental 
backup.
> Well documented and proven.
> But what I'm not so sure about is the case of rebinding when using 
API-calls,
> especially in this case for Exchange and MS-SQL.
> You have to use the VSSPOLICY statement to place the backups in the 
right
> MGMT-Class, now face this situation:
> Customer wants to perform monthly and yearly backups of its databases, 
done as
> copy-backups thus not breaking the full and incremental daily backups.
> ONE VSSPOLICY states to place the copy-backup into a MONTH-MGMT-class, 
the
> other VSSPOLICY states to place the copy-backup into a YEAR-MGMT-class
> Both policies will be in different tdp*.cfg files and are used during 
the tdp-
> backup by option /configfile.
> 
> Will there be a rebindung of the old copy-backups when the respective 
other
> tdp*.cfg file is used for a backup?
> 
> -- 
> Michael Prix
> 

Re: DOMAIN.vmfull on multiple lines in dsm.opt

[Del Hoobler]

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"  wrote on 02/21/2017 
08:18:26 AM:

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

Re: DOMAIN.vmfull on multiple lines in dsm.opt

[Schofield, Neil (Storage & Middleware, Backup & Restore)]

Classification: Public

Hans Christian

I have no solution for splitting the DOMAIN.VMFULL option over multiple lines 
but if this gets unwieldy you may want to think about the alternative approach 
of creating tags in the virtual machine inventory to exclude specific VMs from 
scheduled backups using the -VMTAGDATAMOVER client option.

I believe the case sensitivity of VM names in the DOMAIN.VMFULL option was an 
unintended defect in 7.1.6.0. You should be able to revert to the previous 
behaviour by applying an interim fix or maintenance release that includes APAR 
IT15975.

Regards
Neil Schofield
IBM Spectrum Protect SME
Backup & Recovery | Storage & Middleware | Central Infrastructure Services | 
Infrastructure & Service Delivery | Group IT
LLOYDS BANKING GROUP




Lloyds Banking Group plc. Registered Office: The Mound, Edinburgh EH1 1YZ. 
Registered in Scotland no. SC95000. Telephone: 0131 225 4555. Lloyds Bank plc. 
Registered Office: 25 Gresham Street, London EC2V 7HN. Registered in England 
and Wales no. 2065. Telephone 0207626 1500. Bank of Scotland plc. Registered 
Office: The Mound, Edinburgh EH1 1YZ. Registered in Scotland no. SC327000. 
Telephone: 03457 801 801. Cheltenham & Gloucester plc. Registered Office: 
Barnett Way, Gloucester GL4 3RL. Registered in England and Wales 2299428. 
Telephone: 0345 603 1637

Lloyds Bank plc, Bank of Scotland plc are authorised by the Prudential 
Regulation Authority and regulated by the Financial Conduct Authority and 
Prudential Regulation Authority.

Cheltenham & Gloucester plc is authorised and regulated by the Financial 
Conduct Authority.

Halifax is a division of Bank of Scotland plc. Cheltenham & Gloucester Savings 
is a division of Lloyds Bank plc.

HBOS plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in 
Scotland no. SC218813.

This e-mail (including any attachments) is private and confidential and may 
contain privileged material. If you have received this e-mail in error, please 
notify the sender and delete it (including any attachments) immediately. You 
must not copy, distribute, disclose or use any of the information in it or any 
attachments. Telephone calls may be monitored or recorded.

Re: DOMAIN.vmfull on multiple lines in dsm.opt

[Hans Christian Riksheim]

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  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"  wrote on 02/21/2017
> 03:57:02 AM:
>
> > From: Hans Christian Riksheim 
> > To: ADSM-L@VM.MARIST.EDU
> > Date: 02/21/2017 03:57 AM
> > Subject: DOMAIN.vmfull on multiple lines in dsm.opt
> > Sent by: "ADSM: Dist Stor Manager" 
> >
> > 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.
> >
>

rebinding of objects

[Michael Prix]

Hello,

I'm well aware of the rebinding of objects in case of an incremental backup.
Well documented and proven.
But what I'm not so sure about is the case of rebinding when using API-calls,
especially in this case for Exchange and MS-SQL.
You have to use the VSSPOLICY statement to place the backups in the right
MGMT-Class, now face this situation:
Customer wants to perform monthly and yearly backups of its databases, done as
copy-backups thus not breaking the full and incremental daily backups.
ONE VSSPOLICY states to place the copy-backup into a MONTH-MGMT-class, the
other VSSPOLICY states to place the copy-backup into a YEAR-MGMT-class
Both policies will be in different tdp*.cfg files and are used during the tdp-
backup by option /configfile.

Will there be a rebindung of the old copy-backups when the respective other
tdp*.cfg file is used for a backup?

-- 
Michael Prix

Re: DOMAIN.vmfull on multiple lines in dsm.opt

[Del Hoobler]

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"  wrote on 02/21/2017 
03:57:02 AM:

> From: Hans Christian Riksheim 
> To: ADSM-L@VM.MARIST.EDU
> Date: 02/21/2017 03:57 AM
> Subject: DOMAIN.vmfull on multiple lines in dsm.opt
> Sent by: "ADSM: Dist Stor Manager" 
> 
> 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.
> 

DOMAIN.vmfull on multiple lines in dsm.opt

[Hans Christian Riksheim]

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.