tivoli storage manager version 6.2.2 technical · pdf filetivoli storage manager version 6.2.2...

28.03.2011

1

Advanced Technical Skills (ATS) North America

© 2011 IBM Corporation

Tivoli Storage Manager Version 6.2.2Technical Update

Randy Larson ( [email protected] )Dave Canan ( [email protected] )Advanced Technical Skills


© 2011 IBM Corporation2

TSM Advanced Technical Skills Team� Dave Canan

– [email protected]� Dave Daun

– [email protected]� Tom Hepner

– [email protected]� Randy Larson

– [email protected]

28.03.2011

2



Contents of TSM V6.2.2 Client� Enhancements to ‘SNAPDIFF’

– Unicode support with OnTap 7.3.3 and 8.1– Linux/86 client support for SnapDiff backup

� ASR– Support for

• Windows 7• Windows Vista• Windows 2008 and 2008R2

– Backup– Building WinPE CD

� vStorage API– Add FULL VMware guest backup and restore using VADP– Position for future function



Contents of TSM V6.2.2 Server� New Server functions and options

– See README– http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/topic/com.ibm.its

m.relnotes.doc/readme_server622.html

� DB Reorg Enhancements– See Technote:– http://www-01.ibm.com/support/docview.wss?uid=swg21452146

� APARs– See Technote:– http://www-

01.ibm.com/support/docview.wss?rs=663&q1=apar&q2=server&q3=tsm&q4=version+6.2.2&uid=swg21426379&loc=en_US&cs=utf-8&cc=us&lang=all

28.03.2011

3



Documentation for TSM V6.2.2 Client� V6.2.2 Client Readme

– ftp://service.boulder.ibm.com/storage/tivoli-storage-management/maintenance/client/v6r2/Windows/x64/v622/6.2.2.0-TIV-TSMBAC-README_enu.htm

� V6.2.2 Windows Client Installation and User’s Guide– http://www-01.ibm.com/support/docview.wss?uid=swg27019824

� V6.2.2 Unix and Linux Client Installation and User’s Guide– http://www-01.ibm.com/support/docview.wss?uid=swg27019825



Enhancements to ‘SNAPDIFF’ Processing

Tivoli Storage Manager V6.2.2 Technical Update

28.03.2011

4



SNAPDIFF and Unicode Problem� Backup of files with non 7-bit ASCII name fails for:

– Changed files – New files– Deleted files

� See Technote – http://www-01.ibm.com/support/docview.wss?uid=swg21408335

� DataOnTap 7.3.3– Not supported prior to V6.2.2



6.2.2 New Client Function� File Access Protocol

– Data OnTAP 7.3.3 and 8.1 have a new feature called the "File Access Protocol" on the snapshot difference API

– 8.0 does not contain FAP– Enables snapshot difference to handle file names with 7-bit ASCII

characters as well as non 7-bit ASCII character correctly either via NFS or CIFS.

� V6.2.2 Client enables support for FileAccessProtocol– Allows TSM to backup any files with non 7-bit ASCI– Requires new base snapshot and ‘full incremental” backup– New base required to backup previously skipped files

• See CREATENEWBASE option

� No new server requirements

28.03.2011

5



Combinations with NetApp / nSeries� 6.2.1 client / 7.3.2 DataOnTap

– New, Changed, and deleted files with non ascii file names fail / skipped

� 6.2.1 client / 7.3.3 DataOnTap and FAP– Not formally supported– Undocumented and Untested testflag

� 6.2.2 client / 7.3.2 DataOnTap– New, Changed, and deleted files with non ascii file names fail /

skipped

� 6.2.2 client / 7.3.3 DataOnTap and FAP– All files supported



Testflags� Testflags are

– Not formally tested– Undocumented– Unsupported

� SNAPDIFFONTAPFAP – Allows snapdiff incremental operations on ONTAP version 7.3.3

� SNAPDIFFNAMEFILTEROFF – Files with non-ASCII names are ignored by TSM– NetApp was returning incorrect file names with ONTAP versions lower

than 7.3.3

28.03.2011

6



DataOnTap Migration Possibilities� From non-unicode to non-unicode support

