TSM 6.3 Server - Client Enhancements

Advanced Technical Skills (ATS) North America
Tivoli Storage Manager Client and Server Enhancements for TSM V6.3
IBM Advanced Technical Skills
2012 IBM Corporation
TSM Advanced Technical Support Team

Dave Canan
ddcanan@us.ibm.com
Dave Daun
djdaun@us.ibm.com
Tom Hepner
hep@us.ibm.com
Eric Stouffer
ecs@us.ibm.com
Topics
TSM For ERP Support For RMAN Incremental Backups AES Encryption Processor Value Unit (PVU) Estimate Linux Journal Based Backup (JBB) Linux Path Name Improvements Server Database Backup Improvements Automatic Client Deployment Features VTL Awareness HSM Improvements Miscellaneous Client Functions
TSM For ERP Support For RMAN Incremental Backups
Architectural Overview
Oracle
API
database backup/restore log archive/retrieve
TSM for ERP

integration performance transparency API
Tivoli Storage Manager

automation scalability enterprise-wide
DB Server
TSM Server
TSM for ERP daemon
TSM for ERP Admin. Assistant
DB
Oracle backup process
TSM for ERP shared library
TCP/IP
Integrated FCM & Oracles RMAN Incremental Backup

Database Server (production)
Local Area Network

Database
FlashCopy Manager
FlashCopy / Snapshot Backup FlashCopy Restore FlashCopy Cloning
FCM
Server (backup)
FCM
TSM for ERP
TSM for ERP

Log archive/retrieve, DB restore (PS) Offloaded tape backup to TSM (BS)
TSM for ERP
Storage Area Network

TSM
In previous versions FCM invoked the SAP BRBACKUP command which only supports Full backups. During the snapshot offload, V6.3 ERP Invokes RMANs INCREMENTAL BACKUP
DS8k
Source Volumes Target Volumes TSM Server 2
Server 1
AES Encryption
AES Encryption for authentication protocol

Replacing older DES algorithm with AES algorithm
56bit encryption vs 128bit encryption Specialized devices were capable of breaking DES 56, but AES 128 is orders of magnitude stronger
The following components updated:

Client, client API, Server, Storage Agent, Admin Center and Web client GUI
Local password stores still uses DES56 Passwords between the Java GUI interface and dsmagent are transferred in the clear (web browser to the PID) Open node registration initial password is sent in the clear All components must be 6.3 or authentication will use DES56
Mutual Authentication Process

1. Client creates session key and client token from random numbers 2. Client reads password from disk file, decrypts it 3. Client encrypts session key and client token using password, sends them to server 4. Server decrypts session key and client token using password stored in its database 5. Server generates server token from random number 6. Server encrypts client token and server token using session key, sends them to client 7. Client decrypts both tokens using session key, compares this client token with original token 8. Client encrypts server token using session key, sends it to server 9. Server decrypts server token using session key, compares to original token These steps have been upgraded from DES 56 to AES 128 Encryption
9
Session Key
Whenever a Session key is used, AES 128 is employed A Session Key is used for:
Used to encrypt all admin communications Used when BA client updates password
No other client to server communications is encrypted with Session Key
10 10
New Diagnostics
Hidden parameter available for the server: ALLOWAES ON | OFF | AESONLY The default is on No query command exists to view the setting currently Use this parameter only for testing purposes Down-level client connection attempts (DES 56) would reveal an error message as follows:
ANR0330W: Session session number for node node name (node platformor type) refused - invalid authentication protocol requested.
11 11
Processor Value Unit (PVU) Estimate
12
Agenda
PVU Definition PVU Estimating Overview Value of this New Function Component Descriptions Commands and Output Exporting Data to a Spreadsheet
13
The Processor Value Unit (PVU) License Model

Based on the number, type and model of all server class
CPUs in a TSM environment
Cost is indexed based on the computing power of each

physical machine in the system
A primary goal with PVU licensing is to align an

