Monthly Archives: August 2013

Migration Integrity – Ensuring Chain of Custody with Nava Certus

If you are planning a Google Drive migration and require assurance that the files at the source are exactly the same as the files at the destination, then you may be interested in our “Migration Integrity” feature.

One of the features that we designed into Nava Certus from the very beginning is called Migration Integrity. While this feature is not the most visible to the user, it is perhaps one of the most important for our enterprise customers that may want to ensure a certain chain-of-custody within the migration process. The “chain of custody” may be something that is required by your company’s internal policies or by regulation.

Specifically, the integrity feature provides assurance that every single file that has been migrated has not been altered in any way. For every single file that we migrate, we calculate a cryptographic hash which we later correlate with Google’s own hash (which automatically gets generated for any uploaded file). If the hashes match, we consider the migration to have been a success. If the hashes don’t match for any reason, the particular item will be marked as failed.

Be on the lookout for the next release of Nava Certus, which will feature a “Migration Integrity” report. This report will list every single file migrated, the hash at the source, the hash at the destination, and any errors. You can provide this report to your auditors as proof of the integrity of the migration.

HOWTO: Distributed Google Drive Migration

This post is another in a series of posts about Nava Certus, our Google Drive migration tool. Specifically, we show you the Distributed feature in NC. The beauty of distributed migration is that it allows you to get rid of your file server, but at the same time possibly stay in the “basic” tier of Google Drive storage, thus avoiding extra Google Drive storage costs.

How, do you ask? Well, you may know that Google Apps for Business accounts come with 35GB of free storage (shared between Gmail and Drive). Suppose you have 10TB of data belonging to 1000 users. This is about 10GB on the average for each user. Assuming that no user is consuming above 35GB, then we can move each file to its owner’s account.

The first steps to creating a Distributed migration job are similar to Centralized migration. The contents of the General and Source tabs stay the same, so refer to this previous blog post.

Only the contents of the “Destination” tab will be different.
Destination tab
For destination type, please select “Google Drive (distributed)”

It turns out that the distributed options is much easier to configure, requiring only one option, the mapping file.

Mapping File: A CSV file mapping users on the source to users on the destination. You need to have this prepared prior to starting the migration.

This is all you need in order to configure distributed migration.