Markus,

My "current" best practice is to use the VMFOLDER option and create folders
in the "VMs and templates" view. We have found that if the folder exists
multiple times, all machines are collected and backed up. For example
(pardon my bad the ASCII drawing skills):

vCenter01
[-] [ ] DC1
       [-] |/ Application servers
            [-] Backup_1900_DM01
                 APP01
                 APP02
            [-] NoBackup
                 APPTST01
                 APPTST01
       [-] |/ Domain Controllers
            [-] Backup_1900_DM01
                 DC02
       [-] |/ Mail
            [-] Backup_2300_DM02
                 MX02

So the schedule 1900_DM01 is associated with datamover DM01 and starts at
19:00. It backups the folder Backup_1900_DM01. As you can see the folder is
not unique.
VM's that are backupped are the APP01, APP02 and DC02.
By just moving VM's in and out of the folder structure you can decide when
and what to backup. To make it clear we also have defined NoBackup folders.
The name says it all.


 Only downside is that you cannot use the TDP for VE GUI to administer
these schedules, but for the rest it works great!

Schedule options for this example:
-vmfulltype=vstor -vmbackuptype=fullvm
-asnodename=VE_DC01 -domain.vmfull="VMFOLDER=Backup_1900_DM01"
-MODE=IFIncremental






2015-05-19 13:42 GMT+02:00 David Ehresman <david.ehresman AT louisville DOT 
edu>:

> Keith,
>
> What a good idea!  We do the same.
>
> David Ehresman
> University of Louisville
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Arbogast, Warren K
> Sent: Tuesday, May 19, 2015 7:40 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] including/excluding vms from backups administration
> usability
>
> Markus,
> We add '-NB' to the label in vSphere of the VMs we do not wish to back up.
> Then, we specify '-VM=*-NB' in the schedule options.
>
> QED
>
> Keith Arbogast
> Indiana University
>
> > On May 19, 2015, at 6:49 AM, Markus Engelhard <
> markus.engelhard AT BUNDESBANK DOT DE> wrote:
> >
> > Dear all,
> >
> > we are currently struggling a bit with TSM4VE config and making it more
> > manageable regarding including and excluding vms from backup.
> > For disks, we can exclude individual disks by just adding a line to the
> > optfile looking like
> >
> > exclude.vmdisk "vm1" "Hard Disk 2"
> > exclude.vmdisk "vm2" "Hard Disk 2"
> >
> > works fine, one disk per line and readable.
> >
> > If i want to exclude vms, I have to put them all in one line looking like
> >
> > DOMAIN.VMFULL
> >
> "vmhost=host1;-VM=vm7*,vm1,vm2,vm6,vm101,vm30,vm29,vm465,vm9,vm879,vm102,vm101;VM=7;VM=vm7657"
> >
> > which is not easily readable and hard to maintain as it grows and
> changes.
> > I know about the GUI, but then you always have to logon to the system for
> > each change, plus the exclude for disks is not avaliable.
> > The client will not accept more than one domain.vmfull statement or a cr,
> > all has to be in one line.
> > The options also don´t seem to be available in the client option set as
> > options, which would also be a neat solution.
> > Has anyone made a more readable syntax work, or would this be a case for
> a
> > RFE?
> >
> >
> > Kind regards,
> >
> > Markus
>



-- 
Kind Regards, Groetje,

Marcel Anthonijsz
T: +31(0)299-776768
M:+31(0)6-53421341