Re: [ADSM-L] TDP for SQL gui takes 20 min to display inactive
2012-12-22 04:20:28
Hi Steve.
Check to make sure that the node has backdel=yes specified. I had one
SQL server that was on a legal hold for 4 years and the restore screen
took that long to come up because of the large number of objects. If
backdel is set to no, the logs won't be getting deleted and that may
account for the large number of objects you are seeing.
Regards
Steve
Steven Harris
TSM Admin
Canberra Australia.
On 22/12/2012 12:26 AM, Schaub, Steve wrote:
Tsm server 6.2.4.0
Tsm client 6.2.3.0
Tdp client 6.3.0.1
Windows 2003EE x64
Our DBA's are complaining that when they have to use the TDP gui to restore older
databases by selecting "active/inactive", it sometimes takes 20+ minutes for
the list of databases to refresh.
My first suspicion was that the meta data had somehow gotten off to tape, but I
have confirmed the primary data is all on disk (ST03_DISK_P04), only copypool
(ST03_TAPE_C04) is on tape.
Any ideas what would cause this behavior?
tsm: TSMBCP01>q occ archer_sql ARCHER\COMPOUND\meta*
Node Name Type Filespace FSID Storage Number of Physical Logical
Name Pool Name Files Space Space
Occupied Occupied
(MB) (MB)
---------- ---- ---------- ----- ---------- --------- --------- ---------
ARCHER_SQL Bkup ARCHER\CO- 12 ST03_DISK- 142,148 555.27 662.44
MPOUND\m- _P04
eta\0000
ARCHER_SQL Bkup ARCHER\CO- 12 ST03_TAPE- 141,452 374.17 374.17
MPOUND\m- _C04
eta\0000
tsm: TSMBCP01>q stg st03_disk_p04
Storage Device Estimated Pct Pct High Low Next Stora-
Pool Name Class Name Capacity Util Migr Mig Mig ge Pool
Pct Pct
----------- ---------- ---------- ----- ----- ---- --- -----------
ST03_DISK_- DISK 100 G 2.5 2.5 70 50 ST03_TAPE_-
P04 P04
Steve Schaub
Systems Engineer II, Windows Backup/Recovery
BlueCross BlueShield of Tennessee
-----------------------------------------------------
Please see the following link for the BlueCross BlueShield of Tennessee E-mail
disclaimer: http://www.bcbst.com/email_disclaimer.shtm
|
|
|