applications cost to its capability to do work
Only valid for TSM 6.3 (and above) clients
14
PVU Classifications
Client Backup/Archive/API clients that run on:
MS Win7, MS WinXP Professional, and Apple systems
Server Backup/Archive/API clients that run on:

All systems other than MS Win7, MS WinXP Professional, and Apple systems
Other Retired, test and single user
15
Client vs Server Device Role Override

PVUs are not assigned to client-class devices, only to server-class
devices.
Client-class devices are, in cases, single-user devices. This

distinction is difficult to determine programmatically.
On a NODE definition, the ROLEOVERRIDE parameter allows the

TSM administrator to override PVUESTIMATE assumptions.
ROLEOVERRIDE arguments are CLIENT, SERVER, OTHER, USEREPORTED OTHER will allow the administrator to specify retired machines, test machines etc. that should be ignored USEREPORTED allows you to reset the field
16
Simple Example: TSM for MAIL on Server Device Node X

TSM for Mail client running on Windows 2008 backing up a
Notes Domino server to a TSM EE server
Windows 2008 is running on an Intel Xeon processor model

5500 quad core and reports 2 processors
Per the IBM PVU table, an Intel Xeon model 5500 quad core is
worth 70 pvu
TSM for Mail uses the TSM API and thus requires 1 lan license
plus 1 TDP license
1 TSM EE lan license (for the api) * 70 * 2 = 140 1 TSM for MAIL license Total PVUs * 70 * 2 = 140 280
17
New Command: QUERY PVUESTIMATE
18
PVU Estimation Functions Advantages

TSM clients already communicate and store data to a
centralized database (TSM server)
Collects the CPU description of the client machines and

stores it in the centralized database
Quickly provides a license estimate of the entire TSM

environment
Creates a simple PVU report to plan for future deployment
19
PVU Counting - Limitations

Meant for estimation only Does not provide complete ILMT (IBM License Metric Tool)
function
Does not address Sub-capacity (virtualization: VMware,

wpar, lpar, etc.)
Can not be used to determine license compliance TSM 6.3 clients only Tivoli Monitoring for Tivoli Storage Manager V6.3
Expands upon PVU features in TSM base product e.g. graphical reports
20
IBM Common Inventory Technology (CIT)

Functionally a subset of ILMT Small footprint, transparent to TSM backup/archive client users Used in lots of IBM products today Scans computer for hardware and software components The TSM clients will install it and use it to collect CPU descriptions Scan takes time so will not be run every time the TSM client is
invoked
TSM Storage Agent can also install and use it for this purpose
21
IBM PVU Table

Table that assigns PVU value to each CPU The table is available at
ftp://ftp.software.ibm.com/software/tivoli_support/misc/CandO/PVUTable/
Resides in TSM server installation directory. The TSM server parses and loads data into TSMDB1
PVUESTIMATE_DETAILS (triggered by Query PVUESTIMATE).
The latest PVU table is supplied with the most current TSM release
22
Update NODE ROLEOVERRIDE= command
23
QUERY PVUESTIMATE f=d
24
Export to Spreadsheet
Method 1:
dsmadmc comma select * from pvuestimate_details > pvudata20100702.csv Import comma separated variables format file into spreadsheet.
Method 2:
Run select * from pvuestimate_details in TSM Admin Center and then cut and paste results directly from browser into Excel spreadsheet.
25
Reference Links
Processor Value Unit [PVU] licensing for Distributed Software:
http://www-01.ibm.com/software/lotus/passportadvantage/pvu_licensing_for_customers.html
Sub-capacity licensing FAQs:

http://www-01.ibm.com/software/lotus/passportadvantage/subcapfaqov.html#1
Tivoli product license information:

http://www-947.ibm.com/support/entry/portal/Overview/Software/Tivoli/IBM_License_Metric_Tool
26
Journal Based Backup (JBB) for Linux
27 27
What is JBB?
Change Journal (database) is used
Journal of file system changes is maintained on the local client as the changes occur in real time TSM Journal Daemon process monitors changes and manages the journal
When to use JBB?

