Log Shipping Content Databases in SP2010 and refreshing the listing of site collections

There seems to be a little bit of confusion about what happens to your sites tables/listing of sites when you're log shipping content databases in SharePoint 2010. Let's imagine this scenario. Let's say you create a site collection in your production/live farm. The site provisioning process creates an entry in the sites table in your config DB. The next time the logs get shipped, the site collection will be in the content database in your standby farm. Since you're not log shipping the config DB (it's unsupported) you won't get an entry for your new site in your standby farm. Many places say that you need to detach and reattach your content databases in your standby farm. While this will work, it's not true. You can use PowerShell to make this happen automatically. You could also access the RefreshSitesInConfigurationDatabase method with the SharePoint OM if you want as well.

$db = Get-SPDatabase | where {$_.Name -eq "DatabaseName"}

Comments (2)

  1. mcodyw says:

    I think the reason why there is still confusion is because this authoritative Technet article hasn't been rewritten for 2010.  


    Thank you for the update.  

  2. Ron Grzywacz says:

    I suggested we create a version of that SP 2007 document for SP 2010 this morning. I know it's a little late, but we'll see what happens.

Skip to main content