Hi,

Then again, if you configure these important server to directly write to a 
primary stg pool, with backupstg set to a copy pool, one backup will write to 
two destination at the same time. This will solve the raid 5 overhead and leave 
you with two copies of the "most" important data. 

Regards,

Karel 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
asr AT UFL DOT EDU
Sent: woensdag 21 juli 2004 22:38
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: storage pool raid 1?


==> In article <OF3E4591C3.59EF37FE-ONC1256ED8.004B7645-C1256ED8.004BDA31 AT 
exist DOT se>, Daniel Sparrman <Daniel.Sparrman AT EXIST DOT SE> 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