Cloud & Smarter Infrastructure

Professional Certification Program

Study Guide Series

Exam C2010-511 - IBM Certified

Deployment Professional Tivoli Storage
Manager V7.1
Purpose of Exam Objectives .................................................................. 3
High-level Exam Objectives .................................................................... 4
Detailed Exam Objectives ...................................................................... 10
Section 1 - Planning.............................................................................................. 10
Section 2 - Installation ......................................................................................... 13
Section 3 - Configuration .................................................................................... 22
Section 4 - Administration .................................................................................. 27
Section 5 - Problem Determination................................................................... 38
Next Steps .................................................................................................. 40
Purpose of Exam Objectives
When an exam is being developed, the Subject Matter Experts work together to
define the role the certified individual will fill. They define all of the tasks and
knowledge that an individual would need to have in order to successfully
implement the product. This creates the foundation for the objectives and
measurement criteria, which are the basis for the certification exam.

The Tivoli Certification item writers use these objectives to develop the questions
that they write and which will appear on the exam.

It is recommended that you review these objectives. Do you know how to

complete the task in the objective? Do you know why that task needs to be done?
Do you know what will happen if you do it incorrectly? If you are not familiar with
a task, then go through the objective and perform that task in your own
environment. Read more information on the task. If there is an objective on a
task there is about a 95% chance that you WILL see a question about it on the
actual exam.

After you have reviewed the objectives and completed your own research, then
take the assessment exam. While the assessment exam will not tell you which
question you answered incorrectly, it will tell you how you did by section. This will
give you a good indication as to whether you are ready to take the actual exam
or if you need to further review the materials.

Note: This is the high-level list of objectives. As you review these objectives, click
for a more detailed level of how to perform the task.
High-level Exam Objectives
Section 1 - Planning
Given a customer has signed an IBM contract for the IBM Implementation
Services for storage software", the need to identify customer key stakeholders,
1.1 gather logistical and technical information including infrastructure diagrams
and procedural documents, send invitation to customer to attend initial project
kick-off conference so that detailed information can be gathered.
Given a detailed architectural and software document identifying the software
and hardware that the data resides on, determine client backup methodology
1.2 based on client data so that a document outlining the most efficient and
practical method for meeting the customer data protection and retention
requirements is available.
Given access to key technical personnel and responses to key questions,
1.3 assess and evaluate the skill level so that educational opportunities can be
made.
Given customers policies and /or regulatory requirements of Recovery Point
Objective and Recovery Time Objective of data and applications, determine
1.4
disaster recovery requirements so that a solution that meets the disaster
recovery requirements is available.
Given the clients network architecture determine the required firewall
1.5 configuration in order to enable the data backup and recovery services for
costumers environment.
Section 2 - Installation
Given a functioning TSM V5 environment, access to the IBM FTP site, the
Upgrade and Migration Guide for TSM V5 servers, space on existing server
2.1 system or new system, and compatible media library, upgrade TSM from
Version 5 to Version 7 so that the TSM V5 server and Backup-Archive clients
are upgraded to v7
Given appropriate hardware, software, and networking access, the TSM 7.1.0
2.2 server code and installation documentation, follow the procedures so that the
server is installed.
Given the number of licenses required, issue the register license command so
2.3
that TSM V7.1 is registered.
Given adequate space for the database and recovery logs, instance ID and
2.4 directories,TSM V7.1 Installation Guide, configure the server so that the TSM
server is configured for backing up data.
Given appropriate hardware, software, and networking, access the TSM
2.5 V7.1.0 Backup-Archive client code and installation documentation, follow the
procedures so that the Backup-Archive client is installed.
Given access the TSM V7.1.0 Backup-Archive client code and installation
documentation, select the custom installation method and follow the
2.6
documented process to install the administrative client command line so that
the administrative command line is installed.
 Given supported storage device, manufacturers documentation, and a
2.7 correctly configured TSM V7.1 server, configure the storage device hardware
so that backup data can be written to the device.
Given an installed TSM server, SAN or LAN infrastructure, use the available
TSM tools to collect the information so that the devices can be used as
2.8
destinations for backup, archives or space management such as device
classes and storage pools.
Given the hub server spoke server, collection period, at-risk settings and alert
2.9 triggers, define and install operations center so that operations center is ready
to utilize.
Given the level of encryption, files to encrypt and encryption password, install
2.10
and configure encryption so that files are encrypted prior to being backed up.
Given that the environment requirements are met and the TSM server is
2.11 correctly installed, perform the installation and configuration steps so that the
TSM Backup-Archive client is able to be used for space management (HSM).
Given a VMware ESX or ESXi-based host running VMs and the TSM server
2.12 installed and configured, prepare, install, and configure TSM for Virtual
Environments Version 7.1 so that TSM for Virtual Environments is available.
Given hardware and software requirements are met, TSM server and TSM
client software are installed, and the TSM Information Center has all
2.13
information for a guided configuration available, configure IBM Tivoli
FlashCopy Manager (FCM) so that FCM is configured and available.
Given an installed TSM server, use the available TSM tools to setup a secure
user administration controlled by LDAP so that the Tivoli Storage Manager
2.14
environment is enabled to use an LDAP directory server to authenticate
passwords.
Given the TSM server is installed and configured, prepare, install, and
2.15 configure TSM for Mail and TSM for Databases so that TSM for Mail and TSM
for Databases are available.
Section 3 - Configuration
Given enough file space in different file systems/Drives on an installed OS with
3.1 IBM Tivoli Storage Manager (TSM) server software installed, configure
database and log space so that the database and log space is available.
Given an installed and initialized TSM server with attached Tape libraries,
3.2
define tape libraries so that the Tape Libraries are configured in TSM.
Given an installed and initialized TSM server with attached disk storage and/or
3.3 Tape Libraries, set up pools so that primary storage pools can configured in
TSM.
Given an installed and initialized TSM server and known customer
3.4 requirements for data protection set up policies so that policies are configured
in TSM.
Given an installed and initialized TSM server with defined storage pools and
3.5 knowledge of collocation requirements, define collocation groups so that
nodes can defined in collocation groups.
 Given an installed and initialized TSM server with defined nodes so that nodes
3.6
can schedule their operations.
Given sufficient memory, sequential access, file device class storage pool, list
of client nodes to dedulpicate, define of update a storage pool, register or
3.7 update client nodes, create or update a policy, and schedule or manually run
identify duplicates command so that duplicate date is removed when the data
moves to an enables storage pool.
Given an installed TSM server use the available utilities and commands to
initialize, use, and manage the tape volumes through the different Tivoli
3.8
storage manager states so that the automated tape library is prepared with
tape volumes and can be used for the different data processes in the TSM.
Given the need for bare metal restore, be able to identify the correct bare
3.9
metal restore solution so that customer can be given correct recommendation.
Given the cluster servers are available and the OS is prepared to run as a
cluster, install, configure and manage the TSM software server/client in a
3.10
clustered environment so that the TSM server / client is available in a
clustered environment.
Section 4 - Administration
Given an administrator with system or unrestricted storage privilege, correctly
configured IBM Tivoli Storage Manager (TSM) server and Backup-Archive
4.1 client, configured supported storage devices, working network, define disk, file,
and removable media device classes so that device classes are defined for all
supported device types.
Given an administrator with system privilege, defined appropriate device
classes, and defined random access, primary destination pool, define
sequential access primary storage pool, update destination random access
4.2
and sequential access primary storage pool and specify NEXTSTGPOOL, so
that storage pools are chained together so that data can move from one
device or media type to another.
Given an administrator with system privilege, defined appropriate device
classes, and defined random and sequential access primary storage pools,
define or update a sequential access storage pool with pooltype=copy,
4.3
sufficient space to hold primary pool backups, and with a maxscratch value
specified so that copy storage pools are defined to store storage pool
backups.
Given an administrator with system privilege, defined appropriate device
classes, and defined random and sequential access primary storage pools,
4.4 define or update a sequential access storage pool with pooltype=active,
sufficient space to hold primary pool active-data version backups, with a
maxscratch value specified, so that active-data storage pools are created.
Given an administrator with system or policy privilege, a defined management
class, and client data stored in storage pools, define archive and backup copy
4.5
groups, and run the expire inventory command so that expired data is
removed for the storage pools.
 Given an administrator with system privilege, sequential access storage pools,
