Professional Documents
Culture Documents
Tivoli Storage Manager Client and Server Enhancements for TSM V6.3
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
Architectural Overview
Oracle
API
database backup/restore log archive/retrieve
DB Server
TSM Server
TSM for ERP daemon
TSM for ERP Admin. Assistant
DB
TCP/IP
FlashCopy Manager
FlashCopy / Snapshot Backup FlashCopy Restore FlashCopy Cloning
FCM
Server (backup)
FCM
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
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
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
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
12
Agenda
PVU Definition PVU Estimating Overview Value of this New Function Component Descriptions Commands and Output Exporting Data to a Spreadsheet
13
14
PVU Classifications
Client Backup/Archive/API clients that run on:
MS Win7, MS WinXP Professional, and Apple systems
15
16
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
18
19
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
TSM Storage Agent can also install and use it for this purpose
21
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
23
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
26
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
28 28
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
29 29
Default install path is /opt/filepath. The script has two parameters, start and stop.
The /var/log/messages (or dmesg) output may be monitored to verify the Jbb driver loads successfully:
30 30
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
32 32
33 33
34
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
2012 IBM Corporation
35
36
37
38
39
40
41 41
43 43
44 44
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.
2012 IBM Corporation
46 46
Supported Platforms
47 47
Prerequisites
48 48
49
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.
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
50
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
2012 IBM Corporation
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
52
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
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.
2012 IBM Corporation
56
Site A
Site B
File Server A
File Server B
57
b - hsmtasks a - dsmmove
File Server A
File Server B
58
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
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
FS (filesystem)
add, remove, update threshold migration, demand migration, reconciliation scan, quota, statistics
FILE
premigration, migration recall, partial recall, stream recall stub restore, orphaned
62
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
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
2012 IBM Corporation
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
2012 IBM Corporation
66
67
can scale with the number of TSM servers used for migration and recall operations.
TSM server 1
TSM server 2
TSM server 3
68
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
70
71
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
73
74
75
76
Questions ?
77