– V7.3 to V8.0 – no difference in function

� From non-unicode to unicode support– V7.3 to V7.3.3 – no difference in function– V7.3 to V8.1 – no difference in function

� From unicode to non-unicode support– V7.3.3 to V8.0 – DataOnTap 8.0 does not contain FAP– TSM client will log a warning message in the error log and TSM

Server activity log



6.2.2 New Client Command-line Option� CREATENEWBASE

– NO (Default)• Do not perform a one-time full incremental even if needed• Return code 8 with warning message even if successful

– IGNore• Do not perform a one-time full incremental even if needed• Return code 0

– MIGRate• Perform a one-time full incremental if needed• return code 0 if the operation completes successfully

– YES• Perform a one-time full incremental with new base snapshot• Return code 0

28.03.2011

7



CREATENEWBASE – full description� NO

– Specifies that, regardless of whether the NetApp Data ONTAP file server was upgraded, a base snapshot is not created. By specifying the createnewbase=no option, snapdiff runs an incremental backup.

– This parameter is the default value. – If you specified the NO parameter and an upgrade to the NetApp Data ONTAP file server

was detected, a warning message is recorded in the error log that warns you to run a full incremental backup. The command ends with a return code of 8 even if the backup finished.

� MIGRate– Specifies that if the NetApp Data ONTAP file server was upgraded to a version that

supports Unicode file names, a base snapshot is taken and a scan-based incremental backup is run. The MIGRate parameter is different from the YES parameter because the MIGRate parameter creates a base snapshot only when Tivoli Storage Manager detects that the NetApp Data ONTAP file server version was updated. The YES parameter creates a base snapshot every time the command is run.

– After the incremental backup finishes, no additional migration-related messages are recorded to the error log or the Tivoli Storage Manager server activity log. When the operation finishes, the command ends with a return code of 0.

– Use the MIGRate parameter if you have upgraded the NetApp Data ONTAP file server to support Unicode but you have not yet run a full incremental backup. The MIGRate parameter is ignored if the NetApp Data ONTAP file server has not been upgraded.



CREATENEWBASE – full description� IGNore

– Specifies that a base snapshot of the NetApp Data ONTAP file server is not created, even when the NetApp ONTAP filer was upgraded to support Unicode file names. Instead, snapdiff runs an increment backup.

– The IGNore parameter is different from the No parameter because Ignore suppresses the warning message. Instead, an informational message is recorded in the error log and the Tivoli® Storage Manager activity log that tells you to run a full incremental backup. If the operation finishes successfully, the command ends with a return code of 0.

– Use the IGNore parameter if you have upgraded the NetApp Data ONTAP file server to support Unicode but you have not yet run a full incremental backup. The IGNore parameter is ignored if the NetApp Data ONTAP file server has not been upgraded.

� YES– Specifies that a new base snapshot is taken and the snapdiff option runs a full incremental

backup. Use this option after you upgraded the NetApp Data ONTAP file server or when you want to back up files that might be excluded. The command backs up any files that were missed because there is a Unicode character in their file name.

– If the operation finished, the command ends with a return code of 0. – It is recommended that you do not set createnewbase=yes for any schedule that runs a

daily backup. A full incremental backup can take a long time to finish. Instead, create an additional, monthly schedule that runs the createnewbase=yes option.

28.03.2011

8



SnapDiff support on Linux� Same configuration considerations as AIX

� RHEL 5.0 and SLES 10 Supported– All supported Linux x86/x86_64 client platforms� Except SLES 11 - not supported by NetApp

� New RPM for Hardware plugin– Install TIVsm-BAhdw.i386.rpm

� Load the NetApp libraries at runtime:– Export LD_LIBRARY_PATH=/opt/tivoli/tsm/client/ba/bin

� NetApp userid / password– User account needs to be added to a group with capabilities:– login-http and api-*



SnapDiff support on Linux� Client Options

– SNAPDIFF (No parameters)– DIFFSNAPSHOT

• Create (Default)– Create a new, persistent, snapshot to use as the source snapshot

• Latest – Use the latest snapshot that is found on the file server as the