Incremental backups will query the local journal service and send only changed files / objects to the TSM server when an incremental backup is initiated Ideal for servers with low to moderate number of file system changes
JBB for Linux has 4 components required

Kernel module (filepath driver) Journal Daemon (process that will run continuously) Journal Database (resides on the local file system) TSM Client For more detailed information on TSM Journaling: http://www-01.ibm.com/support/docview.wss?uid=swg21155524
28 28
JBB for Linux

Journal Based Backup
Supports any local filesystem Except GPFS
Similar to the existing JBB functionality on AIX but uses a different daemon startup script and interfaces with the OS kernel differently Architectures
i/p Series Linux x Series Linux z Series Linux
Distributions
RHEL 5.5, 6.0 and SLES 10sp3, 11sp1 filepath kernel extension can be shipped as source code
Can be recompiled for your kernel
29 29
JBB for Linux
Default install path is /opt/filepath. The script has two parameters, start and stop.
Default installation run levels are 3, 4, and 5.
The /var/log/messages (or dmesg) output may be monitored to verify the Jbb driver loads successfully:
30 30
JBB for Linux Compatibility

Attempts to install the filepath driver on unsupported Linux kernel will result in the following type of error:
Preparing... 1:TIVsm-filepath ########################################### [100%] ########################################### [100%]
insmod: error inserting 'filepath.ko': -1 Invalid module format ERROR: Failed to start filepath with error 1
If none of the packages matches your Linux version, you must compile Filepath from source code. The Linux Filepath kernel module is licensed pursuant to the terms of the GNU General Public License ("GPL"). To request the Linux Filepath source code, send an email to tsmosreq@us.ibm.com.
31 31
Linux Path Name Enhancements
32 32
Linux Path Name Enhancements

Linux BA client now supports longer pathnames
Previous limit was 1024 bytes New limit is 4096 bytes Once backed up using the 6.3+ TSM client, it is not possible to restore a long path object using a previous version of the client
33 33
TSM Database Backup Enhancements
34
TSM Database Backup with Multiple Streams

TSM Server TSM Database
DB2 Backup/restore streams
Parallel streams for backup/restore processing give improved throughput Reduced time for database backup/restore Increased scalability of TSM server without impacting database backup On Restore: TSM will attempt to match the number of streams that were used on backup
35
Server Command Changes SET DBRECOVERY

New parameter: NUMStreams
Default 1, max value of 4 Used for all types of DB backups On Backup DB, this is examined along with DEVCLASS MOUNTLIMIT value
If NUMSTREAMS < MOUNTLIMIT, then numstreams used if available and online If NUMSTREAMS > MOUNTLIMIT, then value of mountlimit used if available and online
Remember that DB Backup is highest priority of preemption list.
36
Server Command Changes BACKUP DB

New parameter: NUMSTREAMS
This is an optional parameter. The default value is 1 stream will be used. The maximum allowable value for this is 4. If specified, DB BACKUP will attempt to use the number of streams requested. If this value is greater then the actual number of drives available in the device class, the backup will be limited to the number of drives. Available drives indicates the number of drives defined to the device class (MOUNTLIMIT) or the number of online drives for this device class.
37
Server Command Changes BACKUP DB

New parameter: NUMStreams
This is an optional parameter. The default value is 1 stream will be used. The maximum allowable value for this is 4. If specified, DB BACKUP will attempt to use the number of streams requested. If this value is greater then the actual number of drives available in the device class, this will be limited to the number of drives. Available drives indicates the number of drives defined to the device class (MOUNTLIMIT) or the number of online drives for this device class.
38
Server Command Output Changes Q DB

