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 required to put the domain.vmfull option in the schedule definition,
it can go in the dsm.opt instead.
For me it's much easier to manage there. (I don't know what the character
limit is for that, haven't hit it yet.)
In general, we manage by putting the cluster name in the domain.vmfull
statement, and only listing by name the VM's we want to exclude from that
schedule. And we use a lot of wild cards.
In dsm.opt:
domain.vmfull VMHOSTCLUSTER=clustername; -VM=*Template*,VMexcluded1,
VMexcluded2*,VM*VDIexcluded*,etc
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Meuleman, Ruud
Sent: Tuesday, August 05, 2014 9:14 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TDP for VE clientschedules
Hi all,
We have a VMware vSphere environment with 246 virtual machines. We have 4
datamovers to do backups with TDP for VE.
In the client schedule we define the command:
-vmfulltype=vstor -vmbackuptype=fullvm -asnodename=<nodename that owns
the backupdata> -domain.vmfull="VM=<list with virtual machines, comma
separated>" -MODE=IFIncremental
This command is limited to 512 characters. So, it isn't possible to schedule
all virtual machines at one timestamp, because the hostnames of the virtual
machines don't fit in 4 times 512 characters.
We could make more schedules for the 4 datamovers, but there would be a risk
that client schedules are missed, if a client schedule starts while another one
on the same datamover is still running.
Does anyone have an easy idea for scheduling 246 virtual machines with TDP for
VE?
Kind Regards,
Ruud Meuleman
**********************************************************************
This transmission is confidential and must not be used or disclosed by anyone
other than the intended recipient. Neither Tata Steel Europe Limited nor any of
its subsidiaries can accept any responsibility for any use or misuse of the
transmission by anyone.
For address and company registration details of certain entities within the
Tata Steel Europe group of companies, please visit
http://www.tatasteeleurope.com/entities
**********************************************************************
|
