Automated Backup
Scheduled, policy-driven backup jobs that run without anyone having to remember them.
- Scheduled backup policies
- Retention rules by data type
- Job monitoring and failure alerts
- Application-aware backups where supported
VANTRIX / BACKUP & DISASTER RECOVERY
WHEN EVERYTHING MATTERS.
BE READY.
From automated backups and offsite data protection to recovery planning and restoration, VANTRIX helps businesses prepare for disruptions and protect critical information.
PROTECT · DETECT · RECOVER · CONTINUEWHAT HAPPENS WHEN SYSTEMS GO DOWN?
[ 01 ]RECOVERY SIMULATION
WHAT HAPPENS
WHEN SYSTEMS GO DOWN?
An educational simulation of a disruption and a planned recovery. Start a disruption, then explore how recovery works.
[ 02 ]THE 3-2-1 PRINCIPLE
THREE. TWO. ONE.
A STRONGER BACKUP FOUNDATION.
Scroll to watch one stream of business data become three protected copies. Select each number to see why it matters.
RULE 3 · COPIES
Three copies of important data.
The production data plus at least two backup copies. If one copy is lost or damaged, others remain.
RULE 2 · STORAGE TYPES
On two different types of storage.
Keeping copies on different storage, such as primary storage and separate backup storage, cloud object storage or tape, reduces the chance that a single fault or weakness affects them all.
RULE 1 · OFFSITE
One copy away from the primary site.
A copy in the cloud, at a secondary site or in a separate facility, so a fire, flood, theft or site-wide incident does not reach every copy.
- 01
OFFSITE COPIES
Distance matters. An offsite copy should not share the same building, power or credentials as production.
- 02
CONTROLLED ACCESS
Backup systems deserve their own accounts, limited permissions and, where possible, protected or immutable copies.
- 03
PERIODIC RECOVERY TESTING
A backup is only proven when it has been restored. Scheduled tests show copies are usable and procedures work.
[ 03 ]CAPABILITIES
PROTECTION ACROSS
EVERY CRITICAL LAYER.
Six areas a backup and recovery approach usually covers, from the first scheduled job to the recovery plan itself.
On-Premises Backup
Local backup storage for fast, everyday restores of files, systems and virtual machines.
- Dedicated backup storage or appliances
- Separation from production storage
- Quick local restores
- Capacity planning for retention
Offsite & Cloud Backup
A further copy away from the primary site, so a local event cannot take every copy with it.
- Cloud or secondary-site backup targets
- Encryption in transit and at rest
- Bandwidth and initial-seeding planning
- Data-residency requirements reviewed
Server & Workload Recovery
Restoring complete servers, virtual machines and applications, not just individual files.
- Full-system and VM-level recovery
- File, folder and item-level restores
- Recovery to alternative hardware or platforms
- Documented recovery procedures
Data Protection & Resilience
Making backup copies harder to delete, alter or misuse, including by an attacker.
- Access control and separate backup credentials
- Encryption considerations
- Protected or immutable copies where supported
- Ransomware-resilience planning
Disaster Recovery Planning
Deciding in advance what is recovered first, how, and by whom.
- System priorities and dependencies
- Recovery objectives agreed with the business
- Roles, contacts and runbooks
- Scheduled testing and plan reviews
[ 04 ]RECOVERY OBJECTIVES
HOW MUCH DATA?
HOW MUCH DOWNTIME?
Two questions shape every recovery design. Adjust the values to see what each one means on a timeline.
RPO · RECOVERY POINT OBJECTIVE
How much data could the business afford to lose?
With a 4-hour recovery point, changes made in roughly the last 4 hours before a disruption may need to be re-entered or recovered another way.
- SHAPED BY
- How often data is protected
- Replication or snapshot options
- How fast the data changes
RTO · RECOVERY TIME OBJECTIVE
How long can a service be unavailable?
With an 8-hour recovery time objective, the aim is to have this service usable again within about 8 hours of the disruption.
- SHAPED BY
- Size of the data to restore
- Where recovery runs and how fast it is
- Documented, rehearsed procedures
The trade-off: tighter objectives usually need more frequent protection, faster recovery infrastructure and more investment. Different systems normally get different objectives.
[ 05 ]DISASTER RECOVERY JOURNEY
PREPARATION CHANGES
THE OUTCOME.
Recovery is decided long before a disruption. Six stages turn backups into a dependable recovery capability.
SYSTEM INVENTORY
- Finance systemCRITICAL
- File sharesCRITICAL
- EmailIMPORTANT
- Line-of-business appCRITICAL
- WebsiteIMPORTANT
- ArchiveSTANDARD
PROTECTION DESIGN
ProductionSystems & data
Local backupFast restores
Offsite copySite-level events
SCHEDULED COPIES
- Copy 01Local · protected
- Copy 02Local · protected
- Copy 03Offsite · replicated
- Copy 04Local · protected
JOB REVIEW
- Nightly backupCompleted
- Offsite replicationCompleted
- File server jobWarning · investigated
- Backup storage capacityTrend reviewed
RESTORE TEST · ISOLATED ENVIRONMENT
- Restore a recent copy
- System starts
- Files and records open
- Data is consistent
- Result recorded
RECOVERY TIMELINE
- Select recovery point
- Restore
- Verify
- Resume services
THE ROADMAP BECOMES THE RECOVERY TIMELINE
Know what matters
Identify systems, data and dependencies, and how much disruption each one could tolerate.
OUTCOME · Systems ranked by business impact
Design the protection
Choose backup methods, storage locations, retention and recovery objectives to match the priorities.
OUTCOME · Architecture and objectives agreed
Put copies in place
Implement backup jobs, offsite copies and access controls, and document what is protected.
OUTCOME · Copies created on schedule
Watch every job
Check that jobs complete, investigate failures and track capacity before it becomes a problem.
OUTCOME · Job results reviewed routinely
Prove it works
Restore files and systems in a controlled way to confirm copies are usable and procedures are current.
OUTCOME · Test results recorded
Recover with a plan
When disruption happens, follow the plan: select a clean recovery point, restore, verify and resume.
OUTCOME · Services restored in an agreed order
SCROLL THROUGH THE JOURNEY
[ 06 ]BUSINESS CONTINUITY
BEYOND BACKUP.
TOWARD BUSINESS CONTINUITY.
Five related ideas that are often confused. Select each one to see where it fits in the bigger picture.
REDUCES HOW OFTEN RECOVERY IS NEEDED
COPIES OF DATA
Backup
Creating and keeping copies of data so it can be restored later. Backup provides the material to recover from; on its own it does not bring a service back.
RECOVERY COPIES ARE NOT THE SAME AS HIGH AVAILABILITY
Recovery copies
Separate, point-in-time copies let you go back to a known-good moment after deletion, corruption or ransomware. Recovery takes time, but the past is preserved.
High availability & failover
Redundant systems take over when a component fails, keeping services running. But a deletion or encryption is copied across immediately, so failover does not replace backup.
Most organisations need both: resilience to reduce outages, and recovery copies to undo what resilience cannot.
[ 07 ]TECHNOLOGY ECOSYSTEM
ESTABLISHED BACKUP PLATFORMS.
SELECTED FOR THE REQUIREMENT.
VeeamCohesityCommvault
[ 08 ]PRACTICAL INFORMATION
QUESTIONS,
ANSWERED.
Straight answers to what businesses usually ask about backup, recovery and resilience.
Q01What is the difference between backup and disaster recovery?
Backup creates copies of data that can be restored. Disaster recovery is the wider plan and capability to bring IT services back after a significant disruption: which systems come first, where they run, who does what and how long it should take. Backup is an essential input to disaster recovery, but not the whole of it.
Q02What is the 3-2-1 backup rule?
A widely used planning principle: keep at least three copies of important data, on at least two different types of storage, with at least one copy offsite. Many organisations extend it, for example with an immutable or offline copy and regular recovery testing. It improves resilience but does not guarantee recovery on its own.
Q03What is offsite backup?
A backup copy stored away from the primary location, in a cloud service, a secondary site or a separate facility, so that a fire, flood, theft or site-wide problem does not affect every copy at once.
Q04What is the difference between RPO and RTO?
Recovery Point Objective (RPO) is how much data, measured in time, the business could accept losing; it drives how often data is protected. Recovery Time Objective (RTO) is how long a service can be unavailable before the impact becomes unacceptable; it drives how recovery is designed. Both are usually set per system.
Q05How often should backups be tested?
It depends on how critical a system is and how often it changes. A common approach combines routine checks of backup jobs, regular file-level restore tests and periodic full recovery tests of critical systems, plus a test after any significant change. What matters most is that testing is scheduled and the results are recorded.
Q06Can backups help recover from ransomware?
They can be a key part of recovery, provided the backup copies themselves are protected, for example with separate credentials, restricted access and immutable or offline copies, and a clean recovery point can be identified. Recovery also involves containing the incident and making sure systems are safe before data is restored, so outcomes vary from case to case.
Q07Is cloud backup sufficient on its own?
Cloud backup is a strong way to keep an offsite copy, but relying on it alone can mean slower large restores, dependence on internet bandwidth and a single point of control. Many organisations combine a local copy for fast everyday restores with a cloud or offsite copy for resilience. It is also worth checking whether SaaS data, such as email and collaboration files, is being backed up at all.
PREPARATION IS THE DIFFERENCE.[ 09 ]YOUR RECOVERY APPROACH
PROTECT WHAT
YOUR BUSINESS DEPENDS ON.
Tell VANTRIX about your infrastructure, data-protection requirements and recovery objectives to explore a suitable backup and disaster recovery approach.