Today we are shipping CubeBackup 2.0, a major release that has been in the works for 3 months. There are lots of bug fixes and feature improvements in the new version.
Can I continue to stay with CubeBackup 1.x?
No, you can’t! Based on Google’s API deprecation statement http://googleappsdeveloper.blogspot.com/2014/12/reminder-to-migrate-to-updated-google.html and https://developers.google.com/identity/protocols/OAuth_ref, several APIs used in CubeBackup 1.x will stop working after April 20, 2015. As a result, CubeBackup 1.x will no longer be functional after that date. It is important to upgrade CubeBackup to the new version in order to secure your Google Apps data. We are sorry for the inconvenience, but this upgrade is not optional.
What’s new in CubeBackup 2.0?
- Two-Legged OAuth 2.0 (OAuth2.0 service account) for domain-wide authorization.
CubeBackup 1.x uses 2-Legged OAuth1.0 for authorization. When CubeBackup 1.0 was in development, OAuth2.0 was not yet mature enough for Google Apps domain-wide authorization and hardly any code libraries could be found. However, this situation has changed, and now CubeBackup has been completely moved to OAuth2.0, which offers superior security and flexibility.
- Migration to the latest Google Apps APIs.
The following APIs are used in CubeBackup 2.0:
- Select users by Organization Unit.
With the new Google Admin Directory API, CubeBackup allows you to select backup users by their organization unit. This feature can be very useful for large companies who might wish to apply different backup policies on different departments.
- Excellent multi-language support.
CubeBackup has been completely redesigned to support all languages. It can easily handle multiple languages in a single Google Apps domain now.
- Backup shared files in the Google Drive “Shared with me” folder.
Shared files were not backed up in the old version of CubeBackup. In CubeBackup 2.0, the “Shared with me” files are fully supported.
- Fully backup the whole Gmail folder structure.
In CubeBackup 1.x, only messages in “Inbox”, “Sent Mail”, “Starred” and “All Mail” were backed up. In the new version, the whole mailbox structure, including customized folders/labels, are all included in the backup.
- Improved performance.
Code optimization and the adoption of the latest Google API has improved backup performance in CubeBackup 2.0.
- Bug fixed
Many bugs have been fixed in the new version.
Steps to migrate to the new version.
- Uninstall CubeBackup 1.x.
- Download the latest version of CubeBackup from cubebackup.com.
- Install CubeBackup 2.0.
During the install process, you might be asked to install .Net Framework 4.0 if it’s not preinstalled. For Windows XP, Windows Server 2003 or Windows Server 2008 users, KB2468871 hotfix may also be required in some cases. Please visit the installation page to get more information.
- Start CubeBackup, and follow these instructions for authorization and configuration.
The OAuth2.0 Service account (2-Legged OAuth2.0) authorization can be complicated, so please follow the above instructions carefully.
Because significant changes have been made in CubeBackup 2.0, the backup data is not fully compatible with that of CubeBackup 1.x. Google Drive/Docs and Google Contacts backups are unchanged, but Gmail and Calendar backups are now handled in a slightly different way.
When specifying the backup location, there are two options:
A. Delete all data backed up by CubeBackup 1.x and use CubeBackup 2.0 to backup your Google Apps data from the beginning. This gives you a clean start, but may take longer for the first backup. (Recommended)
B. Keep the backup data of CubeBackup 1.x, and specify the same folder as the backup location for CubeBackup 2.0. Google Drive and Contacts data will be backed up incrementally based on the old data, but CubeBackup 2.0 will create a new backup for Gmail and Calendar data. The new data should overwrite the old backup without any problems. This method saves backup time but makes the backup folder a bit more messy.
If you have any problems or suggestions for CubeBackup, please do not hesitate to contact us: firstname.lastname@example.org. Thanks!