source snapshot

� Mount at root of volume– For instance: /net/home1 is the mount point of /vol/vol1 – dsmc i -snapdiff -diffsnapshot=create /net/home1

28.03.2011

9



New ASR Support forWindows Vista, 2008, Win7




ASR support for Windows 2008, Vista, Windows7� New Platform Support for ASR

– x86: Vista, 2008, Win7– x64: Vista, 2008, Win7, 2008R2

� New ASR VSS Writer– Installed with product

� ASR included in System State backup– No need for separate step– Includes:

• ASR backup document• Volume to disk partition GUID map

28.03.2011

10



WIN-PE CD� ASR relies on WIN-PE

� IBM cannot distribute WIN-PE– Need to obtain WIN-PE tools through MSDN

� Also needed:– OPK - Windows OEM Preinstallation Kit– AIK - Windows Automated Installation Kit– CD or DVD burning software



WIN-PE CD1. Create WIN-PE ISO image directory structure2. Add TSM Client to ISO image directory structure

– Open command prompt – Change directory to tsm installation directory

(C:\tsm_images\TSM_BA_Client)– Run ‘dsmc-pe.cmd set’ or ‘dsmc-pe-x64.cmd set’ to prepare TSM

client– Optionally export TSM registry entries

• regedit /e tsmregistry.reg "HKEY_LOCAL_MACHINE\SOFTWARE\IBM

– Copy tsm installation directory to WIN-PE ISO image directory3. Create ISO image using ‘oscdimg’4. Burn CD from ISO image

28.03.2011

11



Rebuilding Windows� Boot from WIN-PE bootable CD� At command prompt:

1. Edit dsm.opt as appropriate– Nodename and other unique settings– Found at X:\Program Files\Tivoli\TSM\baclient

2. Restore System State– dsmc restore systemstate [-asrmode=yes]– (asrmode defaults to ‘yes’ when running on WIN-PE)

3. Mount restored system volume– MOUNTVOL C:\ \\?\Volume{8d587604-54e6-11df-803c-0014a4db5a82}\– GUID found in tsmvolmap.txt in the adsm.sys directory

4. Restore remainder of system drive – dsmc restore \\computer_name\c$\* c:\ -su=yes -repl=yes

5. Copy C:\Windows\BOOT\PCAT\bootmgr file to a hidden partition

6. Boot from newly create drive



Extending vStorage API for VMware


28.03.2011

12



Background� VMware states they will discontinue VCB

– Still available and supported through ESX 4.1

� TSM BA 6.2.0– Uses VADP for file-level proxy backup– Uses VCB for Full backups

• FULLVM staged through proxy disk• Restore using VMware converter

– VADP and VCB can coexist

� TSM BA 6.2.2– Uses VADP for file-level proxy backup– Uses VADP for Full backups

• Direct read from VMDK files for backup• Direct write to VMDK files for restore



Support� Proxy Platforms

– Windows Server 2003 (32 bit and 64 bit)– Windows Server 2003 R2 (32 bit and 64 bit)– Windows Server 2008 (32 bit and 64 bit)– Windows Server 2008 R2 (64 bit only)

� VMware Platforms– ESX / ESXi – 3.5 and 4.0 and 4.1– vCenter - vSphere 4 and VI 3.5

� Existing commands and schedules will continue to work as before

28.03.2011

13



Installing VADP Support

1. Select Custom Install

2. Select VMware Backup Tools



Windows Proxy View of VMware disk

28.03.2011

14



Datastore View of VMware disk



Full Proxy Backup - VCBVM

Guestw/vmtools

C

DC

VMGuest

VMFSTSM

Server

TSM Client

VCBFramework

Backup Proxy

SAN Storage Subsystem

vmdk vmdk vmdk TapeLibrary

Staging Disk

ServiceConsole

ESX Win 2003/2008

TSM STA(Optional)

Snapshot

1

3

4

5

SAN

LAN

6

7

2

28.03.2011

15



Full Proxy Backup - VCB1. BA client invokes ‘vcbMounter.exe’

