We add a suffix of -NB (no backup) to the label of vms we do not wish to
backup, and then add -vm=*-NB to the schedule option string. We have over
3,400 vms, but we only backup Hard Disk 1 with TSMVE and use TSM Enterprise for
their data disks. We impose a size limit of 60 GB on Hard Disk 1
We have about the same number of virtual machines, and use 1 VM as a datamover.
It's on a 10G network, we move about 4 TB of incrementals per night.
The TSM for VE plug in creates the schedule as you show below. But as you
said, that becomes unwieldy when you have a lot of VM's..
You aren't r
Ruud,
You could specify per ESX host, or better, as we do, per VMFOLDER. This
breaks the TSM4VE web GUI, as it cannot cope with the VMFOLDER option.
You then put your VMs to be backed up in folders i.e. PRODUCTION1,
PRODUCTION2, PRODUCTION3, PRODUCTION4 etc.
Next you setup a schedule with -domain
We are backing up 359 VMs distributed across 10 VMWare host machines. Our
datamovers are VMs. We have one datamover per VMWare host and each can do up
to 6 parallel sessions. From the dsm.opt we have the following options set:
resourceutil 8
vmmaxparallel 6
vmlimitperdatastore 0
vmlimitperhost
