what's new in the tsm 5.2 client agenda

1

IBM Software Group

Oxford University TSM Symposium 2003 | 23 25 Septermber 2003 2003 IBM Corporation

Whats New in the TSM 5.2 ClientAndy Raibeck, Tivoli Storage Manager Client [email protected]

IBM Software Group | Tivoli software

Whats New in the TSM 5.2 Client 2003 IBM Corporation2

Agenda

Summary of new features

A look at:File Grouping

Serviceability enhancements

Volume Shadowcopy Service support

Windows Open File Support

2

IBM Software Group


Summary of new features



New enhancements/features

AIX support for VxFS file systems and Veritas Volume ManagerAUTOMOUNT support for LinuxFile groupingFirewall support for scheduled client operationsGPFS HSM support for pSeries in AIX HACMP/ES clusterJAVA GUI for UNIX Backup-Archive clientsHSM LAN-free tolerationHSM non-root user support for HSM clientsLanguage pack support for Windows Backup-Archive clientsLanguage support improved for HP-UX, Solaris, and Linux/390 clientsMacintosh OS X Unicode supportNDMP file-level restoreNDS backup automation for NetWareQUERY FILESPACE enhancementQUERY IMAGE enhancementQUERY INCLEXCL enhancementQUERY OPTIONS

3



New enhancements/features (2)

QUERY SYSTEMINFOSnapshot support for external snapshot mechanismsSolaris 9 Backup-Archive client and 64-bit HSM client Sparse file handling improvements for UNIX Backup-Archive clientsStreaming mode for HSM on file recallSuSE Linux Version8 Backup-Archive client for pSeries hardwareTRACESEGSIZE option to split trace filesWeb client functional enhancmentsWeb client sticky apps supportWebsphere 5.0 supportWindows First failure data capture for program exceptionsWindows Automated System Recovery (ASR) for XP and 2003Windows 2003 support for System State using VSSWindows on-line image backup for XPWindows Open File Support for Windows 2000 / XPWindows RESETARCHIVEATTRIBUTE option

IBM Software Group


File Grouping

4



History of file grouping

Archive provides a simple form of file grouping by description.Archives can be created, queried, and retrieved by description.

There is no way to ensure that all members of the group are archived.

The first real file grouping implementations were for adaptive subfile backup and Windows system object backup.

All parts of the system object are sent in one transaction to the server.

Due to the large transaction size, the recovery log could be pinned.

File grouping was enhanced for the Windows image backup implementation to support splitting the group across multiple transactions, alleviating the log pinning problem.



History of file grouping (2)

Primary objectives for file grouping in TSM 5.2:Support for IBM WebSphere Application Server 5.0 backup.

Support for Windows 2003 system state backup.

Expose file grouping to the TSM command line client to allow customers to begin building their own custom coordinated backup solutions.

5



What is file grouping?

File grouping is a mechanism for backing up and managing a groupof files as a single entity such that all files in the group are:

bound to the same management class

exported together

expired together

Restored together



Using file grouping

New command line client commands:BACKUP GROUP

RESTORE GROUP

QUERY GROUP

DELETE GROUP

Use virtual file space and group names to bind the group to a management class:

INCLUDE *:\ANDYS_FS\ANDYS_GROUP GROUPMC

6



BACKUP GROUP

BACKUP GROUP options-FILELIST=filelistname

-GROUPNAME=groupname

-MODE=FULL | DIFFERENTIAL

-VIRTUALFSNAME=vfsname



BACKUP GROUP (2)

Example:Filelist name is FILELIST.TXT. File contains:

"C:\Education\OxfordSymposium\What's New in the TSM 5.2 Client.pptc:\mytools\setrc.exet:\OxfordSymposium\abstract1.txt

Command syntax: dsmc backup group -filelist=filelist.txt -virtualfsname=andys_fs

-groupname=andys_group

7



BACKUP GROUP (3)

Output:IBM Tivoli Storage Manager

*** Fixtest, Please see README file for more information ***

Command Line Backup/Archive Client Interface - Version 5, Release 2, Level 0.2

(c) Copyright by IBM Corporation and other(s) 1990, 2003. All Rights Reserved.

Node Name: ANDY

Session established with server BABYLON_5: Windows

Server Version 5, Release 2, Level 0.2

Server date/time: 09/08/2003 00:40:00 Last access: 09/08/2003 00:35:44

Backup GROUP function invoked mode= FULL.

Directory--> 0 \\amr-laptop\c$\Education [Sent]

Directory--> 0 \\amr-laptop\c$\Education\OxfordSymposium [Sent]

Normal File--> 584,704 \\amr-laptop\c$\Education\OxfordSymposium\What's New in the TSM 5.2 Client.ppt [Sent]

Directory--> 0 \\amr-laptop\c$\MyTools [Sent]

Normal File--> 36,864 \\amr-laptop\c$\MyTools\setrc.exe [Sent]

Directory--> 0 \\amr-laptop\myshare\OxfordSymposium [Sent]

Normal File--> 395 \\amr-laptop\myshare\OxfordSymposium\abstract1.txt [Sent]

Directory--> 0 \\amr-laptop\c$\TSM [Sent]

Directory--> 0 \\amr-laptop\c$\TSM\baclient [Sent]

Normal File--> 123 \\amr-laptop\c$\TSM\baclient\filelist.txt [Sent]

Backup processing of 'ANDYS_GROUP' finished without failure.



BACKUP GROUP (4)

Output (continued):Total number of objects inspected: 10

Total number of objects backed up: 10

Total number of objects updated: 0

Total number of objects rebound: 0

Total number of objects deleted: 0

Total number of objects expired: 0

Total number of objects failed: 0

Total number of bytes transferred: 611.09 KB

Data transfer time: 0.03 sec

Network data transfer rate: 20,369.85 KB/sec

Aggregate data transfer rate: 152.16 KB/sec

Objects compressed by: 0%

Elapsed processing time: 00:00:04

C:\TSM\baclient>

8



QUERY FILESPACE

C:\TSM\baclient>dsmc query filespaceIBM Tivoli Storage Manager*** Fixtest, Please see README file for more information ***Command Line Backup/Archive Client Interface - Version 5, Release 2, Level 0.2(c) Copyright by IBM Corporation and other(s) 1990, 2003. All Rights Reserved.

Node Name: ANDYSession established with server BABYLON_5: WindowsServer Version 5, Release 2, Level 0.2Server date/time: 09/08/2003 00:45:43 Last access: 09/08/2003 00:45:34

Num Last Incr Date Type File Space Name--- -------------- ---- ---------------1 00/00/0000 00:00:00 TSMVFS ANDYS_FS

C:\TSM\baclient>



QUERY GROUP

C:\TSM\baclient>dsmc query group {andys_fs}\IBM Tivoli Storage Manager*** Fixtest, Please see README file for more information ***Command Line Backup/Archive Client Interface - Version 5, Release 2, Level 0.2(c) Copyright by IBM Corporation and other(s) 1990, 2003. All Rights Reserved.

Node Name: ANDYSession established with server BABYLON_5: WindowsServer Version 5, Release 2, Level 0.2Server date/time: 09/08/2003 00:47:52 Last access: 09/08/2003 00:47:49

Size Backup Date Mgmt Class A/I Type Group---- ----------- ---------- --- ---- -----

622,086 B 09/08/2003 00:40:00 DEFAULT A FULL ANDYS_FS\ANDYS_GROUP

C:\TSM\baclient>

9



QUERY GROUP (2)C:\TSM\baclient>dsmc query group {andys_fs}\andys_group -showmembersIBM Tivoli Storage Manager*** Fixtest, Please see README file for more information ***Command Line Backup/Archive Client Interface - Version 5, Release 2, Level 0.2(c) Copyright by IBM Corporation and other(s) 1990, 2003. All Rights Reserved.

Node Name: ANDYSession established with server BABYLON_5: Windows

