IBM C2010-509

Free Questions in OTE format

About IBM C2010-509 dump

IBM Tivoli Storage Manager Family

• Given the online resources available, identify IBM Tivoli Storage Manager (TSM) components that work together so that there is an overall data protection solution.
  With emphasis on performing the following tasks:
  • Server Program - Provides backup, archive, and space management services to the clients.
  • Administrative Interface - Administrative interfaces include a command-line administrative client and a Web-based interface that is called the Operations Center.
  • Server Database and Recovery log - The TSM server uses a database to track information about server storage, clients, client data, policy, and schedules. The server uses the recovery log as a scratch pad for the database, recording information about client and server actions while the actions are being performed
  • Server Storage - The server can write data to hard disk drives, disk arrays and subsystems, stand-alone tape drives, tape libraries, and other forms of random-access and sequential-access storage. The media that the server uses are grouped into storage pool.
  • Client Nodes - A client node can be a workstation, a personal computer, a file server, or even another TSM server. The client node has TSM client software that is installed and is registered with the server.
  • Backup-Archive client - The Backup-Archive client allows users to maintain backup versions of files, which they can restore if the original files are lost or damaged. Users can also archive files for long-term storage and retrieve the archived files when necessary.
  • network attached storage (NAS) file server (using NDMP) - The server can use the Network Data Management Protocol (NDMP) to back up and restore file systems that are stored on a NAS file server.
  • Application client - Application clients allow users to initiate online backups of data for applications such as database programs.
  • Application Programming Interface (API) - The API can help you to enhance existing applications to use the backup, archive, restore, and retrieve services that TSM provides.
• Given the online resources available, identify TSM data protection products so that there is an overall data protection solution.
  With emphasis on performing the following tasks:
  • Tivoli Storage Manager for Databases - Performs online, consistent, and centralized backups to avoid downtime, protect vital enterprise data infrastructure and minimize operation costs.
  • Support for Oracle, which interfaces with Oracle Recovery Manager (RMAN), to support Oracle backup and restore utilities.
  • Support for Microsoft SQL Server, which enables users to perform online backups of SQL databases to TSM storage.
• Tivoli Storage Manager for Mail-Utilizes, the APIs provided by e-mail application vendors to perform online "hot" backups and improve restores without shutting down the E-mail server.
  
• Support for Lotus Domino, which exploits the "transaction logging" feature of Domino, enabling the capture of just the database changes for logged databases, thus resulting in less-frequent full backups.
  
• Support for Microsoft Exchange, which can produce the different types of backups specified by Microsoft backup APIs: Full Backups, Incremental Backups, Differential Backups, Copy Backups and Database Copy Backups.
  
• Tivoli Storage Flashcopy Manager -Create and manage fast, application-aware backups and restores which leverage advanced snapshot technologies in IBM and NetApp storage systems.
  
• Can be used with or without a TSM server.
  
• Includes "Flashcopy Manager for Windows", "Flashcopy Manager for Unix and Linux" and "Flashcopy Manager for VMware" and Rocket Device Adapter Pack for IBM Tivoli Storage FlashCopy Manager supports hardware snapshots of non-IBM storage on UNIX and Linux platforms.
  
• Tivoli Storage Manager for Virtual Environments - Provides backup and recovery for virtual environments (Vmware).
  
• Include the ability for recover VM's to original and alternate environments.
  
• Eliminate impact of backup by offloading workload to a vStorage Backup server (proxy).
  
• Tivoli Storage Manager for ERP -Provides data protection features specifically designed for SAP environments.
  
• Tivoli Storage Manager Fastback for Workstations provides continuous data protection and Tivoli Storage Manager Fastback for Servers provides point in time snapshots.
  
• Given the online resources available, describe how to license TSM with the two methodologies currently in use so that capacity licensing understood.
  
• With emphasis on performing the following tasks:
  
• Capacity based licensing applies to Unified Recovery Suite.
  
• Based on capacity being managed in primary TSM storage pools.
  
• Does not include copy pools in capacity for licensing.
  
• Use IBM supplied script file for existing users to obtain correct capacity to license.
  
• Deduplication reduces capacity required for licensing.
  
• Processor Value Unit:
  
