locked
Two SharePoint server Farms using different configuration databases with same content DB's RRS feed

  • Question

  • Hi everyone,

    I am having strange problem while cloning the environments for SharePoint 2007 farm. We cloned the WFE and DB servers with different names. When the configuration wizard has run pointing to the new DB server for complete the new FARM, The config is pointed to the new Database server but the content databases remains same as old. This makes the production and cloned sites pointed to the same content.

    How can this be possible to have a SharePoint farms with separate config DB's and same content DB's. Please advise and now the search service in the production is also broken.


    Thanks keshav,Share point Developer


    • Edited by kesav7902 Thursday, February 6, 2014 1:44 AM more details
    Thursday, February 6, 2014 1:43 AM

Answers

  • Hi,

    This is one reason  why you should always use SQL Aliases when configuring SharePoint 

    Stop the SharePoint Services, you can use Server Manager on the WFE

    From the command line

    1. Enter CLICONFG
    2. Highlight TCPIP, Click Enable
    3. Click on the Alias Tab, and Click Add
    4. Click the TCPIP Radio Button
    5. Enter the (Old Database Server Name) in the Server Alias Box
    6. Enter the (Cloned Database Server Name) Server Name in the Server Name Box
    7. Uncheck, Dynamically Assign
    8. Enter Port 1433, and Click OK. Make sure on your new SQL Server that you don't have an inbound rule blocking Port 1433.
    9. On the new Cloned Server WFE start the SharePoint Services
    10. Run IISReset
    11. On The WFE and the App Server. Start the SharePoint Services, you can use Server Manager

    I would normally test this by stopping the SQL Service on the Old Server and login to SharePoint on the Cloned Server...

    Cheers,


    -Ivan

    Thursday, February 6, 2014 10:32 AM

All replies

  • Hi,

    This is one reason  why you should always use SQL Aliases when configuring SharePoint 

    Stop the SharePoint Services, you can use Server Manager on the WFE

    From the command line

    1. Enter CLICONFG
    2. Highlight TCPIP, Click Enable
    3. Click on the Alias Tab, and Click Add
    4. Click the TCPIP Radio Button
    5. Enter the (Old Database Server Name) in the Server Alias Box
    6. Enter the (Cloned Database Server Name) Server Name in the Server Name Box
    7. Uncheck, Dynamically Assign
    8. Enter Port 1433, and Click OK. Make sure on your new SQL Server that you don't have an inbound rule blocking Port 1433.
    9. On the new Cloned Server WFE start the SharePoint Services
    10. Run IISReset
    11. On The WFE and the App Server. Start the SharePoint Services, you can use Server Manager

    I would normally test this by stopping the SQL Service on the Old Server and login to SharePoint on the Cloned Server...

    Cheers,


    -Ivan

    Thursday, February 6, 2014 10:32 AM
  • Thanks for the reply. It worked for us.

    Thanks keshav,Share point Developer

    Tuesday, February 18, 2014 10:56 PM