update or define storage pools to specify reclamation parameters so that data
4.6
from partially filled tape volumes is consolidated so empty volumes can be
reused.
Given an administrator with system privilege and defined storage pool
hierarchy, set the high and low migration thresholds, and MIGDELAY and
4.7
MIGCONTINUE parameters so that stored client data automatically moves
through the storage pool hierarchy to free up space in the source pool.
Given an administrator with system privilege and defined storage pool
hierarchy, update or define a primary storage pool so the destination is up to
4.8 three target primary, copy, or active-data storage pools, with appropriate
mount points so that client data backups and archives, server imports, and
storage pool migration configured for multiple thread processing.
Given an installed TSM server, automate administrative processes by admin
4.9 scheduling and TSM scripting so that repetitive, manual tasks associated with
managing the server can be automated through TSM schedules and scripts.
Given the required responsibilities of an administrator identify the correct level
4.10 of authority required so that the administrator can perform the required
actions.
Given a configured and running TSM server with attached storage devices ,
defined device classes and defined storage pools from Type primary and
4.11
copy , back up the storage pool so that the backuped client data is protected
against disaster.
Given a configured and running TSM server with attached storage devices and
4.12 defined device classes, backup the database so that the Database is
protected against disaster.
Given a configured and running TSM server, installed Backup-Archive client,
4.13 established network connection and defined communication parameters,
manage the client options so that the client can connect to the TSM server
Given a configured and running TSM server, configured Backup-Archive client,
4.14 knowledge of customer SLA and policy domains, establish include/exclude
lists so that the client can backup its data according Customer SLAs
Given a configured and running TSM server, configured Backup-Archive client,
4.15 knowledge of nodes and client options, set up server option sets so that the
TSM server can centralized set client options for nodes.
Given a configured Backup-Archive client, set up the CAD so that the client
4.16
can used with the Web GUI and/or run the scheduling service.
Given configured TSM environment, portable media device, accessible by
4.17 server and client system, generate backup sets so that backup set data can be
restored on the Backup-Archive client.
Given a source and target server, nodes and their data, and automatic
4.18 failover, set up node replication so that data is automatically replicated over to
a target server.
Given an installed TSM server use the export / import functionality of the TSM
4.19
server so that data can be exported from one TSM server to another.
 Given the necessity for server to server communication and the needed
4.20 parameters define server to server communication so that multiple TSM
servers can work together.
Given an installed and configured TSM server, configure and manage the
TSM options related to the group files so that the TSM server has several
4.21
options to optimize data stream, consistency and management by several
grouping methods
Given an installed and configured TSM clients, configure and manage the
TSM client options related to the group files and nodes so that the TSM client
4.22
has several options to optimize data stream, consistency and management by
several grouping methods.
Given an installed and configured TSM server and clients, configure the TSM
4.23 server and client options so that the TSM client has multiple options to
restore/retrieve files from another TSM client on its own disk.
Given the need to protect NAS devices, determine the correct backup type so
4.24
that the NAS devices are protected.
Given installed TSM server clients are configured, set up archiving so that
4.25
data is ready to be archived.
Given a configured TSM environment, identify the appropriate client options,
determine backup method for Backup-Archive client, determine the Backup-
4.26
Archive interface to perform the backup, and schedule or manually run the
backup operation so that Backup-Archive data can be backed up.
Given a configured TSM environment, identify appropriate client options,
determine the Backup-Archive interface to perform the restore operation, and
4.27
schedule or manually run the restore operation so that data for the Backup-
Archive client can be restored.
Given a configured TSM environment, identify appropriate client options,
determine the Backup-Archive interface to perform the archive, create archive
4.28
description, and schedule or manually run the archive operation so that
Backup-Archive data is archived.
Given a configured TSM environment, identify appropriate client options,
determine the Backup-Archive interface to perform the retrieve operation, and
4.29
schedule or manually run the retrieve operation so that archive data for the
Backup-Archive client is retrieved.
Given a specific node move its data to a new storage pool so that it resides in
4.30
the new storage pool.
Given alert triggers and a list of administrators who need to be notified, set up
4.31
alerting so that alerts are enabled on the TSM servers.
Given the need to restore a database execute the needed commands so that
4.32
the TSM server is restored.
Given an administrator with system privileges, manage the database and
4.33
recovery logs so that the TSM instance performs optimally.
 Given a running TSM server with attached and configured new Tape hardware
4.34 with a new supported Tape technology, transfer data so that the TSM server
uses the new Tape technology.
Section 5 - Problem Determination
Given a configured IBM Tivoli Storage Manager (TSM) environment that has
performed successfully and the TSM V7.1 Problem Determination Guide,
review error logs, alerts, event logs, and schedule logs, query the database
5.1
and storage pools, review the server options file, and run the QUERY
SYSTEM command so that the TSM server performance problems are
identified.
Given a configured TSM environment that has performed successfully on a
LAN or SAN, and the TSM V7.1 Problem Determination Guide, review error
5.2 messages, enable cyclic redundancy checking, and compare current network
throughput with previous network throughput, so that network bottlenecks are
identified
Given a configured TSM environment that has performed successfully and the
TSM V7.1 Problem Determination Guide, use the DB2 utilities to monitor the
5.3 database, review error logs, alerts, and event logs, and query the database
and recovery logs, so that the TSM database performance problems are
identified.
Given a configured TSM environment that has performed successfully and the
TSM V7.1 Problem Determination Guide, review error logs, alerts, event logs,
5.4 and schedule logs, review the client options file, and run the QUERY
SYSTEMINFO command, so that the TSM Backup-Archive client performance
problems are identified.
Detailed Exam Objectives
Section 1 - Planning
1.1. Given a customer has signed an IBM contract for the IBM
Implementation Services for storage software", the need to identify
customer key stakeholders, gather logistical and technical information
including infrastructure diagrams and procedural documents, send
invitation to customer to attend initial project kick-off conference so
that detailed information can be gathered.

SUBTASK(S):
1.1.1. Set up conference with IBM account, IBM Marketing Rep or Services
Specialist or IBM business partner.
1.1.1.1. Gather current software/hardware implemented for IBM team.
1.1.1.2. Review the account history.
1.1.1.3. Create list of Key people to include in initial kick-off conference.
1.1.1.4. Create agenda for kick-off meeting.
1.1.2. Contact customer to arrange kick-off meeting.
1.1.2.1. Introduce yourself and state purpose of meeting.
1.1.2.2. Provide list of people to include, ensure customer agrees with list
and change if necessary.
1.1.2.3. Explain that a questionnaire will be provided and requesting
information on current SLAs ,architectural design,installed
software/ hardware and procedures in place.
1.1.2.4. Set the date and time for the kick-off meeting.
1.1.3. Meet with customer team to kick-off project.t
1.1.3.1. Review signed SOW to ensure the work to be provided is the work
expected.
1.1.3.2. Review Questionnaire for completeness.
1.1.3.3. Review current infrastructure architecture; discuss each area to
ensure you understand and can identify possible network, firewall,
zoning concerns; collect information on data types, estimated data
totals, or software concerns.
1.1.3.4. Review IBM software/hardware prerequisites with customer to
ensure compatibility.
1.1.4. 1.2.4 Draft architectural document.
1.1.4.1. Consolidate all information gathered.
1.1.4.2. Ensure all necessary information has been collected.
1.1.4.3. Provide a high level work schedule.
1.1.4.4. Send copies to IBM team for review.
1.1.5. Send document to customer for approval.
1.1.6. Schedule technical review meeting with customer.
1.1.6.1. Ensure that stakeholders of each area are scheduled.

1.2. Given a detailed architectural and software document identifying the

software and hardware that the data resides on, determine client
 backup methodology based on client data so that a document
outlining the most efficient and practical method for meeting the
customer data protection and retention requirements is available.

SUBTASK(S):
1.2.1. Identify number of servers hosting unstructured data and propose
appropriate IBM data protection product.
1.2.2. Identify number and type of databases and propose appropriate IBM data
protection product.
1.2.3. Identify number and type of email server application and propose
appropriate IBM data protection product.
1.2.4. Identify clients virtual environment platform and propose appropriate IBM
data protection product.
1.2.5. Identify clients storage systems and propose appropriate IBM data
protection product.
1.2.6. Identify remote office data backup requirements and propose appropriate
IBM data protection product.
1.2.7. Identify backup requirements of remote office data and propose
appropriate IBM data protection product.
1.2.8. Identify regulatory and/or companys long term data retention policies and
propose appropriate backup methodology Identify data that might benefit
from IBM FlashCopy Manager.

