Tuesday, March 5, 2013

Understanding SharePoint Replication Engine - User Profile Recovery

Once the full user profile replication is executed via the replication engine, a folder is  created in the log file location with the prefix Full_. The full replication summary is displayed at the end as below:





















The engine maintains the below files to track status of replication.



Full_Err_Push.log :                      Maintains the exceptions during the process
Full_Err_Push_ProfileIndex.log : Contains the Profile Indexes belonging to the failed user profiles.
Full_Instrumentation.log :            Contains the successfully replicated profile names, including index and the timestamp

Full_Err_Acct.rcv :                     Contains the failed user profile list in the <Domain>\<ProfileName> format. One record per row.


According to the result above there are 595 failed profiles. The SharePoint user profile replication engine has the capability to recover the replication failures which occurred during the full replication.

The command for recovery is Start-SPProfileServiceRecoveryReplication
The format of the command would be:

Start SPProfileServiceRecoveryReplication destination <String> Filename <String> source <String> [-DoSocialReplication <SwitchParameter>] [-DoUpgrade <SwitchParameter>] [-EnableInstrumentation <SwitchParameter>] [match <SwitchParameter> subtype] [-Properties < String []>] [timeout <Int32>]

The recovery needs to find out the failed user profile list, which is included in the Full_Err_Acct.rcv file. 

For an instance we can use the command as :

Start-SPProfileServiceRecoveryReplication -Source http://FarmA/mysitehosturl/ -Destination http://FarmB/mysitehosturl/ -FileName "C:\Program Files\Microsoft\SharePoint 2010 Administration Toolkit\Replication Engine\log\Full_634977620010414201\Full_Err_Acct.rcv" -EnableInstrumentation -DoSocialReplication

On executing the recovery, a folder is created in the log which is prefixed by Recovery_. In it contains the log files pertaining to the recovery process.

No comments:

Post a Comment