Server Version 5, Release 2, Level 0.2Server date/time: 09/08/2003 00:49:22 Last access: 09/08/2003 00:47:52

Size Backup Date Mgmt Class A/I Type Group---- ----------- ---------- --- ---- -----

622,086 B 09/08/2003 00:40:00 DEFAULT A FULL ANDYS_FS\ANDYS_GROUP

Size Backup Date Mgmt Class A/I File---- ----------- ---------- --- ----0 B 09/08/2003 00:40:00 DEFAULT A ANDYS_FS\\AMR-LAPTOP\C$0 B 09/08/2003 00:40:00 DEFAULT A ANDYS_FS\\AMR-LAPTOP\MYSHARE0 B 09/08/2003 00:40:00 DEFAULT A ANDYS_FS\\amr-laptop\c$\Education0 B 09/08/2003 00:40:00 DEFAULT A ANDYS_FS\\amr-laptop\c$\Education\OxfordSymposium

584,704 B 09/08/2003 00:40:00 DEFAULT A ANDYS_FS\\amr-laptop\c$\Education\OxfordSymposium\What's New in the TSM 5.

2 Client.ppt0 B 09/08/2003 00:40:00 DEFAULT A ANDYS_FS\\amr-laptop\c$\MyTools

36,864 B 09/08/2003 00:40:00 DEFAULT A ANDYS_FS\\amr-laptop\c$\MyTools\setrc.exe0 B 09/08/2003 00:40:01 DEFAULT A ANDYS_FS\\amr-laptop\myshare\OxfordSymposium

395 B 09/08/2003 00:40:01 DEFAULT A ANDYS_FS\\amr-laptop\myshare\OxfordSymposium\abstract1.txt

C:\TSM\baclient>



RESTORE GROUPC:\TSM\baclient>dsmc restore group {andys_fs}\andys_groupIBM Tivoli Storage Manager*** Fixtest, Please see README file for more information ***Command Line Backup/Archive Client Interface - Version 5, Release 2, Level 0.2(c) Copyright by IBM Corporation and other(s) 1990, 2003. All Rights Reserved.

Restore function invoked.

Node Name: ANDYSession established with server BABYLON_5: Windows

Server Version 5, Release 2, Level 0.2Server date/time: 09/08/2003 00:55:14 Last access: 09/08/2003 00:54:45

Restoring 0 \\AMR-LAPTOP\MYSHARE\OxfordSymposium [Done]Restoring 395 \\AMR-LAPTOP\MYSHARE\OxfordSymposium\abstract1.txt [Done]Restoring 0 \\AMR-LAPTOP\C$\Education\OxfordSymposium [Done]Restoring 584,704 \\AMR-LAPTOP\C$\Education\OxfordSymposium\What's New in the TSM 5.2

Client.ppt [Done]Restoring 0 \\AMR-LAPTOP\C$\MyTools [Done]Restoring 36,864 \\AMR-LAPTOP\C$\MyTools\setrc.exe [Done]

Restore processing finished.

Total number of objects restored: 6Total number of objects failed: 0Total number of bytes transferred: 609.57 KBData transfer time: 0.06 secNetwork data transfer rate: 10,159.60 KB/secAggregate data transfer rate: 25.36 KB/secElapsed processing time: 00:00:24

C:\TSM\baclient>

10

IBM Software Group


Serviceability enhancements



Enhancements and new items

Enhancements:Scheduler tracing

QUERY FILESPACE

New items:Trace file spanning

QUERY SYSTEMINFO command

Crash handler for Windows client

11



Scheduler tracing

Implemented 325 new trace points:Old trace points: 108

New trace points: 433

New trace flag SCHED.

When troubleshooting problems related to client scheduler, use client trace options:

TRACEFILE tracefilename

TRACEFLAGS SCHED



Scheduler tracing example:

Scheduled action is to back up C:\MyTools directory. Why does it complete with RC 8?

12



Scheduler tracing example (pre-5.2):schedobj.cpp ( 602): new_SchedObj: Enteringschedobj.cpp ( 602): new_SchedObj: Enteringschedobj.cpp ( 700): InitScheduler: Enteringschedobj.cpp ( 757): InitSchedulerMode: Enteringschedobj.cpp ( 761): InitSchedulerMode: SCHEDMODE_PROMPTEDschedobj.cpp ( 770): InitSchedulerMode: Not using external timerschedobj.cpp ( 897): Scheduler: Enteringschedobj.cpp ( 959): DoState: Enteringschedobj.cpp (1529): HandleQueryState: Enteringschedobj.cpp (1078): QueryPendingSchedule: Enteringcusched.cpp ( 856): SendSchedQuery: Sending a CSQryPending verb, node: '5200'cusched.cpp ( 857): llAddress: '1501', hlAddress: ''cusched.cpp ( 960): RecvSchedResp: Trying to get a CSQryPendRespVerbschedobj.cpp ( 959): DoState: Enteringschedobj.cpp (1712): HandleExecuteState: Enteringschedobj.cpp (1026): ExecuteSchedule: Enteringschedobj.cpp (2137): DoCommand(): Enteringcusched.cpp ( 408): SendStartOp: Sending a CSStartOpVerb, node: '5200'cusched.cpp ( 409): scheduleName: 'TESTRC', startDateToken: 05/12/2003 12:50:40cusched.cpp ( 477): SendStartOp: Server returned Confirm resp: Confirm=Yesschedobj.cpp (1274): GetCurrentSchedule: Enteringcusched.cpp ( 283): SendSchedResult: Sending a CSResults verb, node: '5200'cusched.cpp ( 284): SchedResult: 8, scheduleName: 'TESTRC', startDateToken: 05/12/2003 12:50:40cusched.cpp ( 368): SendSchedResult: Server returned Confirm resp: Confirm=Yesschedobj.cpp (2622): PruneScheduleLog(): Enteringschedobj.cpp (2628): Schedule Log Pruner started.schedobj.cpp (2629): Schedule Log Retention Days = 10000.schedobj.cpp (2636): Schedule Log NOT pruned. Retention days = NOLIMIT.schedobj.cpp ( 959): DoState: Enteringschedobj.cpp (1529): HandleQueryState: Enteringschedobj.cpp (1078): QueryPendingSchedule: Enteringcusched.cpp ( 856): SendSchedQuery: Sending a CSQryPending verb, node: '5200'cusched.cpp ( 857): llAddress: '1501', hlAddress: ''cusched.cpp ( 960): RecvSchedResp: Trying to get a CSQryPendRespVerbschedobj.cpp ( 959): DoState: Enteringschedobj.cpp (1730): HandleWaitForServerState: Enteringschedobj.cpp (1875): WaitForServerTap: Enteringcusched.cpp ( 820): InboundInit: Inbound session initialized.schedobj.cpp ( 659): delete_SchedObj: Enteringschedobj.cpp ( 659): delete_SchedObj: Enteringschedobj.cpp ( 659): delete_SchedObj: Enteringschedobj.cpp ( 659): delete_SchedObj: Entering

Begin

End (huh?)



Scheduler tracing example (5.2):TSM Trace IBM Tivoli Storage Manager 5.2.0.0 h14Build Date: Fri May 09 10:40:16 2003BEGINNING NEW TRACE

