Upgrade is causing problems

[Divyash]

Hello -

I just upgraded from 5.7 to 5.8 and when I recreate my HA images, everything goes well except when I try to remount the drive on a windows server. I go to Computer Management and I see the drive there, however, I am being prompted to format the drive. Problem is, I have data on that drive. How can I get around this?

Thanks,
Divyash

[Anatoly (staff)]

Hello Divyash,

Could you please tell us what device type are you using? What were the exact steps of the upgrade procedure (have you disconnected from targets first, have you rebooted anything, etc.)?

[jeffhamm]

When you upgrade from V 5.7 to V 5.8, is it required to "recreate the HA images", or just take them offline for a short time during the upgrade process? Is there a PDF of the release notes / upgrade procedure for moving to 5.8?

Thanks,
Jeff

[Anatoly (staff)]

Please see the whole procedure of upgrading to version 5.8 below:

Installation notes

Installation: Previous versions can be updated by installing this version over the existing installation.
Warning: CHAP authentication is not supported for HA device images created in 5.4 and older versions of the software.

Warning: The existing HA devices cannot be upgraded to version 5.8 without bringing the storage offline for a short time.
Please, take the following steps to update the existing HA devices:
1. To prevent data loss, disconnect clients from HA (if it is possible).
2. Update StarWind service on the first HA node. Wait until the service starts. At this step the HA node is unable to synchronize its HA devices and is not accepting the client connections. Client requests are processed by the second HA node. The next step will disconnect the existing client connections.
3. Update the StarWind service on the second HA node. Wait until the service starts.
4. Start synchronization on the first HA node. The second node changes its state to “ready” and starts processing client connections. Now, you can safely connect to the HA device.
5. Wait for synchronization to finish. Now the first HA node can process the client connections too.

[jeffhamm]

So just to clarify, you do NOT have to recreate your HA targets, only take them offline for a short time period, correct?

[Anatoly (staff)]

100% correct

[jimbul]

Just to confirm -

Once both nodes are updated with 5.8, On the first node we initialise full synchronisation (copy data to this device from partner).

At this point, the second node starts servicing client connections (as it is marked as good) and the first node initiates a full copy over of all data from the second (last to be upgraded) over the sync channel.

Sorry if this seems repetitive, just want to get this absolutely right!

Many thanks.

Jim

[Anatoly (staff)]

And correct again!:)

[jimbul]

Implemented, no problems, sync back took 4 hours, but that is around 3 times faster than under 5.7 as saturates both sync channels and sustained read/write seems even better than before now you've lost the ms transport. Really impressive.

[anton (staff)]

Nice you've confirmed this one as working. Thank you!

Implemented, no problems, sync back took 4 hours, but that is around 3 times faster than under 5.7 as saturates both sync channels and sustained read/write seems even better than before now you've lost the ms transport. Really impressive.