• Requires all servers being backed up as well as Tivoli Storage Manaer server to be licensed.
  
• Based upon types of processors and number of active cores being managed/managing.
  
• Processors are weighted by type and model.
  
• Use IBM supplied estimation utility.
  
• Given the requirements of the customers environment, describe the functions of the various TSM add-on products so that the potential add-ons are understood.
  
• With emphasis on performing the following tasks:
  
• IBM Tivoli Storage Manager Flash Copy Manager: Provide fast application-aware backups and restores leveraging advanced snapshot technologies in IBM storage systems.
  
• Supports: Microsoft Exchange, Microsoft SQL, DB2, Oracle, Oracle with SAP environments, VMware, VSS Requestor
  
• IBM Tivoli Storage Manager FastBack: Provide continuous data protection and recovery management for Microsoft Windows and Linux servers.
  
• Performs a block level backup instead of file level backups.
  
• Fast recovery time of data and applications
  
• Supports unified recovery strategy.
  
• Hierarchical Storage Management (HSM) for Windows / Tivoli Storage Manager for Space Management for AIX and Linux. Controls disk storage requirements by automatically migrating rarely used files.
  
• Rapid access to archived data
  
• Reduce backup time by focusing on active files.
  
• Migrate Windows files based on file name, creation date, last access and last time modified.
  
• Given online resources, identify the different types of TSM Reporting available so that the methodology and components that TSM uses for reporting are understood.
  
• With emphasis on performing the following tasks:
  
• Daily monitoring tasks: As a TSM administrator (class is not system), monitor operations daily to ensure that the TSM system is functioning properly. Daily monitoring tasks focus on examining server processes, server database, storage pools, and scheduled operations.
  
• Basic monitoring methods: query and select commands
  
• Operations can be monitored by using a variety of methods, such as using queries or selects to display information about settings and status, gain insight into database operations, or display messages in the activity log.
  
• Monitor TSM accounting records: show the server resources that are used during a session. This information allows resources that are used by a client node session to be tracked.
  
• Monitor using a GUI done through Operations Center.
  
• Log TSM events to receivers: The server and client messages provide a record of TSM activity that can be used to monitor the server. Server messages can be logged and most client messages as events to one or more repositories called receivers.
  
• Report and monitor with Tivoli Monitoring for TSM is available with V6.4: monitors TSM servers. The Cognos reports can be used in Tivoli Common Reporting to generate reports for TSM servers. Tivoli Common Reporting is a component in the Administration Center.
  

IBM Tivoli Storage Manager Server Architecture Concepts

• Given the use of IBM Redbooks, identify IBM Tivoli Storage Manager (TSM) daily housekeeping and maintenance tasks so that knowledge of how/when TSM processing takes place is obtained.
  With emphasis on performing the following tasks:
  
• The daily schedule has a period where clients perform their backups.
  
• Once the clients are finished, the server performs housekeeping.
  
• During the migration process inside the primary storage pool, the data will be copied simultaneously to the copy pools for off-site storage.
  
• To guarantee that all the data is copied successfully, an asynchronous copy process will take place.
  
• The server backs up its database, deletes volume history, saves the device configuration, and creates a list of tapes for vault processing.
  
• The server then migrates the data from disk storage pools to on-site tape pools, reclaims blank space from tape pools.
  
• Finally the expiration process runs.
  
• For a higher level of data protection and availability, some data will be replicated to another server or location
  
• A new client backup begins for the next night.
  
• Given online resources, describe the role TSM policies played in the enforcement of data retention so that customer data is retained per business or legal requirement.
  
• With emphasis on performing the following tasks:
  
• Identify business data retention requirements.
  
• How many backup versions do clients need?
  
• How long do clients need old versions?
  
• TSM policy hierarchy structure is as follows:
  
• policy domain:
  - A policy domain is a way to group TSM clients depending on how to treat their data.
  - A client can belong to only one policy domain.
  
• policy set:
  - A policy set is a group of Management Classes.
  - There can be multiple policy sets within a policy. domain, but only one policy set is active at a time.
  
• management class:
  - Management class is a label attached to a file and describes how the data will be managed by the copy group.
  
