Hi HenryA,
>There is a "post-processing" activity that occurs with every time the backup job runs. So the 3-4 shares that are this big, are taking all night to do their "post-processing" activity, even if there's no new files to back up. This is severely slowing down the rest of the backups.
That part seems a bit suspect, and would be best to open a Support Case and allow Support to review the behavior there. Be sure to include logs from one of the affected jobs. (Use the 1st radio button to export by job, select one of the affected jobs for export)
The post-processing time can make some sense depending on how much data is up there, but if it's really stalling out the other backups would be best to let Support review the debug logs and see if there are places for optimization.
Please share your case number once created for us to review. Thanks!
>There is a "post-processing" activity that occurs with every time the backup job runs. So the 3-4 shares that are this big, are taking all night to do their "post-processing" activity, even if there's no new files to back up. This is severely slowing down the rest of the backups.
That part seems a bit suspect, and would be best to open a Support Case and allow Support to review the behavior there. Be sure to include logs from one of the affected jobs. (Use the 1st radio button to export by job, select one of the affected jobs for export)
The post-processing time can make some sense depending on how much data is up there, but if it's really stalling out the other backups would be best to let Support review the debug logs and see if there are places for optimization.
Please share your case number once created for us to review. Thanks!
Statistics: Posted by david.domask — Jun 12, 2025 9:28 am







