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

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,

Re: rebinding of objects

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

Re: 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

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

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

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

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

rebinding of objects

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

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

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

DOMAIN.vmfull on multiple lines in dsm.opt

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