• copy group:
  - Copy groups consist of rules used to govern the retention of data. There are two types of copy groups: a backup copy group, which holds the rules for backup data, and an archive copy group which holds the rules for archive data.
  
• Given the online resources available from IBM, describe the different backup methodologies provided in TSM so that the backup methodologies are understood.
  
• With emphasis on performing the following tasks:
  
• Identify backup methodology types.
  
• Full - All files are backed up.
  
• Incremental - Only files that have changed since last backup occurred are backed up.
  
• Selective - Overrides Incremental backup and saves selected files regardless if they have changed or not since the last backup.
  
• Image or Logical volume backup - Backing up a file system, or raw logical volume as a single object from the client machine.
  
• Adaptive subfile backup - This is when only changed portions of files are backed up.
  
• Journal-based backup - This is when the client keeps a running list of files as they change. This list is what is used to determine what files get saved when the backup occurs.
  
• Full VM Backup - Used in TSM for Virtual Environments to provide an entire VM Image snapshot which is a single snapshot that contains all of the VM's disks. All data is backed up at the disk block level.
  
• Incremental VM Backup - Backup only the data that has changed since the last full backup completed. All data is backed up at the disk block level.
  
• NDMP Backup - Used for backing up network attached storage (NAS) devices directly to tape library or to TSM server directly.
  Given book/documentation, describe the TSM backup versioning and data retention so that the TSM data storage rules are defined.
  With emphasis on performing the following tasks:
  
• TSM Backup versioning -multiple versions of the same object are saved - There are multiple parameters to set TSM Backup versioning.
  Versioning options:
  
• VEREXISTS: Number of object copies or versions to keep.
  
• VERDELETE: Number of versions to keep when object has been deleted on the client.
  
• Retention options:
  
• RETEXTRA: Number of days to keep inactive versions.
  
• RETONLY: How many days to keep the last object copy in TSM when the object deleted on the client
  
• Version and Data Retentions are defined in policy domains and management classes.
  
• Given an installed TSM client and the use of IBM Redbooks and the TSM V7.1 infocenter, describe how the TSM client is set up and communicates with the server so that knowledge is obtained what to do, how to handle and when action have to be taken when TSM clients want to communicate to the TSM server.
  
• With emphasis on performing the following tasks:
  
• The setup of the TSM client - TSM server communication.
  
• The node is registered (open/closed, domain, sessions).
  
• Authentication (password rules)
  
• Authorization (client owner/client access)
  
• Setup of client automation (polling/prompted)
  
• Firewall protection(client or server session initiation)
  
• The TSM Web client (HTTP:\\xx:1580, webports)
  
• The data flow of the TSM client - TSM server.
  
• Data flow over the LAN
  
• Data flow over the SAN (LANFREE/Storage agent).
  
• Data Flow from Application through API
  
• Given knowledge of TSM, describe the TSM Disaster Reovery Manager (DRM) feature so that the complete backup of all data and ability to recover it in a timely fashion is understood.
  With emphasis on performing the following tasks:
  
• DRM is a function to move backup media and prepare a plan that can help recover the TSM server and clients if a disaster occurs.
  
• DRM creates one copy of the disaster recovery plan file each time you issue the PREPARE command. Multiple copies of the plan should be created for safekeeping.
  
• The PREPARE command is used to generate the recovery plan file.
  
• The PREPARE command should be executed after all primary and active data storage pools have been backed up, the TSM database has been backed up and the MOVE DRMEDIA command has been executed.
  
• The disaster recovery plan file contains the information required to recover a Tivoli® Storage Manager server to the point in time represented by the last database backup operation that is completed before the plan is created. The plan is organized into stanzas, which can be broken out into multiple files
  
• A recovery plan file can be created and stored locally or on another server.
  
• The recovery plan file is a template that contains information, including commands for recovering the database. It contains the following information:
  
• The TSM server recovery procedure.
  
• A list of required database volumes, copy storage pool and active data pool volumes, Devices to read the volumes and TSM database and recovery log space requirements.
  
• Copies of the TSM server option file, configuration file and volume history file.
  
• Commands for performing database and primary storage pool recovery
  
• Commands for registering licenses
  
• Customized, entity specific instructions
  
• Customized machine and recovery media information
  
• Given online resources available, describe how data replication is implemented so that the advantages of replicating data are understood.
  
