2. Introduction to DataGr8
Always innovating to take new services
to market
Custom services
11 employees ®
DataGr8
Exclusive Partner Portfolio
Certified products
Sales expertise with a very unique
background
Sales
6 professional services employees
Dedicated and creative
Data experts
Services
Migration and support
3. Our Partners and services
Datadobe
CAS to CAS Migrations
CAS to NAS Migrations
NAS to NAS Migrations
Centera Manage Services
QUADROtech-IT
Enterprise vault Migrations
Microsoft Exchange Migrations
EMC
Source One Support
Infoarchive Support
NAS & CAS Migration
EPI-USE Labs
Sales Partner for SAP Migration and
Upgrades
HDS
NAS & CAS Migration
5. Our Support
30+ customers SADAC
24-hour support, every workday
Service Desk
6. About QUADROtech
Founded in December 2011 as a MBO from GlassHouse Inc.
63 Employees per end of Q1/2016, constantly growing
Leading global provider of migrations in the “email ecosystem”
Established partners worldwide including Tier1’s: Veritas, Microsoft, HP,
IBM
Headquarters in Switzerland and Subsidiaries in UK and USA
Development and support resides Slovakia – No contractors/outsourcers
are used
7. Use Cases
“Spin-off” of
business units
into separate
entities
Acquisition of
companies
which use
Enterprise
Vault
Consolidating
dispersed
Enterprise
Vault
installations
into a single
directory
Re-
Implementing
Enterprise
Vault with a
completely
redesigned
architecture
Migration of
user archives
between sites
Archive
Migration (e.g
from EV to
cloud or
Exchange)
8. Features
Migrate across Stores, Sites, Directories and AD Forests
Highly automated and workflow based process
Logging and Auditing on item level and extensive reporting
Preservation of Chain of Custody
Migrate what you need – selective migrations
9. Unique Main Features
• Uncouple data from user migrationSync’n Switch
• Or hybrid mode (e.g. ingestion Server
in Azure)
Online or Offline
Migration
• Like the move of Exchange Mailbox
can be used for further automationExternal Triggers
• Utilizing newest extraction and
ingestion technologies, like AIP
Unleashed
Migration Speed
11. Traditional EWS Ingestion
Open MSG
• Parse all MAPI
Properties
Create XML
• Include all
Properties
• Base 64 encode
Establish
EWS
Connection
• for each item
and upload
CAS Server
• Parses XML and
creates
internal BLOB
• Forwards Blob
to MBX Server
Mailbox
Server
• Stores BLOB in
EDB
To upload 100 Messages = 500 steps are required
12. AIP Ingestion
Open MSGs
•Batch 100 items
•Convert directly
into one internal
Blob
Establish EWS
Connection
•Stream the
whole binary
blob
CAS Server
•Nothing to do
for CAS!
•Just forwards
Blob to MBX
Server
Mailbox
Server
•Stores BLOB in
EDB
To upload 100 messages = 4 steps are required
resulting in more throughput and less throttling by CAS
21. To Summarize
No “man in the middle” concept
•Migration Server can’t become the bottleneck
Modular architecture
•More scalability, flexible security and faster migrations
Flexible content flow
•Split migration content from data required to control the
migration
23. Stage 1 – Sync – The Data Migration
Create
Temporary
Archive on
Target
Synchronize
with source
Keep
migrating
delta
Enable
Migration for
User
Check Target
Availability
Collect
Metadata from
Source Archive
Start extraction
and ingestion
process
Wait until
finished
Process restarts
to fetch deltas
24. Stage 2 – Switch – The User Migration
Prevent new
items in
source
Ensure all
migrated
Switch user
to target
environment
Disable Mailbox for
Archiving in Source
Ensure all items
have been
migrated and get
last delta
Fix shortcuts,
links, banners and
appointments in
Mailbox
Remove
permissions on
Source
Disable Legacy
Archive Outlook
Add-In
Delete Source
Archive
26. ArchiveShuttle.cloud
No migration hardware onsite required
Very fast thanks to Enterprise Flash Storage
No migration content leaves customer
security boundaries
Almost no WAN Bandwidth needed
Fastest TTFI (Time-to-first-item) on the
market
27. ArchiveShuttle On Premise
Archive Shuttle Core
• Windows 2008R2 or 2012R2
• 4/8 CPUs
• 8/16GB RAM
• IIS / .NET 4.5 required
SQL Backend
• MS SQL 2005, 2008, 2012 or 2014
• 4/8 CPUs
• 8/16 GB RAM
• Fast Disks (crucial to overall migration
speed)
28. QUADROtech.appliance
Build for migration requirements running the
whole migration infrastructure
Running Windows 2012 R2 & HYPER-V to
virtualize the required Servers
3-tier Storage Technology containing SSD
Flash, SAS and SATA Disks
Available for ArchiveShuttle and
PSTFlightDeck
Typically rented to customers for the
duration of the migration
30. Handling Leaver Data
What happens with legacy archive data from former employees who have left the company?
Typically, these “leavers” don’t have an AD account and a mailbox anymore
as a result there is no target mailbox to which the data can be migrated
Microsoft’s suggestion is to put the mailbox on Legal Hold so the data can still be
discovered/recovered if required
the Office 365 license can then be removed and the leavers data is stored for free by Office 365
Requires many manual steps consisting of the following process:
Create
mailbox in
O365
Assign a
license
Map an
archive to the
mailbox
Migrate
archive data
to the mailbox
After
migration's
complete,
assign the
legal hold
Remove the
license
Repeat
31. Handling Leaver Data (Cont.)
ArchiveShuttle has an automated workflow to handle company leavers process when migrating to Office 365
Orphaned Archives, (leavers without mailbox and/or AD account), can be easily identified within ArchiveShuttle & a different
migration workflow can be applied to those archives
“Rolling” Office 365 licenses are defined, which are used for the migrating leavers
For example, you instruct ArchiveShuttle to use 10 licenses for all your leavers
ArchiveShuttle then creates Office 365 mailboxes for 10 leavers and puts the mailbox on Legal Hold before starting to migrate the data into those
mailboxes
As soon as a leaver is done, the license is removed and added back to the leaver’s license pool, so ArchiveShuttle can reuse the license for
migrating the next leaver
Results in a smooth and automated approach to migrate leaver data without additional licensing costs
in Office 365!
650+ Customers globally
24 hour support (5 days per week)
Focused, dedicated and committed to helping our customers
All QUADROtech products share the same migration methodology which we have bundled in the QUADROtech Migration Framework.
Transparency – what does it mean for us?
Under no circumstances an end user should loose his access to the data that is migrated. Even during the migration.
Fast & Reliable: Even the migration is transparent, usually customers would like to get it done as fast as possible. Developing Enterprise Software requires of course high level of reliability and overall speed to help the customer to finish the migration in time and on budget.
Workflow Based: A workflow based approach gives us and the customers different benefits. First of all we can easily automate certain tasks, like the provisioning of archives or the automatic retry of failed Items. For example ArchiveShuttle is able to differentiate between transient and permanent errors. The transient errors will be retried automatically per default 15 times in 24 h to lock out any issues caused by the environment. Furthermore by being able to adjust the workflows easily in the UI, we can adjust them to meet exactly the customers requirements instead of telling the customer that he has to adjust his requirements to the workflow of the software.
Easy to manage:
The User Interface is very user & engineer friendly allowing to manage the whole migration using a simple web browser. No logins to servers or passwords of sensitive accounts are required to drive the migration. This is very important especially for partners that are offering managed migration services for their customers.
Cost effective:
By taking the “Total Cost of a Project” into consideration we help customers driving these costs down simplifying the deployment, by automating most of the labor intensive tasks and by not requiring any kind of expensive hardware when using our QUADROtech.cloud
A migration application needs to
- open the message file and parse all MAPI(default and custom) properties
- create a XML File containing all those properties and base64 encode all non text properties
- To establish a HTTPS Connection for each item individually to the CAS Server (O365 or Exchange) and to upload the XML (which causes a huge connection overhead and up to an data transfer of 2.9x of item size!)
The CAS Server then parses the XML File and creates an internal BLOB, which will be passed on to the Mailbox Server to store in the Exchange Database.
The parsing results in more CAS Load (=CPU time) and results in heavier throttling by Microsoft.
QUADROtech’s AIP has the ability to batch several items into one binary BLOB.
Per default 100 items will be parsed and the internal Exchange BLOB is created already by ArchiveShuttle
One HTTPS connection is required to upload the whole BLOB to the CAS Server
The CAS Server has nothing to do, as the BLOB is already the internal Exchange BLOB. It just forwards to the Mailbox Server.
This results in LESS CAS time and less throttling.
The most used architecture in migrations is to let the migration server be the “man in the middle” between source and target.
This concept seems to be straight forward, but has several downsides.
As each item is pulled by the migration server over the network from the source and pushed into the target, every single byte of migration traffic has to flow through the migration server itself.
Very often the migration server becomes the bottleneck so that scalability can be just reached by adding more and more Migration Servers – typically each instance requiring its own SQL Database Server.
ArchiveShuttle has a completely different architecture:
The Core Server is not man in the middle, instead modules/agents are deployed to Source and Target Systems
Advantages:
Better scalability, faster migrations
More reliability
Flexible security
The locally deployed module connects to the ArchiveShuttle Core Server using HTTP or HTTPS. No additional firewall ports have to be opened to allow connectivity.
The module establishes a connection every minute and asks for commands.
As the core is aware of every archived item, every mailbox and every ad account it would issue a command back to the asking module.
For example EV Extraction Module running on EV Server 01 please extract these 1000 items with those IDs from my archive.
The Module would follows this command and does it’s “magic”. When finished, it returns a result back to the core.
It’s important to understand that the result is NOT the migration content itself. Instead it is pure metadata. In our example it would be all 1000 Items done successfully or 998 done successfully and 2 failed because of this or that reason.
Now you might ask yourselves what happens to the content itself:
We introduce a different player to the game – the staging area. The Staging Area is nothing else than a small Windows Share, typically between 50 and 100GB. It can be hosted on any device that allows the sharing of a folder.
To complete my example: The extraction module gets the command to extract 1000 items, which it would place on the staging area. Afterwards it would return the result “all 1000 items done” to the core. The next time an ingestion Module, for example the Office 365 ingestion module asks for work, the core would issue a command saying “Office 365 ingestion module, there are 1000 items on the staging area awaiting ingestion, please grab them and ingest them into users X mailbox”. The O365 module then would do the ingestion and deleting the successfully ingested items from the staging area and returning the result containing all Office 365 Id’s for each single message back to the core to complete the chain of custody.
