Disaster recovery
A plan and the tools to bring critical systems back after a serious failure, within a defined time.
- Critical systems identified
- Time and data-loss objectives
- A written, tested plan
Overview
Disaster recovery answers two questions: how long the company can be down and how much data it can afford to lose. From there we design the plan, the replication of critical systems and the tests that show it works.
When it makes sense
- A day of downtime would have a financial or legal impact.
- All servers are in a single location.
- There is no written plan for what to do if the main server fails.
- Customers or audits require business continuity.
What is included
- Impact analysis: critical systems and processes
- Definition of recovery objectives (RTO and RPO)
- Replication of critical systems to another site or to the cloud
- Written recovery plan, with owners and steps
- Planned tests and a results report
- Periodic review of the plan
How we work
- AssessmentWe map what you have, what is critical and what needs to change.
- ProposalWe send the scope, the recommended solution and the terms.
- ImplementationWe install, configure and validate with you.
- SupportWe look after the solution once it is in production.
Brands
Replication and recovery of virtual machines and servers.
We also work with other brands, depending on the project.
Frequently asked questions
What are RTO and RPO?
Does recovery need another building?
Where do we start?
See also
Talk to a specialist
A consultant replies by the next business day.
Keep exploring
Discover what RegalTec does, for whom and with what results.
Services
Custom software, infrastructure and cybersecurity, consulting and managed technical support.
Industries
Specific solutions for each activity, in the private and public sectors.
Case studies
Real projects, without exposing our clients.
Training
Recorded training for each Cegid Primavera module.