Fast2 Playbook
The Playbook is the strategy layer of the Fast2 documentation. It is about the decisions you make before you configure a single task: which extraction strategy fits a live source, how you catch the target up to a moving source, and where you deploy Fast2 relative to the systems it connects. These are architecture and methodology choices, anchored in real field experience and real migration failures.
Fast2 has two hands-on sections, and they answer two different questions.
| Playbook (this section) | Cookbooks | |
|---|---|---|
| Question it answers | Which approach should I choose? | How do I implement this? |
| Altitude | Strategy & architecture | Tactics & recipes |
| Unit | A methodology, a decision matrix, a trade-off | A task config, a code snippet, an API call |
| When you read it | Before the project, during design and scoping | During the project, at the keyboard |
| Example | "Clone & Sweep vs. Snapshot & Drip for a live 800M-document FileNet source" | "Read content and metadata from S3 into a punnet" |
A cookbook tells you how to cook one dish. The playbook tells you how to plan the menu for 500 guests, with dietary constraints and a two-hour service window. You will usually start in the Playbook to choose your approach, then drop into the Cookbooks to build it.
What's in here
- Extracting From a Live ECM: the three bulk-extraction methodologies (Clone & Sweep, Snapshot & Drip, Live Trickle), with a decision matrix, throttling controls, and a defensible sizing baseline. Part 1 of the migration series.
- Delta Migration: how the target catches up to a source that never stops. The four delta-capture mechanisms, layered reconciliation, cutover patterns, and the sign-off ritual. Part 2 of the migration series.
- Deployment Variants: where to run Fast2 relative to the source and target, from on-premise to cloud, hybrid, and AWS Snowball, with the access-control, performance, and debugging trade-offs of each.
- Content Integrity: proving no content was corrupted or lost in transit. The three content-validation strategies (size, retrieved hash, computed hash), their trade-offs, and how Fast2 isolates, logs and retries mismatching assets.
- Metadata Integrity: preserving original creation, modification, and retention dates plus creator/owner identity in the destination, instead of letting the migration run overwrite them.
These articles are written from the field. They name real projects and real failures, because the point of a playbook is to help you avoid repeating them.