As far as I know, the only "requirement" for diskpool is to be big enough to hold 1 day worth of change-data. Obviously, more is better (to a point). We've got a 900GB cache right now, which affords us about 8 days worth of data. We still migrate to tape everyday though. Whether or not you need to RAID the cachepool is kind of a case-by-case basis. In our case, we could afford to lose one day of data out of the cache if a disk failed. The only exception to that is a few big files that go straight to tape anyway.
>>> [EMAIL PROTECTED] 7/21/2004 4:25:07 PM >>> Many shops have the storage pools built on storage where non-raid is not an option. It would be nice to see some storage pool volume sizing reccomendations that don't assume everyone is on 9GB SSA JBOD. Seeing TSM become SFS and SVC aware would be nice as well. [RC] [EMAIL PROTECTED] Sent by: "ADSM: Dist To: [EMAIL PROTECTED] Stor Manager" cc: < [EMAIL PROTECTED] Subject: Re: storage pool raid 1? > 07/21/2004 01:37 PM Please respond to "ADSM: Dist Stor Manager" |-------------------| | [ ] Secure E-mail | |-------------------| ==> In article < [EMAIL PROTECTED] >, Daniel Sparrman < [EMAIL PROTECTED] > writes: > I've seen occasions when disks have failed on a TSM server, and a user calls > to have a single Word document retrieved. You want to be the one explaining > to the user that the disk on the backupserver has failed, and that his/hers > document cannot be restored? :=) "Me too." Additionally, there are increasing amounts of data stored on TSM which are not even "just backups". If you use the DB2 archive log transfer facilities, then between the time you run the log upload and the next time you complete a stgpool backup, your DASD has the only copy of that data in the universe. With a RAID-5 in place and a hot spare, I don't feel too much angst about this, but unmirrored would squick me for sure. We also use TSM as a data store for our content management application; That DASD is in fact the primary data. must must MUST be raided. - Allen S. Rout ============================================================================== IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature. ============================================================================== Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken, or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you.
