Summary

The Backup Client fails to complete successfully if the Analytics event to upload and remove the .gz analytics logs runs during the backup window.

Steps to Reproduce

1. Start the backup client
2. Have the Analytics event fire which uploads and deletes the abc-123.atlassian-analytics.log.YYYY-MM-DD.#.gz file

Expected Results

Backup completes successfully (either by excluding the analytics logs (/var/atlassian/application-data/bitbucket/analytics-logs) from the backup or pausing analytics upload process)

Actual Results

The below exception is thrown in the atlassian-sbc-YYYY-MM-DD.log file:

2016-08-04 03:30:13,935 ERROR [main] c.a.b.i.backup.client.BackupMain A backup could not be created
com.atlassian.bitbucket.internal.backup.client.BackupException: File /var/atlassian/application-data/bitbucket/analytics-logs/abc-123.atlassian-analytics.log.2016-07-30.2.gz cannot be read

Workarounds

1. Set the bitbucket.home.excludes property in backup-default.properties to something like analytics-logs,snapshot,lost+found,.DS_Store, to exclude the analytics-logs directory from backup.
2. Switch to the DIY Backup or adjust the Backup Client time so that it does not conflict with the Analytics upload which should occur at midnight.