none
Two SharePoint Farms, One Fast Server RRS feed

  • Question

  • Hello,

    Here is my setup:

    SharePoint 2010 Farm 1 - 1 User Profile / MySites Web App, 1 "Intranet" Web App, Central Administration

    SharePoint 2010 Farm 2 - Collaboration Web App, Central administration

    FAST Server

    Farm 1 and Farm 2 are logically and categorically separate from each other.  They have no business communicating or sharing information, let alone search results.  Their only similarity is existing in the same network.

    Both farms use the FAST server to provide their search results.  Farm 2 and FAST server were originally created for each other, with Farm 1 being configured for FAST searching at a later time.

    The problem is that searching on Farm 1 will retrieve results from both farms, which is not desirable.  Searching on Farm 2 does not seem to share this problem.

    I have gone through the online documentation from Microsoft that I have found, several other similar questions in the forums, and have so far been luckless in solving the problem.

    I did add a scope to both the query ssa and content ssa on farm 1, which reduced the amount of results from farm 2 by some amount, but did not eliminate them.

    After tinkering I now have no search results (possibly related to doing something to the Search Results web part on the FAST Search Center page of Farm 1's primary web application.

    Anyone with FAST experience, your input would be helpful!

     

    - Matt


    Matt Olson, MS Content Development Specialist MCITP, MCTS
    Monday, April 4, 2011 3:48 PM

Answers

  • Hi Matt

    Here is blog which covers all the steps (and also has a link to the official documentation on the topic):

    http://www.kowalski.ms/2010/07/16/sharepoint-server-2010-enterprise-service-application-publishing-and-consuming-farms/

    Hope that helps

    Regards


    Thomas Svensen | Microsoft Enterprise Search Practice
    Tuesday, April 5, 2011 7:05 PM
    Moderator
  • OK, so at the end of the day, it was not a lack of access, or any problem with the Content or Query SSA's of either farm.  Microsoft does not support using one FAST server to support multiple SharePoint farms independantly but there is, indeed, a way to make it work out.

    It turns out that under a normal searching situation you have either the dropdown that says "all sites," "scope 1," "scope 2," "etc" in it, or you have a plain search box that does not have any other option but the "all sites" scope.  Under normal circumstances you cannot edit this scope at all.  You CAN, however, delete the "all sites" scope...  Once you have deleted it, recreate the scope in a way that it displays the results you want while pointedly excluding the results from the SharePoint Farm, site, web application, or site collection you do not want.  At the end of the day I do not know why I did not think of this, but I guess I must have just assumed that since the scope was not editable then deleting it would have been a bad idea if it was even possible.  I assume that any other scopes created would work in a similar way.

    Let me know if you have any other thoughts on this issue!

     

    - Matt


    Matt Olson, MS Content Development Specialist MCITP, MCTS
    • Marked as answer by M_Olson Tuesday, May 24, 2011 6:08 PM
    Tuesday, May 24, 2011 6:07 PM

All replies

  • Hi Matt

    How did you configure this? Do you do crawling from both SP Farm 1 and SP Farm 2 towards the central FAST installation? If so; that is not a supported configuration, and you will run into various problems, especially if you did not specify different FAST collection names for the two collections (it defaults to "sp"). If both are feeding to "sp", the will effectively overwrite each other's entries, and you may get weird behavior like what you describe.

    The proper way to configure this is by doing all the crawling from one farm. Next, you should set up a trust between the farms (http://technet.microsoft.com/en-us/library/ee704552.aspx) and publish the FAST Query SSA Proxy from the crawling farm to the consuming farm.

    Regards

     


    Thomas Svensen | Microsoft Enterprise Search Practice
    Monday, April 4, 2011 8:11 PM
    Moderator
  • Thomas,

    Thanks for your reply, I believe the situation is actually one where both farms are feeding "sp."  I will look into creating new fast collections as well as the other things you mentioned.

    I will be back to confirm my results!

    - Matt


    Matt Olson, MS Content Development Specialist MCITP, MCTS
    Monday, April 4, 2011 8:17 PM
  • OK,

    I have done the part with exchanging the certificates between the two farms, and now I suppose I have some questions:

    Farm 2 is the original "consumer" of the FAST server, and as such it has FAST Content and FAST Query SSA's.  Does this farm, therefore, keep both of its FAST SSA's, while I delete the same from Farm1?

    Is there supposed to be a way to publish the SSA proxy, as it exists in Central administration?  The server is only providing an option to publish the actual SSA and not its proxy.


    Matt Olson, MS Content Development Specialist MCITP, MCTS
    Monday, April 4, 2011 9:40 PM
  • Is there a guide out there for completing this specific process?  I have tried the publishing method (I created a new content source on Farm 2 and then published the query SSA), but I think  I may have missed a step, somewhere.  I am currently trying the method of creating a second fast collection with separate content and query ssa's on Farm 1, but the crawl is taking forever.  If this does not work, I will try a different angle on the publishing method (this time, re-creating my search center site afterwards).

     

    - Matt


    Matt Olson, MS Content Development Specialist MCITP, MCTS
    Tuesday, April 5, 2011 3:34 PM
  • Hi Matt

    Here is blog which covers all the steps (and also has a link to the official documentation on the topic):

    http://www.kowalski.ms/2010/07/16/sharepoint-server-2010-enterprise-service-application-publishing-and-consuming-farms/

    Hope that helps

    Regards


    Thomas Svensen | Microsoft Enterprise Search Practice
    Tuesday, April 5, 2011 7:05 PM
    Moderator
  • Sadly, this did not work for me.  The Content SSA will not crawl Farm 1.
    Matt Olson, MS Content Development Specialist MCITP, MCTS
    Friday, April 8, 2011 5:45 PM
  • Hi Matt

    Do you know why the Content SSA will not crawl Farm 1? If the user account running the search service has Full Read Access to the web application, this should work fine.

    Regards


    Thomas Svensen | Microsoft Enterprise Search Practice
    Tuesday, April 12, 2011 2:33 PM
    Moderator
  • I do not know.  I set up the Search Service account from Farm 2 to have practically full control over the site collections in question.  I am fairly sure I added the user to Farm 1 at the CA level as well.

    Do I need to have Content SSAs on both farms?


    Matt Olson, MS Content Development Specialist MCITP, MCTS
    Tuesday, April 12, 2011 2:37 PM
  • Hi Matt

    Regular site access rights are not sufficient for crawling. You also need to run this in the SP command shell on the content farms:

    Stsadm -o addpermissionpolicy -url http://rootsite -permissionlevel "Full Read" -userlogin domain\username

    Regards


    Thomas Svensen | Microsoft Enterprise Search Practice
    Wednesday, April 13, 2011 10:45 AM
    Moderator
  • Thomas,

    Thank you for your help but this did not help me either.  I put in a support ticket with Microsoft about this issue, so hopefully they will be able to fill me in.  Maybe there was some crucial early step that I missed and when they walk me through the situation I will be able to mark your suggestions as the answers to this question.

     

    - Matt


    Matt Olson, MS Content Development Specialist MCITP, MCTS
    Wednesday, April 27, 2011 2:14 PM
  • OK, so at the end of the day, it was not a lack of access, or any problem with the Content or Query SSA's of either farm.  Microsoft does not support using one FAST server to support multiple SharePoint farms independantly but there is, indeed, a way to make it work out.

    It turns out that under a normal searching situation you have either the dropdown that says "all sites," "scope 1," "scope 2," "etc" in it, or you have a plain search box that does not have any other option but the "all sites" scope.  Under normal circumstances you cannot edit this scope at all.  You CAN, however, delete the "all sites" scope...  Once you have deleted it, recreate the scope in a way that it displays the results you want while pointedly excluding the results from the SharePoint Farm, site, web application, or site collection you do not want.  At the end of the day I do not know why I did not think of this, but I guess I must have just assumed that since the scope was not editable then deleting it would have been a bad idea if it was even possible.  I assume that any other scopes created would work in a similar way.

    Let me know if you have any other thoughts on this issue!

     

    - Matt


    Matt Olson, MS Content Development Specialist MCITP, MCTS
    • Marked as answer by M_Olson Tuesday, May 24, 2011 6:08 PM
    Tuesday, May 24, 2011 6:07 PM