IBM C2010-511

Free Questions in OTE format

About IBM C2010-511 dump

Planning

• 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.
  
• With emphasis on performing the following tasks:
  
• Set up conference with IBM account, IBM Marketing Rep or Services Specialist or IBM business partner.
  
• Gather current software/hardware implemented for IBM team.
  
• Review the account history.
  
• Create list of Key people to include in initial kick-off conference.
  
• Create agenda for kick-off meeting.
  
• Contact customer to arrange kick-off meeting.
  
• Introduce yourself and state purpose of meeting.
  
• Provide list of people to include, ensure customer agrees with list and change if necessary.
  
• Explain that a questionnaire will be provided and requesting information on current SLA's ,architectural design,installed software/ hardware and procedures in place.
  
• Set the date and time for the kick-off meeting.
  
• Meet with customer team to kick-off project.t
  
• Review signed SOW to ensure the work to be provided is the work expected.
  
• Review Questionnaire for completeness.
  
• 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.
  
• Review IBM software/hardware prerequisites with customer to ensure compatibility.
  
• Draft architectural document.
  
• Consolidate all information gathered.
  
• Ensure all necessary information has been collected.
  
• Provide a high level work schedule.
  
• Send copies to IBM team for review.
  
• Send document to customer for approval.
  
• Schedule technical review meeting with customer.
  
• Ensure that stakeholders of each area are scheduled.
  
• 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.
  
• With emphasis on performing the following tasks:
  
• Identify number of servers hosting unstructured data and propose appropriate IBM data protection product.
  
• Identify number and type of databases and propose appropriate IBM data protection product.
  
• Identify number and type of email server application and propose appropriate IBM data protection product.
  
• Identify client's virtual environment platform and propose appropriate IBM data protection product.
  
• Identify client's storage systems and propose appropriate IBM data protection product.
  
• Identify remote office data backup requirements and propose appropriate IBM data protection product.
  
• Identify backup requirements of remote office data and propose appropriate IBM data protection product.
  
• Identify regulatory and/or company's long term data retention policies and propose appropriate backup methodology Identify data that might benefit from IBM FlashCopy Manager.
  
• Given access to key technical personnel and responses to key questions, assess and evaluate the skill level so that educational opportunities can be made.
  
• With emphasis on performing the following tasks:
  - Arrange meeting with key technical personnel only.
  - Ask pertinent questions regarding technical skills and knowledge.
  - Analyze information gathered from interviews.
  - Identify skill gaps.
  - Align skill gaps with education opportunities.
  
• Given customer's 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.
  
• With emphasis on performing the following tasks:
  
• Translate and document customer's business polices into data retention rules.
  
• Transform data retention rules into IBM Tivoli Storage Manager (TSM) policy.
  
• Determine if data will require offsite copies.
  
• Create TSM management classes that meet policy requirements.
  
• Identify and document data requiring regulatory handling.
  
• Identify clients that house regulatory data.
  
• Separate data/clients into groups based on regulatory retention.
  
• Determine if a Long Term Retention server (Archive) is needed.
  
• Identify and document nodes eligible for node replication.
  
• Identify and document nodes with large numbers of files and data.
  
• Identify and document nodes eligible for traditional Disaster Recovery methodology.
  
• Consolidate created documents and perform additional analysis.
  
• Propose logical architecture for configuration of Disaster Recovery Module.
  
• Given the client's network architecture determine the required firewall configuration in order to enable the data backup and recovery services for costumer's environment.
  
• With emphasis on performing the following tasks:
  
• Engage customer's network team to work on a collaborative effort in the appropriate configuration required to enable data backup and recovery services.
  
• Document required changes on current firewall configuration to enable data backup and recovery services.
  
• Document procedure with the appropriate network configuration requirements of IBM data protection products.
  

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 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
  
• With emphasis on performing the following tasks:
  - Verify the system requirements for TSM V7.
  - Determine the upgrade plan.
  
• Upgrade the server and database on the same system by using media to transfer the database.
  
• Upgrade the server and database on the same system by using the network to transfer the database.
  
• Upgrade the server and database on a new system by using media to transfer the database.
  
• Upgrade the server and database on a new system by using the network to transfer the database.
  
• Install a new TSM V7 server on new hardware and allow the TSM V5 server's data to expire.
  
• Prepare the TSM V5 database for upgrading.
  
• Issue the convert ussfilespace command.
  
• Back up the storage pools.
  
• Back up the V5 database and configuration files.
  
• Install the upgrade utilities package (DSMUPGRD).
  