1.3. Given access to key technical personnel and responses to key

questions, assess and evaluate the skill level so that educational
opportunities can be made.

SUBTASKS:
1.3.1. Arrange meeting with key technical personnel only.
1.3.2. Ask pertinent questions regarding technical skills and knowledge.
1.3.3. Analyze information gathered from interviews.
1.3.4. Identify skill gaps.
1.3.5. Align skill gaps with education opportunities.

1.4. Given customers policies and /or regulatory requirements of

Recovery Point Objective and Recovery Time Objective of data and
applications, determine disaster recovery requirements so that a
solution that meets the disaster recovery requirements is available.

SUBTASK(S):
1.4.1. Translate and document customers business polices into data retention
rules.
1.4.1.1. Transform data retention rules into IBM Tivoli Storage Manager
(TSM) policy.
1.4.1.2. Determine if data will require offsite copies.
1.4.1.3. Create TSM management classes that meet policy requirements.
1.4.2. Identify and document data requiring regulatory handling.
1.4.2.1. Identify clients that house regulatory data.
1.4.2.2. Separate data/clients into groups based on regulatory retention.
1.4.2.3. Determine if a Long Term Retention server (Archive) is needed.
1.4.3. Identify and document nodes eligible for node replication.
1.4.4. Identify and document nodes with large numbers of files and data.
1.4.5. Identify and document nodes eligible for traditional Disaster Recovery
methodology.
1.4.6. Consolidate created documents and perform additional analysis.
1.4.7. Propose logical architecture for configuration of Disaster Recovery Module.

1.5. Given the clients network architecture determine the required firewall
configuration in order to enable the data backup and recovery
services for costumers environment.

SUBTASK(S):
1.5.1. Engage customers network team to work on a collaborative effort in the
appropriate configuration required to enable data backup and recovery
services.
1.5.2. Document required changes on current firewall configuration to enable
data backup and recovery services.
1.5.3. Document procedure with the appropriate network configuration
requirements of IBM data protection products.
Section 2 - Installation
2.1. Given a functioning TSM V5 environment, access to the IBM FTP site,
the Upgrade and Migration Guide for TSM V5 servers, space on
existing server system or new system, and compatible media library,
upgrade TSM from Version 5 to Version 7 so that the TSM V5 server
and Backup-Archive clients are upgraded to v7

SUBTASK(S):
2.1.1. Verify the system requirements for TSM V7.
2.1.2. Determine the upgrade plan.
2.1.2.1. Upgrade the server and database on the same system by using
media to transfer the database.
2.1.2.2. Upgrade the server and database on the same system by using
the network to transfer the database.
2.1.2.3. Upgrade the server and database on a new system by using
media to transfer the database.
2.1.2.4. Upgrade the server and database on a new system by using the
network to transfer the database.
2.1.2.5. Install a new TSM V7 server on new hardware and allow the TSM
V5 servers data to expire.
2.1.3. Prepare the TSM V5 database for upgrading.
2.1.3.1. Issue the convert ussfilespace command.
2.1.3.2. Back up the storage pools.
2.1.3.3. Back up the V5 database and configuration files.
2.1.3.4. Install the upgrade utilities package (DSMUPGRD).
2.1.3.5. Run the DSMUPG PREPAREDB utility.
2.1.4. Prepare the V7 space.
2.1.4.1. Install the TSM V7 server code, but do not configure.
2.1.4.2. Create directories and user ID for the V7 instance.
2.1.4.3. Run DSMSERV LOADFORMAT utility.
2.1.5. Perform the upgrade.
2.1.5.1. Extract data from V5 database with DSMUPGRD EXTRACTDB
utility.
2.1.5.2. Insert V5 database date to V7 database with DESMSERV
INSERTDB utility.
2.1.5.3. Configure the new system for database backup.
2.1.6. Perform post upgrade tasks.
2.1.6.1. Back up the new database.
2.1.6.2. Verify the database contents.
2.1.7. Install TSM Backup-Archive clients V7.

2.2. Given appropriate hardware, software, and networking access, the

TSM 7.1.0 server code and installation documentation, follow the
procedures so that the server is installed.

SUBTASK(S):
2.2.1. Verify software and hardware requirements.
2.2.2. Access the TSM V7.1.0 server code from download file or DVD.
2.2.3. Extract code to install directory.
2.2.4. Follow wizards steps or command line installation method.

2.3. Given the number of licenses required, issue the register license
command so that TSM V7.1 is registered.

SUBTASK(S):
2.3.1. Determine the number of licenses required.
2.3.2. Use REGISTER LICENCE FILE=TSM.LIC or REGISTER LICENCE
FILE=TSMEE.LIC.
2.3.3. Issue the QUERY LICENSE command to verify TSM is registered.

2.4. Given adequate space for the database and recovery logs, instance ID
and directories,TSM V7.1 Installation Guide, configure the server so
that the TSM server is configured for backing up data.

SUBTASK(S):
2.4.1. Create instance owner user ID.
2.4.2. Create empty directories for database and recovery logs, owned by the
instance user.
2.4.3. Open the configuration utility (dsmicfgx) and follow the steps.
2.4.4. Verify the comments in the dsmserv.opt file.

2.5. Given appropriate hardware, software, and networking, access the

TSM V7.1.0 Backup-Archive client code and installation
documentation, follow the procedures so that the Backup-Archive
client is installed.

SUBTASK(S):
2.5.1. Verify software and hardware requirements.
2.5.2. Access the TSM V7.1.0 Backup-Archive code from download file or DVD.
2.5.3. Extract code to install directory.
2.5.4. Follow wizards steps or command line installation method.
2.5.5. Create client options file.
2.5.5.1. Create dsm.opt or use the client options file configuration wizard
2.5.5.2. Enter nodename, communication method, server address, and
port 1500, or comparable port.
2.5.6. Use the wizard to set up the Web client
2.5.7. Utilize the operations center or command to associate the node with
schedules and policies.

2.6. Given access the TSM V7.1.0 Backup-Archive client code and
installation documentation, select the custom installation method and
 follow the documented process to install the administrative client
command line so that the administrative command line is installed.

SUBTASK(S):
2.6.1. Verify software and hardware requirements.
2.6.2. Access the TSM V7.1.0 Backup-Archive code from download file or DVD.
2.6.3. Extract code to install directory.
2.6.4. Select the custom install.
2.6.5. Select the Administrative client command line feature to be installed.
2.6.6. Follow wizards steps or command line installation method.

2.7. Given supported storage device, manufacturers documentation, and a

correctly configured TSM V7.1 server, configure the storage device
hardware so that backup data can be written to the device.

SUBTASK(S):
2.7.1. Verify the device is supported.
2.7.2. Determine element numbers for libraries with multiple drives.
2.7.3. Install device according the manufacturers documentation.
2.7.4. Determine appropriate drivers.
2.7.4.1. Download Tivoli device drivers for non-IBM devices.
2.7.4.2. Download IBM device drivers for IBM devices.
2.7.4.3. Define an unsupported drive as GENERICTAPE.

2.8. Given an installed TSM server, SAN or LAN infrastructure, use the
available TSM tools to collect the information so that the devices can
be used as destinations for backup, archives or space management
such as device classes and storage pools.

SUBTASK(S):
2.8.1. Depending on the Operating System configure appropriate device drivers.
2.8.1.1. In general find the correct driver for the device and then load the
native driver for the device.
2.8.1.2. If the native driver is not available from the vendor be sure to
check the list of supported devices in Tivoli Storage Manager Web
pages, then use the Tivoli Storage Manager driver.
2.8.2. Identify media types available with customer's hardware.
2.8.3. Determine network connectivity and protocols available, use the TSM
utilities like TSMDLST to list the information
2.8.4. The same steps for the path definitions have to be repeated for every TSM
Storage agent.
2.8.5. If the TSM server is set up as library manager, the same steps have to be
repeated for the TSM library clients.
2.8.6. Configure library, drives, path.
2.8.7. Define the device classes by using the library names.
2.8.8. If necessary use the command perform libaction when updates or
reconfiguration has to be done.
2.8.9. Use the device classes to create the necessary storage pools.

