You can find a few interesting bits about VERITAS products here.
The following are a couple of tools that we have built that helped us use and maintain VERITAS implementations. Please excuse the lack of documentation and information.
Disclaimer: All scripts/tools are provided as-is, with no guarantees. Please read through the code before use to make sure you understand it's use and function. Please contact the script owner if there are any issues or suggestions.
| Tool | Version | Owner/Contact | Description |
|---|---|---|---|
| createMatrix | 1.6 | Todd Stansell | gather static information about EMC symmetrix config (requires symcli tools available from EMC) |
| cricket | – | See website | a trends-based monitoring tool. Successor to MRTG. |
| cron-edit | 1.10 | Todd Stansell | used mainly for cronjob failover in a VCS environment |
| emcprint | 1.20 | Todd Stansell | complement to vxprint that includes additional symmetrix info (requires createMatrix) |
| jtplex | – | Jon Tourtellot | to convert vxprint output to a comma-separated matrix that can easily be imported into Excel to clearly view the VxVM layout. |
| mirrorRoot | 1.22 | Todd Stansell | mirror the root disks by mirroring A -> B, reinitialize A, then mirroring B -> A. Will now also create swap slice and set dumpdevice. (follows Trantham/Howard theory below) |
| save-vxconfigs | 1.11 | Todd Stansell | a simple tool to save a copy of your VERITAS volume manager configuration information for recovery |
| vxplot | 1.13 | Todd Stansell | converts vxstat data to gnuplot format and plots it (was vxstat2gnuplot) |
| vxtop | – | George Schlossnagle | a script written in python that uses vxstat output to display a "top"-like view (requires threading and curses python modules) |
|
VxOpForce_Encap VxDuplicate |
– | Andrei Ryjov | The scripts are pretty self-descriptive. Take a look at the rest of the tools available at http://spasu.net/Pub |
The following tip is officially unsupported, but also significantly useful way to get VxVM installed on a machine in the least-intrusive way. The idea is that you create a rootdg diskgroup on a simple slice of your internal drives (the more the better, so VxVM can still function if you suffer a disk failure). I was going to put the whole procedure here, but I just checked Doug's tip page and he's got it there (tip #15), so I'll just link to his:
We would also like to thank those of you who participated in our B.O.F. session on Wednesday. It was very interesting to see what kinds of troubles other people are having as well as what kinds of hardware people use.
From what people said, EMC is everywhere, and frequently not by the choice of the technical people. I find that interesting, because, that is the same answer I have heard over and over.
Another point that came out of our discussions is simple - make sure you're running the latest patches, software revisions, and firmware levels. They are much more important than they used to be and it is critical to be using tested configurations, especially in a SAN environment.