• Run the DSMUPG PREPAREDB utility.
  
• Prepare the V7 space.
  
• Install the TSM V7 server code, but do not configure.
  
• Create directories and user ID for the V7 instance.
  
• Run DSMSERV LOADFORMAT utility.
  
• Perform the upgrade.
  
• Extract data from V5 database with DSMUPGRD EXTRACTDB utility.
  
• Insert V5 database date to V7 database with DESMSERV INSERTDB utility.
  
• Configure the new system for database backup.
  
• Perform post upgrade tasks.
  
• Back up the new database.
  
• Verify the database contents.
  
• Install TSM Backup-Archive clients V7.
  
• 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.
  With emphasis on performing the following tasks:
  
• Verify software and hardware requirements.
  
• Access the TSM V7.1.0 server code from download file or DVD.
  
• Extract code to install directory.
  
• Follow wizards steps or command line installation method.
  
• Given the number of licenses required, issue the register license command so that TSM V7.1 is registered.
  With emphasis on performing the following tasks:
  
• Determine the number of licenses required.
  
• Use REGISTER LICENCE FILE=TSM.LIC or REGISTER LICENCE FILE=TSMEE.LIC.
  
• Issue the QUERY LICENSE command to verify TSM is registered.
  
• 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.
  With emphasis on performing the following tasks:
  
• Create instance owner user ID.
  
• Create empty directories for database and recovery logs, owned by the instance user.
  
• Open the configuration utility (dsmicfgx) and follow the steps.
  
• Verify the comments in the dsmserv.opt file.
  
• 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.
  
• With emphasis on performing the following tasks:
  
• Verify software and hardware requirements.
  
• Access the TSM V7.1.0 Backup-Archive code from download file or DVD.
  
• Extract code to install directory.
  
• Follow wizards steps or command line installation method.
  
• Create client options file.
  
• Create dsm.opt or use the client options file configuration wizard
  
• Enter nodename, communication method, server address, and port 1500, or comparable port.
  
• Use the wizard to set up the Web client
  
• Utilize the operations center or command to associate the node with schedules and policies.
  
• 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.
  With emphasis on performing the following tasks:
  
• Verify software and hardware requirements.
  
• Access the TSM V7.1.0 Backup-Archive code from download file or DVD.
  
• Extract code to install directory.
  
• Select the custom install.
  
• Select the Administrative client command line feature to be installed.
  
• Follow wizards steps or command line installation method.
  
• Given supported storage device, manufacturer's documentation, and a correctly configured TSM V7.1 server, configure the storage device hardware so that backup data can be written to the device.
  With emphasis on performing the following tasks:
  
• Verify the device is supported.
  
• Determine element numbers for libraries with multiple drives.
  
• Install device according the manufacturers documentation.
  
• Determine appropriate drivers.
  
• Download Tivoli device drivers for non-IBM devices.
  
• Download IBM device drivers for IBM devices.
  
• Define an unsupported drive as GENERICTAPE.
  
• 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.
  With emphasis on performing the following tasks:
  
• Depending on the Operating System configure appropriate device drivers.
  
• In general find the correct driver for the device and then load the native driver for the device.
  
• 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.
  
• Identify media types available with customer's hardware.
  
• Determine network connectivity and protocols available, use the TSM utilities like TSMDLST to list the information
  
• The same steps for the path definitions have to be repeated for every TSM Storage agent.
  
• If the TSM server is set up as library manager, the same steps have to be repeated for the TSM library clients.
  
• Configure library, drives, path.
  
• Define the device classes by using the library names.
  
• If necessary use the command "perform libaction" when updates or reconfiguration has to be done.
  
• Use the device classes to create the necessary storage pools.
  
• 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.
  With emphasis on performing the following tasks:
  
• Choose a hub server.
  
• Determine spoke servers to be monitored.
  
• Specify a collection period for the operation center data.
  
• Specify at-risk settings for the 3 types of TSM clients being monitored.
  
• 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.
  With emphasis on performing the following tasks:
  
• Determine level of encryption to utilize and update option file.
  
• Update include/exclude statements to identify files to encrypt.
  
• Select an encryption password.
  
• Decide to use or not to use a password key-ring.
  
• Validate encryption with "query backup".
  
• 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).
  With emphasis on performing the following tasks:
  
• Before installing the TSM for Space Management client on any system, review the general requirements and considerations:
  anti-virus software
  how often these files are accessed
  how the file system is accessed.
  
• Install on the TSM Backup-Archive client the space management software.
  
