Short answer
FirstNet checks this during discovery. If your initial full backup will not complete over your available bandwidth in time, FirstNet agrees a controlled seeding approach with you before go-live, such as moving the first full backup offline.
In detail
The first full backup, called seeding, is usually the largest and slowest transfer. After that, jobs send changed data, so ongoing traffic depends mainly on how much your data changes each day.
What FirstNet looks at when planning seeding:
- The current protected data size and expected monthly growth
- Your daily change rate, even as a rough estimate
- Available bandwidth and latency to the vault over internet or VPN
- Your backup window and any application constraints
- Any hard deadline, such as an audit or the end of a contract
The final approach depends on data volumes, change rate, bandwidth and the agreed delivery timeline, and source-side compression and deduplication can reduce what has to be transferred. Once jobs are running, FirstNet performs test backups and test restores to verify integrity before onboarding is complete. If you have a fixed date, raise it early so feasibility and an accelerated plan can be checked.
Source: FirstNet Backup & Disaster Recovery as a Service service page →
Didn’t answer your question?