![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
[...] Why would I need to waste CPU on ASM mirroring when the company has already paid for the device that can do it automatically, with its own CPU? |

#3
| |||
| |||
|
|
Hi, we use the mirroring feature delivered by ASM at two sites. And we do this most of all because of saving money ![]() |
|
Think about a two node RAC, each node sitting in a separate data center at the same building, but in different rooms because of security reasons. Fire or water will destroy normally only one site (hopefully) So, regarding this scenario, you will normally use two storages, one for each data center. Now you have the choice, use the ASM mirroring feature to make all mirroring over both storages or use some build in feature delivered by the storage manufacturer. Last one will often cause expensive investments, because this feature is not cost free. In this case we use ASM mirroring with two failure group, one on each storage. So we have no single point of failure. Bye Joerg |
#4
| |||
| |||
|
|
efore the IT, companies were working like in the opening scene of Monty Python's "Meaning of Life": an army of accountants |
#5
| |||
| |||
|
|
[...] Now, this is a perfectly reasonable explanation: ASM does for free what the storage manufacturer charges for: replication between 2 different SAN devices. Makes perfect sense. How are you satisfied with the performance? That, of course, means that the server CPU cycles are used for disk mirroring. Is it a big burden? The companies that I worked for have usually used external redundancy, provided by the SAN itself plus a standby database, usually in maximum performance mode, to minimize the impact on the primary. In one case, the standby replication went over WAN from Louisville, KY to NYC, NY. It did consume very significant communication resources, completely devouring a T2 line. |

#6
| |||
| |||
|
|
we use the mirroring feature delivered by ASM at two sites. And we do this most of all because of saving money ![]() |
|
So, regarding this scenario, you will normally use two storages, one for each data center. Now you have the choice, use the ASM mirroring feature to make all mirroring over both storages or use some build in feature delivered by the storage manufacturer. Last one will often cause expensive investments, because this feature is not cost free. |
#7
| |||
| |||
|
|
Now you have the choice, use the ASM mirroring feature to make all mirroring over both storages or use some build in feature delivered by the storage manufacturer. Last one will often cause expensive investments, because this feature is not cost free. And ASM does the mirroring out of what? *Thin air? *Doesn't it need ahigh speed interconnect, just like the storage replication does? *It's not included in the cost of Oracle... Sorry, but I don't see why ASM has to be cheaper when it needs the same high performance hardware connection as the storage. And please, don't anyone jump in and tell me that ASM is "highly optimized": it isn't, and that is NOT what I am talking about. |
![]() |
| Thread Tools | |
| Display Modes | |
| |