• Understand the difference between the HSM for Windows and the TSM space management for UNIX
  
• Determine which client options are appropriate.
  
• 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:
  
• The TSM to which files migrate or pre-migrate
  
• The include-exclude file that applies for each TSM server.
  
• How often space usage is checked on your file systems
  
• How often your file systems are automatically reconciled
  
• How often candidates are searched for automatic migrations
  
• How many automatic migration processes for each file system can migrate files in parallel
  
• How many days to keep an obsolete file copy in Tivoli Storage Manager storage before the copy expires.
  
• Whether to use two-way orphan check reconciliation (for GPFS™ only)
  
• Configure the management classes and storage pool destinations in the TSM server for the space managed data.
  
• Configure the TSM HSM client.
  
• Add and configure space management for a file system:
  
• Migrate files.
  
• Back up and restoring file systems before migrating.
  
• Recall migrated files.
  
• Reconcile file systems.
  
• Space management daemons
  
• Verify the client is working.
  
• Given a VMware ESX or ESXi-based host running VM's 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.
  With emphasis on performing the following tasks:
  
• 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.Identify the customer's virtual environment backup needs and the product or combination of products that will best fit their needs.
  
• TSM Backup-Archive client in guest
  
• TSM for VE
  
• TSM FCM for VE
  
• TSM data protection modules
  Identify the different Data Protection for VMware types of backup and restore functions:
  
• Full VM backups
  
• Incremental VM backups
  
• File level restore
  
• Instant restore
  
• Full VM restore
  
• Full VM instant restore
  Determine how TSM nodes are used in a virtual environment:
  
• vCenter node
  
• datacenter node
  
• VMCLI node
  
• Data mover node
  Determine which TSM for VE GUI to utilize:
  
• direct access via GUI in Web
  
• VMware Web Client directly in Web browser
  
• vSphere Windows client
  Set up data protection methodology:
  
• Incremental forever backup strategy
  
• Periodic full backup strategy
  
• Controlling which disks are processed
  
• VM templates and vApps in a vSphere environment
  
• Automated client failover
  
• Full VM instant restore environment requirements
  Set up Mount, file-level restore, and instant restore of volumes:
  
• Data Protection for VMware Recovery agent configurations
  
• Mounting snapshots overview
  
• File-level restore overview
  
• Instant restore overview
  Configure Self-contained application protection:
  
• Application protection for Microsoft Exchange Server and SQL Server
  
• Configure self-contained application protection
  
• Verify self-contained application
  
• Application protection for Active Directory domain controllers
  
• Prepare the installation of Data Protection for VMware by reviewing prerequisite information before attempting to install Data Protection for VMware.Installing Data Protection for VMware.
  
• Data Protection for VMware Recovery Agent
  
• Recovery Agent command-line interface
  
• Documents
  
• Data Protection for VMware Enablement File
  
• Data Protection for VMware vSphere GUI
  
• Data Protection for VMware vCloud GUI
  
• Data mover
  Identify and know how to configure Data Protection for VMware:
  
• Use the configuration wizard for an initial configuration or to complete minor changes.
  
• Use the Edit Configuration notebook to edit existing configuration settings.
  
• Start and run services for Data Protection for VMware.
  
• Tape configuration guidelines
  
• Configure systems for iSCSI mount.
  
• Configure the Data Protection for VMware Recovery Agent GUI.
  
• Configure Cygwin for use when restoring files from a Linux machine
  
• Modify the VMCLI configuration file.
  
• Migrate to an incremental forever backup strategy.
  
• Integrate Tivoli Storage Manager for Virtual Environments with Tivoli #Storage FlashCopy Manager for VMware.
  
• Identify the Data Protection for VMware backup scenarios for backing up VMware vSphere or vCloud data:
  
• vCloud environment backup scenarios
  
• vSphere environment backup scenario
  
• Incremental forever backup scenario
  
• Periodic full backup scenario
  
• Include scenarios
  
• Management class scenarios
  
• Control disk scenarios
  
• Control disks used by applications
  
• Cluster and data store backup scenarios
  
• Parallel backup processing
  
• Active Directory domain controller protection scenario
  ]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.
  With emphasis on performing the following tasks:
  
• Describe FCM:
  
• Benefits of FCM
  
• Back up and restore methods with FlashCopy and snapshots.
  
• Database cloning
  
• FCM components
  
• Evaluate capacity planning.
  
• Install the product on UNIX and Linux systems.
  
• Install the product on Windows systems.
  