2.9. Given the hub server spoke server, collection period, at-risk settings
and alert triggers, define and install operations center so that
operations center is ready to utilize.

SUBTASK(S):
2.9.1. Choose a hub server.
2.9.2. Determine spoke servers to be monitored.
2.9.3. Specify a collection period for the operation center data.
2.9.4. Specify at-risk settings for the 3 types of TSM clients being monitored.

2.10. Given the level of encryption, files to encrypt and encryption

password, install and configure encryption so that files are encrypted
prior to being backed up.

SUBTASK(S):
2.10.1. Determine level of encryption to utilize and update option file.
2.10.2. Update include/exclude statements to identify files to encrypt.
2.10.3. Select an encryption password.
2.10.4. Decide to use or not to use a password key-ring.
2.10.5. Validate encryption with query backup.

2.11. Given that the environment requirements are met and the TSM server
is correctly installed, perform the installation and configuration steps
so that the TSM Backup-Archive client is able to be used for space
management (HSM).

SUBTASK(S):
2.11.1. Before installing the TSM for Space Management client on any system,
review the general requirements and considerations:
2.11.1.1. anti-virus software
2.11.1.2. how often these files are accessed
2.11.1.3. how the file system is accessed.
2.11.2. Install on the TSM Backup-Archive client the space management
software.
2.11.3. Understand the difference between the HSM for Windows and the TSM
space management for UNIX
2.11.4. Determine which client options are appropriate.
2.11.5. The TSM for Space Management client is configured by setting options
in the dsm.sys and dsm.opt files. The options generally affect all space-
managed file systems, and determine the following things:
2.11.5.1. The TSM to which files migrate or pre-migrate
2.11.5.2. The include-exclude file that applies for each TSM server.
 2.11.5.3. How often space usage is checked on your file systems
2.11.5.4. How often your file systems are automatically reconciled
2.11.5.5. How often candidates are searched for automatic migrations
2.11.5.6. How many automatic migration processes for each file system
can migrate files in parallel
2.11.5.7. How many days to keep an obsolete file copy in Tivoli Storage
Manager storage before the copy expires.
2.11.5.8. Whether to use two-way orphan check reconciliation (for
GPFS only)
2.11.6. Configure the management classes and storage pool destinations in the
TSM server for the space managed data.
2.11.7. Configure the TSM HSM client.
2.11.7.1. Add and configure space management for a file system:
2.11.7.2. Migrate files.
2.11.7.3. Back up and restoring file systems before migrating.
2.11.7.4. Recall migrated files.
2.11.7.5. Reconcile file systems.
2.11.7.6. Space management daemons
2.11.8. Verify the client is working.

2.12. Given a VMware ESX or ESXi-based host running VMs and the TSM
server installed and configured, prepare, install, and configure TSM
for Virtual Environments Version 7.1 so that TSM for Virtual
Environments is available.

SUBTASK(S):
2.12.1. Find and read the multiple documentation resources that are provided to
assist with specific tasks because Data Protection for VMware provides
several components to assist with protecting your VMs, vApps, and
organization vDCs.
2.12.2. Identify the customer's virtual environment backup needs and the product
or combination of products that will best fit their needs.
2.12.2.1. TSM Backup-Archive client in guest
2.12.2.2. TSM for VE
2.12.2.3. TSM FCM for VE
2.12.2.4. TSM data protection modules
2.12.3. Identify the different Data Protection for VMware types of backup and
restore functions:
2.12.3.1. Full VM backups
2.12.3.2. Incremental VM backups
2.12.3.3. File level restore
2.12.3.4. Instant restore
2.12.3.5. Full VM restore
2.12.3.6. Full VM instant restore
2.12.4. Determine how TSM nodes are used in a virtual environment:
2.12.4.1. vCenter node
 2.12.4.2. datacenter node
2.12.4.3. VMCLI node
2.12.4.4. Data mover node
2.12.5. Determine which TSM for VE GUI to utilize:
2.12.5.1. direct access via GUI in Web
2.12.5.2. VMware Web Client directly in Web browser
2.12.5.3. vSphere Windows client
2.12.6. Set up data protection methodology:
2.12.6.1. Incremental forever backup strategy
2.12.6.2. Periodic full backup strategy
2.12.6.3. Controlling which disks are processed
2.12.6.4. VM templates and vApps in a vSphere environment
2.12.6.5. Automated client failover
2.12.6.6. Full VM instant restore environment requirements
2.12.7. Set up Mount, file-level restore, and instant restore of volumes:
2.12.7.1. Data Protection for VMware Recovery agent configurations
2.12.7.2. Mounting snapshots overview
2.12.7.3. File-level restore overview
2.12.7.4. Instant restore overview
2.12.8. Configure Self-contained application protection:
2.12.8.1. Application protection for Microsoft Exchange Server and SQL
Server
2.12.8.2. Configure self-contained application protection
2.12.8.3. Verify self-contained application
2.12.8.4. Application protection for Active Directory domain controllers
2.12.9. Prepare the installation of Data Protection for VMware by reviewing
prerequisite information before attempting to install Data Protection for
VMware.
2.12.10. Installing Data Protection for VMware.
2.12.10.1. Data Protection for VMware Recovery Agent
2.12.10.2. Recovery Agent command-line interface
2.12.10.3. Documents
2.12.10.4. Data Protection for VMware Enablement File
2.12.10.5. Data Protection for VMware vSphere GUI
2.12.10.6. Data Protection for VMware vCloud GUI
2.12.10.7. Data mover
2.12.11. Identify and know how to configure Data Protection for VMware:
2.12.11.1. Use the configuration wizard for an initial configuration or to
complete minor changes.
2.12.11.2. Use the Edit Configuration notebook to edit existing
configuration settings.
2.12.11.3. Start and run services for Data Protection for VMware.
2.12.11.4. Tape configuration guidelines
2.12.11.5. Configure systems for iSCSI mount.
2.12.11.6. Configure the Data Protection for VMware Recovery Agent
GUI.
 2.12.11.7. Configure Cygwin for use when restoring files from a Linux
machine
2.12.11.8. Modify the VMCLI configuration file.
2.12.11.9. Migrate to an incremental forever backup strategy.
2.12.11.10. Integrate Tivoli Storage Manager for Virtual Environments
with Tivoli Storage FlashCopy Manager for VMware.
2.12.12. Identify the Data Protection for VMware backup scenarios for backing
up VMware vSphere or vCloud data:
2.12.12.1. vCloud environment backup scenarios
2.12.12.2. vSphere environment backup scenario
2.12.12.3. Incremental forever backup scenario
2.12.12.4. Periodic full backup scenario
2.12.12.5. Include scenarios
2.12.12.6. Management class scenarios
2.12.12.7. Control disk scenarios
2.12.12.8. Control disks used by applications
2.12.12.9. Cluster and data store backup scenarios
2.12.12.10. Parallel backup processing
2.12.12.11. Active Directory domain controller protection scenario

2.13. Given hardware and software requirements are met, TSM server and
TSM client software are installed, and the TSM Information Center has
all information for a guided configuration available, configure IBM
Tivoli FlashCopy Manager (FCM) so that FCM is configured and
available.

SUBTASK(S):
2.13.1. Describe FCM:
2.13.1.1. Benefits of FCM
2.13.1.2. Back up and restore methods with FlashCopy and snapshots.
2.13.1.3. Database cloning
2.13.1.4. FCM components
2.13.2. Evaluate capacity planning.
2.13.3. Install the product on UNIX and Linux systems.
2.13.4. Install the product on Windows systems.
2.13.5. Install the product on VMware systems.
2.13.5.1. Install on the production server.
2.13.5.2. Install separately on backup or clone servers.
2.13.5.3. Install in silent mode.
2.13.6. Perform Common tasks.
2.13.7. Configure the product on UNIX and Linux systems.
2.13.8. Configure storage environments.
2.13.8.1. Back up and clone server assignment.
2.13.8.2. Manage backups and clones with the DEVICE_CLASS
parameter.
2.13.8.3. Configuring for remote mirroring
 2.13.8.4. Required daemons on the production and backup systems