05/12/2003 12:52:43.717 : trace.cpp (1514): Tracing to file: C:\tsm520ch14\debug\bin\winnt_unicode\trace520.txt05/12/2003 12:52:43.717 : trace.cpp (1515): Tracefile maximum length set to 0 MB.05/12/2003 12:52:43.717 : trace.cpp (1525): ----------------------------------------------------------------05/12/2003 12:52:43 - Trace begun.05/12/2003 12:52:43.717 : trace.cpp (1535): Unicode Client05/12/2003 12:52:43.757 : schedobj.cpp ( 670): schedObj allocated successfully.05/12/2003 12:52:43.757 : schedobj.cpp ( 756): QuerySchedPeriod = 1205/12/2003 12:52:43.757 : schedobj.cpp ( 757): MaxCmdRetries = 205/12/2003 12:52:43.757 : schedobj.cpp ( 758): RetryPeriod = 2005/12/2003 12:52:43.757 : schedobj.cpp ( 818): InitSchedulerMode: SCHEDMODE_PROMPTED05/12/2003 12:52:43.757 : schedobj.cpp ( 828): InitSchedulerMode: Not using external timer05/12/2003 12:52:43.877 : schedobj.cpp ( 781): bNonInteractive = true05/12/2003 12:52:43.877 : schedobj.cpp (1062): schedState = Query05/12/2003 12:52:43.977 : schedobj.cpp (1188): optSendQuery() rc = 005/12/2003 12:52:43.977 : schedobj.cpp (1211): rc = 005/12/2003 12:52:43.977 : schedobj.cpp (1221): ClientSchedMode = 2, schedModeOptOld = 0, schedMode = 205/12/2003 12:52:43.977 : schedobj.cpp (1235): ClientSchedMode = 2, schedModeOptOld = 2, schedMode = 205/12/2003 12:52:43.987 : cusched.cpp ( 939): cuInsertVerb() rc = 005/12/2003 12:52:43.987 : cusched.cpp ( 965): cuInsertVerb() rc = 005/12/2003 12:52:43.987 : cusched.cpp ( 982): cuInsertVerb() rc = 005/12/2003 12:52:43.987 : cusched.cpp (1008): sessSendVerb() rc = 005/12/2003 12:52:43.987 : cusched.cpp ( 253): SendSchedQuery() rc = 005/12/2003 12:52:43.987 : cusched.cpp (1050): sessRecvVerb() rc = 005/12/2003 12:52:43.987 : cusched.cpp (1081): cuExtractVerb() rc = 005/12/2003 12:52:43.987 : cusched.cpp (1108): cuExtractVerb() rc = 005/12/2003 12:52:43.987 : cusched.cpp (1120): cuExtractVerb() rc = 005/12/2003 12:52:43.987 : cusched.cpp ( 268): RecvSchedResp() rc = 005/12/2003 12:52:43.987 : schedobj.cpp (1266): server max retries = 1005/12/2003 12:52:43.987 : schedobj.cpp (1274): server retry wait = 505/12/2003 12:52:43.987 : schedobj.cpp (1282): server refresh = 605/12/2003 12:52:43.987 : schedobj.cpp (1687): QueryPendingSchedule() rc = 005/12/2003 12:52:43.987 : schedobj.cpp (3536): Schedule name: TESTRC05/12/2003 12:52:43.987 : schedobj.cpp (3537): Action: Incremental05/12/2003 12:52:43.987 : schedobj.cpp (3538): Objects: c:\mytools\05/12/2003 12:52:43.987 : schedobj.cpp (3539): Options: 05/12/2003 12:52:43.987 : schedobj.cpp (3540): Start time: 05/12/2003 12:52:3005/12/2003 12:52:44.017 : schedobj.cpp (1732): Schedule mode is PROMPTED05/12/2003 12:52:44.017 : schedobj.cpp (1748): query sched period = 6, max command retries = 10, retry period = 505/12/2003 12:52:44.017 : schedobj.cpp (1756): schedule refresh minutes = 36005/12/2003 12:52:44.017 : schedobj.cpp (1772): schedule length = 6, start attempt = 0, execute on query = false05/12/2003 12:52:44.017 : schedobj.cpp (1068): schedState = Execute05/12/2003 12:52:44.017 : schedobj.cpp (1914): continue scheduling = true

Info for next schedule

13



Scheduler tracing example (5.2):05/12/2003 12:52:44.017 : schedobj.cpp (2280): Building command string:05/12/2003 12:52:44.017 : schedobj.cpp (2297): argString: 'Incremental '05/12/2003 12:52:44.017 : schedobj.cpp (2330): argString: 'Incremental '05/12/2003 12:52:44.017 : schedobj.cpp (2336): argString: 'Incremental c:\mytools\'05/12/2003 12:52:44.017 : schedobj.cpp (2428): Checking for preschedule command05/12/2003 12:52:44.017 : schedobj.cpp (2429): blockCmd = false, postBlockCmd = false05/12/2003 12:52:44.017 : schedobj.cpp (2450): PRE command = 'setrc 0', wait = true05/12/2003 12:52:44.017 : schedobj.cpp (2461): buf = 'setrc 0'05/12/2003 12:52:44.027 : schedobj.cpp (2467): Executing command05/12/2003 12:52:44.027 : schedobj.cpp (3264): buf = 'setrc 0'05/12/2003 12:52:44.027 : schedobj.cpp (3265): wait_flag = true05/12/2003 12:52:44.027 : schedobj.cpp (3266): Executing command05/12/2003 12:52:44.057 : schedobj.cpp (3270): command rc = 005/12/2003 12:52:44.057 : schedobj.cpp (2469): command rc = 005/12/2003 12:52:44.057 : schedobj.cpp (2492): ACTION=Incremental05/12/2003 12:52:44.057 : schedobj.cpp (2666): retries = 1005/12/2003 12:52:44.057 : schedobj.cpp (2669): CheckSession() rc = 005/12/2003 12:52:44.057 : cusched.cpp ( 501): cuInsertVerb() rc = 005/12/2003 12:52:44.057 : cusched.cpp ( 518): cuInsertVerb() rc = 005/12/2003 12:52:44.057 : cusched.cpp ( 542): sessSendVerb() rc = 005/12/2003 12:52:44.057 : cusched.cpp ( 555): sessRecvVerb() rc = 005/12/2003 12:52:44.057 : schedobj.cpp (2674): cuSendStartOp() rc = 005/12/2003 12:52:48.353 : schedobj.cpp (2679): schCmdEx() rc = 005/12/2003 12:52:48.353 : schedobj.cpp (2757): Checking for postschedule command05/12/2003 12:52:48.353 : schedobj.cpp (2758): blockCmd = false, postBlockCmd = false05/12/2003 12:52:48.353 : schedobj.cpp (2777): POST command = 'setrc 5', wait = true05/12/2003 12:52:48.353 : schedobj.cpp (2788): buf = 'setrc 5'05/12/2003 12:52:48.353 : schedobj.cpp (2793): Executing command05/12/2003 12:52:48.353 : schedobj.cpp (3264): buf = 'setrc 5'05/12/2003 12:52:48.353 : schedobj.cpp (3265): wait_flag = true05/12/2003 12:52:48.353 : schedobj.cpp (3266): Executing command05/12/2003 12:52:48.373 : schedobj.cpp (3270): command rc = 505/12/2003 12:52:48.373 : schedobj.cpp (2795): command rc = 505/12/2003 12:52:48.393 : schedobj.cpp (3306): resultrc = 805/12/2003 12:52:48.393 : schedobj.cpp (3307): actionIsCmd = false05/12/2003 12:52:48.393 : schedobj.cpp (3308): RetryPeriod = 505/12/2003 12:52:48.393 : schedobj.cpp (3309): gRC = enabled05/12/2003 12:52:48.393 : schedobj.cpp (3325): success = true05/12/2003 12:52:48.403 : schedobj.cpp (3365): retries = 10

Post-schedule command failed

Scheduled operation

Here is the pre-schedule command

Pre-schedule command ran successfully

Scheduled operation ran successfully

Post-schedule command



