Hi Daniel,
It took a while before this email got published on adsm.org...
However, I read the message and I wanted to address the specific issue not the
general one with people are complaining about restore times, which they often
do.
To me the key sentence was "The server has a lot of files, almost 7 million
including the copypool".
I'm sure we both would find a suitable solution even if we attacked the problem
from different angles.
//Henrik
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Daniel
Sparrman
Sent: den 7 september 2010 22:44
To: ADSM-L@vm.marist.edu
Subject: [ADSM-L] Ang: Re: Ang: 50Mb restored in 4.18h
Hi there Henrik
I asked a few questions to try to get a pointer.
Concerning my point on TSM performance, Nicklas was the one saying he had the
organisation complaining on TSM for poor performance. Perhaps you should read
his first message, and you'd understand why I said as I said. Scroll down this
message and you will know what I'm talking about (last line)
Regards
Daniel
-"ADSM: Dist Stor Manager" skrev: -
Till: ADSM-L@VM.MARIST.EDU
Från: Henrik Vahlstedt Sänt av: "ADSM: Dist Stor Manager"
Datum: 09/07/2010 09:44
Ärende: Re: Ang: 50Mb restored in 4.18h
Hi,
I am sure everything is configured correct at Niklas site. Test classic vs nqr
restore and you will be suprised.
//Henrik
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Daniel
Sparrman
Sent: den 7 september 2010 09:40
To: ADSM-L@vm.marist.edu
Subject: [ADSM-L] Ang: 50Mb restored in 4.18h
Hi there
To begin with, TSM as a product has no issues with fast restores. If the data
isnt placed correctly, restores might slow up though.
- Did you restore files or files and directories?
- Are you storing directories on tape or in a dedicated diskpool using DIRMC?
- Considering it was only 117 files, the average sice was 427KB. Are you using
collocated tape pools, or is there a chance the files was spread across the
tape?
When a restore takes this amount of time for just a small amount of size/files,
it usually points towards files / directories being spread across the tape.
Usually when doing restores of large fileservers (which I asume this is)
sorting out what needs to be restored on the TSM server-side is what takes
time, but since you got to "Waiting for files" pretty fast, I'd say you have
files/directories spread widely across the tape.
Best Regards
Daniel Sparrman
-"ADSM: Dist Stor Manager" skrev: -
Till: ADSM-L@VM.MARIST.EDU
Från: Niklas Lundström Sänt av: "ADSM: Dist Stor
Manager"
Datum: 09/07/2010 07:02
Ärende: 50Mb restored in 4.18h
Hello
I just did a restore of 50Mb and it took 4h 18min If it had been 50Gb I
wouldn't complain
Total number of objects restored: 114
Total number of objects failed: 0
Total number of bytes transferred: 50.99 MB
Data transfer time:9,426.15 sec
Network data transfer rate:5.53 KB/sec
Aggregate data transfer rate: 3.36 KB/sec
Elapsed processing time: 04:18:55
The server has a lot of files, almost 7 million including the copypool. The
TSM DB is really big, 180Gb and 94% full.
TSM Server 5.5.4.
Does anyone have a clue of why the restore took so long?
It found what volumes to mount fast, but then the client was "Waiting for files
from the server."
People here are complaining about TSM and that the restores takes long time and
it's hard to defend it when the restore takes so long...
Med vänlig hälsning
Niklas Lundström
Niklas Lundström
Storage Administrator
Swedbank AB (publ)
105 34 Stockholm
Telefon: +46 (0)8 5859 5164
Mobil: +46 (0)70 24 76 345
Vi ber dig lägga märke till att detta e-postmeddelande kan innehålla
konfidentiell information.
Om du felaktigt blivit mottagare av detta meddelande ber vi dig informera
avsändaren om felet genom att använda svara-funktionen. Vi ber dig också att
radera e-postmeddelandet utan att skicka det vidare eller kopiera det.
Trots att vi intygar att e-postmeddelandet och eventuella bilagor inte
innehåller virus och andra fel som kan påverka datorn eller IT-systemet där det
mottages och läses, öppnas det på mottagarens eget ansvar. Vi tar inte på oss
något ansvar för förlust eller skada, som har uppstått i samband med att
e-postmeddelandet mottagits och använts.
_
Please note that this message may contain confidential information. If you have
received this message by mistake, please inform the sender of the mistake by
sending a reply, then delete the message from your system without making,
distributing or retaining any copies of it.
Although we believe that the message and any attachment are free from viruses
and ot