Short answer
In a FirstNet DRaaS event, you declare the incident, replicas of your systems are started in the FirstNet DR site, users connect through the agreed secure access model, and you operate from DR until your primary site is restored and services fail back under change control.
In detail
The five steps:
- Declare: you confirm the DR event and which systems need to be recovered
- Fail over: replicas start in the FirstNet DR site; on Platform-Only you initiate this, and on Managed DR FirstNet assists as contracted
- Connect: users and administrators reach recovered systems through the scoped network model and secure access, such as VPN and firewall rules
- Operate: systems run from the DR site while the primary site is repaired
- Fail back: services return to the primary site in a controlled way, using a planned runbook and change control
How smoothly this goes depends on preparation. Before an incident, FirstNet needs your workload list and what is critical, your RTO and RPO targets, connectivity and secure access details, application dependencies such as DNS and Active Directory, and the recovery order. These are captured during onboarding and proven in DR tests, so the steps are rehearsed rather than improvised.
Source: FirstNet Backup & Disaster Recovery as a Service service page →
Didn’t answer your question?