• Install the product on VMware systems.
  
• Install on the production server.
  
• Install separately on backup or clone servers.
  
• Install in silent mode.
  
• Perform Common tasks.
  
• Configure the product on UNIX and Linux systems.
  
• Configure storage environments.
  
• Back up and clone server assignment.
  
• Manage backups and clones with the DEVICE_CLASS parameter.
  
• Configuring for remote mirroring
  
• Required daemons on the production and backup systems
  
• Post-installation and configuration
  
• Configure the product on Windows systems.
  
• The four FCM components that operate in Windows environments include:
  
• MMC Snapin and Base System Services
  
• VSS Requestor
  
• FlashCopy Manager for Microsoft Exchange Server
  
• FlashCopy Manager for Microsoft SQL Server
  
• Configure the product for VMware systems.
  
• FCM for VMware profile
  
• FCM VMware target set definitions
  
• Select the FLASHCOPY_TYPE
  
• Attach a backup of an NFS data store on IBM System Storage N series and NetApp storage systems.
  
• Start and stop services for FCM for VMware.
  
• Password administration
  
• GSKit configuration
  
• 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.
  With emphasis on performing the following tasks:
  
• Check requirements, minimum levels of tivoli storage manager servers and clients.
  
• Configure SSL or TLS for LDAP directory servers.
  
• Configure Tivoli Directory Server for TLS on the iKeyman GUI.
  
• Configure Tivoli Directory Server for TLS on the command line.
  
• Configure Windows Active Directory for TLS/SSL.
  
• Configure the Tivoli Storage Manager server to authenticate passwords with an LDAP directory server.
  
• Register nodes and administrator IDs to authenticate passwords with an LDAP directory server.
  
• Identify the LDAP directory server usage: effects on performance.
  
• Audit the LDAP directory server to clean up the server.
  
• Recover an LDAP server with replication or other methods.
  
• 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.
  With emphasis on performing the following tasks:
  
• @Install the Tivoli Directory Server client.
  
• Configure the client.
  
• Determine retention policies to be configured.
  
• Determine schedules.
  
• Create pools, if needed.
  

Configuration

• 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.
  With emphasis on performing the following tasks:
  
• Estimate the amount of needed space.
  
• Create/Mount empty directories for Database, Active log, ArchiveLog and FailoverLog.
  
• Create/Mount Directories for Active log mirror or enable OS-Mirroring.
  
• Check and set permissions and ownership for Log-Directories to the defined Instance user.
  
• Initialize DB and Log Directories with dsmicfgx-Wizard or "dsmserv format"-command.
  
• Given an installed and initialized TSM server with attached Tape libraries, define tape libraries so that the Tape Libraries are configured in TSM.
  With emphasis on performing the following tasks:
  
• Identify OS devices for attached libraries.
  
• Configure device driver.
  
• Configure native vendor driver.
  
• If native driver not available, configure Tivoli Storage Manager generic driver.
  
• Define libraries in the TSM server.
  
• Check if SANDiscovery is enabled.
  
• Define library drives with "perform libaction" for each library.
  If SAN Discover is unavailable:
  
• Define paths to Libraries.
  
• Define drives for each library.
  
• Define paths to drives.
  
• 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.
  With emphasis on performing the following tasks:
  
• Determine the SLA requirements for nodes for restoring.
  
• Determine which Nodes uses which Types of Storage pools.
  
• Create directories for disk and file pools on OS.
  
• Check and set permissions and ownership of directories.
  
• Define needed device classes.
  Define storage pools in TSM according to:
  
• Device Class
  
• deduplication
  
• collocation requirements
  
• Migration Thresholds
  
• Reclamation Thresholds
  
• Number of Scratch-Volumes
  
• Define volumes for disk storage pools.
  
• Given an installed and initialized TSM server and known customer requirements for data protection set up policies so that policies are configured in TSM.
  With emphasis on performing the following tasks:
  
• Identify different requirements to group this in different policy domains.
  
• Define policy domains.
  
• Define policy set.
  
• Identify per group different Retentions and/or different storage requirements and define Management Classes.
  Define Backup and Archive copy groups per Management Class according to:
  
• retentions
  
• storage pool destination
  
• versioning for backup
  
• Define default Management class per policy set.
  
• Validate policy set.
  
• Activate policy set.
  
• 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.
  With emphasis on performing the following tasks:
  
• Identify SLAs that require collocation for restore performance.
  
• Identify Nodes and Files paces which can be grouped in different collocation groups.
  