2.13.8.5. Post-installation and configuration
2.13.9. Configure the product on Windows systems.
2.13.9.1. The four FCM components that operate in Windows
environments include:
2.13.9.2. MMC Snapin and Base System Services
2.13.9.3. VSS Requestor
2.13.9.4. FlashCopy Manager for Microsoft Exchange Server
2.13.9.5. FlashCopy Manager for Microsoft SQL Server
2.13.10. Configure the product for VMware systems.
2.13.10.1. Tivoli Storage FlashCopy Manager for VMware profile
2.13.10.2. Tivoli Storage FlashCopy Manager for VMware target set
definitions
2.13.10.3. Select the FLASHCOPY_TYPE
2.13.11. Attach a backup of an NFS datastore on IBM System Storage N series
and NetApp storage systems.
2.13.11.1. Start and stop services for FCM for VMware.
2.13.11.2. Password administration
2.13.11.3. GSKit configuration

2.14. Given an installed TSM server, use the available TSM tools to setup a
secure user administration controlled by LDAP so that the Tivoli
Storage Manager environment is enabled to use an LDAP directory
server to authenticate passwords.

SUBTASK(S):
2.14.1. Check requirements, minimum levels of tivoli storage manager servers
and clients.
2.14.2. Configure SSL or TLS for LDAP directory servers.
2.14.2.1. Configure Tivoli Directory Server for TLS on the iKeyman GUI.
2.14.2.2. Configure Tivoli Directory Server for TLS on the command line.
2.14.2.3. Configure Windows Active Directory for TLS/SSL.
2.14.3. Configure the Tivoli Storage Manager server to authenticate passwords
with an LDAP directory server.
2.14.4. Register nodes and administrator IDs to authenticate passwords with an
LDAP directory server.
2.14.5. Identify the LDAP directory server usage: effects on performance.
2.14.6. Audit the LDAP directory server to clean up the server.
2.14.7. Recover an LDAP server with replication or other methods.

2.15. Given the TSM server is installed and configured, prepare, install, and
configure TSM for Mail and TSM for Databases so that TSM for Mail
and TSM for Databases are available.

SUBTASK(S):
2.15.1. Install the Tivoli Directory Server client.
2.15.2. Configure the client.
2.15.3. Determine retention policies to be configured.
2.15.4. Determine schedules.
2.15.5. Create pools, if needed.
Section 3 - Configuration
3.1. Given enough file space in different file systems/Drives on an installed
OS with IBM Tivoli Storage Manager (TSM) server software installed,
configure database and log space so that the database and log space
is available.

SUBTASK(S):
3.1.1. Estimate the amount of needed space.
3.1.2. Create/Mount empty directories for Database, Active log, ArchiveLog and
FailoverLog.
3.1.3. Create/Mount Directories for Active log mirror or enable OS-Mirroring.
3.1.4. Check and set permissions and ownership for Log-Directories to the
defined Instance user.
3.1.5. Initialize DB and Log Directories with dsmicfgx-Wizard or dsmserv
format-command.

3.2. Given an installed and initialized TSM server with attached Tape
libraries, define tape libraries so that the Tape Libraries are configured
in TSM.

SUBTASK(S):
3.2.1. Identify OS devices for attached libraries.
3.2.2. Configure device driver.
3.2.2.1. Configure native vendor driver.
3.2.2.2. If native driver not available, configure Tivoli Storage Manager
generic driver.
3.2.3. Define libraries in the TSM server.
3.2.4. Check if SANDiscovery is enabled.
3.2.5. Define library drives with perform libaction for each library.
3.2.6. If SAN Discover is unavailable:
3.2.6.1. Define paths to Libraries.
3.2.6.2. Define drives for each library.
3.2.6.3. Define paths to drives.

3.3. Given an installed and initialized TSM server with attached disk
storage and/or Tape Libraries, set up pools so that primary storage
pools can configured in TSM.

SUBTASK(S):
3.3.1. Determine the SLA requirements for nodes for restoring.
3.3.2. Determine which Nodes uses which Types of Storage pools.
3.3.3. Create directories for disk and file pools on OS.
3.3.4. Check and set permissions and ownership of directories.
3.3.5. Define needed device classes.
3.3.6. Define storage pools in TSM according to:
3.3.6.1. Device Class
 3.3.6.2. deduplication
3.3.6.3. collocation requirements
3.3.6.4. Migration Thresholds
3.3.6.5. Reclamation Thresholds
3.3.6.6. Number of Scratch-Volumes
3.3.7. Define volumes for disk storage pools.

3.4. Given an installed and initialized TSM server and known customer
requirements for data protection set up policies so that policies are
configured in TSM.

SUBTASK(S):
3.4.1. Identify different requirements to group this in different policy domains.
3.4.2. Define policy domains.
3.4.3. Define policy set.
3.4.4. Identify per group different Retentions and/or different storage
requirements and define Management Classes.
3.4.5. Define Backup and Archive copy groups per Management Class according
to:
3.4.5.1. retentions
3.4.5.2. storage pool destination
3.4.5.3. versioning for backup
3.4.6. Define default Management class per policy set.
3.4.7. Validate policy set.
3.4.8. Activate policy set.

3.5. Given an installed and initialized TSM server with defined storage
pools and knowledge of collocation requirements, define collocation
groups so that nodes can defined in collocation groups.

SUBTASK(S):
3.5.1. Identify SLAs that require collocation for restore performance.
3.5.2. Identify Nodes and Files paces which can be grouped in different
collocation groups.
3.5.3. Determine collocation groups.
3.5.4. Define collocation groups.
3.5.5. Define collocation group members according to:
3.5.5.1. Node names
3.5.5.2. File spaces
3.5.6. Check policy domains of nodes according to collocation parameters of
destination storage pools.

3.6. Given an installed and initialized TSM server with defined nodes so
that nodes can schedule their operations.

SUBTASK(S):
3.6.1. Identify nodes which can group their operations at one time.
3.6.2. Define schedules according to:
3.6.2.1. Policy Domains
3.6.2.2. Scheduled action
3.6.2.3. Scheduled start time
3.6.3. Associate nodes to schedules.
3.6.4. Configure and start client schedulers.

3.7. Given sufficient memory, sequential access, file device class storage
pool, list of client nodes to dedulpicate, define of update a storage
pool, register or update client nodes, create or update a policy, and
schedule or manually run identify duplicates command so that
duplicate date is removed when the data moves to an enables storage
pool.

SUBTASK(S):
3.7.1. Identify client-side or server-side method for deduplicating data.
3.7.2. Create new sequential access, file device class storage pool or update
existing sequential access, file device class storage pool as a next-in-
chain pool.
3.7.3. Set up client-side deduplication.
3.7.3.1. Add deduplication=yes to the dsm.opt file.
3.7.3.2. Create or update a policy to use the deduplication storage pool.
3.7.3.3. Update or register the client node with
deduplication=clientorserver
3.7.4. Set up server-side deduplication.
3.7.4.1. Query option to verify deduprequiresbackup is set to Yes.
3.7.4.2. Update or register the client node with deduplication=serveronly.
3.7.5. Schedule or manually run IDENTIFY DUPLICATES command.

3.8. Given an installed TSM server use the available utilities and
commands to initialize, use, and manage the tape volumes through
the different Tivoli storage manager states so that the automated tape
library is prepared with tape volumes and can be used for the different
data processes in the TSM.

SUBTASK(S):
3.8.1. Identify the different types of volumes in TSM (libvolume, volume,
drmedia).
3.8.2. Identify the different states of the tape volumes (scratch, private).
3.8.3. Identify how the the lifecycle of a tape volume is controlled (volhistory).
3.8.4. Prepare a tape volume to be used in TSM.
3.8.5. Make the tape volume available in the tape library for TSM.
3.8.6. Ensure that an automated library is in a consistent state.
3.8.7. Check a storage volume out of an automated library.
3.8.8. Dismount a sequential, removable volume by the volume name.
3.8.9. Label volumes in manual or automated libraries.
3.8.10. Display information about one or more libraries.
3.8.11. Display information about a library volume.
3.8.12. Change the status of a storage volume.

3.9. Given the need for bare metal restore, be able to identify the correct
bare metal restore solution so that customer can be given correct
recommendation.

SUBTASK(S):
3.9.1. Determine need for Bare Metal Restore.
3.9.2. Narrow down bare metal solution between ASR, TBMR, SysBack ,or TSM
for VE.

