Forum Discussion
I don't think this Mrinal is using a cluster. There is nothing in the original post that would indicate a cluster is being used. If this is not a cluster then the diskgroup needs to be a Secondary diskgroup and not a Clustered diskgroup.
Also the vxclus command mentioned by Mike would not be needed if this is not a cluster.
My main concern here is the location of the D:\ drive letter. Is it on a disk of its own or is it just a partition on the same disk as the OS C:\ drive. VVR will not able to replicate it if it is a partition on the same drive that the OS C:\ drive is on.
In addition to this you will also need additional diskspace to use for the replicator log. Most configurations use a replicator log that is about 20-33% the size of the volume being replicated. But as Mike mentioned the vradvisor utility will help you size the replicator log per your specific requirements.
For the bandwidth, you will need to determine how much bandwidth is actually available. "24mbps shared" typically means that actual bandwidth available for replication is much less than 24mbps. Have your network people tell you the average and peak usage of the link. This should give you an idea of what is available for replication to use without impacting normal traffic on the link. Then as long as Oracle updates the disks at less than this speed, then the bandwidth will be fine. If Oracle is making changes faster than the available bandwidth then replication will fall behind.
You can use VVR compression to maybe increase the amount of data that VVR can replicate beyond the avaialble bandwidth. This feature compresses the VVR data packets before sending them on the network. Some data does not compress very well so VVR will send either the compressed or uncompressed packet depending on which is smaller for the data being sent. I would recommend using using the lastest CP for 6.0 if you are going to use VVR compression.
Thank you,
Wally
Related Content
- 6 months ago
- 9 years ago
- 10 years ago