• Determine collocation groups.
  
• Define collocation groups.
  Define collocation group members according to:
  
• Node names
  
• File spaces
  
• Check policy domains of nodes according to collocation parameters of destination storage pools.
  
• Given an installed and initialized TSM server with defined nodes so that nodes can schedule their operations.
  With emphasis on performing the following tasks:
  
• Identify nodes which can group their operations at one time.
  Define schedules according to:
  
• Policy Domains
  
• Scheduled action
  
• Scheduled start time
  
• Associate nodes to schedules.
  
• Configure and start client schedulers.
  
• 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.
  With emphasis on performing the following tasks:
  
• Identify client-side or server-side method for deduplicating data.
  
• 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.
  
• Set up client-side deduplication.
  
• Add deduplication=yes to the dsm.opt file.
  
• Create or update a policy to use the deduplication storage pool.
  
• Update or register the client node with deduplication=clientorserver
  
• Set up server-side deduplication.
  
• Query option to verify deduprequiresbackup is set to "Yes".
  
• Update or register the client node with deduplication=serveronly.
  
• Schedule or manually run IDENTIFY DUPLICATES command.
  
• 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.
  With emphasis on performing the following tasks:
  
• Identify the different types of volumes in TSM (libvolume, volume, drmedia).
  
• Identify the different states of the tape volumes (scratch, private).
  
• Identify how the the lifecycle of a tape volume is controlled (volhistory).
  
• Prepare a tape volume to be used in TSM.
  
• Make the tape volume available in the tape library for TSM.
  
• Ensure that an automated library is in a consistent state.
  
• Check a storage volume out of an automated library.
  
• Dismount a sequential, removable volume by the volume name.
  
• Label volumes in manual or automated libraries.
  
• Display information about one or more libraries.
  
• Display information about a library volume.
  
• Change the status of a storage volume.
  
• 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.
  With emphasis on performing the following tasks:
  
• Determine need for Bare Metal Restore.
  
• Narrow down bare metal solution between ASR, TBMR, SysBack ,or TSM for VE.
  
• 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.
  With emphasis on performing the following tasks:
  
• Identify Cluster environment configuration and use.
  
• Identify the different types of cluster environments.
  
• Active/Active: Pool cluster resources
  
• Active/Passive: Fault tolerant
  
• Concurrent access
  
• Configure the Backup-Archive client in a cluster environment.
  
• Check the prerequisites before configuring the Backup-Archive client to back up cluster and non-cluster volumes.
  
• Configure a TSM server for Windows in a Microsoft failover cluster environment
  
• Microsoft Failover Cluster environment overview
  
• Windows operating systems Tape failover for nodes in a cluster
  
• Windows operating systems Planning for a clustered environment
  
• Set up Tivoli Storage Manager in a Microsoft Failover Cluster.
  
• Windows operating systems Maintaining the clustered environment
  
• Configure Tivoli® Storage FlashCopy® Manager to operate in clustered environments with SQL Server, or file system workloads.
  
• Tivoli Storage FlashCopy Manager for SQL: Tivoli Storage Manager configuration
  
• Configure an AIX environment for clustering.
  
• Requirements for a PowerHA cluster
  
• PowerHA failover and failback
  
• Install and configure PowerHA SystemMirror for AIX.
  
• Install the TSM server on a production node for PowerHA.
  
• Install the TSM client on a production node for PowerHA.
  
• Verify the configuration of the TSM server for PowerHA.
  
• Set up the standby node for PowerHA.
  
• Define the removable media storage devices to AIX for PowerHA.
  
• Complete the cluster manager and TSM configurations.
  
• Troubleshoot the PowerHA clustered environment.
  
• Configure a Linux clustered environment.
  
• Install Data Protection for SQL Server in a cluster environment.
  

Administration

• 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.
  With emphasis on performing the following tasks:
  
• Define disk device classes for random access storage pools.
  
• Define file device classes for sequential access storage pools.
  
• Define removable media device classes.
  
• 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.
  With emphasis on performing the following tasks:
  
• Define a sequential access primary storage pool.
  
• Update destination random access primary storage pool and specify NEXTSTGPOOL.
  
• Update other sequential access primary storage pool and specify NEXTSTGPOOL.
  
• 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.
  With emphasis on performing the following tasks:
  
• Determine which storage pool protection will be used.
  
• Define or update a sequential access storage pool with pooltype=copy.
  
• Include a maxscratch value.
  
• Ensure copypool size is sufficient to hold primary pool backups.
  
