Re: standby on SAN ? or use internal storage

[Arup Nanda]

Rahul,   The purpose of standby is to failover to it when the primary fails - which could range from the CPU failure to SAN failure. Although modern SANs are pretty robust, you account for the remote chance of failure by building a standby. Placing the database on teh same SAN as the primary does not really buy you any extra high availability feature, does it? You have a single point of failure, the SAN.   So your Standby should use storage not in the same place as the primary. However, using the standby server's internal disks could render your filesystems inaccessible if the server fails. But in some hosts, this is not a problem either; the SAs can mount the internal disks on another machine and recover data - check with your SA. If this is not the case, place the standby database on a different SAN.   So your preffered options are (in descending order)   (1) Primary Server - with two primary instances Primary SAN with the two primary databases Standby server Standby SAN   (2) Primary Server - with two primary instances Primary SAN with the two primary databases Standby server Internal storage on standby server   HTH.   Arup ----- Original Message ----- From: Rahul To: Multiple recipients of list ORACLE-L Sent: Monday, March 24, 2003 12:18 AM Subject: standby on SAN ? or use internal storage list, i'm a bit confused on whether to put the standby DB on the SAN storage or use the internal storage of the standby host !!!   config a two instances on primary server, data-files on SAN, hot standby db files on SAN too. standby instances for both primary on another machine   config b both primary on SAN, standby db files on the itnernal storage of standby machine   any thoughts  ?   TIA Rahul