Set include options to specify the VMs or vApps that you
want to include for backup services.
The scenarios documented in this section are based on the correct
use of the following
Tivoli® Storage
Manager backup-archive
client options:
Therefore, before implementing an include strategy based on these
scenarios, make sure to review these options in
Client options reference .
Include scenarios in a vSphere environment
When VMware virtual machine data is backed up, it is bound to
a management class that is specified by the vmmc option.
You can use the include.vm option to override
the management class that is specified by vmmc and
bind the backed up data for a virtual machine to a different management
class.
The include.vm option does not override
or affect the management class that is specified by the vmctlmc option,
which binds backed up VMware control files to a specific management
class.
Assume that the following management classes exist and
are active on the
Tivoli Storage
Manager server:
- MCFORTESTVMS
- MCFORPRODVMS
- MCUNIQUEVM
The following
include.vm statement
in the client options file binds all virtual machines that have names
that begin with VMTEST to the management class called MCFORTESTVMS:
include.vm vmtest* MCFORTESTVMS
The
following
include.vm statement in the client
options file binds a virtual machine that is named WINDOWS VM1 [PRODUCTION]
to the management class called MCFORPRODVMS:
include.vm "WINDOWS VM1 ?PRODUCTION?" MCFORPRODVMS
The
virtual machine name must be enclosed in quotation marks because it
contains space characters. Also, the question mark wildcard is used
to match the special characters in the virtual machine name.
The
following
include.vm statement in the client
options file binds a virtual machine that is named VM1 to a management
class that is named MCUNIQUEVM:
include.vm VM1 MCUNIQUEVM
Include scenarios in a vCloud environment
When
you back up a VMware vCloud vApp, the backed up data is bound to a
management class that is specified by the vappmc option.
You can use the include.vapp option to override
the management class that is specified by vappmc and
bind the backed up data for a vApp to a different management class.
Assume
that the following management classes exist and are active on the
Tivoli Storage
Manager server:
- MCFORTESTVAPPS
- MCFORPRODVAPPS
- MCUNIQUEVAPP
The following
include.vapp statement
in the client options file binds all vApp backups to the management
class called MCFORTESTVAPPS. Wildcards are used in the vApp specification
to target all vApps in all organizations and all organization virtual
data centers:
include.vapp *::*::* vm vmtest* MCFORTESTVAPPS
The
following
include.vapp statement in the client
options file binds all vApps in ORG1 and ORG1VDC to the management
class called MCFORPRODVAPPS:
include.vapp "ORG1::ORGVDC1::*" MCFORPRODVAPPS
The
following
include.vapp statement in the client
options file binds a vApp that is named VAPP1 to a management class
that is named MCUNIQUEVAPP:
include.vapp MY_ORG::MY_VDC::VAPP1 MCUNIQUEVAPP