Yes we had this problem it would take 4+ days to restore a 200k file from a
backupset. Version 4.2.2.13 fixed this issue.

IC34528 TSM RESTORE BACKUPSET IS EXTREMELY SLOW ON WIN2K BECAUSE OF 
        ILLEGAL LENGTH INDICATOR CAUSED BY MISMATCHED READ LENGTH.

But if you are going to upgrade, I suggest going to one of the version 5's
so you can get support. We are running server version 5.1.6.3 on windows
with little to complain about.

Hope it helps, 
Mark Bertrand

-----Original Message-----
From: Sascha Braeuning
[mailto:Sascha.Braeuning AT SPARKASSEN-INFORMATIK DOT DE]
Sent: Friday, December 12, 2003 7:22 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: bad performance when restoring single files from a backupset


Hello,

I performed a backupset from one of our servers (Windows NT). The backupset
was generated on a HP Ultrium LTO drive, which is conected to the TSM
Server (also Windows NT TSM Version 4.2.2.0) via SCSI. The generation
process of the backupset ran 2,5 hours. Now I tried to read the contents of
the backupset (q backupsetcontents). The read process takes more than one
day!! When I think of restoring a single file from this backupset, I get
crazy!

Can anybody help me or has an explanation of such a difference between
backing up and restoring?

Mit freundlichen Grüßen

Sascha Bräuning
DB/DC C/S-Systeme/Überwachungsverfahren FE/KA

Sparkassen Informatik GmbH & Co.KG
Wilhelm-Pfitzer-Straße 1
70736 Fellbach
Telefon: 0711/5722-2144
Telefax: 0711/5722-2147
Notes: Sascha Bräuning/6322/FE/SI/DE@Sparkassen-Informatik
E-Mail: sascha.braeuning AT sparkassen-informatik DOT de