• With emphasis on performing the following tasks:
  
• Node replication is the process of incrementally copying or replicating data that belongs to Backup-Archive client nodes from one TSM server to another.
  
• Source and Target servers:
  
• The server from which client node data is replicated is called a source replication server.
  
• The server to which client node data is replicated is called a target replication server.
  
• A server may be both a source replication server for one set of client nodes and a target replication server for a different set of client nodes.
  
• Replicated data:
  - Both active and inactive backup data may be replicated.
  - Archive data may be replicated.
  - TSM for Space Management client data may be replicated.
  - Only data that is not on the target server is replicated.
  
• If both the source and target storage pools are enabled for deduplication, only the extents not stored on the target are replicated.
  
• Automatic failover:
  - The client receives connection information for the target replication server from the source replication server during normal operations.
  - If the client cannot connect to the source replication server, it will log into the target replication server where it is only allowed to recover data.
  
• Default replication configuration replicates all backup, archive and space-managed data in all file spaces in all replication enabled nodes.
  
• Advantages of node based replication:
  - Easier to manage than device based replication.
  - TSM operations are reported in term such as node names and file names making is easier to report.
  - Replicated data may be encrypted during transmission.
  
• Given online resources available, describe deduplication in TSM so that Deduplication is understood.
  
• With emphasis on performing the following tasks:
  
• Data deduplication is a method for eliminating redundant data in order to reduce the storage that is required to retain the data. Only one instance of the data is retained in a deduplicated storage pool. Other instances of the same data are replaced with a pointer to the retained instance.
  
• Deduplication in Tivoli Storage Manger can only be applied to storage pools defined as sequential access disk (FILE). Deduplication does not apply to storage pools defined as TAPE.
  
• Tivoli Storage Manger performs Deduplication at either the client side or the server side.
  In client-side data deduplication, the processing is distributed between the server and the backup-archive client during the backup process. This redu
• ces the amount of data being transmitted from the client to the TSM server.
  
• In server-side data deduplication, processing takes place exclusively on the server after the data is backed up.
  Given knowledge of TSM, describe the TSM Scheduling process so that scheduling a TSM Backup client operation is understood.
  With emphasis on performing the following tasks:
  
• Create the TSM Client Schedule on the server.
  
• Associate client nodes with the schedule.
  
• Start the scheduler on the client.
  
• Display the schedule information.
  
• Check the status of scheduled operations on the TSM server.
  
• Query Event command.
  
• Operations Center dashboard
  
• Given online resources, describe the role of the interface to the TSM server so that the administrator/ operator knows how to manage/monitor correctly the TSM server(s).
  With emphasis on performing the following tasks:
  
• Web interfaces for server administration and for the Backup-Archive client
  
• The Operations Center provides Web and mobile access to status information about the TSM environment. This interface can be used to monitor multiple servers and com-plete some administrative tasks. The interface also provides Web access to the command line.
  
• The Administration Center allows access TSM server functions from any workstation that is using a supported Web browser. The interface also allows Web access to the command line. The Admin center has very limited monitoring.
  
• The command-line interface
  
• Manage servers with the Operations Center.
  
• IBM® Tivoli® Storage Manager Operations Center is a Web-based user interface for monitoring your storage management environment. The Administration Center interface is also available, but the Operations Center is the preferred monitoring interface.You can now do the following additional administrative tasks through the Operations Center:
  - Customize the settings for servers and clients by editing the server and client properties.
  - View or cancel the sessions and processes that are in progress by using the Active Tasks view for servers.
  - View the sessions and processes that succeeded or failed by using the Completed Tasks view for servers.
  - View activity log messages that are related to specific alerts, sessions, and processes. These activity log messages are available on the Alerts page and in the Active Tasks and Completed Tasks views.
  - Manually back up clients, storage pools, and the server database.
  - View the replication server configuration for a client.
  - Register clients, and configure basic backup settings.
  - Suppress risk warnings for specific clients.
  - View the authority level of the administrator ID that is used to log in to the Operations Center.
  
• Hub and spoke servers:The first TSM server that connects to the Operations Center is designated as a hub server. In a multiple-server environment, more servers can connect, called spoke servers. The spoke servers send alerts and status information to the hub server.
  