� ‘vcbMounter’ contacts VMware (vCenter, ESX, etc)2. Invokes vmtools on guest3. ESX creates Snapshot4. VCB copies Snapshot to staging disk on proxy5. BA client reads files in staging area6. BA client sends backup data to TSM server

� Multiple files including control info� Grouped on TSM server in VMFULL filespace

7. Optional use of storage agent



Full Proxy Backup – vStorage API

C

DC

VMGuest

VMFSTSM

Server

TSM Client

vStorageAPI

Backup Proxy

SAN Storage Subsystem

vmdk vmdk vmdk TapeLibrary

ServiceConsole

ESX Win 2003/2008

TSM STA(Optional)

Snapshot

1

3

4SAN

LAN

5

6

VMGuest

w/vmtools

2

28.03.2011

16



Full Proxy Backup – vStorage API1. BA client uses vStorage API

� API contacts VMware (vCenter, ESX, etc)2. Invokes vmtools on guest3. ESX creates Snapshot

�No staging disk on proxy

4. BA client reads VMDK directly through SAN5. BA client sends backup data to TSM server

� Multiple files including control info� Grouped on TSM server in \VMFULL filespace

� Different filespace name on server from VCB backups6. Optional use of storage agent



Auto discovery of New VMware guests� Feature of V6.2.0

– Ability to query vCenter for a list of guests– ESX / ESXi – 3.5 and 4.0– vCenter - vSphere 4 and VI 3.5

� DOMAIN defines guests to be processed for backups– Tivoli Storage Manager uses the domain when processing the backup

vm command without specifying which virtual machines to process� Only one DOMAIN statement for each backup type

– DOMAIN.VMFULL• Creates list of VMs eligible for full VM backups

– DOMAIN.VMFILE• Creates list of VMs eligible for file-leve backups

28.03.2011

17



Auto discovery - DOMAIN.backuptype� ALL-VM

– Selects all virtual machine guests found on vCenter or ESX– Only valid for DOMAIN.VMFULL

� ALL-WINDOWS– Selects all Windows guests

� VMHOST=esx1.ibm.com,esx2.ibm.com– Selects all guests on an ESX host

� VMFOLDER=foldername1,foldername2– Selects all guests with a folder



Configuring VMware Connection� Option ‘VMCHOST’ specifies where to connect

– VMCHOST [address]– vCenter or ESX server

� vCenter / ESX Administrator ID– VMCUSER [option]

� vCenter / ESX password– GUI preferences editor– Command “dsmc set password -type=vcb host userid password”� Note: Not encrypted if coded directly in options file

� TSM connects to VMCHOST and obtains list of all VM guests including– Host ESX server name– OS type– Owning folder

28.03.2011

18



Configuring TSM Client Nodes� File level backup requires the TSM administrator to define a

nodename for the guest and setup proxy node authority– REGister NOde VMGUEST1 password– REGister NOde PROXYNODE password– GRant PROXynode TArget=VMGUEST1 AGent=PROXYNODE

� Backup vm -vmbackuptype=fullvm – Backup occurs as all backups use the same Nodename

� Backup vm -vmbackuptype=file– Backup of VM fails if Nodename and Proxy have not been defined

ANS1662I Agent Node: 'backupproxy1' Target Node: 'shuffle'ANS1532E Proxy Rejected: Proxy authority has not been granted to this node.ANS4150E Incremental backup of Virtual Machine 'shuffle' failed with RC 5722

– These errors appear in server activity log• Visible to TSM Admin without searching client error log



Considerations with VADP fullvm backup� New client options on ‘backup vm’

– VMFULLTYPE = VCB | VSTOR• Default is VCB in V6.2.2• Default will be VSTOR in V6.3

– CBT does not imply Incremental Backup of Images� New option for management class

– VMMC <mcname>� Vmbackdir (VCB only)

– Destination on proxy for fullvm– Ignored with vStorage API

� Vmbacknodelete (VCB only)– Optionally save FULLVM image– Ignored with vStorage API

28.03.2011

19



Considerations with VADP fullvm backup in V6.2.2� No subfile backup

� Client-side deduplication is available– Assuming V6.2 TSM server– Consider server option “CLIENTDEDUPTXNlimit”