Scheduler tracing example (5.2):05/12/2003 12:52:48.403 : schedobj.cpp (3369): CheckSession() rc = 005/12/2003 12:52:48.403 : cusched.cpp ( 309): SchedResult = 805/12/2003 12:52:48.403 : cusched.cpp ( 346): success = true05/12/2003 12:52:48.403 : cusched.cpp ( 357): cuInsertVerb() rc = 005/12/2003 12:52:48.403 : cusched.cpp ( 374): cuInsertVerb() rc = 005/12/2003 12:52:48.403 : cusched.cpp ( 395): sessSendVerb() rc = 005/12/2003 12:52:48.413 : cusched.cpp ( 408): sessRecvVerb() rc = 005/12/2003 12:52:48.413 : schedobj.cpp (3375): cuSendSchedResult() rc = 005/12/2003 12:52:48.413 : schedobj.cpp (3426): schedCompleteAction = NONE05/12/2003 12:52:48.413 : schedobj.cpp (1062): schedState = Query05/12/2003 12:52:48.463 : schedobj.cpp (1188): optSendQuery() rc = 005/12/2003 12:52:48.463 : schedobj.cpp (1211): rc = 005/12/2003 12:52:48.463 : schedobj.cpp (1221): ClientSchedMode = 2, schedModeOptOld = 2, schedMode = 205/12/2003 12:52:48.463 : schedobj.cpp (1235): ClientSchedMode = 2, schedModeOptOld = 2, schedMode = 205/12/2003 12:52:48.473 : cusched.cpp ( 939): cuInsertVerb() rc = 005/12/2003 12:52:48.473 : cusched.cpp ( 965): cuInsertVerb() rc = 005/12/2003 12:52:48.473 : cusched.cpp ( 982): cuInsertVerb() rc = 005/12/2003 12:52:48.473 : cusched.cpp (1008): sessSendVerb() rc = 005/12/2003 12:52:48.473 : cusched.cpp ( 253): SendSchedQuery() rc = 005/12/2003 12:52:48.473 : cusched.cpp (1050): sessRecvVerb() rc = 005/12/2003 12:52:48.473 : cusched.cpp (1081): cuExtractVerb() rc = 005/12/2003 12:52:48.473 : cusched.cpp (1108): cuExtractVerb() rc = 005/12/2003 12:52:48.473 : cusched.cpp (1120): cuExtractVerb() rc = 005/12/2003 12:52:48.473 : cusched.cpp ( 268): RecvSchedResp() rc = 005/12/2003 12:52:48.473 : schedobj.cpp (1266): server max retries = 1005/12/2003 12:52:48.473 : schedobj.cpp (1274): server retry wait = 505/12/2003 12:52:48.473 : schedobj.cpp (1282): server refresh = 605/12/2003 12:52:48.483 : schedobj.cpp (1687): QueryPendingSchedule() rc = 005/12/2003 12:52:48.483 : schedobj.cpp (3536): Schedule name: TESTRC05/12/2003 12:52:48.483 : schedobj.cpp (3537): Action: Incremental05/12/2003 12:52:48.483 : schedobj.cpp (3538): Objects: c:\mytools\05/12/2003 12:52:48.483 : schedobj.cpp (3539): Options: 05/12/2003 12:52:48.483 : schedobj.cpp (3540): Start time: 05/13/2003 12:52:3005/12/2003 12:52:48.513 : schedobj.cpp (1732): Schedule mode is PROMPTED05/12/2003 12:52:48.513 : schedobj.cpp (1748): query sched period = 6, max command retries = 10, retry period = 505/12/2003 12:52:48.513 : schedobj.cpp (1756): schedule refresh minutes = 36005/12/2003 12:52:48.513 : schedobj.cpp (1772): schedule length = 6, start attempt = 1439, execute on query =

false05/12/2003 12:52:48.513 : schedobj.cpp (1795): Schedule mode is PROMPTED05/12/2003 12:52:48.513 : schedobj.cpp (1806): not using external timer05/12/2003 12:52:48.513 : schedobj.cpp (1074): schedState = WaitForServer05/12/2003 12:52:53.581 : schedobj.cpp (1961): user abort05/12/2003 12:52:53.591 : schedobj.cpp ( 698): schedObj = 0xF5881405/12/2003 12:52:53.591 : schedobj.cpp ( 698): schedObj = 0x0

Query for next scheduled operation.

RC and status that will be reported to server.

14



QUERY FILESPACE enhancements

QUERY FILESPACE now accepts a fully-specified or wildcarded file space specification.

Especially useful in Unix environment where there may be a very large number of file spaces.

now accepts NAS node queries. Use NASNODENAME and CLASS to view NAS file spaces.

has a new message, No file spaces for node nodename' were found on the server matching the search criteria.



QUERY FILESPACE enhancementsExamples:

tsm> q fi

Num Last Incr Date Type File Space Name

--- -------------- ---- ---------------

1 00/00/0000 00:00:00 NTFS \\bart\c$

2 00/00/0000 00:00:00 NTFS \\comic-book-guy\d$

3 00/00/0000 00:00:00 NTFS \\homer\c$

4 00/00/0000 00:00:00 NTFS \\maggie\c$

5 00/00/0000 00:00:00 NTFS \\marge\c$

6 00/00/0000 00:00:00 NTFS \\milhouse\e$

7 00/00/0000 00:00:00 NTFS \\patty\c$

8 00/00/0000 00:00:00 NTFS \\selma\c$

tsm> q fi \\?ar*


--- -------------- ---- ---------------

1 00/00/0000 00:00:00 NTFS \\bart\c$

5 00/00/0000 00:00:00 NTFS \\marge\c$

tsm> q fi *y\?$


--- -------------- ---- ---------------

2 00/00/0000 00:00:00 NTFS \\comic-book-guy\d$

7 00/00/0000 00:00:00 NTFS \\patty\c$

tsm> q fi \\ma*


--- -------------- ---- ---------------

4 00/00/0000 00:00:00 NTFS \\maggie\c$

5 00/00/0000 00:00:00 NTFS \\marge\c$

tsm> q fi *e\c$


--- -------------- ---- ---------------

4 00/00/0000 00:00:00 NTFS \\maggie\c$

5 00/00/0000 00:00:00 NTFS \\marge\c$

15



Trace file spanningTSM backup-archive client tracing previously controlled by three options:

TRACEFILE filename Specifies the name of the trace file.TRACEFLAGS flag1 flag2 flagn Specifies which trace flag(s) to use.TRACEMAX n Specifies the maximum size of the trace file in MB which, when reached, will cause tracing to wrap back to the beginning of the file (e.g. the trace file is circular); limited to 2047 MB (just under 2 GB).

Large trace files present the following issues:Wrapped trace file size limit of 2047 MB may be too small.Large trace files often require that the customer use some kind of file splitter tool to split the trace into multiple, smaller files.

New trace option in TSM 5.2:TRACESEGSIZE n When this option is used, the trace file will be written to multiple files, with each file being limited to n MB in size. 0 n 1000



Trace file spanning (2)New/changed trace file behavior:

If TRACEMAX and TRACESEGSIZE are unspecified, then the trace will be unbounded (as before).

If TRACESEGSIZE is specified but TRACEMAX is not specified, thenthe trace will be segmented, and the total size will be unbounded.

If TRACEMAX and TRACESEGSIZE are both specified, then the trace will be segmented, growing to a maximum combined size of TRACEMAX, at which point tracing will wrap back to the first segment.

If TRACEMAX 1000 and TRACESEGSIZE is unspecified, then tracing will wrap back to the beginning of the file (as before).

16



Trace file spanning (2)New/changed trace file behavior (continued):

If TRACEMAX > 1000 and TRACESEGSIZE is unspecified, then TRACESEGSIZE will default to 1000.

If TRACEMAX and TRACESEGSIZE are both specified but TRACESEGSIZE > TRACEMAX, then TRACESEGSIZE will assume the value of TRACEMAX.

When the trace is being segmented, each segments file name will be of the form filename.n where filename is the name specified by TRACEFILE and n is an integer. n will be 1 for the first segment, 2 for the second segment, etc.

NetWare limited to 8.3 name, so for TRACEFILE, just specify the file name part, and omit the extension.




When a segment reaches TRACESEGSIZE MB in size, it will be closed, and the next segment will be opened.