• The Admin Center : The Administration Center is installed as a component of the Tivoli® Inte-grated Portal. The Administration Center can be used to centrally configure and manage TSM environment. Not available in TSM V7.1 the admin center from 6.3.4 must be used.The Administration Center has wizard for housekeeping, maintenance scripts, deployment scripts, DRM. Al these items are not yet implemented in the operational center.
  

IBM Tivoli Storage Manager Storage and Device Concepts

• Given knowledge of IBM Tivoli Storage Manager (TSM), describe the storage hierarchy in TSM so that the way TSM organizes storage pools is understood.
  
• With emphasis on performing the following tasks:
  
• Disk storage pool - a random access device (referred as hard disk). The disk storage pool can be configured as primary storage pool.
  
• Sequential storage pool -This can be a hard disk device but configured as FILE device class, or a tape or optical devices. The sequential storage pool can be configured as primary or copy storage pool.
  
• Primary storage pools -When client node data is backed up, archived, or migrated, the data are stored in a primary storage pool.
  
• Copy Storage pool - A copy storage pool provides an additional level of protection for client data and is created for the express purpose of backing up a primary storage pool. Copy storage pool volumes are used to provide recoverability of the TSM server environment.
  
• Active Data pool-Provides faster recovery since only active data is in the active data pool.It resides on a sequential device.
  
• Primary pools can be chained together to create a hierarchy.
  
• Migration thresholds - They specify when TSM server starts or stops migrating data from a storage pool to the next storage pool in the TSM storage pool hierarchy.
  
• Deduplication- To reduce the physical amount of storage and to store more data on online disk, deduplication in the sequential storage pool can be used in TSM. It will work in the kind of post processing and work together with client side deduplication a node replication.
  
• Given knowledge of TSM, describe Tivoli Storage pool management so that TSM reclamation and migration processes are understood.
  With emphasis on performing the following tasks:
  
• Data expiration - When the backup/archive data has exceeded its versioning or data retention limits, TSM server will delete (expire) that object, thus free up space on the storage media.
  
• Reclamation -Reclamation makes the fragmented space on a sequential volume usable again by moving unexpired objects from one volume to another volume within the same storage pool, thus make the original volume available for reuse.
  
• Off-site volumes reclamation - TSM cannot physically move the data from one of these volumes to another because they are in an off-site vault, not available in the library. TSM manages reclamation for an off-site copy pool by obtaining the active files from a primary storage pool or from an on-site volume of a copy pool. These files are then written to a new volume in the copy pool, and the TSM database is updated with the new location of the files. The new volume will be moved to the off-site location, and the off-site volume, will be listed as empty and moved back to the on-site scratch pool for reuse.
  
• Migration- Data migration is the process of moving data from one storage pool to another within the storage hierarchy. Usually data is migrated from higher performance (more costly) media to lower performance or less expensive media. This process frees up space on the higher performance (more costly) storage to be reused.
  
• Data in copy storage pools and active data pools cannot be migrated.
  
• Data migrated from a deduplicated storage pool to a non-deduplicated storage pool will be reconstructed to occupy it's normal (non-deduplicated) amount of space
  
• There must be enough space in the pool to receive the data. Volumes must be added to a sequential access pool in order to increase the size of the pool.
  
• Given online resources available explain collocation so that collation is understood.
  
• With emphasis on performing the following tasks:
  
• Collocation is the process of isolating client or group of clients data to their own isolated volumes within a storage pool.
  
• Collocation can be performed for a single node, a group of nodes, a single filespace or a group of filespaces.
  
• The benefits using Collocation is that upon a restore the client(s) data can be retrieved from individual volumes much more quickly.
  
• The collocation option is generally where the client requires a fully optimized recovery time.
  
• Reduces # of volume mounts required for restore, retrieve, or recall of a large number of files from the storage pool
  
• Reduces the amount of time required for these operations
  
• There is a trade-off in performance (reducing volume mounts) and cost (minimizing the number of volumes) since isolating a client(s) data into separate volumes more space/media is used as those pools defined for the collocating client are not used by any other clients.
  

IBM Tivoli Storage Manager Client Concepts