� No compression– Except when used with client-side deduplication

� No client encryption

�Positioning for follow-on function



Restore VM views with V6.2.2� VCB

� vStorage API

28.03.2011

20



Considerations with VADP fullvm backup� VADP uses Changed Block Tracking (CBT)

– Effectively ‘used blocks’– No ‘incremental’ backup

� VADP and VCB create different filespaces on server

� Deleting VCB full backups– From BA client:

• dsmc delete group {VMFULL}\TSM\VMFULL\<vmname>• dsmc delete group {VMFULL}* -ina –pick

– From server• dsmadmc delete filespace VMFULL



Restoring FULLVM backups� RESTORE VM vmname

-vmname=newname -datacenter=TivoliARCClab -host=boots.usca.ibm.com -datastore=ds4700_svt

� VMNAME: Virtual machine display name� DATACENTER: VMware datacenter name defined to the

vSphere vCenter� HOST: VMware ESX host server defined to vCenter Datacenter� DATASTORE: Location for volume data and configuration files

28.03.2011

21



Restore GUI



Summary of TSM V6.2.2 Client� Enhancements to ‘SNAPDIFF’

– Unicode support with OnTap 7.3.3 and 8.1– Linux/86 client support for SnapDiff backup

� ASR– Support for: Windows 7, Windows Vista, Windows 2008 and 2008R2– Build and use WinPE CD for recovery

� vStorage API– Add FULL VMware guest backup and restore using VADP– Position for future function

28.03.2011

22



Miscellaneous V6.2.2 Server Updates




First Some New Server Functions in V6.2.2� Support for AIX Version 7.1 is available in Tivoli Storage

Manager Version 6.2.2. � Support for append-only mode with IBM LTO Generation 5� Using larger chunk sizes for data deduplication� Detailed output now available for the QUERY MOUNT

command – QUERY MOUNT format=detailed now include owner, session ID, and

process ID for a mount point. � -New server options for administrative client operations

– ADMINCOMMTIMEOUT – ADMINIDLETIMEOUT

� New parameter REFRESHSTATE for AUDIT LIBRARY� Updated SELECT * FROM DRMSTANZA output

28.03.2011

23



Server DB Reorganization Enhancements




Agenda� Limitations/Shortcomings in reorganization (reorg) processing.� Enhancements/Improvements introduced to improve reorg

processing� Overview of new parameters in V6.1.4.3 / V6.2.2.0 related to

reorg processing� Index reorgs

– Current limitations if index reorgs are enabled– Should you enable them and how?

� Issues still to be addressed in future software levels related to reorg processing

� DB2 utilities related to reorganizations.

28.03.2011

24



Limitations/Shortcomings in Reorganization Processing � Unexpected database growth

– Reasons: • If the machine is under-provisioned, DB2 may not be able to organize the data optimally

and therefore will allow the DB to grow• Even if the machine is properly provisioned, the workload of the TSM server may not

allow time to perform data reorganization. • Incorrect selection of which tables needing to be reorganized sometimes occurred • Indicies were not reorganized• Various DB2 APARs

– IC69506 – DB2 Policy Definitions Do Not Allow for Automatic Reoganization of Indicies

– L175744 – Reorgchk F2 recommends a Reorg even though used space near allocated

– IC70080 Tablespace corruption due to IN-MEMORY POOL CONTROL BLOCK OUT OF SYNCH WITH POOL PAGE 0 IN REGARDS TO LAST INITIALIZED SMP EXTENT

– IC70082 - HWM TOO LOW DUE TO TIMING WINDOW WHEN NEW SMP EXTENT ALLOCATED



Limitations/Shortcomings in Reorganization Processing (cont.)

� Excessive active log / archive log space being used:– Reasons :

• Customers needed to have enough archive log space around to keep 2 cycles of database backups.

• Reorganizations sometimes started when there long running transactions already running (for example a TSM DB backup or a long running backup).

• Sometimes DB2 selected tables for reorganization that didn’t need to be reorganized (thus using extra log space). See slide titled “High level overview of TSM and DB2 Reorg Process”