• 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.
  With emphasis on performing the following tasks:
  
• Define or update a sequential access storage pool with pooltype=active.
  
• Include a maxscratch value.
  
• Ensure active data pool size is sufficient to hold active versions of the data in primary pool backups.
  
• Define or update a policy domain for active data.
  
• 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.
  With emphasis on performing the following tasks:
  
• Define an archive copygroup with a specified retention period.
  
• Define a backup copy group with a specified retention period.
  
• Define a backup copy group with a specified number of versions to retain.
  
• Schedule or manually run expire inventory.
  
• 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.
  With emphasis on performing the following tasks:
  
• Specify reclamation parametrs with the define or update storage pool command.
  
• Set the reclamation process number.
  
• Set the reclamation type, threshold or snaplock.
  
• Set the reclamation target storage pool.
  
• Schedule or manually run reclaim stgpool command when the threshold is high.
  
• 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.
  With emphasis on performing the following tasks:
  
• Set the high migration threshold with the define or update storage pool command.
  
• Set the low migration threshold with the define or update storage pool command.
  
• Set the MIGDELAY parameter.
  
• Set the MIGCONTINUE parameter.
  
• 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.
  With emphasis on performing the following tasks:
  
• 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.
  
• Specify the mount limit for associated primary, copy, or active-data storage pools.
  
• 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.
  With emphasis on performing the following tasks:
  
• Identify Server automation.
  
• Automate server operations.
  
• Automate a basic administrative command schedule.
  
• Tailoring schedules
  
• Copying schedules
  
• Deleting schedules
  
• Manage scheduled event records.
  TSM server scripts:
  
• Define a server script.
  
• Manage server scripts.
  
• Run a server script.
  
• Use macros.
  
• Given the required responsibilities of an administrator identify the correct level of authority required so that the administrator can perform the required actions.
  With emphasis on performing the following tasks:
  
• Identify the level of privilege required for an administrator.Review that the admin privileges are correct for what the admin needs to do in Operations Center .
  
• Issue a grant authority command.
  
• 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.
  With emphasis on performing the following tasks:
  
• Determine which Copypool should hold data from which primary storage pool.
  
• Backup of primary Storagepool to Copypool with BACKUP STG:
  
• Schedule
  
• Manually run
  
• Initiate with the Operations Center
  
• Check Actlog against failures.
  
• 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.
  With emphasis on performing the following tasks:
  
• If necessary, check if Storage pool backups are completed.
  
• Determine the device class, which should use for the database backup.
  
• Determine type of backup:
  
• Full
  
• Incremental
  
• Snapshot
  Start the Backup with BACKUP DB:
  
• Schedule
  
• Manually run
  
• Initiate with the Operations Center
  
• Check Actlog against failures.
  
• 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
  With emphasis on performing the following tasks:
  
• Determine method to edit the client options.
  
• Windows: Edit dsm.opt
  
• 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.
  
• Determine which client options are appropriate.
  
• Define option TCPSERVERADDRESS to the TSM server IP address or DSN name.
  
• Define option TCPPORT to the TSM server port.
  
• Define option COMMMETHOD.
  
• Determine which Scheduler-Mode should used:
  
• POLLING (default)
  
• PROMPTED
  Determine the password handling:
  
• PASSWORDACCESS PROMPTED (default)
  
• PASSWORDACCESS GENERATE
  
• Verify other needed options.
  
• Verify that the client is working.
  
• 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 SLA's
  With emphasis on performing the following tasks:
  
• Determine the need of excludes and/or includes for different Objects according the customer SLA.
  
• Determine Objects that need special management classes.
  
• Define include/exclude-Rules in a file.
  
• Define option INCLEXCL in dsm.opt/dsm.sys
  
• 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.
  With emphasis on performing the following tasks:
  
• Determine nodes which can use a client option set.
  
• Determine client options which can set from the server.
  
• Identify the priorities.
  
• Define client option set.
  
• Define client option to the client option set.
  
• Update node to associate Node with client option set.
  
• 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.
  With emphasis on performing the following tasks:
  
• Determine that client option SESSIONINITIATION=SERVERONLY is not set.
  
• Determine which CAD services are need:
  
• Web GUI
  
• Scheduler
  
• On Unix/Linux define Option MANAGEDSERVICES in dsm.sys
  
• On Unix/Linux define Option CLIENTTCPPORT in dsm.sys
  
• On Unix/Linux start the dsmcad deamon
  
• On Windows use the Wizard in Preferences-Menu of the Backup-Archive GUI to configure and start the CAD service.
  
