#AvePoint Cloud Backup for Office 365 July 2018

Release Date: July 22, 2018

• Users in the account pool will be dynamically distributed for performing the backup job. If the number of users in the account pool does not satisfy the actual need, you can add users to the account pool when performing the backup job. The users added to account pool will be automatically distributed for backup within 15 minutes.

• Users in the account pool will be dynamically distributed for performing the backup job. If the number of users in the account pool does not satisfy the actual need, you can add users to the account pool when performing the backup job. The users added to account pool will be automatically distributed for backup within 15 minutes.

• The object discovery logic has been improved. If an object failed to be discovered in a backup job, the next backup job will automatically include this object and back up the changes of this object since the time it was modified after a successful backup.

• The job status definition has been improved to now include the Warning backup status in the job report. The Warning backup status definition will be automatically enabled for all customers. If you want to disable it, contact AvePoint Support.

• If an object failed in a backup job, the object will be marked as Warning in the job report. If the warning object fails in the next three backup jobs, the object backup status will be updated to Failed. The failed objects will still be included in the future backup jobs for retrying to unlimited times.

• When restoring the Teams conversations, the conversations created within one month will be restored to the same HTML file.