My concern here is I'm going from SCST 1.0 to 2.0 right?
Upgrading the secondary, rebooting it, then starting failover services will put it back as a secondary node (andthe disk should be in sync) (which should all go ok), I then failover (hold my breath and hope VMWare plays nice with the new build) if all is ok then can't I run in this setup (hit the sync disk button, so drbd keeps the primary node data in sync) for a day or so, incase something shows up.
If I go ahead and upgrade the primary I have no fall back if something does go wrong after a "little" time. I'm then stuck with a dead system, hosting down and having to pay $300 a pop per machine to get support on correcting it. Where I can leave the primary on a known working version (SCST 1.0) and just fail back, at least I don't have a downed environment and I can then work issues though with you guys... calmly.
Yes I'm working on a worst case senario but isn't that what we plan for....
Reply With Quote