• 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.
  With emphasis on performing the following tasks:
  
• Understand the benefits and usage of backup sets.
  
• Generate backup set on server.
  
• Generate backup set for individual client node.
  
• Generate backup set for node groups.
  
• Generate table of contents.
  
• Restore backup set on client.
  
• 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.
  With emphasis on performing the following tasks:
  
• Define the source and target server.
  
• Enable replication for specific nodes and a specific type of data.
  
• Validate replication configuration.
  
• Set up automatic failover.
  
• 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.
  With emphasis on performing the following tasks:
  
• Review data that can be exported and imported.
  
• Export data directly to another server.
  
• Prepare to export to another server for immediate import.
  
• Monitor the server-to-server export process.
  
• Export and import data using sequential media volumes.
  
• Export tasks.
  
• Import data from sequential media volumes.
  
• Identify Exporting/ importing tasks.
  
• Export/Import administrator information
  
• Export/Import client node information
  
• Export/Import policy information
  
• Export/Import server data
  
• Plan for sequential media used to export data.
  
• 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.
  With emphasis on performing the following tasks:
  
• Determine for what operations server to server communication is needed.
  
• Identify the servers and their parameters required to define and verify server to server communications.
  
• Issue the server to server definitions.
  
• 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
  With emphasis on performing the following tasks:
  
• Manage multiple servers through the Operations Center.
  
• Route commands.
  
• Set up server groups.
  
• Define a server group and members of a server group.
  
• Manage server groups.
  
• Manage group members.
  
• Query server availability.
  
• Keep client files together using collocation:
  
• Identify the effects of collocation on operations.
  
• Identify how the server selects volumes with collocation enabled.
  
• Identify how the server selects volumes with collocation disabled.
  
• Configure collocation on or off .
  
• Configure collocation of copy storage pools and active data pools.
  
• Plan for and enabling collocation.
  
• Identify collocation for a group, single client node or file space level.
  
• 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.
  With emphasis on performing the following tasks:
  
• Backup-Archive client:
  
• Back up group.
  
• Delete group.
  
• Query group.
  
• Restore group.
  
• HSM
  
• File groups
  
• Create a new file group.
  
• Edit a file group.
  
• 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.
  With emphasis on performing the following tasks:
  
• Restore or retrieve files to another workstation using the virtual node name option.
  
• Authorize another user to restore or retrieve files from another node.Restore or retrieve files from another client node.
  
• Given the need to protect NAS devices, determine the correct backup type so that the NAS devices are protected.
  With emphasis on performing the following tasks:
  
• Understand the backup types available for NAS and the SLA.
  
• If using NDMP backup
  
• Determine if going straight to tape or over the network to TSM.
  
• Determine if a TOC is needed.
  
• Set up the management class and domain for the NAS backups.
  
• Register a node with type=nas.
  
• Define a datamover with type = nas.
  
• If backing up a nSeries or netApps appliance:
  
• Consider Snapmirror to tape for an image backup.
  
• Consider Snapdiff for an incremental file level backup.
  
• Given installed TSM server clients are configured, set up archiving so that data is ready to be archived.
  With emphasis on performing the following tasks:
  
• Identify the difference in TSM between archiving and backup server automation.
  
• Identify Archive operations overview.
  
• Implement archive policies.
  
• Configure the backup archive client to select how archived files are managed.
  
• Manage storage usage for archives:
  
• Minimize archive storage use.
  
• Reduce archive storage use for client nodes with many archives.
  
• Prevent archive of directory-level access permissions.
  
• 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.
  With emphasis on performing the following tasks:
  
• Identify appropriate client options.
  
• Determine backup method for Backup-Archive client.
  
• Use incremental (complete).
  
• Use incremental by date.
  
• Use incremental (without journal).
  
• Use always backup (selective).
  
• Use image.
  
• Use logical volume backup.
  
• Determine the backup-archive interface to perform the backup.
  
• Use the command line.
  
• Use the GUI.
  
• Use the Web client.
  
• Schedule or manually run the backup operation
  
• 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.
  With emphasis on performing the following tasks:
  
• Identify appropriate client options.
  
• Determine the Backup-Archive interface to perform the restore operation.
  
• Use the command line.
  
• Use the GUI.
  
• Use the Web client.
  
• Determine classic or no query.
  
• Schedule or manually run the restore operation.
  
• 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.
  With emphasis on performing the following tasks:
  
• Identify appropriate client options.
  
• Determine the backup-archive interface to perform the archive.
  
