HP StorageWorks 12000 - Virtual Library System EVA Gateway Manual page 201

• Keep mount point: The Keep Mount Point setting on each node must be set to Yes using the com-
mand keepmp=yes. This command only works if there are no client sessions running when enabled.
Update node * keepmp=yes
Replace the asterisk (*) with a node name to update an individual node.
• Resource utilization: Use the "resourceutilization" option in your dsm.sys file to regulate the level
of resources the TSM server and client can use during processing. To limit the number of backup
sessions per resource (i.e., per tape drive) to one, use the resourceutilization setting of 2; this is
equivalent to limiting the VLS to one stream. If you do not limit the number of resources to one,
multiple backup sets will appear in the user interface for a single backup and the deduplication
ratios will be significantly reduced.
• Management classes: To assign a management class other than the default to all files, use an include
statement in your client systems options file, or by using an include-exclude file specified by the
"inclexcl" option. To specify your own default management class for files that are not explicitly
included, specify the following as the first include or exclude option defined:
For non-Windows hosts (e.g., HPUX, Linux, AIX), add the following to the dsm.sys file for the
appropriate directories being backed up:
• This will backup all directories and files under /backup/:
include /backup/.../* mgmt_class_name
• This will backup all directories and files under /:
include /.../* mgmt_class_name
For Windows hosts, to specify a management class named mgmt_class_name for all files to
which you do not explicitly assign a management class, add the following to the dsm.opt file
for Windows systems for the appropriate volumes/directories being backed up:
• This will backup all directories and files under e:\backup:
include e:\backup\...\* mgmt_class_name
• This will backup all directories and files under e:\:
include e:\...\* mgmt_class_name
• This will backup all directories and files under d:\:
include d:\...\* mgmt_class_name
The management class names are not case-sensitive.
• Disk pools: A disk pool is a primary storage pool that stores data on disks. When using TSM, the
primary disk pool is typically the initial destination for data being backed up. This storage pool
is sized to accommodate the projected amount of daily changed data in your environment, as
with an incremental backup. The disk pool is typically configured to migrate to the next storage
pool in the hierarchy, the tape storage pool. When TSM migrates data from a disk pool, it determ-
ines what data to migrate based on the node that has the most amount of data stored in the disk
pool. TSM moves the data for each node in the order in which it was written to the storage pool.
The cache feature on the primary disk pool, which is disabled by default, allows a rapid restore
of recently backed up data as necessary.
The recommended option is to eliminate the disk pool and back up directly to the VLS. However,
if you continue using a disk pool for some of your backups (for example, to provide a very high
availability primary pool), the disk pool must be sized to contain the entire night's backup to ensure
good deduplication. At a minimum, the disk pool must be equal to you largest nightly backup.
• Copy storage pools: The copy storage pool provides a way to recover from disasters or media
failures. TSM relies on the process of backing up its primary storage pools to an off-site copy pool
to recover the TSM environment if a disaster (e.g., destruction of the data center) occurs. With a
backup of the TSM database in a remote location, the off-site copy storage pool is a duplicate of
HP StorageWorks VLS and D2D Solutions Guide 201