• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

SLOW restore of 3 Meg of data

tsmerian

ADSM.ORG Member
Joined
Sep 10, 2002
Messages
6
Reaction score
1
Points
0
Website
Visit site
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

ADSM.ORG Member
Joined
Sep 13, 2002
Messages
3
Reaction score
0
Points
0
Location
Roanoke, VA. USA
Website
Visit site
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

ADSM.ORG Member
Joined
Sep 12, 2002
Messages
13
Reaction score
0
Points
0
Location
Tampa,Florida
Website
Visit site
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.
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 18 18.2%
  • Keep using TSM for Spectrum Protect.

    Votes: 61 61.6%
  • Let's be formal and just say Spectrum Protect

    Votes: 12 12.1%
  • Other (please comement)

    Votes: 8 8.1%

Forum statistics

Threads
31,750
Messages
135,360
Members
21,746
Latest member
NasriSaleh
Top