What is the best way to remove a dead server from a PolyServe Matrix?

[Brian Fitzgerald_1]

We have an 8 node PolyServe 3.6.0 Matrix running the SQL Server utility. One of the nodes had a major hardware failure and is no longer participating in the matrix.

However, it is still defined in the matrix and is still listed as the backup server for about 10 SQL instances. It is not a primary node for any instance.

We do not want to rebuild and rejoin this server to the matrix and would instead prefer to remove it as a backup node and from the matrix configuration entirely.

What's the best way to do this? Can I just rehost the instances that use the server as a backup by removing the node in the host list? Then remove the server from the config? Do I need to devirtualized the affected instances instead? Will any operation complete that concerns this node since the server is not there to notify that it is being removed?

Thanks for any comments or helpful experiences,
Brian

P.S. This thread has been moved from General to Polyserve Solutions. - Hp Forum moderator

[IBaltay]

Hi,
after the failure of the Polyserve cluster nodes, it should be fenced out from the cluster and if any application was active at that time on this server the next backup is now holding it. You are free to remove the cluster node from the cluster completely. And after the completely new cluster node addition and SQL installation on it, you can define it as a backup for any SQL instances. The instances have most probably more then 1 backup so now they should run at other cluster nodes. Thats why the instance has not been devirtualized. You cannot rehost the instance from the failed cluster node. But if it was not the only instance backup it allready failed over to some other instance backup....

[Emil Velez]

you should not de-virtualize the instance.


I think your procedure that you outlined should work.

1. Check the rehost list of each instance and vsql server and remove that node from the list.

2. delete the node from the configuration using the configuration manager.

This should not interrupt any instances that are running.