Replication is failing between to Endpoint Protection Manager (SEPM) sites.
Around 10% to 20% during the "Downloading" status, the replications fails with the error "Failed to submit".
The filegroup FG_LOGINFO has reached its upper limit on the SQL server hosting the SEPM database.
Adjust the upper limit for the FG_LOGINFO filegroup on the SQL server:
SQL Permissions Required: sa or user with sysadmin server role.
NOTE: You may need to experiment with different values depending on how much log information you are storing, so monitor the scm-server log for future "FG_LOGINFO" errors. If you continue to see these errors, you will need to readjust this value higher.
NOTE: Use this method with caution. If the DB is reaching the set size limitations, there may be DB corruption present.
A common misconception is that lowering the log retention settings will reduce size of the filegroup on the SQL server. The only effect this will have is limit the number of entries in the file itself. The rest of the space in the file will remain as whitespace and the filesize itself will remain the same.
For example, the default log retention settings set to 60 days and 10000 lines. The default filegroup upper limit is 20MB. If you lower the number of log entries to 30 days and 5000 lines, the sem5_loginfo will then only contain 30 days or 5000 lines of log information (which ever is reached first), however filesize will stay at 20MB.
To actually reduce the filesize of the sem_loginfo file, you must use the SQL shrink process as described here:
NOTE: In the Shrink File dialog, be sure to select "Data" as the File Type and "FG_LOGINFO" as the Filegroup.
To lower the log retention settings:
NOTE: This change will take effect at the SEPM's local midnight time as part of the daily SEPM maintenance. Once that has happened, you can then run the shrink procedure on the SQL server.