Migrating the OCS Enterprise Edition Back-End Databases

There is a blog post here: http://blogs.technet.com/dodeitte/archive/2009/06/05/how-to-move-ocs-enterprise-sql-database-to-another-server.aspx

This post outlines the basic process of taking the databases offline, migrating them, mounting them in the new instance and running LCSCMD to update the pool backened.

I recently did this in a production deployment of R2 and actually found a missing step, there was also a post on the Technet forums with a user having the same issue so I figured I would post the updated process here. This may not always be the case, but a key thing to check, and what ended up being the fix in my situation was the actual pool setting in active directory.

I believe the attribute that the below command updates is msRTCSIP-BackEndServer

LCSCmd.exe /Forest /Action:UpdatePoolBackend /PoolName:<pool name> /poolbe:<SQL instance name (machineinstance name)>

When I ran through this process I found that when I opened ADSI Edit and browsed to this attribute it actually had not changed.

adsieditbackenddatabase

The DN For the pool object will be located at : CN=Poolname,CN=Pools,CN=RTC Service,CN=Microsoft,CN=System/Config Container,DC=Domain,DC=com

 

Again this may not always be the case but in my experience this was thef ix for the issue.

tweetmeme_source = ‘winxnetuc’;
tweetmeme_service = ‘bit.ly’;

(140)

If you like it, share it!

    Posted on by admin in LCS, LCS 2005 SP1, Microsoft, OCS, OCS 2007 R2, Unified Communications 2 Comments

    2 Responses to Migrating the OCS Enterprise Edition Back-End Databases

    1. Mac

      Aye, you're right. This took me yonks to find when I first did. I've done this a few times and this attrib has never been updated.

       
    2. Mac

      Aye, you're right. This took me yonks to find when I first did. I've done this a few times and this attrib has never been updated.

       

    Add a Comment