3.10. Given the cluster servers are available and the OS is prepared to run
as a cluster, install, configure and manage the TSM software
server/client in a clustered environment so that the TSM server / client
is available in a clustered environment.

SUBTASK(S):
3.10.1. Identify Cluster environment configuration and use.
3.10.2. Identify the different types of cluster environments.
3.10.2.1. Active/Active: Pool cluster resources
3.10.2.2. Active/Passive: Fault tolerant
3.10.2.3. Concurrent access
3.10.3. Configure the Backup-Archive client in a cluster environment.
3.10.3.1. Check the prerequisites before configuring the Backup-Archive
client to back up cluster and non-cluster volumes.
3.10.4. Configure a TSM server for Windows in a Microsoft failover cluster
environment
3.10.4.1. Microsoft Failover Cluster environment overview
3.10.4.2. Windows operating systems Tape failover for nodes in a cluster
3.10.4.3. Windows operating systems Planning for a clustered
environment
3.10.4.4. Setting up Tivoli Storage Manager in a Microsoft Failover
Cluster
3.10.4.5. Windows operating systems Maintaining the clustered
environment
3.10.5. Configure Tivoli Storage FlashCopy Manager to operate in clustered
environments with SQL Server, or file system workloads.
3.10.5.1. Tivoli Storage FlashCopy Manager for SQL: Tivoli Storage
Manager configuration
3.10.6. Configure an AIX environment for clustering.
3.10.6.1. Requirements for a PowerHA cluster
3.10.6.2. PowerHA failover and failback
3.10.6.3. Install and configure PowerHA SystemMirror for AIX.
 3.10.6.4. Install the TSM server on a production node for PowerHA.
3.10.6.5. Install the TSM client on a production node for PowerHA.
3.10.6.6. Verify the configuration of the TSM server for PowerHA.
3.10.6.7. Set up the standby node for PowerHA.
3.10.6.8. Define the removable media storage devices to AIX for
PowerHA.
3.10.6.9. Complete the cluster manager and TSM configurations.
3.10.6.10. Troubleshoot the PowerHA clustered environment.
3.10.7. Configure a Linux clustered environment.
3.10.8. Install Data Protection for SQL Server in a cluster environment.
Section 4 - Administration
4.1. Given an administrator with system or unrestricted storage privilege,
correctly configured IBM Tivoli Storage Manager (TSM) server and
Backup-Archive client, configured supported storage devices, working
network, define disk, file, and removable media device classes so that
device classes are defined for all supported device types.

SUBTASK(S):
4.1.1. Define disk device classes for random access storage pools.
4.1.2. Define file device classes for sequential access storage pools.
4.1.3. Define removable media device classes.

4.2. Given an administrator with system privilege, defined appropriate

device classes, and defined random access, primary destination pool,
define sequential access primary storage pool, update destination
random access and sequential access primary storage pool and
specify NEXTSTGPOOL, so that storage pools are chained together so
that data can move from one device or media type to another.

SUBTASK(S):
4.2.1. Define a sequential access primary storage pool.
4.2.2. Update destination random access primary storage pool and specify
NEXTSTGPOOL.
4.2.3. Update other sequential access primary storage pool and specify
NEXTSTGPOOL.

4.3. Given an administrator with system privilege, defined appropriate

device classes, and defined random and sequential access primary
storage pools, define or update a sequential access storage pool with
pooltype=copy, sufficient space to hold primary pool backups, and
with a maxscratch value specified so that copy storage pools are
defined to store storage pool backups.

SUBTASK(S):
4.3.1. Determine which storage pool protection will be used.
4.3.2. Define or update a sequential access storage pool with pooltype=copy.
4.3.3. Include a maxscratch value.
4.3.4. Ensure copypool size is sufficient to hold primary pool backups.

4.4. Given an administrator with system privilege, defined appropriate

device classes, and defined random and sequential access primary
storage pools, define or update a sequential access storage pool with
pooltype=active, sufficient space to hold primary pool active-data
version backups, with a maxscratch value specified, so that active-
data storage pools are created.
SUBTASK(S):
4.4.1. Define or update a sequential access storage pool with pooltype=active.
4.4.2. Include a maxscratch value.
4.4.3. Ensure active data pool size is sufficient to hold active versions of the data
in primary pool backups.
4.4.4. Define or update a policy domain for active data.

4.5. Given an administrator with system or policy privilege, a defined

management class, and client data stored in storage pools, define
archive and backup copy groups, and run the expire inventory
command so that expired data is removed for the storage pools.

SUBTASK(S):
4.5.1. Define an archive copygroup with a specified retention period.
4.5.2. Define a backup copy group with a specified retention period.
4.5.3. Define a backup copy group with a specified number of versions to retain.
4.5.4. Schedule or manually run expire inventory.

4.6. Given an administrator with system privilege, sequential access

storage pools, update or define storage pools to specify reclamation
parameters so that data from partially filled tape volumes is
consolidated so empty volumes can be reused.

SUBTASK(S):
4.6.1. Specify reclamation parametrs with the define or update storage pool
command.
4.6.1.1. Set the reclamation process number.
4.6.1.2. Set the reclamation type, threshold or snaplock.
4.6.1.3. Set the reclamation target storage pool.
4.6.2. Schedule or manually run reclaim stgpool command when the threshold is
high.

4.7. Given an administrator with system privilege and defined storage pool
hierarchy, set the high and low migration thresholds, and MIGDELAY
and MIGCONTINUE parameters so that stored client data automatically
moves through the storage pool hierarchy to free up space in the
source pool.

SUBTASK(S):
4.7.1. Set the high migration threshold with the define or update storage pool
command.
4.7.2. Set the low migration threshold with the define or update storage pool
command.
4.7.3. Set the MIGDELAY parameter.
4.7.4. Set the MIGCONTINUE parameter.
4.8. Given an administrator with system privilege and defined storage pool
hierarchy, update or define a primary storage pool so the destination
is up to three target primary, copy, or active-data storage pools, with
appropriate mount points so that client data backups and archives,
server imports, and storage pool migration configured for multiple
thread processing.

SUBTASK(S):
4.8.1. Update or define a primary storage pool so the destination is up to a
maximum of three target primary, copy, or active-data storage pools.
4.8.2. Specify the mount limit for associated primary, copy, or active-data
storage pools.

4.9. Given an installed TSM server, automate administrative processes by

admin scheduling and TSM scripting so that repetitive, manual tasks
associated with managing the server can be automated through TSM
schedules and scripts.

SUBTASK(S):
4.9.1. Identify Server automation.
4.9.2. Automate server operations.
4.9.3. Automate a basic administrative command schedule.
4.9.3.1. Tailoring schedules
4.9.3.2. Copying schedules
4.9.3.3. Deleting schedules
4.9.4. Manage scheduled event records.
4.9.5. TSM server scripts:
4.9.5.1. Define a server script.
4.9.5.2. Manage server scripts.
4.9.5.3. Run a server script.
4.9.6. Use macros.

4.10. Given the required responsibilities of an administrator identify the

correct level of authority required so that the administrator can
perform the required actions.

SUBTASK(S):
4.10.1. Identify the level of privilege required for an administrator.
4.10.2. Review that the admin privileges are correct for what the admin needs to
do in Operations Center .
4.10.3. Issue a grant authority command.

4.11. Given a configured and running TSM server with attached storage
devices , defined device classes and defined storage pools from Type
primary and copy , back up the storage pool so that the backuped
client data is protected against disaster.
SUBTASK(S):
4.11.1. Determine which Copypool should hold data from which primary storage
pool.
4.11.2. Backup of primary Storagepool to Copypool with BACKUP STG:
4.11.2.1. Schedule
4.11.2.2. Manually run
4.11.2.3. Initiate with the Operations Center
4.11.3. Check Actlog against failures.

4.12. Given a configured and running TSM server with attached storage
devices and defined device classes, backup the database so that the
Database is protected against disaster.

SUBTASK(S):
4.12.1. If necessary, check if Storage pool backups are completed.
4.12.2. Determine the device class, which should use for the database backup.
4.12.3. Determine type of backup:
4.12.3.1. Full
4.12.3.2. Incremental
4.12.3.3. Snapshot
4.12.4. Start the Backup with BACKUP DB:
4.12.4.1. Schedule
4.12.4.2. Manually run
4.12.4.3. Initiate with the Operations Center
4.12.5. Check Actlog against failures.

