More control and improved insight with the CloudM November product release

With the latest Backup 1.3 release, users can now choose to backup their data to AWS as an alternative to Google storage for improved data governance. New audit logs and stats placed prominently within the module give your further insight and control over your systems.

In addition, admins will be better positioned to troubleshoot when things go wrong: should delta backups fail more than 5 times in a row, further delta backups will be put on hold and the status set to “Requires Action”. Users can filter by status, dive into details to understand why the failure occurred and resume the backup once resolved.

Lastly, a new “Purge Backup” step in our offboarding workflow is particularly useful for customers who use Backup and Archive: leavers data will be moved into Archive while backups will be purged after a customisable period of contingency. Since Archive storage is typically cheaper, this functionality can significantly reduce storage costs.

Archive 2.0 is also seeing feature updates that give you more control and insight, such as an expansion of storage regions and a new audit log for user views of the “Restore” section for regulatory, compliance and internal investigative purposes. 

We’ve also made some improvements to the UI so that Archive phases can be better distinguished.

For customers using our onboarding workflows to reduce the need for manual interference and free up IT admin time, we’re introducing an additional offboarding step that automatically assigns a Google Workspace license to historic users, so that further steps that require a license such as Archive, Migrate Mail and Transfer Ownership can be completed without intervention. As historic users typically still have Google Archive User (AU) or Cloud Identity licenses assigned, offboarding these users can result in significant savings. 

In addition to the new onboarding step, we have also added your offboarding and Archive statistics to the dashboard for better visibility. Lastly, we’ve made manual email signature syncs quicker as they can now be pushed through at Smart Team level rather than the organizational unit (OU).