Old Version 5.5 Secondary (partner) node AWOL
Posted: 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.
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.