• Sometimes DB2 would repeat a reorganization that it had already done also using extra log space.

28.03.2011

25



Limitations/Shortcomings in Reorganization Processing (cont.)

� Poor Server performance, or server performance degrading over time.– Reasons:

• Reorganization process is a heavy user of CPU and log space. Before 6.1.4.3 and V6.2.2.0, table reorgs were enabled and could run 24 hours a day.

• Reorgs sometimes started against tables that didn’t need to be reorganized.

• By default, DB2 reorganization and TSM reorganization were enabled at the same time. One or the other should be enabled, but not both. How to disable DB2 AUTO_REORG covered later in presentation.



Enhancements/Improvements That Have Been Introduced to Improve Reorganization Processing

� Unexpected DB Growth should stop or slow significantly.– It is still important that you have a proper provisioned machine– A start time for reorgs can now be specified, as well as a duration that

reorgs are allowed to run. (V6.1.4.3 / V6.2.2.0) � Excessive active log / archive log space being used

– It is now only necessary to have 1 backup cycle worth of archive log space instead of 2. (V6.1.4.1 / V6.2.1.0)

– APAR IC65197 addressed a problem where reorg would start when a long running transaction was currently running. (V6.1.3.2 / V6.2)

– APAR IC67387 introduced the ARCHLOGUSEDTHRESHOLD parameter (V6.1.4.0 / V6.2.2.0). Allows a DB backup to start when Archive Log filesystem utilization reaches define percentage value.

� Server performance degrading over time– More control over when reorganization occurs (V6.1.4.3 / V6.2.2.0)

28.03.2011

26



New Parameters in V6.1.4.3/V6.2.2.0 Related to Reorganization Processing

� ALLOWREORGTABLE– Specifies whether reorgs of tables will be done for TSM DB– Value of YES | NO (default is YES)

� REORGBEGINTIME– Specifies start time for reorg processing– Value specified as HH:MM (default 6:00 AM)– Only applicable if ALLOWREORGTABLE set to YES

� REORGDURATION– Specifies how long reorg processing can run– After each table is completed, this value is checked to see if next can

start

This parameters needs a server restart, they are not available with setopt



“High level” simplified overview of TSM and DB2 Table Reorg Process

ReorgBeginTime

API call done to DB2 to query which tables are eligible to be reorganized

API call to DB2 to reorganize first table in list

ReorgDuration Reached? YesDONE

No

API call to DB2 to reorganize next table in list

28.03.2011

27



Index Reorganizations (new in V6.1.4.3 / V6.2.2.0)� Be aware of limitations if index reorganizations are enabled in

V6.1.4.3/V6.2.2.0– Index reorgs cannot be paused if enabled. – The thread that does the index reorg is the same thread that monitors to see if

an automatic backup is needed. Because of this, automatic monitoring of the need for a DB backup is not done. Customers doing an index reorg must manually kick off a DB backup if needed.

– Index reorgs will generate lots and lots and lots of archive logs. Additional archive log space (and possibly failoverarchivelog space) will be needed.

– It is still possible, due to current DB2 code levels, that after an index reorganization is finished, DB2 may decide it needs to be reorganized again.

� Should you enable index reorganizations for these levels ?– Work with TSM support if you think you need to do this. DB2 utilities can help

here to decide if this is needed. They will provide guidance on how to enable them, and assist in deciding if it is needed.



Issues still to be Addressed in Future Software Levels Related to Reorganization Processing.

� There are still several issues to be resolved with DB2 and reorganizations– Some will be addressed in V6.1.5 / V6.2.3

• Allow index reorgs to be paused• Pausing of index reorgs will allow DB backup to occur if needed• Proper selection of which tables needing to be reorganized.• Others documented in Technote:

http://www.ibm.com/support/docview.wss?uid=swg21452146

– Others will not be addressed until a future release of TSM, when a new release of DB2 is available.• One example here is release of free space in tables and indicies after a reorganization

has occurred.

28.03.2011

28



DB2 Utilities/Commands/Parameters Related to Reorganizations.

� DB2 Auto_Reorg configuration parameter� db2dart utility� db2 reorgchk command� db2pd –reorgs –db tsmdb1 utility



