SAN config

Apr. 28th, 2004 10:58 am
sobrique: (Default)
[personal profile] sobrique
You know, it always rather scares me a little bit when I'm reconfiguring our SAN (Storage Area Network).
It's kinda 9Tb of disk, attached to ... well a lot of our _really ultra critical_ servers.

And so doing configuration operations which are basically unmap, and split apart this volume, rebuild it and reassign it always have the thought of 'now if I'd done that on the _wrong_ volume I'd have completely fucked $SERVER'.

Or worse, done something really stupid like write disable the entire system. That would have been bad too.

Never mind eh? They're brave enough to trust me to do it :).

I have to say, this is yet another situation though, where the GUI is such a bag of arse it's untrue compared to the command line.

example - GUI is java bloaty. To do the job above I'd have to do it in separate stages, and I'd have to wait 1-2 hours for each to complete because it'll not let you interfere in a configuration operation.
So that'd be unmap.
Dissolve device.
Build meta
Map to new FA port.
Configure zoning and volume access.

Would take about 6 hours. (to be fair, the dissolve and build meta are the biggies there).

The CLI I can do the same thing in 3 stages:
unmap (10 minutes)
dissolve and reassemble meta (ok, this still takes time)
Map and zone and access.

But I can do it as a single script, so it 'just does it' rather than me having to babysit it.

Which is nice.
This account has disabled anonymous posting.
If you don't have an account you can create one now.
HTML doesn't work in the subject.
More info about formatting

Profile

sobrique: (Default)
sobrique

December 2015

S M T W T F S
  12345
6789101112
13141516171819
20212223242526
2728 293031  

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Feb. 20th, 2026 02:27 pm
Powered by Dreamwidth Studios