During space/site backup/restore Confluence could skip some records for various reasons. For e.g. record could be invalid, it's dependencies couldn't be resolved or attachment file couldn't be found. This information about skipped records is added to the atlassian-confluence.log file. When process finishes users could see in UI how many records were skipped. If user wants to check what exactly was skipped and whether they are OK with the fact that records aren't included in backup or not restored, they will need to search through the whole confluence log file to be able to find what exactly was skipped.

I suggest to consider introducing additional place where this information could be stored, so user could access it without going through all logs. For e.g. it could be:

a) Additional file related to the job (will be deleted after 2 weeks together with the job)

b) Backup/Restore service will create Confluence page which will be mentioned in job. When job is deleted this page could also be removed (we will need to have a special space for such pages)