|
|
Post by gary1445 on Jan 4, 2019 12:50:21 GMT
This Recovery Tool proves very beneficial in conditions when document libraries become inaccessible, server downtime error occurs or data becomes unusable due to drive failure, bad backups and accidental file deletion from WSS websites. This Tool is well embedded with two file repair modes – Raw mode and Live SQL Instance that enables its user extract files and folders from corrupt MDF database effortlessly and instantly. Sophisticated that effectively repairs inaccessible all MDF files and recovers the database instantly.This Recovery tool hassle free recover SharePoint format using Raw and Live SQL Instance mode. To know more about: www.mannatsoftware.com/stellar-phoenix-sharepoint-recovery.html |
|
|
|
Post by jessewalter375 on Oct 1, 2020 13:19:02 GMT
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:
Configure Mirroring or Log shipping for the following databases between production and DR SQL servers
Content database(s)
Managed Metadata database
UPA profile database
UPA social database
In DR farm provision required web applications with a temporary databases for My Sites and other sites
In DR farm provision a Managed Metadata service application with a temporary database
To test the fail-over process:
Restore all above databases with RECOVERY in the DR SQL server
Attach content databases to web applications in DR farm
Update the Managed Metadata service application in DR farm to point to failed-over production MMS database
Provision a new User profile service application in DR farm and ensure to use the failed-over production Profile and Social databases as you cannot change the UPA databases post-provisioning the service application
Login to the site in DR farm and confirm that all related social and enterprise tagging information is accessible for documents in the document library
Hope this information was helpful to you
Apps4Rent | O365CloudExperts | CloudDesktopOnline
|
|