4.13. Given a configured and running TSM server, installed Backup-Archive

client, established network connection and defined communication
parameters, manage the client options so that the client can connect
to the TSM server

SUBTASK(S):
4.13.1. Determine method to edit the client options.
4.13.1.1. Windows: Edit dsm.opt
4.13.1.2. Unix/Linux: Edit Stanza in dsm.sys and edit dsm.opt
Client Configuration Wizard in the Backup/Archive GUI.
Individual or enterprise option sets will be utilized.
4.13.2. Determine which client options are appropriate.
4.13.3. Define option TCPSERVERADDRESS to the TSM server IP address or
DSN name.
4.13.4. Define option TCPPORT to the TSM server port.
4.13.5. Define option COMMMETHOD.
4.13.6. Determine which Scheduler-Mode should used:
4.13.6.1. POLLING (default)
4.13.6.2. PROMPTED
4.13.7. Determine the password handling:
4.13.7.1. PASSWORDACCESS PROMPTED (default)
4.13.7.2. PASSWORDACCESS GENERATE
4.13.8. Verify other needed options.
4.13.9. Verify that the client is working.

4.14. Given a configured and running TSM server, configured Backup-

Archive client, knowledge of customer SLA and policy domains,
establish include/exclude lists so that the client can backup its data
according Customer SLAs

SUBTASK(S):
4.14.1. Determine the need of excludes and/or includes for different Objects
according the customer SLA.
4.14.2. Determine Objects that need special management classes.
4.14.3. Define include/exclude-Rules in a file.
4.14.4. Define option INCLEXCL in dsm.opt/dsm.sys

4.15. Given a configured and running TSM server, configured Backup-

Archive client, knowledge of nodes and client options, set up server
option sets so that the TSM server can centralized set client options
for nodes.

SUBTASK(S):
4.15.1. Determine nodes which can use a client option set.
4.15.2. Determine client options which can set from the server.
4.15.3. Identify the priorities.
4.15.4. Define client option set.
4.15.5. Define client option to the client option set.
4.15.6. Update node to associate Node with client option set.

4.16. Given a configured Backup-Archive client, set up the CAD so that the
client can used with the Web GUI and/or run the scheduling service.

SUBTASK(S):
4.16.1. Determine that client option SESSIONINITIATION=SERVERONLY is not
set.
4.16.2. Determine which CAD services are need:
4.16.2.1. Web GUI
4.16.2.2. Scheduler
4.16.3. On Unix/Linux define Option MANAGEDSERVICES in dsm.sys
4.16.4. On Unix/Linux define Option CLIENTTCPPORT in dsm.sys
4.16.5. On Unix/Linux start the dsmcad deamon
4.16.6. On Windows use the Wizard in Preferences-Menu of the Backup-Archive
GUI to configure and start the CAD service.
4.17. Given configured TSM environment, portable media device, accessible
by server and client system, generate backup sets so that backup set
data can be restored on the Backup-Archive client.

SUBTASKS:
4.17.1. Understand the benefits and usage of backup sets.
4.17.2. Generate backup set on server.
4.17.2.1. Generate backup set for individual client node.
4.17.2.2. Generate backup set for node groups.
4.17.2.3. Generate table of contents.
4.17.3. Restore backup set on client.

4.18. Given a source and target server, nodes and their data, and automatic
failover, set up node replication so that data is automatically
replicated over to a target server.

SUBTASK(S):
4.18.1. Define the source and target server.
4.18.2. Enable replication for specific nodes and a specific type of data.
4.18.3. Validate replication configuration.
4.18.4. Set up automatic failover.

4.19. Given an installed TSM server use the export / import functionality of
the TSM server so that data can be exported from one TSM server to
another.

SUBTASK(S):
4.19.1. Review data that can be exported and imported.
4.19.2. Export data directly to another server.
4.19.2.1. Prepare to export to another server for immediate import.
4.19.2.2. Monitor the server-to-server export process.
4.19.3. Export and import data using sequential media volumes.
4.19.4. Export tasks.
4.19.5. Import data from sequential media volumes.
4.19.6. Identify Exporting/ importing tasks.
4.19.6.1. Export/Import administrator information
4.19.6.2. Export/Import client node information
4.19.6.3. Export/Import policy information
4.19.6.4. Export/Import server data
4.19.6.5. Plan for sequential media used to export data.

4.20. Given the necessity for server to server communication and the
needed parameters define server to server communication so that
multiple TSM servers can work together.

SUBTASK(S):
4.20.1. Determine for what operations server to server communication is needed.
4.20.2. Identify the servers and their parameters required to define and verify
server to server communications.
4.20.3. Issue the server to server definitions.

4.21. Given an installed and configured TSM server, configure and manage
the TSM options related to the group files so that the TSM server has
several options to optimize data stream, consistency and management
by several grouping methods

SUBTASK(S):
4.21.1. Manage multiple servers through the Operations Center.
4.21.2. Route commands.
4.21.3. Set up server groups.
4.21.4. Define a server group and members of a server group.
4.21.5. Manage server groups.
4.21.6. Manage group members.
4.21.7. Query server availability.
4.21.8. Keep client files together using collocation:
4.21.8.1. Identify the effects of collocation on operations.
4.21.8.2. Identify how the server selects volumes with collocation
enabled.
4.21.8.3. Identify how the server selects volumes with collocation
disabled.
4.21.8.4. Configure collocation on or off .
4.21.8.5. Configure collocation of copy storage pools and active data
pools.
4.21.8.6. Plan for and enabling collocation.
4.21.8.7. Identify collocation for a group, single client node or file space
level.

4.22. Given an installed and configured TSM clients, configure and manage
the TSM client options related to the group files and nodes so that the
TSM client has several options to optimize data stream, consistency
and management by several grouping methods.

SUBTASK(S):
4.22.1. BA client:
4.22.1.1. Back up group.
4.22.1.2. Delete group.
4.22.1.3. Query group.
4.22.1.4. Restore group.
4.22.2. HSM
4.22.3. File groups
4.22.3.1. Create a new file group.
4.22.3.2. Edit a file group.
4.23. Given an installed and configured TSM server and clients, configure
the TSM server and client options so that the TSM client has multiple
options to restore/retrieve files from another TSM client on its own
disk.

SUBTASK(S):
4.23.1. Restore or retrieve files to another workstation using the virtual node
name option.
4.23.2. Authorize another user to restore or retrieve files from another node.
4.23.3. Restore or retrieve files from another client node.

4.24. Given the need to protect NAS devices, determine the correct backup
type so that the NAS devices are protected.

SUBTASK(S):
4.24.1. Understand the backup types available for NAS and the SLA.
4.24.2. If using NDMP backup
4.24.2.1. Determine if going straight to tape or over the network to TSM.
4.24.2.2. Determine if a TOC is needed.
4.24.2.3. Set up the management class and domain for the NAS backups.
4.24.2.4. Register a node with type=nas.
4.24.2.5. Define a datamover with type = nas.
4.24.3. If backing up a nSeries or netApps appliance:
4.24.3.1. Consider Snapmirror to tape for an image backup.
4.24.3.2. Consider Snapdiff for an incremental file level backup.

4.25. Given installed TSM server clients are configured, set up archiving so
that data is ready to be archived.

SUBTASK(S):
4.25.1. Identify the difference in TSM between archiving and backup server
automation.
4.25.2. Identify Archive operations overview.
4.25.3. Implement archive policies.
4.25.4. Configure the backup archive client to select how archived files are
managed.
4.25.5. Manage storage usage for archives:
4.25.5.1. Minimize archive storage use.
4.25.5.2. Reduce archive storage use for client nodes with many archives.
4.25.5.3. Prevent archive of directory-level access permissions.

4.26. Given a configured TSM environment, identify the appropriate client

options, determine backup method for Backup-Archive client,
determine the Backup-Archive interface to perform the backup, and
 schedule or manually run the backup operation so that Backup-
Archive data can be backed up.

