Larry,
Update to the latest release. If the problem persists, open a support case with our support team.
Larry,
Update to the latest release. If the problem persists, open a support case with our support team.
The replicated nodes are currently active on the other server. Can I do the update/reboot whatrver is necessary without any affect on the other? I'm assuming I can. And are the error status of Persistent Reservation Synchronization normal for a period of time after a node crash? What is happening at this time?
Thanks.
First step would be to move the resources back to the proper node, and be sure there are not any problems with this.
Second would be to move all the resources from node2 to node1 and update node2.
Third, move resources to node2 and update node1
Lastly, move resources back to default locations after all updates.
Persistent reservation system has been improved in most current release.
Thank you for the step by step. I appreciate it.
Larry