Old Version 5.5 Secondary (partner) node AWOL

Software-based VM-centric and flash-friendly VM storage + free version

Moderators: anton (staff), art (staff), Anatoly (staff), Max (staff)

Post Reply
AlnTech
Posts: 1
Joined: Thu May 07, 2015 3:10 am

Thu May 07, 2015 3:29 am

We have a production system which was never kept up to date due to our current SLA with our customers as we could not get the required down time period.

And like some people who have seen issues with installing "latest versions"/ Patches causing issues without going through testing (as budgets have never been available for extra hardware) we are always reluctant to upgrade to the latest until various possible issues were resolved.

This version suffers from an issue that if either node goes down for any reason (when the hosts are still connected) the other node performs a BSOD, and reboot.

The system is now coming up to being 4+ years old and is starting to suffer from Hardware issues, on the secondary node (partner).

The two nodes are connected to VMware ESXi servers and they are using MPIO to server between the two nodes, we have already had to disable some paths to some of the volumes on the secondary node (Partner) due to Disks failing and RAID 10 volumes issues, and will need to power down various VM's to disable the other paths (as well as possibly re-registering them in vCenter).

The question(s) I have is when this secondary node (partner) goes AWOL, will the primary still work correctly and not fill up with "logs" for transactions, or will we need to delete the HA connections and create them as basic disks, if so how do we convert them to a basic disk image from a HA image. As I can remember doing this once before when we had an emergency down time/Failure.
User avatar
Tarass (Staff)
Staff
Posts: 113
Joined: Mon Oct 06, 2014 10:40 am

Thu May 07, 2015 10:42 am

If you make up your mind to stick with version 5.5, yes, this procedure will require downtime, you'll need to remove HAImage from SW console and re-create it as a standalone device from existing file. Note that even after new device creation, there can be a problem with missing datastore in ESX because of wrong disk shift. Below you will find the guide explaining how to fix this:
http://knowledgebase.starwindsoftware.c ... age-files/
For 5.5 header size is 65536

If you make up your mind to upgrade to the latest version, please follow our upgrade FAQ. Unfortunately, the above mentioned disk shift issue applies to upgrade as well.
Senior Technical Support Engineer
StarWind Software Inc.
Post Reply