e i g h t - c u b e d . c o m 

EVA reorg

The EVAs I have here at work were configured a number of years ago (by HP I suspect, with little to no input as to what they were going to be used for). One of them has a single disk group containing multiple storage for multiple Windows, both development and production (eek).

The other contains the application data for the application that runs on OpenVMS, and again, both development/QA and production data are stored on the same disk group.

This was a disaster waiting to happen, and happen it did, with a runaway process on QA causing major performance impact to the production system.

Fortunately, I'd been advocating for a number of years to split production and QA data into separate disk groups, and now (funnily enough) I have the mandate to begin just such a move.

As most of our data disks are in multi-member host based shadow sets, I can do this online with zero downtime. Management was most surprised when I informed them of this (they'd obviously overlooked that point in my previous communications). I pointed out that yes, this was VMS, not that other product that's in use here...