Q DB F=D ANR2017I Administrator SERVER_CONSOLE issued command: QUERY DB F=D Database Name: TSMDB1 Total Size of File System (MB): 2,048,000 Space Used by Database(MB): 12,576 Free Space Available (MB): 1,574,486 Total Pages: 983,044 Usable Pages: 982,908 Used Pages: 977,736 Free Pages: 5,172 Buffer Pool Hit Ratio: 98.4 Total Buffer Requests: 928,387 Sort Overflows: 0 Lock Escalation: 0 Package Cache Hit Ratio: 89.2 Last Database Reorganization: 06/09/10 11:30:50 Full Device Class Name: OUTFILE Number of Backup Streams: 4 Incrementals Since Last Full: 0 Last Complete Backup Date/Time: 01/21/10 10:37:59 <--- NEW for 6.3
39
Server Command Output Changes Q Volhist

Date/Time: 01/21/10 10:37:59 Volume Type: BACKUPFULL Backup Series: 7 Backup Operation: 0 Volume Seq: 25 Device Class: OUTFILE Volume Name: /lspace/tsmsrv1/fspace/64095693.DBV Volume Location: Command: Database Backup ID High: 0 Database Backup ID LOW: 21,968,899 Database Backup Home Position: 0 Database Backup HLA: /NODE0000/ Database Backup LLA: FULL_BACKUP.20100121103759.1 Database Backup Total Data Bytes (MB) : 12,494.88 Database Backup total Log Bytes (MB) : 220.11 Database Backup Block Num High: -1 Database Backup Block Num Low: -1 Database Backup Stream Id: 1 <- NEW for 6.3 <- NEW for 6.3 Database Backup Volume Sequence for Stream: 2
40
Automatic Client Deployment
41 41
The Autodeployment Process
To learn more: http://www-01.ibm.com/software/sysmgmt/products/support/supp_tech_exch.html

Click Previous Webcasts tab, search for Automatic Client Deployment (use quotes) 42 42
Automatic Client Deployment 6.3 Changes

Customers with a large number of TSM clients need the ability to easily manage the client distribution and updating of client code TSM 6.2 supports Windows only client maintenance distribution The goal of the TSM 6.3 design is to enable the Backup-Archive client deployment for non-Windows platforms The new design also enables automatic upgrade to latest release of 5.5.*.*, 6.1.*.*, 6.2.*.* or higher Previously, only an upgrade to the latest 6.2 release was supported
43 43
Auto Deployment Capabilities

Using the TSM Administration Center: Automatically discover client maintenance levels available on the FTP site Automatically retrieve packages required by client maintenance levels, store packages on the TSM server and manage the packages (view, specify retention) Schedule distribution of maintenance levels to specific clients or groups of clients Review the client distribution status
44 44
Capabilities not covered in TSM 6.3

Distribution of other TSM components (e.g., Storage Agent, Data Protection, HSM, etc) Client distribution of maintenance for downgrade/rollback scenarios (e.g., from 6.2.1.1 to 6.2.1.0) Client distribution of the initial installation. The ability to push update to clients that dont have the scheduler service running The current design does not support cluster node deployment Ability to alter which installation components installed
45 45
Upgrade Paths
The key difference is that for Windows, automatic upgrade of 5.4 clients is supported. For non-Windows, only 5.5 and above may be automatically upgraded using the auto deployment functionality.
46 46
Supported Platforms
47 47
Prerequisites
48 48
Virtual Tape Library (VTL) Awareness
49
The Problem With Virtual Tape Libraries (VTLs)
Multiple virtual drives offers configuration flexibility but can lead to many more total drives configured that in physical configurations
This causes drive allocation overhead to become a performance consideration
1. 2. 3.
Allocating a tape volume and a tape drive has several parts

Device type determination Selecting a mount point Mounting a volume on the selected drive
Step 2 requires:
Each drive inspected to determine its read/write capabilities and device type compatibility with the mount point request may be repeated several times during the entire process Validate each drive is online Validate each drive has a valid online path for this mount request
Results in significant delays in drive selection