The maximum numer of trace segments is calculated as follows:

#segs = TRACEMAX / TRACESEGSIZE

If the remainder is nonzero, add 1 to #segs

17




The beginning of the trace will showBEGINNING NEW TRACE

The end of each trace segment will have a line like this:Continued at beginning of segment 2

The beginning of each trace segment will have a line like this:Continued from end of segment 1

The end of the trace will showEND OF DATA - close

TRACEMAX has been enhanced to support values (expressed in MB) up to 4,294,967,295 (2^32 1).

If the trace file already existed, the old client behavior was to append to the existing file. This has been discontinued; the trace data will now be written at the beginning of the file.



New QUERY SYSTEMINFO commandOften when diagnosing problems, customers are asked to submit multiple pieces of information, including (but not necessarily limited to):

dsmerror.log

dsmsched.log

dsm.opt

operating system information

client version

include/exclude lists

TSM service configuration information (Windows)

TSM policy information

more

The QUERY SYSTEMINFO command is intended to help facilitate the gathering of this information.

18



QUERY SYSTEMINFO syntax

Query SYSTEMInfo [itemlist] [-CONSole | -FILEName=filename]

itemlist is one or more of the following:CLUSTER Cluster name on Unix, NetWare; cluster configuration on WindowsDSMOPTFILE Contents of client options fileDSMSYSFILE Contents of system options fileENV Environment variablesERRORLOG Contents of backup-archive client error log

* FILESNOTTOBACKUP Enumeration of Windows registry keyHKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup

FILE[=filename] Information on TSM client files or specified fileINCLEXCL Same as output from QUERY INCLEXCL

* KEYSNOTTORESTORE Enumeration of Windows registry keyHKLM\ControlSet001\Control\BackupRestore\KeysNotToRestore

MSINFO Windows system informationOPTIONS Same as output from QUERY OPTIONSOSINFO Client operating system version informationPOLICY Same as output from QUERY MGMTCLASS -DETAILREGISTRY Enumeration of Windows registry key HKLM\SOFTWARE\IBM\ADSM and

HKLM\SYSTEM\CurrentControlSet\Services for installed client services



QUERY SYSTEMINFO syntax (2)* SCHEDLOG Contents of client schedule log* SFP[=filename] Information on all Windows files protected by Systme File Protection or indicates whether

the specified file is protectedSYSTEMOBJECT Same as output from SHOW SYSTEMOBJECT

(*) did not make it into the pubs, but are in the README file.

-CONSole The command output is written to the console-FILEName=filename The command output is written to the file named filename

The default itemlist is all applicable items.The default output behavior is to write the output to ./dsminfo.txt

Use the QUERY trace flag to trace QUERY SYSTEMINFO.

19



QUERY SYSTEMINFO sample output

Full system information report generated 05/15/2003 22:28:47

===============================================================================TSMVERSION===============================================================================IBM Tivoli Storage ManagerCommand Line Backup/Archive Client Interface - Version 5, Release 2, Level 0.0 h15build date: Thu May 15 21:01:22 2003

===============================================================================DSMOPTFILE===============================================================================commmethod tcpiptcpserveraddress localhostnodename mordenpasswordaccess generateschedmode prompted

preschedulecmd "setrc 0"postschedulecmd "setrc 5"

*traceflags sched*tracefile trace520.txt

schedlogname mysched.logerrorlogname myerror.log



QUERY SYSTEMINFO sample output (2)

===============================================================================OPTIONS===============================================================================

ACTIVATEKEY: YESAFSBACKUPMNTPNT: YESALLOWWILDCARDCH: NO

ARCHSYMLINKASFILE: YESASRMODE: NO

AUTOFSRENAME: NOAUTOMOUNT:

BACKUPREGISTRY: YESCANDIDATESINTERVAL: 1

CHANGINGRETRIES: 4CHECKFORORPHANS: NOCHECKTHRESHOLDS: 5

CLUSTERNODE: NOCOMMMETHOD: T

COMMRESTARTDURATION: 60COMMRESTARTINTERVAL: 15

COMPRESSALWAYS: YESCOMPRESSION: NO

COMPUTERNAME: DATEFORMAT: 1

.

.

.

20




===============================================================================INCLEXCL===============================================================================*** FILE INCLUDE/EXCLUDE ***Mode Function Pattern (match from top down) Source File---- --------- ------------------------------ -----------------Excl Directory C:\tsmlvsa\tsmlvsacache Operating SystemExcl All C:\WINDOWS\System32\NtmsData\...\* Operating SystemExcl All C:\WINDOWS\system32\NtmsData\* Operating SystemExcl All C:\WINDOWS\System32\MSDtc\trace\dtctrace.log Operating SystemExcl All C:\WINDOWS\System32\MSDtc\MSDTC.LOG Operating SystemExcl All C:\WINDOWS\System32\inetsrv\metabase.xml Operating SystemExcl All C:\WINDOWS\System32\inetsrv\metabase.bin Operating SystemExcl All C:\WINDOWS\System32\inetsrv\mbschema.xml Operating SystemExcl All C:\WINDOWS\System32\config\system.log Operating SystemExcl All C:\WINDOWS\System32\config\system.alt Operating SystemExcl All C:\WINDOWS\System32\config\system Operating SystemExcl All C:\WINDOWS\System32\config\software.log Operating SystemExcl All C:\WINDOWS\System32\config\software Operating SystemExcl All C:\WINDOWS\System32\config\security.log Operating SystemExcl All C:\WINDOWS\System32\config\security Operating SystemExcl All C:\WINDOWS\System32\config\sam.log Operating System...



QUERY SYSTEMINFO sample output (4)===============================================================================FILESNOTTOBACKUP===============================================================================[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]ASR Log File=%SystemRoot%\repair\asr.log[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]ASR Error File=%SystemRoot%\repair\asr.err[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]Client Side Cache=%SystemRoot%\csc\* /s[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]Internet Explorer=%UserProfile%\index.dat /s[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]Memory Page File=\Pagefile.sys[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]Microsoft Writer (Bootable State)=%SystemRoot%\Registration\*.clb

[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]Netlogon=%SystemRoot%\netlogon.chg[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]Power Management=\hiberfil.sys[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]VSS Default Provider=\System Volume Information\*{3808876B-C176-4e48-B7AE-04046E6CC752} /s

[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]Task Scheduler=%SYSTEMROOT%\schedlgu.txt[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]Temporary Files=%TEMP%\* /s[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]Winlogon debug=%WINDIR%\debug\*[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]Catalog Database=%SystemRoot%\System32\CatRoot2\* /s[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]MS Distributed Transaction Coordinator=C:\WINDOWS\System32\MSDtc\MSDTC.LOG

[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]DRM=C:\Documents and Settings\All Users\DRM\* /s[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]System Restore=\System Volume Information\_restore{71CC4CB3-DF4C-4E83-BDCB-F1845301242D}\* /s

[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]Norton AntiVirus Defs=C:\Program Files\Common Files\Symantec Shared\VirusDefs\* /s

[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]Registry Writer=%SystemRoot%\system32\NtmsData\*[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]VSS Service DB=\System Volume Information\*.{7cc467ef-6865-4831-853f-2a4817fd1bca}DB

[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]VSS Service Alternate DB=\System Volume Information\*.{7cc467ef-6865-4831-853f-2a4817fd1bca}ALT

.

.

.

21



QUERY SYSTEMINFO sample output (5)===============================================================================KEYSNOTTORESTORE===============================================================================[SYSTEM\ControlSet001\Control\BackupRestore\KeysNotToRestore]Plug & Play=CurrentControlSet\Enum\[SYSTEM\ControlSet001\Control\BackupRestore\KeysNotToRestore]Mount Manager=MountedDevices\[SYSTEM\ControlSet001\Control\BackupRestore\KeysNotToRestore]Fault Tolerance=Disk\[SYSTEM\ControlSet001\Control\BackupRestore\KeysNotToRestore]Installed Services=CurrentControlSet\Services\*[SYSTEM\ControlSet001\Control\BackupRestore\KeysNotToRestore]Active Directory Restore=CurrentControlSet\Services\NTDS\Restore In

