In this post I will go over on what is needed to successfully fail over to a SharePoint 2010 DR farm and restore content along with social and enterprise tagging information. For this post I will focus on the Content database, and the User profile and Managed Metadata service applications. I assume in your production farm you have a site collection with various document libraries in which social features such as ratings and keywords have already been activated and users have tagged and rated a number of documents. While rating information should be available post fail-over in the DR Farm (the Avg. Rating column in the content database gets synced with the Social database via a timer job) we need to fail-over Managed Metadata and User Profile service applications to provide full access to all existing social and tagging information.
Here are the steps that I would follow to fully test the DR planning:
To test the fail-over process:
Note. User Profile User Profile Replication tool can also be considered as well.