Lync server 2013 Backup Service Error EVENT ID 4049 – After File Share Migration

Dare PojuSkype for business Solutions Architect
Lync server 2013 or Skype for business Backup Service Error ID 4049 – After File Share Migration

Microsoft's TechNet documentation does a great job explaining how to migrate the Lync/Skype for Business server / pool file share to a new location, but one still needs to address backup issues or errors that occur with pools that were paired that may still be referencing the old file share directories during exporting and importing of data forth and back.

The backup service synchronizes Lync data in paired front end pools. The backup service is crucial for disaster recovery of a pool that is paired with another pool located in a different location in case there is a failure. It actively writes and consumes data like CMS stores, buddy lists or conference directory IDs from its own pool file share location -- the heart of the backup process. Since each pool will have its own file store, the backup service on pool A will copy (export) the data into the file share location of pool B, and the pool B will equally do the same thing. You can use get-csbackupserviceconfiguration to find out the maximum allowed data it can export and import and the how often it does the exporting and importing.

At one of my client's locations, after the migration of the Lync Server 2013 file share from one storage location to another, we started seeing the error displayed in the image below on the front end Server (CMS Master) from the backup pool.

If you have just completed a file share migration from one file store location to another as documented here [u][/u] (or using any other good instructions from the Internet) you may still be getting error event ID 4049 from the front server of the paired pool if you have done pool pairing.

C--Users-oa30914-Desktop-Issues-and-.pngYou notice when you run (Get-CsBackupServiceStatus -PoolFqdn for Import Status, you will get “ErrorStatus” for identity such as ConfServices.DataConf depending on the identity associated with what is referenced in the event ID error.

Reason: The backup pool servers are still able to locate the old file share directory on the network that is no longer present in the topology, or while looking into the new file share location, it saw a temp file that points to old file share. That is causing the backup pool backup service import to fail.


I found this error very common  after File share Migration and Every time, I have been able to resolve it by deleting or cut and paste all the .tmp files from X-WebServicesXX\CollabJournal of new File share folder to somewhere else using my comment found here on TechNet : [u][/u]

If you open those .tmp file, one of them has a pointer to the old file share and so the backup pool backup service will be reading the content of that file and reporting same in event ID 4049.  But deleting this file, will allow the backup service of the pool u migrated its file share to create new files into that Collab journal location, that wont point to old fileshare directory anymore. Note that sometimes, there are lots of white ( .tmp) files, but If you successfully find it and open the culprit .tmp file you are looking for, you will observe this. The moment you remove that file or relocate it the backup service from backup pool will adjust and fix itself - it works like a charm. When you run Get-CsBackupServiceStatus -PoolFqdn | select -ExpandProperty BackupModules again for the pool that was showing its importstatus as ErrorState for previously, it will show "NormalState"

Here is the Sample of file the Culprit file when you open it:

<Journal Id="738de5aa-b39f-4dd0-8136-6bdbc9b983d8" Root="\\\New_FileShare\1-WebServices-68"><JournalEntry Id="d0fa76c8-f47c-47ae-a13e-114f68e4d790" Index="1" CreationTimeUtc="12/13/2016 19:32:16" ChangeType="Deleted" Path="\\\OldFileShare\1-WebServices-68\CollabMetadata\{634663CF-EE44-4CAD-B603-67B1EC5F83F8}\JYKZLYG5\Serialized.dat" LastWriteTimeUtc="12/13/2016 19:32:16"/><JournalEntry Id="6197d70d-690c-4906-b133-4fa5045d142d" Index="3" CreationTimeUtc="12/13/2016 19:32:16" ChangeType="Deleted" Path="\\\OldFileShare\1-WebServices-68\CollabMetadata\{634663CF-EE44-4CAD-B603-67B1EC5F83F8}\JYKZLYG5\SerializedBackup.tmp" LastWriteTimeUtc="12/13/2016 19:32:16"/><JournalEntry Id="bf4e5d15-8a04-4d54-9461-cac8895abb4d" Index="5" CreationTimeUtc="12/13/2016 19:32:16" ChangeType="Deleted" Path="\\\OldFileShare\1-WebServices-68\CollabMetadata\{634663CF-EE44-4CAD-B603-67B1EC5F83F8}\JYKZLYG5\SerializedWebContent.dat" LastWriteTimeUtc="12/13/2016 19:32:16"/><JournalEntry Id="e85f2a64-51aa-4953-80ea-62311b20dc0b" Index="7" CreationTimeUtc="12/13/2016 19:32:16" ChangeType="Deleted" Path="\\\OldFileShare\1-WebServices-68\CollabMetadata\{634663CF-EE44-4CAD-B603-67B1EC5F83F8}\JYKZLYG5\SerializedWebContentBackup.tmp" LastWriteTimeUtc="12/13/2016 19:32:16"/><JournalEntry Id="b9fcdec7-39ae-4dd7-afd6-579c5fe2c8d0" Index="10" CreationTimeUtc="12/13/2016 19:32:53" ChangeType="Deleted" Path="\\\OldFileShare\1-WebServices-68\CollabMetadata\{BC01D4AB-AFD3-4A4C-B424-16B7E4C31575}\VP36SMHY\Serialized.dat" LastWriteTimeUtc="12/13/2016 19:32:53"/><JournalEntry Id="9b75bd23-9d12-403b-a9fb-aa10706c2f75" Index="12" CreationTimeUtc="12/13/2016 19:32:53" ChangeType="Deleted"


Dare PojuSkype for business Solutions Architect

Comments (0)

Have a question about something in this article? You can receive help directly from the article author. Sign up for a free trial to get started.