• Use the command line.
  
• Use the GUI.
  
• Use the Web client.
  
• Create archive description, if not using default.
  
• Schedule or manually run the archive operation.
  
• 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.
  With emphasis on performing the following tasks:
  
• Identify appropriate client options.
  
• Determine the Backup-Archive interface to perform the retrieve operation.
  
• Use the command line.
  
• Use the GUI.
  
• Use the Web client.
  
• Schedule or manually run the retrieve operation.
  
• Given a specific node move its' data to a new storage pool so that it resides in the new storage pool.
  With emphasis on performing the following tasks:
  
• Determine the need for move node data.
  
• Execute a move node data.
  
• 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.
  With emphasis on performing the following tasks:
  
• Determine define and refine the alert triggers.
  
• Determine if alert emails are required and turn them on if needed.
  
• Determine and enable specific administrators to receive alert emails or alert summaries.
  
• Given the need to restore a database execute the needed commands so that the TSM server is restored.
  With emphasis on performing the following tasks:
  
• Obtain the volume history file and device configuration file.
  
• Obtain the database backup volumes.
  
• Recreate the database and recovery log directories if needed.
  
• Run the database restore commands as either a point-in-time or current state.
  
• Run the audit library command to synchronize the library inventories.
  
• Given an administrator with system privileges, manage the database and recovery logs so that the TSM instance performs optimally.
  With emphasis on performing the following tasks:
  
• Monitor database, active log and archive log size using the Operations Center.
  
• If database size uses ca. 80% of space:
  
• Extend Database space.
  
• Extend file systems of database directories.
  
• Load balance the database.
  
• If active log size is small due to excess frequency of backups.
  
• Adjust files system size of active log.
  
• Adjust ACTIVELOGSIZE in dsmserv.opt.
  
• Restart the TSM instance.
  
• If Size of archive log directory does not fit:
  
• Adjust file system size of archive log directory.
  
• Adjust frequency of TSM database backups of type full.
  
• Define retention of database backups.
  
• Set DRMDBBACKUPEXPIREDAYS.
  
• Schedule or manually run DELETE VOLHISTORY for used types of database backups.
  
• Determine DB2 Reorganization issues, needed for TSM
  
• Define a reorganization window in a low usage time with the server options REORGBEGINTIME and REORGDURATION.
  
• Define ALLOWREORGTABLE=yes.
  
• Define ALLOWREORGINDEX=yes for TSM-Servers which uses deduplication.
  
• 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.
  With emphasis on performing the following tasks:
  
• Define device class for new hardware.
  
• Define storage pools for new device class.
  
• Include storage pools in existing Hirarchy and policy domains.
  
• If necessary MOVE DATA from one storage pool to another.
  

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 and storage pools, review the server options file, and run the QUERY SYSTEM command so that the TSM server performance problems are identified.
  With emphasis on performing the following tasks:
  
• Review error log:
  
• Check log files.
  
• Review with the Operations Center.
  
• Review alerts with the Operations Center.
  
• Review activity log with the Operations Center.
  
• Query the activity log.
  
• Review with the Operations Center.
  
• Query the database and storage pools to ensure they are online.
  
• Review dsmserv.opt settings to see if they have been changed.
  
• Review schedule log.
  
• Run QUERY SYSTEM command to collect consolidated system information.
  
• Contact support about running a trace.
  
• 
  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
  With emphasis on performing the following tasks:
  
• Review error messages.
  
• Enable cyclic redundancy checking.
  
• Use server ping to check the heartbeat.
  
• 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.
  With emphasis on performing the following tasks:
  
• Use DB2 utilities to monitor the database.
  
• Review error log:
  
• Check log files.
  
• Review with the Operations Center.
  
• Review alerts with the Operations Center
  
• Review activity log with the Operations Center.
  
• Query the activity log.
  
• Review with the Operations Center.
  
• Query the database and recovery logs for available space.
  
• Contact support.
  
• 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.
  With emphasis on performing the following tasks:
  
• Determine if the problem is isolated to a node or group of nodes.
  
• Review error log:
  
• Check log files.
  
• Review with the Operations Center.
  
• Review alerts with the Operations Center.
  
• Review activity log with the Operations Center.
  
• Query the activity log.
  
• Review with the Operations Center.
  
• Check dsmwebcl.log .
  
• Check Schedlog.
  
• Review client options files settings to see if they have been changed.
  
• Run QUERY SYSTEMINFO command to collect consolidated system information.
  
• Contact support about running a trace.