Hi @Wael_El_Kamhawy
Restoring an old Sharepoint_Config database backup to the current farm can be a risky procedure and is generally not recommended. The Sharepoint_Config database is a crucial part of the SharePoint environment as it stores the configuration settings for the entire farm, including timer jobs, services, and features.
When you restore an old Sharepoint_Config database backup to the current farm, you may encounter several issues:
Version Mismatch: The restored database might be from a different version or patch level of SharePoint than your current farm. This could lead to compatibility issues and unexpected behavior.
Data Inconsistency: The restored configuration database may contain outdated information, which can lead to data inconsistencies and conflicts with the current state of the farm.
Orphaned Objects: When restoring an old configuration database, orphaned objects may be left behind in the farm, causing errors and potential data loss.
Timer Jobs and Services: The timer jobs and services associated with the restored configuration database may not align properly with the current farm's requirements, leading to job failures or issues with service applications.
Unsupported Scenario: Microsoft does not support restoring a SharePoint_Config database from an older backup to a newer version. Doing so may void support for your SharePoint environment.
Instead of restoring an old configuration database, consider the following steps to troubleshoot and fix the Profile Synchronization issue:
Check ULS Logs: Analyze the SharePoint ULS logs to identify specific errors or warnings related to the User Profile Service. This can provide valuable insights into the root cause of the synchronization problem.
Restart Services: Try restarting the User Profile Service and related services to see if that resolves the synchronization issue.
Check Permissions: Ensure that the service accounts running the User Profile Service have the necessary permissions on the SharePoint_Config database and other related databases.
Review Recent Changes: If possible, review any recent changes or updates that might have been made to the SharePoint farm or the User Profile Service. This can help pinpoint the cause of the synchronization problem.
Apply Patches and Updates: Ensure that your SharePoint farm is up to date with the latest patches and updates. Sometimes, known issues are fixed in newer updates.
Use SharePoint Health Analyzer: Run the SharePoint Health Analyzer to detect and resolve any configuration-related issues in the farm.
If none of the above steps help resolve the synchronization issue, consider engaging Microsoft Support or SharePoint experts to assist with troubleshooting and resolution. They can provide guidance tailored to your specific SharePoint environment and ensure a more reliable solution without risking the integrity of the SharePoint_Config database.
