SLOW restore of 3 Meg of data

[tsmerian]

Hello fellow TSM'ers,



I'm losing my hair of this problem... Here's my system:



TSM Server 4.1.3 for MVS

TSM Client 5.1 on Windown NT



The promlem is that it is taking 24 hours to restore 900 files totalling 2 meg of data! This client's data drive is comprised of A LOT of small files (~2K) totalling 50 gigs for the filespace. This totalls A LOT of files. I started a restore at 10am yesterday, and it is now only 1/3 of the way done (about 24 hours). I don't have a good explanation for why it is taking so long. Is it because the are so many files for TSM to look through to find the 3,000 that I need? Would turning collocation of help me?



Any input is appreciated,



Theo Merian

COUNTRY Insurance & Financial Services

 

[mibcf1]

It could be mounts and dismounts that are taking so long. If the data is on many tapes and the mount retention time is high, then that could make the restore take a long time. Look to see if you have a lot of mounts and dismounts. Colocation would possibly help in future restores if what I described is what you have. Just my .02 Maybe someone with a more expert opinion could offer more.

 

[jwsnlutz]

What is the length of time this data has been stored over. Could be alot of tape mounts, but 2 megs of data is small.

I would check the location of this nodes data thru a select statement like this,



select node_name as Node,count(distinct volume_name) as "Number of tapes used" from volumeusage group by node_name



then find which tapes:

xxxx= node name



select volume_name,node_name from volumeusage where node_name='xxxx' group by volume_name,node_name



and that should give you an idea of the amount of tapes the data may be over.

Also check the NIC speed of the client and the TSM server.

I have seen very poor results anytime a NIC has been set to AUTO DETECT.