Maintenance work

[sobrique]

Tonight, I will mostly be doing a first SAN attach to a new SAN.
It's very exciting.
However, the 'schedule' as released to our customer reps looks like this:

17:00 Ensure Server connectivity to NEW SAN
17:00 Shutdown server
18:00 Connect server and configure to new SAN
18:00 Test copy data to new SAN.
18:30 Check Data and verify
19:00 Start Data Copy
20:00 Check Copy data and estimate Timings
22:00 Check copy data activity
00:00 Check Copy Data activity
05:00 Check and re-etimate timings
07:00 Check and re-estimate timings, check cluster-partner availability
07:00 Decision to carry on or revert to original system.

Now, as far as I'm concerned, if it takes more than 7 hours to transfer 600Gb SAN->SAN then something's buggered anyway, and we'll be aborting, thankyouverymuch. We have 2 HBAs (host-bus adaptor) in this server. One will be connected to the 'old' SAN transferring data at 1Gb/s (thats giga-bit, not gigabyte). The other will be connecting to the 'new' SAN and transferring at 2Gb/s. Now in an ideal case that means a read rate of 100Mb per second. You never get that, but if it's below 30% (30Mb/sec = 100Gb/hr) then I'll be taking that to mean something's shafted.

Even so, I find it ominous to see any 'plan' than involves activity (by me) at 2 hour intervals, up to midnight, and at 5am.

Comments

[sobrique.livejournal.com]

That's most likely because I post just after getting into work at 08:30 or so.

Either that, or I spam lots.

Maybe both.

[nuala.livejournal.com]

:D