Hi, good tips.
Any way of excluding backup of those machines that are not running(guestState: notRunning) with any rule? Regards, Hans Chr. On Wed, Jan 23, 2013 at 4:20 PM, Arbogast, Warren K <[email protected]>wrote: > Hi Ken, > We have been using TSMVE 6.4 for a couple months, I wouldn't call the > following a set of best practices, but they work well for the restore > service we provide. > > File restore services are still provided with TSM Extended Edition. > Nothing different there. Recovery of the first disk on virtual machines is > provided with TSMVE 6.4. Should disaster strike, the frst disk is restored > by TSMVE, then files and directories are restored with TSM Extended > Edition. We only snapshot the first disk. > > Our standard virtual machine is created here with a first disk of 60 GB > and additional disks for data storage. VM admins are encouraged to install > their OS on the first disk. We snapshot the first disk only by adding this > statement to dsm.opt for each data mover; INCLUDE.VMDISK "*" "Hard Disk 1" > > If the first disk of a virtual machine is greater than 60 GB, that guest > is excluded from snapshots by appending '-NB' to its display name in the > vSphere client. Then, '*-NB' [ star dash NB ] is added to the exclusion > filter in the TSMVE plug-in when a scheduled or run-now backup is created. > > We use one data mover per cluster, and put the data mover on the cluster > it backs up for performance reasons. We exclude the data mover from the > backup using the filter, and back it up with TSM/EE. Each cluster is > scheduled for backups once a week, and two versions are kept. Our largest > cluster has 12 hosts and about 420 guests. Our 'vmlimit' options are fairly > conservative, and could change with more experience. Here they are: > > VMMAXPARALLEL 8 > VMLIMITPERHOST 0 > VMLIMITPERDATASTORE 1 > > So far, so good. > > Best wishes, > Keith Arbogast > Indiana University > >
