Backup and recovery designed around how your business needs to come back online, and tested before an incident.
Protect the data. Prove you can recover.
We design backup and disaster recovery around the way your business needs to come back online. We use Veeam, NinjaOne and a secure recovery design to protect endpoints, servers, Microsoft 365, identity, cloud and critical infrastructure. Then we test recovery before an incident forces you to. A green backup job does not tell you if a critical app can return in time, if the restore point is clean, or if your people know the order to recover in.
Backup is the mechanism. Recovery is the outcome.
We start with the impact on your business and work back to the technology. What must come back first? How much data can you afford to lose? How long can the outage last? Which systems must recover together?
If the recovery need is not defined, the backup design is guesswork.
Workloads
Find the devices, servers, SaaS, identity, cloud and apps that need their own backup.
RPO
Set the most data the business can afford to lose between recovery points.
RTO
Set how fast each workload or service must come back after a disruption.
Dependencies
Know which identity, network, database, app and server links decide the order you recover in.
Veeam and NinjaOne solve different recovery problems.
We don’t force every workload into one backup product. We use Veeam where recovery is complex, and NinjaOne where backup works best alongside endpoint and managed IT operations.
Veeam Data Platform
Backup and DR for large, complex estates.
Best for critical servers, virtual machines, hybrid and multi-cloud, and formal DR. It suits customers who need advanced recovery tests, orchestration and the freedom to move between platforms. Version 13.1, the current release, adds more hypervisor choice, stronger malware detection and deeper enterprise recovery.
Virtual, physical, cloud and unstructured workloads
Hardened backups that can’t be altered
Veeam Data Cloud Vault: fully managed cloud storage that is always immutable. It holds a separate recovery copy, and Australian storage regions are available
Recovery Orchestrator: build recovery plans, automate tests and track whether you really meet your RPO and RTO
Verified clean recovery: restore in isolation, scan and check, so infected systems don’t go back into production
Restore to any supported hypervisor or cloud, so your backup isn’t tied to one vendor
Microsoft 365 protection through Veeam Data Cloud
NinjaOne Backup
Backup built into the way your devices are managed.
Best where endpoint, server and SaaS backup should sit beside RMM, patching, monitoring, automation and remote support in one place. It suits many spread-out devices, smaller server estates, Microsoft 365 and customers who use Vectra SONAR.
Some environments need one platform. Others suit a blend. We confirm the final design after discovery, rather than picking a product first.
Workload
What it needs
Platform
Critical virtual infrastructure
Complex restores, moving between platforms, automated recovery and formal DR.
Veeam
Distributed workstations
Simple protection, set by policy and built into the way devices are run each day.
NinjaOne
Microsoft 365
Exchange, OneDrive, SharePoint and Teams protection. The choice depends on scale, retention and service model.
Either
Microsoft Entra ID
Protect identity objects, roles and settings when you need to get the Microsoft identity layer back.
Designed fit
Formal DR and failover
Recovery plans, dependencies, automated tests and orchestration, with RTO and RPO results written down.
Veeam
Managed IT environment
Backup health and recovery handled in the same service as endpoint management and support.
NinjaOne
Mixed enterprise estate
Use a different platform where the workload, recovery or running needs truly differ.
Blended
Design the backup so it survives the incident.
Ransomware and destructive attacks go after recovery systems, because removing the backup takes away your options. So the recovery platform needs its own security controls.
Immutability
Make recovery data hard to change
Use immutable storage and protected retention, so a compromised admin can’t simply encrypt or delete every usable restore point.
Separation
Fewer shared points of failure
Keep backup admin, logins and storage apart from production, so one breach does not become a backup breach.
Clean recovery
Restore without letting the attacker back in
Use malware detection, known-good restore points and controlled restores to cut the risk of reinfection.
Identity protection
Recover access as well as data
Include key identity settings and directory services in the plan, so users and admins can actually log in after an outage.
Recovery testing
Prove it before the outage
Test sample files, workloads and recovery plans on a schedule, and keep evidence that the process works.
Response integration
Link backup to cyber operations
Make recovery part of incident response, so security and infrastructure teams agree when to restore, from which point and into where.
A SaaS app that stays online is not a backup you control.
Microsoft keeps the platform running. Your organisation still owns many of the risks: deletion, retention, sync errors, harmful changes and getting business data back. We use Veeam Data Cloud or NinjaOne SaaS Backup, depending on your needs and operating model.
Exchange Online
Recover mailboxes, messages and related user data without relying only on native retention.
OneDrive
Restore single files, folders or larger sets of user data after deletion, damage or a harmful change.
SharePoint
Protect supported sites, libraries and shared data that business processes rely on.
Microsoft Teams
Protect supported Teams structures, files and shared content as part of your wider Microsoft 365 plan.
Microsoft Entra ID
Protect supported users, groups, roles, policies and settings, so identity can be recovered after a mistake or attack.
Retention and governance
Keep backups as long as the business, the law and compliance need, rather than assuming the SaaS platform keeps everything for ever.
Backup needs somebody to own the failures too.
For SONAR customers, Vectra can take day-to-day ownership of supported backup services. You no longer have to watch job failures, capacity and restore requests yourself.
Watch supported backup jobs, policy status and coverage, so gaps in protection are found early.
Failure fixes
Fix failed jobs and storage, agent, network and policy issues, rather than just passing on alerts.
Policy management
Keep schedules, retention and supported workload coverage up to date as the environment changes.
Restore coordination
Help users and technical teams recover files, SaaS data, endpoints or systems within the agreed scope.
Reporting
Cover backup health, exceptions, restores and next steps in regular service reviews.
Recovery readiness
Coordinate regular restore tests, or formal DR tests where they are part of your service.
A DR plan is the order in which the business comes back.
Disaster recovery is not a second copy of the data. It is the written, tested process for bringing technology services back in the right order after a major failure, cyber incident or site outage. We help you define and build that plan around the real dependencies in your environment.
1
Step 1: Business impact
Find the services whose outage would do the most operational, financial, safety or compliance harm.
2
Step 2: Recovery priorities
Group workloads into realistic recovery tiers, each with set RPO and RTO targets.
3
Step 3: Dependencies
Map the identity, DNS, network, databases, storage, apps and outside services that decide the recovery order.
4
Step 4: Recovery design
Choose the backup, replication, cloud recovery, storage and orchestration controls that deliver the result you need.
5
Step 5: Runbooks
Write down who does what, the technical steps, escalation, checks and decision points.
6
Step 6: Test and improve
Run the plan, keep evidence, find the weak points and update the design as your environment changes.
What a mature recovery capability should give you.
Results vary by product, licence, storage design and workload. RPO and RTO targets must be proven by testing. Backup software alone does not guarantee them.
Known recovery times: tested RPO and RTO for critical workloads, not guesses.
Ransomware resilience: restore points stay safe even if live systems or admin logins are breached.
Independent SaaS recovery: get Microsoft 365 and identity data back without relying only on native retention.
Cleaner incident recovery: known-good restore points, so compromised systems don’t go straight back into service.
Less guesswork: dependencies, roles and runbooks written down before the outage.
Portable protection: you keep your options as workloads move between your own servers and the cloud.
Audit evidence: proof that backups, retention, recovery tests and DR plans are kept up to date.
Clear ownership: SONAR can manage backup health and restores as an ongoing service.
Backup and recovery, without the jargon.
What is the difference between backup and disaster recovery?
Backup makes copies of data or systems that you can recover. Disaster recovery sets out how critical technology services are restored after a major outage or cyber incident. It covers recovery priorities, dependencies, RPO, RTO, roles and recovery steps.
What is RPO?
Recovery Point Objective is the most data loss you can accept, measured in time. For example, a four-hour RPO means the recovery design should normally give you a restore point no more than four hours old.
What is RTO?
Recovery Time Objective is the target time to restore a workload or service after a disruption. Different systems can have different RTOs, based on their impact on the business.
Does Vectra use Veeam for backup and disaster recovery?
Yes. We use Veeam Data Platform for enterprise backup and recovery, hybrid and multi-cloud protection, cyber resilience and more advanced disaster recovery needs.
Does Vectra use NinjaOne Backup?
Yes. NinjaOne Backup suits customers who want endpoint, server and SaaS protection in the same platform they use for endpoint management, patching, monitoring and automation.
Should Microsoft 365 be backed up separately?
If you need an independent way to recover, third-party SaaS backup can protect Exchange, OneDrive, SharePoint, Teams and other supported Microsoft 365 data. It guards against deletion, ransomware, wrong settings and retention limits. The design should match your own retention and recovery needs.
Can Microsoft Entra ID be backed up?
Yes. Current backup platforms can protect supported Microsoft Entra objects and settings. We can include identity recovery in your wider Microsoft 365 and disaster recovery design where needed.
What is immutable backup?
Immutable backup is stored so that it can’t be changed or deleted during the set protection period. It lowers the risk that ransomware, a compromised admin or a mistake wipes out every usable restore point.
How often should disaster recovery be tested?
It depends on how critical the service is, how often things change, your compliance duties and your recovery design. Critical services generally need testing more often than low-impact ones. What matters is that recovery is tested on a set schedule and after major change.
Can Vectra manage backups for us?
Yes. Through Vectra SONAR, we can monitor and run supported backup systems as part of the managed IT service. That includes backup health, fixing failures, policy management, restore coordination, reporting and agreed recovery testing.
Start with a conversation.
Speak to us about your cyber governance and compliance requirements.
We use essential cookies to make this site work, and anonymous analytics cookies to understand how it's used. You can accept all, reject non-essential, or review our cookies policy.
