ISSUE CAUSE In TSM 6.3, there are two possible reasons: 1) The physical memory is too low, 2) The TSM server has been rebooted recently, and the cache hit ratios needs a few days to increase up to 98. SOLUTION Increase the physical memory if it is case 1). Just leave it, the warning should … Continue reading TSM 6.3: Database Cache Hit Ratio Is Too Low →

ISSUE Some events are missed from the results of command ‘q event * * begind=today-1’. CAUSE This is due to the schedule has been updated. SOLUTION This is stupid I think. The workaround I use is to check the activity log by running ‘q actlog begind=today-1 begint=xx:xx:xx endd=today-1 endt=yy:yy:yy’

TSM SQL database restoration method is very flexible. My example is just a small taste of it. Example 1: Restore DB with same name to the same server 1) Delete the table dbo.ChunkData from the ReportServerTempDB to simulate the scenario of data loss. 2) Open flash copy manager on TSM_Client01 and set Replace=True in the … Continue reading TSM 6.3: Restore SQL Database →

There are two  types of backup method in Tivoli Data Protection for SQL Sever: VSS and Legacy. VSS backup only supports Full, Legacy backup supports Full, Differential and Log. VSS backup supports instant restore (volume level), fast restore (file level), but it only can restore the data to the server with same name. Legacy backup … Continue reading TSM 6.3: Backup SQL Database →