• Given knowledge of IBM Tivoli Storage Manager (TSM), describe the backup and restore functions so that backup and restore functions are understood.
  
• With emphasis on performing the following tasks:
  
• The backup process uses versions of files.
  
• During a backup operation, TSM server determines the number of versions to retain, Version Retention is controlled by policy domains in the TSM server.
  
• During a backup operation, TSM server determines how long to keep the extra file versions. Version expiration is controlled by policy domains in the TSM server.
  
• The Restore function-Copies the active or inactive file back to the workstation from the storage pool.
  
• Given online resources, describe the Archive and Retrieve functions so that the Archive and Retrieve functions are understood.
  
• With emphasis on performing the following tasks:
  
• Archive operations overview:
  
• for long retention of data
  
• a full copy of the data (file & directories(path))
  
• no versioning
  
• the possibility to delete file on original location (deletefiles)
  
• managed by management class and archive copy group
  
• packaged based on description.
  
• When a user requests the archiving of a file or a group of files, the IBM® Tivoli® Storage Manager determine its eligibility.
  
• Checks the files against the user's include-exclude list to see if any management classes are specified:
  
• TSM uses the default management class for files that are not bound to a management class.
  
• If no include-exclude list exists, TSM uses the default management class unless the user specifies another management class.
  
• Checks the management class for each file to be archived.
  
• If the management class does not contain an archive copy group, the file is not archived.
  
• To frequently create archives for the same data, consider using instant archive (backup sets).
  
• The archive command archives a single file, selected files, or all files in a directory and its subdirectories on a server.
  
• To release storage space on your workstation, delete files as you archive them using the deletefiles option.
  
• Retrieve is the copy from the file(s) back to the original or any other workstation whenever the file(s) are needed again.
  
• Given knowledge of TSM, describe the TSM Space management for disks so that the space management for disks is understood.
  
• With emphasis on performing the following tasks:
  
• TSM has two features:TSM for Space Management (UNIX)TSM HSM for Windows (Windows)
  
• Space Management (also known as Hierarchical Storage Management (HSM)) is a data management system that automatically moves data between high-cost storage and low-cost storage pool in TSM. Space management can be used to store the unstructured (not referenced) data on slower devices, and then copy data to faster disk drives only when needed. When a file is migrated the space management leaves a stub file as a reference to the file.
  
• The space management daemon monitors the way files are used and lets policies be automated as to which files can safely be moved (migrated) to slower devices and which files should stay on the hard disks.
  
• The space management manages the migration of individual files, files from parts of file systems, or complete file systems, to remote storage in TSM.
  
• Any migrated files has a stub on the original location, Which means that migrated files can be accessed, opened, and updated by the application.
  
• The Space Management functions:Migrate migrates files from a local file system to storage.Recall returns the files either automatically or selectively.
  
• Given knowledge of TSM and SAN Infrastructure and the basics of LAN-free data movement, explain the principles of LAN-free and LAN-based backup so that the configuration and principles of operation is understood.
  
• With emphasis on performing the following tasks:
  
• Explain the principles of operation for LAN-free data movement.
  
• Tivoli Storage Manager for Storage Area Networks (SAN agent) is an agent that resides on a TSM client which read and write backup and archive data directly to SAN storage
  
• LAN-free data movement decreases the load on the TSM server allowing for a greater number of concurrent client sessions
  
• The SAN storage agent is typically installed on a client system that shares storage resources with the TSM server.
  
• Understand the inter-communication among TSM server, storage agent, and TSM client.
  
• Metadata such as file name and size is sent from the client to the TSM server over the LAN and stored in the TSM server database.
  
• The SAN storage agent communicates with the TSM server through the LAN to coordinate shared SAN device and volume access.
  
• If a failure occurs in the SAN path between the SAN storage agent and the device, the client may be configured to failover and use LAN communications with the TSM server for data transfer.
  
• Given detailed information about data protection strategies described in IBM TSM documentation, explain how NAS Filers can be protected with Network Data Management Protocol (NDMP) and SnapDiff so that network attached storage filer with NDMP and SnapDiff data protection are understood.
  
• With emphasis on performing the following tasks:
  
• Describe NDMP based backup:
  
