Upgrading from 4622 to 5087.

[AdStar]

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....

Cheers
Ad

[Gr-R]

Using the instructions above, you will have minimal downtime, and minimal data to sync. Your way, you may need to sync the entire VG.
SCST 2 has been available and in use since build 4786, as well as in ESX4.x. So it plays just fine.

[AdStar]

Just a quick update, upgrade worked flawlessly, primary and secondary nodes have been upgraded.

Everything seems to be nice and stable, will run some iometer checks next maintenance window.

Thanks for your help Gr-R

Cheers
Ad

[Gr-R]

Just a quick update, upgrade worked flawlessly, primary and secondary nodes have been upgraded.

Everything seems to be nice and stable, will run some iometer checks next maintenance window.

Thanks for your help Gr-R

Cheers
Ad

woot !

Let us know how your test turn out.