Replication fails after restoring a backup older than 30 days

Products

• Endpoint Protection

Issue/Introduction

After you restore a backup older than 30 days to a server that is a remote replication partner to a Symantec Endpoint Protection Manager (SEPM) 12.1.5 (12.1 RU5) server, replication fails.
 

The SCM server log may show the following messages:

• Replication from remote site Site2 to local site Site1 finished unsuccessfully
• Unexpected server error. 
• Unable to fetch changed data from remote site [Site2]: Failed to save downloadedContent for…

 
The replication log may include the following messages:

• THREAD 138 SEVERE: Error processing Incremental Delta 
  results: com.sygate.scm.server.util.ServerException: Unexpected server error.
• LaunchXDeltaAndWait Error : xdelta returned non-zero result. Result: 1
• Error: Cannot merge patches for file filename
   

Cause

A definitions delta file is larger than 100 MB.

A delta file larger than 100MB may also occur if you upgrade a Symantec Endpoint Protection (SEP) 11.x client to 12.1.5, upgrade a client that has content older than 30 days, or use a JDB file that is older than 30 days.
 

Resolution

To work around this issue, perform one of the following tasks:  

• On the remote Symantec Endpoint Protection Manager, reduce the number of LiveUpdate content revisions stored to 1, run LiveUpdate, and then initiate replication. Once replication succeeds, you can reset the number of content revisions back to the original (or desired) number. To reduce LiveUpdate revisions, see the task "Change the LiveUpdate settings to reduce space requirements" in the knowledge base article Increasing Symantec Endpoint Protection Manager available disk space before an upgrade.
    
• Disable content replication with the instructions provided in the knowledge base article Changing the replication frequency and content