• NDMP backups are done because, NDMP is the interface provided by the network attached storage filer manufacturers to initiate data protection (or restores). The following backup methods are available:
  - File-level backup and restore for NDMP operations - it is useful to specify that the TSM server will collect and store file-level information in a table of contents (TOC).
  - Directory-level backup and restore - a backup at a directory level will reduce backup and restore times By defining virtual file spaces, a file system backup can be partitioned among several NDMP backup operations and multiple tape drives.
  - NAS file system image backups can be either full or differential image backups. Using the SnapDiff option with the incremental command streamlines the incremental backup process. The command runs an incremental backup of the files that were reported as changed by NetApp instead of scanning all of the volume for changed files.
  
• NDMP backup operations by using Celerra file server integrated checkpoints makes backup faster.
  
• If restoring a differential image, TSM automatically restores the full backup image first, followed by the differential image.
  
• Data formats for NDMP backup operations:
  
• The NDMP format is not the same as the data format used for traditional TSM backups. The NETAPPDUMP format is used if the network attached storage file server is a NetApp or an IBM® System Storage® N Series device. The CELERRADUMP is used if the NAS file server is an EMC Celerra device. For all other NAS devices, the stgpool format is NDMPDUMP.
  
• Back up and restore by using NetApp SnapMirror to Tape feature.
  
• Large NetApp file systems can be backed up by using the NetApp SnapMirror to Tape feature. Using a block-level copy of data for backup, the SnapMirror to Tape method is faster than a traditional NDMP full backup and can be used when NDMP full backups are impractical.
  
• Use the NDMP SnapMirror to Tape feature as a disaster recovery option for copying large NetAppfile systems to auxiliary storage.
  
• Using a parameter option on the BACKUP NODE and RESTORE NODE commands, file systems can be backed up by using SnapMirror to Tape. Consider the following guidelines before you use it as a backup method:
  - The SnapMirror to Tape backup or restore operation can only be initiated from the TSM admin CLI or using a TSM admin schedule.
  -There is no differential backups of SnapMirror images possible.
  -There is no directory-level backup available using SnapMirror to Tape
  -There is no NDMP file-level restore operation available from SnapMirror to Tape images.
  
• Given the online resources available, describe how to use administrative schedules so that administrative scheduling is understood.
  
• With emphasis on performing the following tasks:
  
• An administrative schedule is a directive to trigger an action on a Tivoli Storage Manager server.
  
• It is different from a client schedule in that it specifies an action to be performed on the Tivoli Storage Manager server.
  
• It consists of a server command and extra parameters describing when the action should happen.
  

IBM Tivoli Storage Manager Client Implementation

• Given a correctly set up system and network which meet the requirements, and access to the IBM Tivoli Storage Manager (TSM) code, determine whether the installation is new and follow the documented installation steps for any supported operating system so that the TSM client is installed on the system.
  
• With emphasis on performing the following tasks:
  
• Determine the OS platform.
  
• Determine if this is a new installation or an upgrade.
  
• Read appropriate documentation and Support Flashes on the IBM Tivoli support Web site.
  
• Identify location of most current TSM code, patches and fixes.
  
• Select the necessary product parts and features.
  
• Install the TSM client code to any supported operating system from the appropriate media /CD or electronic image.
  
• Install the language packs from the appropriate media (CD or electronic image).
  
• Verify the code installed correctly.
  
• Given the need to register a client to TSM, log on to TSM as admin, determine policy information based on SLA, run commands to register node, schedule the client for automatic backup so that a user can perform backups and restore of the user's data.
  
• With emphasis on performing the following tasks:
  
• Open the administrative CLI on the TSM server.
  
• At the CLI prompt; log in to TSM with an administrator account
  
• Perform commands to register the client node on the TSM server.
  
• Associate the client node with a client schedule on the TSM server.
  
• Open the TSM B/A client CLI and authenticate the client node with TSM server.
  
• Verify the client scheduler service is started on the client node and has successfully communicated with the TSM server.
  
• Given the need to perform a client backup manually as opposed to automated scheduling, log on to the Backup-Archive GUI client, select the backup icon, determine files/folders identified requiring back up so that the files identified as needing a manual back up have been copied to the TSM server.
  
• With emphasis on performing the following tasks:
  
• Open the Backup-Archive GUI client.
  