DB2 Utilities/Parameters Related to Reorganizations. (cont)� DB2 Auto_Reorg configuration parameter

– Either TSM reorgs should be enabled OR DB2 reorgs, but not both.– If ALLOWREORGTABLE is set to YES, then db configuration

parameter AUTO_REORG should be set to OFF. • This can be examined by doing:

db2 connect to tsmdb1db2 get db cfg for tsmfb1 (look for setting of auto_reorg parameter)

– If it is set to ON, disable it by: (TSM restart needed)db2 connect to tsmdb1db2 update db cfg for tsmdb1 using auto_reorg OFF

– Documented in APAR IC73978 . See:• https://www-304.ibm.com/support/entdocview.wss?uid=swg1IC73978

28.03.2011

29



DB2 Utilities/Parameters Related to Reorganizations. (cont)� db2dart utility

– Lots of output provided here; for now, we are only looking at one part to see if a reorg might be needed. We are interested in seeing if there are any free extents below the HWM that are available.

– Do the following commands from a DB2 Command Processor. For each of the following commands, it will prompt for a table space ID. Enter the number inside the brackets of the filename for the tablespace ID.db2dart tsmdb1 /dhwm /RPT dart_tsid{2}.outdb2dart tsmdb1 /dhwm /RPT dart_tsid{4}.outdb2dart tsmdb1 /dhwm /RPT dart_tsid{5}.outdb2dart tsmdb1 /dhwm /RPT dart_tsid{6}.out

– Look at the end of the report for lines beginning with ‘Number of’. Example:

Number of free extents below highwater mark: 0Number of used extents below highwater mark: 7817



DB2 Utilities/Commands/Parameters Related to Reorganizations. (cont)

� “db2 reorgchk current statistics on table all” command– There are a total of 8 formulas applied against tables / indices to see if

they need to be reorganized. (3 formulas are used for tables, and 5 formulas are used for indicies) In the output from reorgchk, an * in the REORG column for that formula means that the table might benefit from a reorganization. For indices, only formula 5 is important to look at.

– Lots of output provided with the reorgchk command; See the DB2 command reference on how to interpret.• http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=/com.ibm.db2.luw.

admin.config.doc/doc/r0011479.html– Do the following commands from a DB2 Command Processor.

db2 connect to tsmdb1db2 reorgchk current statistics on table all > reorgchk.txt

– Support should be contacted if the customer wishes to enable index reorgs.

28.03.2011

30



DB2 Utilities/Commands/Parameters Related to Reorganizations. (cont)

� db2pd –reorgs –db tsmdb1– Provides a history of reorg activity.– Look at the Status column in the output. A value of ‘Started’ in that

column indicates a reorg for that table / index is currently in process. A value of ‘Done’ in that column indicates it is finished, and the line of output will also indicate when it finished.

– TSM activity log will also issue messages indicating tables / indicies that have been reorganized 10-01-2011 11:37:13 ANR1806I Table reorganizing and updating statistics

performed successfully for Backup.Objects. (SESSION:3196)

10-01-2011 11:43:20 ANR0294I Reorganization for table Backup.Objects ended.– Lots of output provided with the db2pd command; see the DB2

command reference for more information:• http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=/com.ibm.db2.luw.

admin.config.doc/doc/r0011479.html– Do the following commands from a DB2 Command Processor.

db2pd –reorgs –db tsmdb1 > db2pd.reorg.txt



Server Reorganization Enhancements - Summary� Many issues/limitations existed with Reorgs

– Some have been addressed before V6.2.2.0/V6.1.4.3– Some important enhancements were addressed at V6.1.4.3/V6.2.2.0– Limitations still exist - some improvements are yet to come.

� DBs cannot be reduced in size currently due to APARs that are opened against DB2.

� Index Reorgs introduced with V6.1.4.3/V6.2.2.0– Not enabled by default– Customers should work with support if they want to try this

• DB2 utilities exist to help in this area.• Support also have scripts as well to help interpret output

tivoli storage manager version 6.2.2 technical · pdf filetivoli storage manager version 6.2.2...

Documents