Progress\[SYSTEM\ControlSet001\Control\BackupRestore\KeysNotToRestore]Pending Rename Operations=CurrentControlSet\Control\Session

Manager\PendingFileRenameOperations[SYSTEM\ControlSet001\Control\BackupRestore\KeysNotToRestore]LDM Boot Information=CurrentControlSet\Services\dmio\boot info\[SYSTEM\ControlSet001\Control\BackupRestore\KeysNotToRestore]Windows Setup=Setup\SystemPartition[SYSTEM\ControlSet001\Control\BackupRestore\KeysNotToRestore]Session Manager=CurrentControlSet\Control\Session

Manager\AllowProtectedRenames[SYSTEM\ControlSet001\Control\BackupRestore\KeysNotToRestore]ASR Information=CurrentControlSet\Control\ASR\[SYSTEM\ControlSet001\Control\BackupRestore\KeysNotToRestore]Removable Storage Manager=CurrentControlSet\Control\NTMS\ImportDatabase[SYSTEM\ControlSet001\Control\BackupRestore\KeysNotToRestore]LDM Boot Information (dmboot)=CurrentControlSet\Services\dmboot\[SYSTEM\ControlSet001\Control\BackupRestore\KeysNotToRestore]Norton AntiVirus Defs=HKEY_LOCAL_MACHINE\Software\Symantec\SharedDefs\



===============================================================================SFP===============================================================================

c:\windows\apppatch\acgenral.dll (protected)c:\windows\apppatch\aclayers.dll (protected)c:\windows\apppatch\acspecfc.dll (protected)c:\windows\apppatch\acxtrnal.dll (protected)c:\program files\common files\microsoft shared\web server extensions\40\isapi\_vti_adm\admin.dll (protected)c:\program files\common files\microsoft shared\web server extensions\40\_vti_bin\_vti_adm\admin.exe (protected)c:\windows\system32\admwprox.dll (protected)c:\windows\system32\adsiis.dll (protected)c:\windows\system32\ahui.exe (protected)c:\windows\system32\apphelp.dll (protected)c:\windows\apppatch\apphelp.sdb (protected)c:\windows\system32\asycfilt.dll (protected)

...c:\windows\system32\ansi.sys (protected)c:\windows\system32\apcups.dll (protected)c:\windows\system32\drivers\apmbatt.sys (protected but not found on this machine)c:\windows\system32\inetsrv\appconf.dll (protected)c:\windows\system32\append.exe (protected)...

Done!

Ending statistics:Protected files found on this machine: 2241Protected files not found on this machine: 848Protected files with indeterminate status: 0Total protected files: 3089


22



QUERY SYSTEMINFO sample output (7)===============================================================================ENV===============================================================================ALLUSERSPROFILE=C:\Documents and Settings\All UsersAPPDATA=C:\Documents and Settings\andy\Application DataBasemake=C:\Program Files\Microsoft SDK\Include\BKOffice.MakBkoffice=C:\Program Files\Microsoft SDK\.CommonProgramFiles=C:\Program Files\Common FilesCOMPUTERNAME=AMR-LAPTOPComSpec=C:\WINDOWS\system32\cmd.exeHOMEDRIVE=C:HOMEPATH=\Documents and Settings\andyINCLUDE=c:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\include\;C:\Program Files\Microsoft SDK\Include;C:\Program Files\Microsoft Visual Studio\VC98\atl\include;C:\Program Files\Microsoft Visual Studio\VC98\mfc\include;C:\Program Files\Microsoft Visual Studio\VC98\include

INETSDK=C:\Program Files\Microsoft SDK\.JAVA_HOME=C:\j2sdk1.4.0_02LIB=c:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\Lib\;C:\Program Files\Microsoft SDK\Lib;C:\Program Files\Microsoft Visual Studio\VC98\mfc\lib;C:\Program Files\Microsoft Visual Studio\VC98\lib

LOGONSERVER=\\AMR-LAPTOPMSDevDir=C:\Program Files\Microsoft Visual Studio\Common\MSDev98...USERNAME=andyUSERPROFILE=C:\Documents and Settings\andyVS71COMNTOOLS=c:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\windir=C:\WINDOWS



QUERY SYSTEMINFO sample output (8)===============================================================================ERRORLOG===============================================================================05/16/2003 08:41:23 ANS1092W No files matching search criteria were found05/16/2003 12:25:48 ANS1107E Invalid option/value: '-CON'

===============================================================================SCHEDLOG===============================================================================Unable to open file 'mysched.log' (it may not exist)===============================================================================POLICY===============================================================================Domain Name : ZHADUMActivated Policy Set Name : STANDARDActivation date/time : 05/12/2003 11:20:14Default Mgmt Class Name : STANDARDGrace Period Backup Retn. : 30 day(s)Grace Period Archive Retn.: 365 day(s)

MgmtClass Name : STANDARDDescription : Space Management Technique : NoneAuto Migrate on Non-Usage : 0Backup Required Before Migration: YESDestination for Migrated Files : SPACEMGPOOLCopy GroupCopy Group Name........: STANDARDCopy Type..............: BackupCopy Frequency.........: 0 day(s)Versions Data Exists...: 2 version(s)Versions Data Deleted..: 1 version(s)Retain Extra Versions..: 30 day(s)Retain Only Version....: 60 day(s)Copy Serialization.....: Shared StaticCopy Mode..............: ModifiedCopy Destination.......: SHADOWPOOL

23




===============================================================================SYSTEMOBJECT===============================================================================stat rc system object---- ---- -------------OK 0000 COM+ Databasen/a 4312 Certificate Server DatabaseOK 0000 Event Logn/a 4312 File Replication Servicen/a 4312 MSCS DatabaseOK 0000 System and Boot Filesn/a 4312 System Volumen/a 4312 Windows NT Directory ServicesOK 0000 Registryn/a 4312 RSM DatabaseOK 0000 WMI Databasen/a 4312 System Staten/a 4312 System Servicessrv 3030 Automated System Recovery



QUERY SYSTEMINFO sample output (10)===============================================================================OSINFO===============================================================================BASIC OPERATING SYSTEM INFORMATION:

OperatingSystem: Windows XP ProfessionalExtendedInfo: YesMajorVersion: 5MinorVersion: 1BuildNumber: 2600PlatformId: VER_PLATFORM_WIN32_NTCSDVersion: Service Pack 1

EXTENDED OPERATING SYSTEM INFORMATION:ServicePackMajor: 1ServicePackMinor: 0VER_SUITE_DATACENTER: NoVER_SUITE_ENTERPRISE: NoVER_SUITE_PERSONAL: NoVER_SUITE_SMALLBUSINESS: NoVER_SUITE_SMALLBUSINESS_RESTRICTED: NoVER_SUITE_TERMINAL: NoVER_NT_WORKSTATION: NoVER_NT_DOMAIN_CONTROLLER: NoVER_NT_SERVER: No

SYSTEM INFORMATION:Processor architecture: x86Number of processors: 1Active Processor Mask: 0x00000001

24