• Prepare for backup by selecting the backup icon.
  
• Identify and select files identified requiring backup.
  
• Perform backup of selected files.
  
• Verify files have been successfully backed up.
  
• Given the need to perform a client restore: log on to the Backup-Archive GUI client, select the restore icon, select versioning criteria, identify files/folders that need to be restored so that files saved on the TSM server have been copied back to the local system.
  
• With emphasis on performing the following tasks:
  
• Open the Backup-Archive GUI client..
  
• Prepare for restore by selecting the restore icon
  
• Select versioning options.
  
• Identify and select the files that are required to be restored.
  
• Perform restore of the selected files.
  
• Given online resources, use the cross client restore so that the recovery of the TSM client files can be achieved on different hardware (server).
  
• With emphasis on performing the following tasks:
  
• If the data to be restored is owned by the user:To restore or retrieve files to another workstation, use the virtualnodename option to specify the node name of the workstation from which the files were backed up. Then restore or retrieve files as if working from the original workstation. If the files are not restored or retrieved to the same directory name on the alternate workstation, enter a different destination.
  
• If the data to be restored is not owned by the user:After users grant appropriate access to their files on the server, restore or retrieve those files to a local system.Display file spaces for another user on the server, restore the backup versions of files for another user, or retrieve the archive copies for another user to a local file system using the GUI Access Another Node. Or If using commands, use the fromnode option to indicate the node.
  
• Important: The Tivoli® Storage Manager client can use file space information when restoring files. The file space information can contain the name of the computer from which the files were backed up. If restoring files from another TSM client node and a destination for the restored files is not specified, the client uses the file space information to restore the files.
  
• Given the need to verify a scheduled client backup completed, log on to TSM, query the events to determine the status of the backup, determine course of action based on results so that the status of the backup has been identified.
  
• With emphasis on performing the following tasks:
  
• Open the administrative CLI.
  
• At the CLI prompt; log in to TSM.
  
• Perform query to determine the status of the backup.
  
• Determine next steps based on the output. ie failure, success, missed.
  
• Query the TSM activity log to gather further information if necessary.
  
• Recommend course of action based on findings.
  
• Given a properly installed and configured TSM client environment and an error has occurred, review the various logs, so that the TSM client issue has been identified.
  
• With emphasis on performing the following tasks:
  
• Observe client backup failure in Operation Center.
  
• Review the Tivoli Storage Manager client activities in the activity log.
  
• Check the schedule log and webcl log for additional messages.
  
• Check the client error log for error messages.
  
• Search for Error conditions on the operating system level.
  
• Search for assistance at IBM support sites.
  
• Given online resources, identify how to determine the at-risk status of a TSM client so that the appropriate actions can be taken.
  With emphasis on performing the following tasks:
  
• The Overview page of the Operations Center shows the following information of the TSM clients.A client is considered to be at risk if a problem occurs during its most recent scheduled backup, or during a backup that starts within a specified time interval. The term backup also includes archive operations for Tivoli® Storage Manager for ERP clients.Use the information that is shown in the TSM clients section to check for failed or missed backups and to determine whether backup schedules are running as expected.
  
• The Tivoli® Storage Manager Operations Center Version 7.1 helps to manage the storage environment. The following at-risk management function in the Operations Center is available:
  
• Suppress risk warnings for specific clients.SET STATUSATRISKINTERVAL - Specifies whether to enable client at-risk activity interval evaluation.SET NODEATRISKINTERVAL - Specifies at-risk mode for an individual node.SET VMATRISKINTERVAL - Specifies the at-risk mode for an individual VM filespace.TYPE (Required) -Specifies which at-risk evaluation mode the status monitor should use when evaluating the at-risk classification for the specified nodes VM filespace. Specify one of the following values: DEFAULT / BYPASSED / CUSTOM CUSTOM setting requires an Interval setting. Specifies the amount of time, in hours, between client backup activity before the status monitor considers the client at-risk. SET STATUSSKIPASFAILURE - Specifies whether to use client at-risk skipped files as failure evaluation; Specifies whether to enable the check for skipped files during the last backup. This check signifies that the client is at-risk if any files were skipped. Client data that is skipped or not backed up properly is considered at risk.