Clusterf***

[MarillionFan]

Oo do tell. You can change the names to protect the guilty.

Oh, your terrible.

[MarillionFan]

With databases SY it is normally necessary to update the Live server.

But if you do, the process is to backup right before, notify and disconnect all users, take down application services, update, then bring it all back up after you've run through the process on test.

Anyway that's what I made one client attempt to do this week. They're test box is still down because they can't work out how to restart the service. I'm bloody glad i didn't go gung ho and try my changes on live first.

[suityou01]

With databases SY it is normally necessary to update the Live server.

But if you do, the process is to backup right before, notify and disconnect all users, take down application services, update, then bring it all back up after you've run through the process on test.

Anyway that's what I made one client attempt to do this week. They're test box is still down because they can't work out how to restart the service. I'm bloody glad i didn't go gung ho and try my changes on live first.

You patronising b******

HTH BIDI

[MarillionFan]

You patronising b******

HTH BIDI

No worries.

I'm giving a lesson on how to suck eggs later next week. If you have a granny you'd like to enroll?

[NotAllThere]

I recall when our DB server stopped responding. But the failover wouldn't trigger, because the controller was trying to do a clean shutdown, and couldn't because a process was hanging. So we told our good friend Bob to force a shutdown of the DB server, which Bob was reluctant to do, as it wasn't in the SOP. Eventually, the op manager persuaded him - "Pull the bloody plug out if you have to - JFDI".

Only Bob, didn't. He shut down ALL the servers.

Oh, and naturally, when we tried to bring it all back, the failover db server wouldn't come up. Bob just couldn't work it out. Fortunately, Scotty worked out that one of the network cards had failed, knew how to get in via one of the others, and got that back online somewhat faster than the four hours the datacentre were quoting.

13000 users, around the world, unable to log on for an hour. How we laughed.

[MarillionFan]

I recall when our DB server stopped responding. But the failover wouldn't trigger, because the controller was trying to do a clean shutdown, and couldn't because a process was hanging. So we told our good friend Bob to force a shutdown of the DB server, which Bob was reluctant to do, as it wasn't in the SOP. Eventually, the op manager persuaded him - "Pull the bloody plug out if you have to - JFDI".

Only Bob, didn't. He shut down ALL the servers.

Oh, and naturally, when we tried to bring it all back, the failover db server wouldn't come up. Uhuru just couldn't work it out. Fortunately, Scotty worked out that one of the network cards had failed, knew how to get in via one of the others, and got that back online somewhat faster than the four hours the datacentre were quoting.

13000 users, around the world, unable to log on for an hour. How we laughed.

WTF. Are you Captain Kirk?

[NotAllThere]

No, it was bob who couldn't work it out. Not Uhuru.

[suityou01]

Oi, where's my tags gone?