SUBTASKS:
4.26.1. Identify appropriate client options.
4.26.2. Determine backup method for Backup-Archive client.
4.26.2.1. Use incremental (complete).
4.26.2.2. Use incremental by date.
4.26.2.3. Use incremental (without journal).
4.26.2.4. Use always backup (selective).
4.26.2.5. Use image.
4.26.2.6. Use logical volume backup.
4.26.3. Determine the backup-archive interface to perform the backup.
4.26.3.1. Use the command line.
4.26.3.2. Use the GUI.
4.26.3.3. Use the Web client.
4.26.4. Schedule or manually run the backup operation

4.27. Given a configured TSM environment, identify appropriate client

options, determine the Backup-Archive interface to perform the
restore operation, and schedule or manually run the restore operation
so that data for the Backup-Archive client can be restored.

SUBTASKS:
4.27.1. Identify appropriate client options.
4.27.2. Determine the Backup-Archive interface to perform the restore operation.
4.27.2.1. Use the command line.
4.27.2.2. Use the GUI.
4.27.2.3. Use the Web client.
4.27.3. Determine classic or no query.
4.27.4. Schedule or manually run the restore operation.

4.28. Given a configured TSM environment, identify appropriate client

options, determine the Backup-Archive interface to perform the
archive, create archive description, and schedule or manually run the
archive operation so that Backup-Archive data is archived.

SUBTASKS:
4.28.1. Identify appropriate client options.
4.28.2. Determine the backup-archive interface to perform the archive.
4.28.2.1. Use the command line.
4.28.2.2. Use the GUI.
4.28.2.3. Use the Web client.
4.28.3. Create archive description, if not using default.
4.28.4. Schedule or manually run the archive operation.
4.29. Given a configured TSM environment, identify appropriate client
options, determine the Backup-Archive interface to perform the
retrieve operation, and schedule or manually run the retrieve
operation so that archive data for the Backup-Archive client is
retrieved.

SUBTASKS:
4.29.1. Identify appropriate client options.
4.29.2. Determine the Backup-Archive interface to perform the retrieve operation.
4.29.2.1. Use the command line.
4.29.2.2. Use the GUI.
4.29.2.3. Use the Web client.
4.29.3. Schedule or manually run the retrieve operation.

4.30. Given a specific node move its data to a new storage pool so that it
resides in the new storage pool.

SUBTASK(S):
4.30.1. Determine the need for move node data.
4.30.2. Execute a move node data.

4.31. Given alert triggers and a list of administrators who need to be

notified, set up alerting so that alerts are enabled on the TSM servers.

SUBTASK(S):
4.31.1. Determine define and refine the alert triggers.
4.31.2. Determine if alert emails are required and turn them on if needed.
4.31.3. Determine and enable specific administrators to receive alert emails or
alert summaries.

4.32. Given the need to restore a database execute the needed commands
so that the TSM server is restored.

SUBTASK(S):
4.32.1. Obtain the volume history file and device configuration file.
4.32.2. Obtain the database backup volumes.
4.32.3. Recreate the database and recovery log directories if needed.
4.32.4. Run the database restore commands as either a point-in-time or current
state.
4.32.5. Run the audit library command to synchronize the library inventories.

4.33. Given an administrator with system privileges, manage the database

and recovery logs so that the TSM instance performs optimally.

SUBTASK(S):
4.33.1. Monitor database, active log and archive log size using the Operations
Center.
4.33.2. If database size uses ca. 80% of space:
4.33.2.1. Extend Database space.
4.33.2.2. Extend file systems of database directories.
4.33.2.3. Load balance the database.
4.33.3. If active log size is small due to excess frequency of backups.
4.33.3.1. Adjust files system size of active log.
4.33.3.2. Adjust ACTIVELOGSIZE in dsmserv.opt.
4.33.3.3. Restart the TSM instance.
4.33.4. If Size of archive log directory does not fit:
4.33.4.1. Adjust file system size of archive log directory.
4.33.4.2. Adjust frequency of TSM database backups of type full.
4.33.5. Define retention of database backups.
4.33.5.1. Set DRMDBBACKUPEXPIREDAYS.
4.33.5.2. Schedule or manually run DELETE VOLHISTORY for used
types of database backups.
4.33.6. Determine DB2 Reorganization issues, needed for TSM
4.33.6.1. Define a reorganization window in a low usage time with the
server options REORGBEGINTIME and REORGDURATION.
4.33.6.2. Define ALLOWREORGTABLE=yes.
4.33.6.3. Define ALLOWREORGINDEX=yes for TSM-Servers which
uses deduplication.

4.34. Given a running TSM server with attached and configured new Tape
hardware with a new supported Tape technology, transfer data so that
the TSM server uses the new Tape technology.

SUBTASK(S):
4.34.1. Define device class for new hardware.
4.34.2. Define storage pools for new device class.
4.34.3. Include storage pools in existing Hirarchy and policy domains.
4.34.4. If necessary MOVE DATA from one storage pool to another.
Section 5 - Problem Determination
5.1. Given a configured IBM Tivoli Storage Manager (TSM) environment
that has performed successfully and the TSM V7.1 Problem
Determination Guide, review error logs, alerts, event logs, and
schedule logs, query the database and storage pools, review the
server options file, and run the QUERY SYSTEM command so that the
TSM server performance problems are identified.

SUBTASK(S):
5.1.1. Review error log:
5.1.1.1. Check log files.
5.1.1.2. Review with the Operations Center.
5.1.2. Review alerts with the Operations Center.
5.1.3. Review activity log with the Operations Center.
5.1.3.1. Query the activity log.
5.1.3.2. Review with the Operations Center.
5.1.4. Query the database and storage pools to ensure they are online.
5.1.5. Review dsmserv.opt settings to see if they have been changed.
5.1.6. Review schedule log.
5.1.7. Run QUERY SYSTEM command to collect consolidated system
information.
5.1.8. Contact support about running a trace.

5.2. Given a configured TSM environment that has performed successfully

on a LAN or SAN, and the TSM V7.1 Problem Determination Guide,
review error messages, enable cyclic redundancy checking, and
compare current network throughput with previous network
throughput, so that network bottlenecks are identified

SUBTASK(S):
5.2.1. Review error messages.
5.2.2. Enable cyclic redundancy checking.
5.2.3. Use server ping to check the heartbeat.

5.3. Given a configured TSM environment that has performed successfully

and the TSM V7.1 Problem Determination Guide, use the DB2 utilities
to monitor the database, review error logs, alerts, and event logs, and
query the database and recovery logs, so that the TSM database
performance problems are identified.

SUBTASK(S):
5.3.1. Use DB2 utilities to monitor the database.
5.3.2. Review error log:
5.3.2.1. Check log files.
5.3.2.2. Review with the Operations Center.
5.3.3. Review alerts with the Operations Center
5.3.4. Review activity log with the Operations Center.
5.3.4.1. Query the activity log.
5.3.4.2. Review with the Operations Center.
5.3.5. Query the database and recovery logs for available space.
5.3.6. Contact support.

5.4. Given a configured TSM environment that has performed successfully

and the TSM V7.1 Problem Determination Guide, review error logs,
alerts, event logs, and schedule logs, review the client options file,
and run the QUERY SYSTEMINFO command, so that the TSM Backup-
Archive client performance problems are identified.

SUBTASK(S):
5.4.1. Determine if the problem is isolated to a node or group of nodes.
5.4.2. Review error log:
5.4.2.1. Check log files.
5.4.2.2. Review with the Operations Center.
5.4.3. Review alerts with the Operations Center.
5.4.4. Review activity log with the Operations Center.
5.4.4.1. Query the activity log.
5.4.4.2. Review with the Operations Center.
5.4.5. Check dsmwebcl.log .
5.4.6. Check Schedlog.
5.4.7. Review client options files settings to see if they have been changed.
5.4.8. Run QUERY SYSTEMINFO command to collect consolidated system
information.
5.4.9. Contact support about running a trace.
Next Steps
1. Take the IBM Certified Deployment Professional Tivoli Storage Manager
V7.1 assessment test using the promotion code csistudy for $10 ($20 USD
savings).

2. If you pass the assessment exam, visit pearsonvue.com/ibm to schedule

your testing sessions. Use the promotion code tivguide to receive 20% off.

3. If you failed the assessment exam, review how you did by section. Focus
attention on the sections where you need improvement. Keep in mind that
you can take the assessment exam as many times as you would like ($10
per exam), however, you will still receive the same questions only in a
different order.