QUERY SYSTEMINFO sample output (11)===============================================================================REGISTRY===============================================================================[SOFTWARE\IBM\ADSM\CurrentVersion]FolderName=Tivoli Storage Manager[SOFTWARE\IBM\ADSM\CurrentVersion]Path=C:\TSM\...[SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\Nodes\ANDY\BABYLON_5]Password=37 14 9f 5b ......[SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\Scheduler Service]TSM Client Acceptor=Client Acceptor Service[SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\Scheduler Service]TSM Remote Client Agent= ...[SYSTEM\CurrentControlSet\Services\TSM Client Acceptor]Type=0x00000110[SYSTEM\CurrentControlSet\Services\TSM Client Acceptor]Start=0x00000003[SYSTEM\CurrentControlSet\Services\TSM Client Acceptor]ErrorControl=0x00000001[SYSTEM\CurrentControlSet\Services\TSM Client Acceptor]ImagePath="C:\TSM\baclient\dsmcad.exe"[SYSTEM\CurrentControlSet\Services\TSM Client Acceptor]DisplayName=TSM Client Acceptor[SYSTEM\CurrentControlSet\Services\TSM Client Acceptor]ObjectName=LocalSystem[SYSTEM\CurrentControlSet\Services\TSM Client Acceptor\Parameters]ADSMClientKey=Client Acceptor Service[SYSTEM\CurrentControlSet\Services\TSM Client Acceptor\Parameters]OptionsFile=C:\TSM\baclient\dsm.opt[SYSTEM\CurrentControlSet\Services\TSM Client Acceptor\Parameters]EventLogging=1[SYSTEM\CurrentControlSet\Services\TSM Client Acceptor\Parameters]ClientNodeName=ANDY[SYSTEM\CurrentControlSet\Services\TSM Client Acceptor\Parameters]PartnerName=TSM Remote Client Agent...[SYSTEM\CurrentControlSet\Services\TSM Remote Client Agent]Type=0x00000110[SYSTEM\CurrentControlSet\Services\TSM Remote Client Agent]Start=0x00000003[SYSTEM\CurrentControlSet\Services\TSM Remote Client Agent]ErrorControl=0x00000001[SYSTEM\CurrentControlSet\Services\TSM Remote Client Agent]ImagePath="C:\TSM\baclient\dsmagent.exe"[SYSTEM\CurrentControlSet\Services\TSM Remote Client Agent]DisplayName=TSM Remote Client Agent[SYSTEM\CurrentControlSet\Services\TSM Remote Client Agent]ObjectName=LocalSystem[SYSTEM\CurrentControlSet\Services\TSM Remote Client Agent\Parameters]ADSMClientKey=Remote Client Agent Service[SYSTEM\CurrentControlSet\Services\TSM Remote Client Agent\Parameters]OptionsFile=C:\TSM\baclient\dsm.opt[SYSTEM\CurrentControlSet\Services\TSM Remote Client Agent\Parameters]EventLogging=1[SYSTEM\CurrentControlSet\Services\TSM Remote Client Agent\Parameters]ClientNodeName=ANDY...===============================================================================CLUSTER===============================================================================ERROR: OpenCluster() failed with Win32 rc 1753



QUERY SYSTEMINFO sample output (12)===============================================================================CLUSTER===============================================================================CLUSTER VERSION INFORMATION

Cluster name: STORMAN2CLUSTERMajor version: 5Minor version: 0Build number: 2195Cluster service vendor ID: Microsoft(R) Cluster serviceWindows service pack: Cluster highest version: 0Cluster lowest version: 0Mixed cluster versions: No

CLUSTER RESOURCESFound object 'STORMAN2WS', type 'NODE'

Found object 'IP Address', type 'RESTYPE'

Found object 'Network Name', type 'RESTYPE'

Found object 'Local Quorum', type 'RESTYPE'Owner: STORMAN2WSGroup: Cluster GroupState: OnlineResource type: 'Local Quorum'Disk signature: 777Device name: 'E:'Volume label: ''Serial number: '6CB45CF1'Maximum file name component length: '255'File system: 'NTFS'Drive letter is sticky: YesResource is removable: NoFile system usable by cluster service: YesFile system is case preserving: YesFile system is case sensitive: YesFile system stores Unicode file names: YesFile system preserves and enforces ACLs: Yes

25



QUERY SYSTEMINFO sample output (13)Found object 'DHCP Service', type 'RESTYPE'

Found object 'Distributed Transaction Coordinator', type 'RESTYPE'

Found object 'File Share', type 'RESTYPE'

Found object 'Generic Application', type 'RESTYPE'

Found object 'Generic Service', type 'RESTYPE'

Found object 'IIS Server Instance', type 'RESTYPE'

Found object 'MSMQ', type 'RESTYPE'

Found object 'NNTP Server Instance', type 'RESTYPE'

Found object 'Physical Disk', type 'RESTYPE'

Found object 'Print Spooler', type 'RESTYPE'

Found object 'SMTP Server Instance', type 'RESTYPE'

Found object 'Time Service', type 'RESTYPE'

Found object 'WINS Service', type 'RESTYPE'



QUERY SYSTEMINFO sample output (14)Found object 'Local Quorum', type 'RESOURCE'

Owner: STORMAN2WSGroup: Cluster GroupState: OnlineResource type: 'Local Quorum'Disk signature: 777Device name: 'E:'Volume label: ''Serial number: '6CB45CF1'Maximum file name component length: '255'File system: 'NTFS'Drive letter is sticky: YesResource is removable: NoFile system usable by cluster service: YesFile system is case preserving: YesFile system is case sensitive: YesFile system stores Unicode file names: YesFile system preserves and enforces ACLs: Yes

Found object 'Cluster IP Address', type 'RESOURCE'Owner: STORMAN2WSGroup: Cluster GroupState: OnlineResource type: 'IP Address'

Found object 'Cluster Name', type 'RESOURCE'Owner: STORMAN2WSGroup: Cluster GroupState: FailedResource type: 'Network Name'

Found object 'Cluster Group', type 'GROUP'

Found object 'Local Area Connection 2', type 'NETWORK'

Found object 'Local Area Connection 2 - STORMAN2WS', type 'NETINTERFACE'

Total resources found: 23

26




===============================================================================FILE===============================================================================...File name: dsmc.exe8.3 name:

File size: 1974339

Created: Thursday 15 May 2003 22:27:46.0134Accessed: Monday 19 May 2003 10:03:31.0919Written: Monday 19 May 2003 10:02:36.0419

File attributes:Archive bit set: YesCompressed: NoDirectory: NoEncrypted: NoHidden: NoNormal: NoOffline: NoRead-only: NoReparse point: NoSparse: NoSystem file: NoTemporary file: No

...



QUERY SYSTEMINFO sample output (16)===============================================================================MSINFO===============================================================================System Information report written at: 05/19/03 10:05:34System Name: AMR-LAPTOP[System Summary]

Item ValueOS Name Microsoft Windows XP ProfessionalVersion 5.1.2600 Service Pack 1 Build 2600OS ManufacturerMicrosoft CorporationSystem Name AMR-LAPTOPSystem Manufacturer IBMSystem Model 265363USystem Type X86-based PCProcessor x86 Family 6 Model 11 Stepping 1 GenuineIntel ~1199 MhzBIOS Version/Date IBM 1EET65WW (1.14 ), 07/16/2002SMBIOS Version 2.31Windows Directory C:\WINDOWSSystem Directory C:\WINDOWS\System32Boot Device \Device\HarddiskVolume1Locale United StatesHardware Abstraction Layer Version = "5.1.2600.1106 (xpsp1.020828-1920)"User Name AMR-LAPTOP\andyTime Zone Pacific Standard TimeTotal Physical Memory 384.00 MBAvailable Physical Memory 182.99 MBTotal Virtual Memory 1.27 GBAvailable Virtual Memory 874.17 MBPage File Space921.86 MBPage File C:\pagefile.sys

27



Crash handler for WindowsNeed first failure data capture

Dr. Watson is a fine debugger, but there is no guarantee that Dr. Watson is installed as the default debugger.

if Dr. Watson is installed, there is no guarantee that it is configured as we would like.

Windows client crash handler logs a record of the crash to dsmcrash.log (all)

creates a user crash dump (mini dump) that can be sent to the lab for post-mortem analysis (all)

displays a pop-up message with information about the crash (GUI)

