My potential setup with this TSM server is to add a single Dell MD1000 with 15
750GB SATA drives. I'm currently using all SCSI disk (12TB) and an LTO3
library. No problems yet. I'm just needing more primary storage. The MD1000
does have the option for SAS drives but only in 300 GB drives. I guess I'm
leaning toward the SAS drives and give up some storage space. I can't really
afford a performance hit.
Thanks for all the responses.
>>> Lawrence Clark <Larry_Clark AT THRUWAY.STATE.NY DOT US> 7/12/2007 7:47 AM
In our situation we plan on putting primary storage pools on SATA,
keeping copypools on cartridge because of the constraint that copypools
behave like virtual volumes.
>>> Andy.Huebner AT ALCONLABS DOT COM 07/12/2007 9:32 AM >>>
To me it is not the incoming, but the outgoing that is the greatest
concern. If the next pool is physical tape, be sure you have enough
speed to keep up with your tape drives. If the disks cannot keep up
with the physical tape drives then performance will not be acceptable.
Since many VTLs use ATA disks we know it can be done.
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
Sent: Thursday, July 12, 2007 3:24 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] SATA disk?
I have been doing some extensive testing on the entire disk storage
The first question, is what is the feed? i.e. how many network
does the TSM Server have. I am assuming all your larger systems are
to go LAN FREE direct to tape. Also, what volume are you backing up.
The disk geometry that I have used for testing is 146GB 15K FC, 300GB
FC and the 500GB 7.5K SATA drives. All in RAID 5 configurations,
for the array that they are in. Any cached disk subsystem, will cache
Io writes and to an extent 'hide' disk performance from the host.
with TSM, the sustained high write profile through a backup window
the disk array cache becomes filled with 'write pending' data when
SATA drives. This is data in cache waiting to be destaged, i.e.
the physical spindles. The FC disks showed a write pending amount, but
once the array starts to favour the destage, the disks can keep up-
retaining a good host performance- 4 times that of the SATA.
In this case the disk array usually has to throttle the host, and I
been seeing 50%+ wait_io on the SAR output of the TSM server.
I personnally would advise, for larger systems do not use SATA. It's
profile is more suited to a low IO activuity and certainly not the
susteined IO that is seen during the TSM daily operation.
Also, bare in mind rebuild times on SATA. RAID 6 (dual parity) will
the write down even more, RAID 5 may present a 30 hour + period of
exposure to data in the pools.
Johnny Lea <jlea AT DIS.UMSMED DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
ADSM-L AT VM.MARIST DOT EDU
[ADSM-L] SATA disk?
Has anyone used SATA drives for primary storage. Is it really a bad
Individuals who have received this information in error or are not
authorized to receive it must promptly return or dispose of the
information and notify the sender. Those individuals are hereby
that they are strictly prohibited from reviewing, forwarding,
copying, distributing or using this information in any way.
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and delete this e-mail.
unauthorized copying, disclosure or distribution of the material in
e-mail is strictly forbidden.
Please refer to http://www.db.com/en/content/eu_disclosures.htm for
additional EU corporate and regulatory disclosures.
This e-mail (including any attachments) is confidential and may be
legally privileged. If you are not an intended recipient or an
authorized representative of an intended recipient, you are prohibited
from using, copying or distributing the information in this e-mail or
its attachments. If you have received this e-mail in error, please
notify the sender immediately by return e-mail and delete all copies of
this message and any attachments.
The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and may
contain information that is confidential, privileged, and/or otherwise exempt
from disclosure under applicable law. If this electronic message is from an
attorney or someone in the Legal Department, it may also contain confidential
attorney-client communications which may be privileged and protected from
disclosure. If you are not the intended recipient, be advised that you have
received this message in error and that any use, dissemination, forwarding,
printing, or copying is strictly prohibited. Please notify the New York State
Thruway Authority immediately by either responding to this e-mail or calling
(518) 436-2700, and destroy all copies of this message and any attachments.
Individuals who have received this information in error or are not authorized
to receive it must promptly return or dispose of the information and notify the
sender. Those individuals are hereby notified that they are strictly prohibited
from reviewing, forwarding, printing, copying, distributing or using this
information in any way.