migrating from one OCS2007R2 install to a new OCS2007R2 RRS feed

  • Question

  • i have ServerA with OCS2007 R2 enterprise with SQL 2005 installed locally. i want to move my test users to ServerB that will also have SQL 2005 install locally. the reason is serverA is overloaded and i need to free it from OCS.

    when trying to install a new enterprise pool to serverB, it gives me an error about the fact that the AD accounts are already created and probably the other adprep/domainprep items already executed from my first install. the error is "Specified back-end for the pool is currently being used by another pool"

    any ideas? i have searched these forums and others. how can i have two enterprise pools using 2007 R2? i can then just swing my test users from one FQDN to the other?

    Wednesday, April 29, 2009 6:45 PM

All replies

  • You must setup a new SQL instance to host the new pool
    If the two pools are running you can easily move users between pools via the Admin tools
    Note  : SQL is supposed to be on another server and not installed on the OCS Server

    - Belgian Unified Communications Community : http://www.pro-exchange.be -
    Wednesday, April 29, 2009 7:20 PM
  • I have tried setting up a new pool on ServerB which is a new SQL instance technically since it's a different server. i get this error

    [0x03EC7819] Back-end specified for the pool is already used by other pools. 

    It then displays the LDAP path of "Backend in use by Pool CN=MyPool,CN=Pools,CN=RTC Service,CN=Services,CN=Configuration,DC=mydomain,DC=net"

    Since this is a semi-test enviroment for only a few users; i wanted to keep the server footprint small but still try out the fully featured enterprise edition.

    Wednesday, April 29, 2009 7:26 PM
  • Did you have another OCS server in the past?
    You may not have removed it correctly from AD and re-used the server name?
    - Belgian Unified Communications Community : http://www.pro-exchange.be -
    Wednesday, April 29, 2009 8:08 PM
  • nope, never had OCS before in the past and i know the servername is unique. My naming convention prevents duplicates. I appreciate you responding to me so quickly; i hope you can get me on the right track. Thanks again

    Wednesday, April 29, 2009 8:10 PM
  • So what is MyPool? Is it installed on Server A?
    Then it seems to be using Server B as SQL Backend...
    - Belgian Unified Communications Community : http://www.pro-exchange.be -
    Wednesday, April 29, 2009 8:18 PM
  • MyPool is the OCS install on ServerA. ServerA has SQL 2005 std installed locally on it as well and that houses the 1st OCS 2007 R2 Databases.

    just to reiterate; i would like a parallel install on ServerB with local SQL 2005 std (i know it's not recommended). So a new pool using a new (local) sql server for it's databases under the same domain. I only have the one forest/domain.


    Wednesday, April 29, 2009 8:20 PM
  • Go to the Admin console and check the pool, then select the Database tab on the right

    Does it say :
    Database Instance Name: (local)\rtc
    - Belgian Unified Communications Community : http://www.pro-exchange.be -
    Wednesday, April 29, 2009 8:28 PM
  • It has the Database Instance Name: localhost

    I was pretty sure about this since i just installed serverB just yesterday from scratch while ServerA has had OCS 2007 R2 installed for about a month or so.

    Wednesday, April 29, 2009 8:29 PM
  • So I suppose it checks for the name "localhost" and tells you that it is already used by a pool and that is correct
    I guess this is one of the reasons that you need SQL on another server...
    - Belgian Unified Communications Community : http://www.pro-exchange.be -
    Wednesday, April 29, 2009 8:37 PM

  • Even if there is only 1 single R2 Enterprise edition server pool in a setup, it is a requirement to set up a separate physical server to provide the backend database services. For R2, it must be SQL Server 2005 SP1 or SQL Server 2008. Multiple different instances can exist on the same SQL server to serve the various R2 server roles / pools. Additionally, a common SQL instance should be configured for OCS front-end servers that belong to the same Enterprise pool.

    I have not tested the setup you described and suspect the conflicts or errors could be due to the database residing on the R2 server itself in an enterprise pool setup, which is not a supported configuration.

    Wednesday, April 29, 2009 8:37 PM
  • something you said sparked an idea.. and i'll be damned.. it worked.

    i was using the database servername of LOCALHOST for ServerB. since ServerA is using the same database servername. So i just went back throug the 'create enterprise pool' and used the ServerB as the servername instead of LOCALHOST and it worked!!

    Anyways; thank you for your help!

    Wednesday, April 29, 2009 8:41 PM

  • By the way, localhost is predefined in the hosts file and points to the machine itself by default ( I would recommend that you modify this or better still, refrain from using localhost as a machine name in the future to avoid similar problems.

    Glad to hear that your issue is resolved. Thanks.

    Wednesday, April 29, 2009 9:20 PM
  • by the way i got all set up. i know have two enterprise pool servers each using their own local sql database.

    Thursday, April 30, 2009 3:30 AM