This article describes the challenges of keeping valuable hardware-replicated data safe. Being able to access and manipulate the cloned data is crucial and often neglected. This article describes the different types of data replication and the procedure to access a hardware-replicated set of data on Solaris. This article provides specific Solaris Volume Manager tips for system, storage, and database administrators who want get the most of Solaris Volume Manager software in their data centers.
Solaris Volume Manager Performance & Hardware Replication
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Having tested and used the Volume Manager, I found
it a rather flaky product, likely to cause troubles in Murphy like situations. Another brain dead thing is the non
ability to give configured pieces names which actually make sense. Well, one can always have an Excel sheet handy, which maps d1 to /dont/call/me/names. 🙂
I wouldn’t trash the product just because you can’t give easy names to the metadevices you create. I don’t think you would trash linux just because it names devices representing hard drive partitions as hda#/sda# or whatever and you can’t really name it anything different. As for Volume Manager being flaky, please don’t spread FUD based on absolutely nothing. I’ve been using Volume Manager for about 5 years since the days it was called Solstice DiskSuite and all I can say is that it is a very robust and bullet-proof product. Now with soft partitions the Volume Manager is a better value product than Veritas VxVM provided it now comes with Solaris for free.
It’s obvious that you haven’t bothered reading the freaking article as it’s not giving an SVM-specific presentation – SVM and VxVM are given equal attention. Therefore, I am not sure what exactly you’re chveking about.