Previously - Recommend library with fewer than 80 drives Interim fixes have raised this recommendation to 120
See Technote: http://www-01.ibm.com/support/docview.wss?uid=swg21425849
50
Changes for TSM V6.3

Create new LIBTYPE of VTL
Same as LIBTYPE SCSI But with new function
Internal processing changes

Bypass mixed media analysis
Reasonable to assume VTLs do not mix media
Bypass some drive analysis

Expect all VTL drives have paths to all servers
If either of these characteristics are not true, the overall performance can degrade to the same levels as the SCSI library type; especially during times of high stress when most drives are in use concurrently.
51
Changes in definitions
DEFine LIBRary lib_name LIBType=VTL
Must be a library which would otherwise be LIBT=SCSI RELABELSCRATCH defaults to YES for LIBT=VTL Other parameters are same as SCSI libraries
UPDate LIBRary lib_name LIBType=VTL or SCSI

New update command Can switch between VTL and SCSI library types
Define paths for all servers to all drives

This is already best practice for libraries Use device class MOUNTLIMIT setting to limit allocation by individual server sharing this library
52
New PERFORM LIBACTION command

PERForm LIBACTion library_name
ACTion=DEFine | DELete SOURCe=source_name DEVICE=device_name PREFIX=prefix
Applies to libtype=SCSI and VTL Defines:

Path to library All drives found in the library Paths to drives found in the library
Non-local drives will be assigned UNDISCOVERED paths Requires SANDISCOVERY

53
Hierarchical Storage Management Enhancements
54
HSM Enhancements
HSM for Windows - Stub moving tool HSM for Unix/Linux migrate/recall log HSM for Unix/Linux Tape optimized recall HSM for Unix/Linux - Multiple Server Support
55
HSM for Windows Moving Migrated Data Without Recalling

Requirement No 1: Ability to move HSM for Windows stubs across volume boundaries without the need to recall them. Addressed with the stub moving tools (dsmmove / hsmtasks)
Requirement No 2: Ability to change volume drive letters, computer name or to put a disk into another computer Addressed with a new HW mapping mechanism
Note: Host name and drive letter are important for HSM for Windows. If host name or drive letter of a stub is changed, access to data may be lost.
56
Moving Stub Files to a Different Location

User or project is moving from one site to another (distant) site. Files should be transferred without recall to disk. Old file server (including HSM) will continue to work.
Site A
File content on TSM
Site B
File Server A
Stub files in file system
File Server B
57
Moving Stub Files to a Different Location

User or project is moving from one site to another (distant) site. Files should be transferred without recall to disk. Old file server (including HSM) will continue to work. Steps/Tools involved:
a - move stub files to new file server (dsmmove command) b - move content to new TSM server (hsmtasks service)
Site A File content on TSM Site B
b - hsmtasks a - dsmmove
File Server A
Stub files in file system
File Server B
58
Renaming or Moving an HSM File Server Volume

Goal: attach disk storage to new file server
SERVER1 (Old)
SERVER2 (New)
A HW volume mapping can be configured in the HSM for Windows GUI to map the new drive name (like \\HSMSERV1\F$) back to the old name (like \\HSMSERV2\F$). Other examples: change the computer name or volume drive letter or add the existing server to a cluster system
59
Renaming or Moving an HSM File Server Volume

Goal: attach disk storage to new file server
SERVER1 (Old)
SERVER2 (New)
A HW volume mapping can be configured in the HSM for Windows GUI to map the new drive name (like \\HSMSERV1\F$) back to the old name (like \\HSMSERV2\F$). Other examples: change the computer name or volume drive letter or add the existing server to a cluster system
60
Logging of HSM Migrate and Recall Operations

All TSM for Space Management platforms (Unix and Linux) Purpose is to monitor normal operations
Error conditions logged in appropriate error logs
Same structure as error logs today

