locked
stsadm -o renameserver question in regard to disaster recovery RRS feed

  • Question

  • Started off with:
    SPSQL = Principal
    SPSQL2 = Mirror

    Scenario 1 (What works)
    I have setup SQL mirroring and failing over (principal -> mirror) and (mirror -> principal) works just great with the stsadm renameserver. This example is a what I call a nice fail-over using the ALTER DATABASE dbase SET PARTNER FAILOVER command.

    Scenario 2 (disaster scenario).
    Principal fails hard. I run the ALTER DATABASE dbase SET PARTNER FORCE_SERVICE_ALLOW_DATA_LOSS and then do the stsadm renameserver and I am able to connect to the Mirror which has not became Prinicipal because of the  SET PARTNER FORCE_SERVICE_ALLOW_DATA_LOSS alter command.

    Now here is the issue. I bring my  crashed Principal and drop the mirror and now the SQL Database server is now healthy. Now when I run the stsadm renameserver command I cannot flip back to this SQL server. I get:

    C:\>stsadm -o renameserver -oldservername spsql2 -newservername spsql

    The server spsql2 could not be found in the farm.  This operation is only valid for servers that are joined to the farm.


    So I have spsql2 working and I want to fail back to the crashed prinicpal (SPSQL) after I removed the Mirror from the SQL Databases.


    Is there a -force renameserver ability through maybe a registry hack or something else? I hope this makes sense!!






    Friday, October 24, 2008 6:17 PM

Answers

  • Could you perhaps setup a SQL alias via the cliconfg.exe (SQL Client Config tool), that way the name of the server will stay the same as far as MOSS is concerned.
    .NET Developer, Brisbane, Australia, http://httpcode.com
    Saturday, October 25, 2008 8:12 AM