Get-CsBackupServiceStatus ErrorState

Before performing an Invoke-CsPoolFailover, it is always a good idea to make sure that the Backup Service is running properly. You should run the cmdlet from both sides to verify that you have

 

Get-CsBackupServiceStatus -poolfqdn pool01.infrastructurehelp.com

 

RunspaceId          : be5ae52b-3f48-4d15-8d36-842d4f5cacf6

ActiveMachineFqdn   : fe01.infrastructurehelp.com

OverallExportStatus : SteadyState

OverallImportStatus : ErrorState

BackupModules       : {UserServices.PresenceFocus:[SteadyState,ErrorState],

                      ConfServices.DataConf:[SteadyState,NormalState],

                      CentralMgmt.CMSMaster:[NotInitialized,NormalState]}

 

 

Get-CsBackupServiceStatus -poolfqdn pool02.infrastructurehelp.com

 

RunspaceId          : be5ae52b-3f48-4d15-8d36-842d4f5cacf6

ActiveMachineFqdn   : fe4.infrastructurehelp.com

OverallExportStatus : SteadyState

OverallImportStatus : NormalState

BackupModules       : {UserServices.PresenceFocus:[FinalState,NormalState],

                      ConfServices.DataConf:[SteadyState,NormalState],

                      CentralMgmt.CMSMaster:[SteadyState,NotInitialized]}

 

Above, you can see that the import on pool01 failed. An issue can occur when moving a large number of users between pools where the databases don’t properly synch up during the moves. In such a case, there might be a user account, or more, that appears in both databases.

 

Microsoft support can provide a copy of the PoolConflictCorrector tool, which reads through the databases and identifies any user accounts that appear on both sides of the environment. If there are any duplicates found, the tool will prompt you to correct each one. This will fix most issues with Backup Service failures.

 

.\PoolConflictCorrector.exe -pool1fqdn pool01.infrastructurehelp.com -pool2fqdn pool02.infrastructurehelp.com -logfile PCC.log

 

Checking data in backend database in both pools…

 

Below entities have pool ownership conflict.

      User mother.goose@infrastructurehelp.com

      User jack.b.nimble@infrastructurehelp.com

 

The tool will find the right ownership for each conflicted entity and ask for your confirmation before correcting the conflict in backend database. Are you ready to continue? Type YES to continue. Type any other to abort: YES

 

User mother.goose@infrastructurehelp.com is owned by pool pool01.infrastructurehelp.com. Please double check and confirm the pool ownership before correcting the conflict in backend database. Type YES to continue. Type any other to skip this entity: YES

 

Conflict for User mother.goose@infrastructurehelp.com have been successfully corrected.

 

User jack.b.nimble@infrastructurehelp.com is owned by pool pool13bdc.schwab.com. Please double check and confirm the pool ownership before correcting the conflict in backend database. Type YES to continue. Type any other to skip this entity: YES

 

Conflict for User jack.b.nimble@infrastructurehelp.com have been successfully corrected.

 

While the issue is fairly rare, the tool is very easy to use and seems to resolve the issue. By the way, the “have” statement in the results is actually the grammar as provided by Microsoft.

Advertisements
This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s