For instance: format and pruning
New options to configure the HSM log function:

HSMLOGMAX HSMLOGEVENTFLAGS HSMLOGRETENTION HSMLOGNAME
SONAS specific options:

-logname=filespec on commandline File system configuration changes will be logged 61
Controlling the Logging of Events

SYSTEM
start/stop fail over/back task execution
FS (filesystem)
add, remove, update threshold migration, demand migration, reconciliation scan, quota, statistics
FILE
premigration, migration recall, partial recall, stream recall stub restore, orphaned
Default is no events are tracked

Use HSMLOGEVENTFLAGS option to enable logging
62
HSM for Unix/Linux Tape Optimized Recall

Objective is provide optimized recall processing of a list of files
Previously files in a list were recalled independently
Recall tool will sort a list of files by tape volume and location
Generates a collection of sorted file lists One output list per tape volume, plus one for non-tape
dsmrecall [-PREView] -FILEList=<file list name> <fsname>

-FILEList= fsname -PREView User provided list of fully qualified filenames filesystem where files reside Generate lists and collection but does not start the recall process
New option: HSMMAXREcalltapedrives

63
Input FILELIST Requirements

1. 2. 3. 4. 5.
Each entry must be a fully qualified path to a file or a relative path Each entry must be on a new line No entry contains wild card characters Each entry results in the processing of only one file object The file name can be enclosed in quotes if the file name contains any spaces
files are skipped with a warning
6. The HSM client ignores any entry that is not valid 1. No directories are included in the file list 2. Each entry in the list must be from the same file system which is
specified with the dsmrecall command
Any files from other file systems will be skipped and written to an
unprocessed list stored in the .SpaceMan/tapeOptimizedRecall/ directory with the name filelist.unprocessed.<fsname>
64
FILELIST Processing
1. 2. 3. 4.
Recall tool reads input filelist Queries TSM server retrieving: Migration Status Volume ID and location Sorts by volume ID and location Generates ordered filelists for each volume ID
65
Collection Processing
d s m r e c a ll
F ile L is t
re a d s F ile L is t . o rd e re d . T a p e 1 re a d s F ile L is t . o rd e re d . C o lle c t io n
w o rk e r1
R e c a ll Tape1
w o rk e r2
R e c a ll Tape2 F ile L is t . o rd e re d . T a p e 2
T S M S e rv e r
1. 2. 3.
Recall tool reads input collection file Starts worker thread for each sorted filelist Up to maximum option Plus one thread for the non-tape filelist Worker thread invokes file recall for file in the sorted filelist
66
Notes Regarding Tape Optimized Recall

Transparent recall unchanged Transparent recall has no priority
Recall is queued with other requests
Maximum concurrent recalls is minimum of:

Number of sorted lists HSMMAXREcalltapedrives setting Plus 1 if there is a list for non-tape
Can use -PREVIEW option to manipulate recalls

resequence collection list to modify order of tape usage
67
HSM for Unix/Linux - Multiple Server Support

The objective of this feature is to
enhance the TSM HSM client to be able to handle multiple TSM Server instances for each single file system.
With this new feature the HSM client

GPFS
can scale with the number of TSM servers used for migration and recall operations.
Migration / Recall / Reconciliation
Useful for very large file systems to

enhance scalability and performance of HSM operations.
The feature is available for GPFS

environments only on Linux x86 and AIX. GPFS Version 3.4 and above.
TSM server 1
TSM server 2
TSM server 3
68
Changes to Support Multiple Server Support

Commands
HSM migrate and recall commands BA backup and restore commands GPFS mmbackup command Other HSM utility commands are updated
Configuration
The multiple server feature will be enabled by a new option in the dsm.opt file (HSMMULTISERVER YES) The classical HSM automigration daemons must be disabled (dsmmonitord, dsmscoutd) GPFS policy migration is used
The option HSMDISABLEAUTOMIGDAEMONS YES must be set
69
Adding TSM Servers to an Existing Managed Filesystem

