Important data needs a plan
Place files, systems and applications in the backup plan according to their value and dependencies
ABRIT Backup
Before setup, identify the data to protect, how copy status will be checked and the route for a restoration request
Why Backup
A backup copy alone does not establish recovery readiness. Know what is covered and how a restore will be checked
Place files, systems and applications in the backup plan according to their value and dependencies
Verification and restore testing help reveal issues before a recovery is needed
Protection scope
The final scope is defined after reviewing your environment
Back up selected virtual machines and related settings
Create copies of selected business files and folders
Assess backup requirements for applications and their data
Backup model
Connect backup policy to execution, verification and recovery planning
Define scope, sequence and timing around data priorities
Review runs and copies, and record items requiring follow-up
Review sample restores and the response path with your team if they are included in the agreed scope
Managed lifecycle
The stages adapt to each organization's environment
Agree on the scope, priorities and approach
Create copies according to the agreed schedule
Check execution and report findings
Define restore testing and recovery-plan reviews within the agreed scope
Recovery readiness
RPO and RTO are planning concepts. Their targets require a separate assessment of business needs and technical dependencies
Discuss how much data change the organization can tolerate losing
Discuss the target time for restoring a service against real dependencies and capabilities
Getting started
We review systems and recovery priorities before implementation
Review systems, data and priorities
Define policy, scope and backup method
Set up and check the service in your environment
Make monitoring, reporting and review routine
Recovery readiness
Discuss your data, backup approach and recovery priorities with ABRIT