displays information about the crash on the console (B-A CLI, Admin CLI,dsmcutil.exe)

Exploits the Windows debugging API.



Crash handler for Windows (2)This is the 5.2.0 version of the crash reported in APAR IC36240 (WINDOWS CLIENT WILL CRASH IF THE STGPOOL DEFINED IN THE DEFMGMT CLASS DOES NOT EXIST)

28



Crash handler for Windows (3)Here is what the same crash looks like from the CLI:

C:\tsm520>dsmc i c:IBM Tivoli Storage ManagerCommand Line Backup/Archive Client Interface - Version 5, Release 2, Level 0.0 h14(c) Copyright by IBM Corporation and other(s) 1990, 2003. All Rights Reserved.

Node Name: NOSTGSession established with server BABYLON_5: WindowsServer Version 5, Release 1, Level 6.4Server date/time: 05/14/2003 22:44:57 Last access: 05/14/2003 22:43:29

Incremental backup of volume 'C:'IBM Tivoli Storage ManagerVersion: 5.2.0.0 h14Build date: Tue May 13 21:05:53 2003

dsmc.exe caused exception C0000005 (EXCEPTION_ACCESS_VIOLATION) at 001B:00476022

Register dump:EAX=00000002 EBX=0155EDA0 ECX=00000000 EDX=00000000 ESI=00D94C9CEDI=0017F5D8 EBP=001704F8 ESP=0155ED34 EIP=00476022 FLG=00010293CS=001B DS=0023 SS=0023 ES=0023 FS=0038 GS=0000

Crash dump successfully written to file 'C:\tsm520\dsmcrash.dmp'

Stack Trace:001B:00476022 (0x00548090 0x0017063C 0x00548090 0x001706AC) dsmc.exe

C:\tsm520>



Crash handler for Windows (4)This is the content from dsmcrash.log

--------------------------------------------------------------------------------2003/05/14 21:29:46IBM Tivoli Storage ManagerVersion: 5.2.0.0 h14Build date: Tue May 13 21:05:53 2003

dsm.exe caused exception C0000005 (EXCEPTION_ACCESS_VIOLATION) at 001B:0050A882

Register dump:EAX=00000002 EBX=0185EDA0 ECX=00000000 EDX=00000000 ESI=00DBDEA8EDI=00187D20 EBP=00183AE0 ESP=0185ED34 EIP=0050A882 FLG=00010293CS=001B DS=0023 SS=0023 ES=0023 FS=0038 GS=0000

Crash dump successfully written to file 'C:\tsm520\dsmcrash.dmp'

Stack Trace:001B:0050A882 (0x0066AD58 0x00183C24 0x0066AD58 0x00183C94) dsm.exe

29

IBM Software Group


Volume Shadowcopy Service Support



What is Volume Shadowcopy Service (VSS)?Over time there has been a proliferation of specialized APIs for backing up different Windows components, each with their own unique interfaces.

The goal of VSS is to provide a simple, consistent backup/restore framework that can be used by and for all system components.

VSS-enabled components include writers that coordinate with VSS to make sure that their component-specific data is consistent [for backup].

The backup software (requestor) communicates with VSS. VSS coordinates the snapshot activity.

Microsoft Volume Shadowcopy (or Snapshot) Service (VSS) is an integral part of the Windows XP and 2003 operating systems.

We expect that over time, Microsoft will expect all backup applications to use this service.

30



System object, system state, system services

System state, as defined by Microsoft, refers to:Boot and system files

Active Directory

SysVol

Certificate Server information

Cluster database

Registry

COM+ class registration database

System state should be treated as a single entity for backup andrestore purposes.



System object, system state, system services (2)

System services, again as defined by Microsoft, refers to:Event logs

RSM

Remote Storage Service

FRS

Terminal Server Licensing

WMI

IIS Metabase

System services may be treated individually.

31



System object, system state, system services (3)TSM introduced the term system object to refer to both system state and system services.

Starting with version 5.2, TSM uses VSS to back up system state and system services for Windows 2003.

New file space names SYSTEM STATE and SYSTEM SERVICESwill be created on the TSM server.

While VSS is also available for XP, a complete set of writers for XP is not available. Therefore TSM will continue to use the legacy system object-based backup method for Windows XP.

Since VSS is not available at all for Windows 2000, the legacy backup method will be used for that OS as well.



System object, system state, system services (4)Individual components that are part of the system state will not be selectable for backup or restore.

The primary reasons for this are:Microsoft does not define or document interdependencies that mayexist between these components.

Microsoft recommends that system state components not be treatedseparately for backup/restore purposes.

Components under system services are selectable for individual backup and restore.

The TSM DOMAIN option can now specify SYSTEMSTATE and SYSTEMSERVICES.

32



TSM options for managing system state/servicesThe TSM DOMAIN option can now specify SYSTEMSTATE and SYSTEMSERVICES.

INCLUDE.SYSTEMSTATE can be used to bind the system state AND system service backups to the desired management class.

EXCLUDE.SYSTEMSERVICE can be used to exclude individual system services from backup.

IBM Software Group


Windows Open File Support

33



BackgroundAn open file is a file that is open by one or more applications.

Two facets of open files:Locked

Not locked

Files that are not locked can be opened by another application (including TSM) and thus can be backed up by TSM.

Files that are locked can not be opened by any application (including TSM), and thus can not be backed up.

While support for open files was a long-standing requirement for TSM, the real requirement was for locked files.

TSM 5.2 delivers open (locked) file support.



A brief history

TSM path to open file support (OFS) for Windows starts with image backup, initially available on some Unix platforms.

Image backup requires a stable, non-changing view of the file system. On Unix, the implementation involves unmounting the file system before the backup operation, thereby making the file system unavailable for user/application access. For Windows, such an implementation would not fly.

Logical Volume Snapshot Agent (LVSA) was developed to allow TSM to create a backup of the volume as it existed at a point in time while allowing concurrent access to the volume by users and applications (online image backup).

34



A brief history (2)

Online image backup with LVSA processing:Snapshot of volume is created.

SNAPSHOTFSIDLEWAIT and SNAPSHOTFSIDLERETRIES are used to determine when the volume is idle.

TSM proceeds to back up the volume image.

As applications generate file changes, before the new data blocks are written, LVSA copies the old data blocks to a safe location (the Old Blocks File or OBF).

After volume image is backed up, the snapshot is stopped.

The OBF is backed up.

LVSA is implemented as a Windows filter driver.



A brief history (3)

Hard disk

LVSA

OBF

Application

(1) (6)

(5)(4)

(3) (2)

(1) Application issues a write.

(2) LVSA intercepts write and reads old data blocks.

(3) LVSA writes old data blocks to OBF.

(4) New data is written to disk.

(5) Application issues a read, LVSA reads data from disk.

(6) LVSA passes data to application.

Snapshot copy-on-write

35



Open file support

Open file support builds upon the online image backup technology.

Exploits the LVSA to present the snapshot volume as a new read-only file system on a virtual volume.

LVSA processes read requests to the virtual volumeIf the requested data exists in a block in the OBF, then the read will be satisfied with data from the OBF.

If the requested data is not in the OBF, then the read will be satisfied with data from the real volume.

TSM OFS support works by reading data from the virtual volume. Because this is a separate file system from the OS perspective, files locked on the real FS are not considered locked on the virtual volume.



Open File Support (2)

If selected during install, no further configuration is necessary; all backup and archive operations will use OFS.

INCLUDE.FS x: FILELEVELTYPE=DYNAMIC will disable OFS for volume x:

INCLUDE.FS x: FILELEVELTYPE=SNAPSHOT will enable OFS for volume x: (if OFS support is installed/enabled).

OFS can also be enabled/disabled via the GUI setup wizard.

Enabling/disabling OFS will require a reboot.

If snapshot can not be taken due to volume being too busy, operation will revert to non-OFS.

36

IBM Software Group


Questions?

Thank you!