First upgrade to multiple server support
Update options with HSMMULTISERVER YES
Add existing TSM server as first server in the server list

dsmmigfs addmultiserver -server=<server1name> <fsname>
Run dsmMultiServerUpgrade .pl script.

This script will couple all existing managed files with the managing TSM server the file system is managed against
Add additional TSM servers to server list

dsmmigfs addmultiserver -server=<server2name> <fsname> When new files are migrated HSM will round-robin through the available servers
Query environment with

dsmmigfs querymultiserver <filesystemname>
70
Miscellaneous Client Functions
71
New 64-bit Clients

64-bit native Linux Intel (x64)
For x64 Linux, the environments supported in TSM 6.3 are: Sles 10 and 11 and RH 5 and 6
Solaris (SPARC)
For Solaris the environments supported in TSM 6.3 are: Solaris 10 for SPARC Update 1 or higher
Macintosh (Intel)
For MacIntosh Intel, the environments supported in TSM 6.3 are: MacOS 10.6 and 10.7
72
Miscellaneous Backup/Archive Client Updates
Linux now supports upgrade installation

rpm U
Simplified configuration of client in an MSCS cluster

New Back/Archive Client configuration wizard for cluster support
73
Cluster Configuration Wizard - Start
74
Cluster Configuration Wizard Select Group
75
Cluster Configuration Wizard Select Drives
76
Questions ?
77

TSM 6.3 Server - Client Enhancements

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

TSM 6.3 Server - Client Enhancements

Загружено:

Авторское право:

Доступные форматы

Advanced Technical Skills (ATS) North America

IBM Advanced Technical Skills

2012 IBM Corporation

Advanced Technical Skills (ATS) North America

TSM Advanced Technical Support Team

2012 IBM Corporation

Advanced Technical Skills (ATS) North America

2012 IBM Corporation

Advanced Technical Skills (ATS) North America

TSM For ERP Support For RMAN Incremental Backups

2012 IBM Corporation

Advanced Technical Skills (ATS) North America

TSM for ERP

Tivoli Storage Manager

Oracle backup process

TSM for ERP shared library

2012 IBM Corporation

Advanced Technical Skills (ATS) North America

Integrated FCM & Oracles RMAN Incremental Backup

Local Area Network

TSM for ERP

TSM for ERP

TSM for ERP

Storage Area Network

2012 IBM Corporation

Advanced Technical Skills (ATS) North America

2012 IBM Corporation

Advanced Technical Skills (ATS) North America

AES Encryption for authentication protocol

The following components updated:

2012 IBM Corporation

Advanced Technical Skills (ATS) North America

Mutual Authentication Process

Advanced Technical Skills (ATS) North America

No other client to server communications is encrypted with Session Key

2012 IBM Corporation

Advanced Technical Skills (ATS) North America

2012 IBM Corporation

Advanced Technical Skills (ATS) North America

Processor Value Unit (PVU) Estimate

2012 IBM Corporation

Advanced Technical Skills (ATS) North America

2012 IBM Corporation

Advanced Technical Skills (ATS) North America

The Processor Value Unit (PVU) License Model

Cost is indexed based on the computing power of each

A primary goal with PVU licensing is to align an

Only valid for TSM 6.3 (and above) clients

2012 IBM Corporation

Advanced Technical Skills (ATS) North America

Server Backup/Archive/API clients that run on:

Other Retired, test and single user

2012 IBM Corporation

Advanced Technical Skills (ATS) North America

Client vs Server Device Role Override

Client-class devices are, in cases, single-user devices. This

On a NODE definition, the ROLEOVERRIDE parameter allows the

2012 IBM Corporation

Advanced Technical Skills (ATS) North America

Simple Example: TSM for MAIL on Server Device Node X

Windows 2008 is running on an Intel Xeon processor model

2012 IBM Corporation

Advanced Technical Skills (ATS) North America