Google Vault Best Practices
Note: The Google Vault Extractor requires that you have the .NET Framework version 4.6.1 or later installed on the computer on which you install and run the Extractor. To determine the .NET Framework version currently installed, follow the instructions provided by Microsoft: How to: Determine Which .NET Framework Versions Are Installed.
You can download the Google Vault Extractor here: https://api.bittitan.com/public/downloads/GoogleVaultExport/GoogleVaultExportSetUp.exe.
The key to successfully migrating a Google Vault is understanding what is migrating, and how much of it will be migrated. When engaging a new Google Vault project, get the following information to help size the workload:
- What mail?
Everything in the “Permanently Deleted” folder
- Capture permanently deleted content by running this search: label:^deleted
- Google Vault is a mirror of a current mailbox; migrating the entire Google Vault while performing a mail migration will result in many duplicates. Because Google Vault contains everything the associated mailbox does, the only folder you need to migrate from Google Vault is the “Permanently Deleted” folder.
- Set the following Advanced Options in the Google Vault migration project:
- Filter Folders: ^(?!Permanently Deleted$) KB004670
- Support Options (fill in the preferred Destination folder for Google Vault Items): FolderMapping=”^Permanently Deleted->Google Vault Items” KB005017
- Important: Do not run more than 30 instances of Google Vault Extractor. Google Vault can support a maximum of 30 parallel exports.
- Vault size?
- Accurately reporting the amount of data migrating out of Google Vault is key to assessing licensing needs. KB005370
- What users?
- While Google Vault captures all mailbox data, typically only a subset of users are needed.
- Generating a specific list of Google Vault users will reduce the size and time of the migration.
- Log in to the Google Admin panel: http://admin.google.com, then click on Users, select the top, far right-side menu represented by three vertical dots, and select Download Users.
Timing is everything!
Google Vault represents a current version of a production mailbox, as opposed to a point-in-time capture. Because of this, we recommend only migrating the Google Vault once all data is at rest (no changes are taking place) on the Source system. This ensures that no new items or changes to existing items are missed for migration. Because the Google Vault is at rest during migration, using a Full Migration strategy will get everything from Azure to the Destination with the least amount of touch possible.