We do mirror our tape pools.For each pool that has been defined we do
     have a copy tape pool.Actually i wanted to nullify the disk usage
     which would have come down drastically in case of RAID 5.Currently the
     utilization of the HDD space is double.
     I do agree with your statement that RAID 5 is slow for writes but at
     the same time is faster for read.

     Anuvinder


______________________________ Reply Separator _________________________________
Subject: Re: RAID5 Vs Mirroring
Author:  jdbach (jdbach AT WAL-MART DOT COM) at internet
Date:    6/22/01 6:45 PM


Do you mirror your tapes?  If not, that is where I would start to increase
my redundancy.  The DISK storage pools ussually contain data for a short
period of time.  The tapes for a long period of time.

RAID 5 is slow for writes.  Depending on how much data you are moving
through the storage pools, it may be fast enough.  I would never use it.

Jeff Bach

> -----Original Message-----
> From: Anuvinder Chauhan [SMTP:Anuvinder.CHAUHAN AT ST DOT COM]
> Sent: Friday, June 22, 2001 6:57 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      RAID5 Vs Mirroring
>
>      Hi All,
>
>      Currently we are running AIX over RS/6000 with TSM on top of it.This
>      is further integrated to the IBM 3494 library.
>      In the current scenario we have mirroring implemented only for the
> TSM
>      database .I want to built in more redundancy therefore planning to go
>      for RAID 5 implementation.There is no redundancy for the data backed
>      up by the storage pools.Size of the database is around 115GB.
>
>      I would like to know does going in for RAID 5 is a wise decision and
>      what are the implications involved.
>
>
>      Regards
>
>      Anuvinder Chauhan
>      System Administrator
>      ST Microelectronics Ltd.
>      INDIA.


**********************************************************************
This email and any files transmitted with it are confidential
and intended solely for the individual or entity to
whom they are addressed.  If you have received this email
in error destroy it immediately.
**********************************************************************