Endpoints
Laptops and desktops, including the ones that work away from the office and rarely touch the internal network.
Data resilience
Data backup and recovery with Druva, operated by Lynxsource
A backup is only worth the restore it allows on the bad day. We operate Druva as a managed service so your critical data — endpoints, servers, SaaS, and cloud workloads — has continuous copies outside your perimeter, out of reach of an attack or a human error.
We do not hand over a console and step away. We configure the policies, watch that every backup completes, test the restores before you need them, and are on the other end when something has to be recovered. You get the outcome — data that comes back — not another tool to administer.
- Operating since
- 2009
- Certification
- ISO 27001:2022
- Model
- MSSP
- Presence
- 5 countries
The definition
What is managed backup and recovery with Druva?
It means Lynxsource configures, watches, and tests your data copies in Druva for you, and stands beside you during the restore when it is needed, instead of handing you a console for your team to administer.
Data is not lost in only one way. Ransomware encrypts it, a disk fails, someone deletes the wrong folder, an employee leaves and their mailbox goes with them. All four end the same way: somebody asks whether there is a copy, and the answer arrives late.
A managed service changes what you are buying. Instead of the tool, you hire whoever defines what gets backed up and how often, checks that last night’s copy actually completed, confirms the restore works before you need it, and performs the recovery with you. The license stays yours; what changes is who answers.
The scope
What data does Lynxsource protect with Druva?
Endpoints and servers, data living in SaaS — Microsoft 365 and Google Workspace — cloud workloads, and the retention compliance demands.
These are not five separate backups but one policy applied wherever the data lives. A file that starts on a laptop, passes through a shared Microsoft 365 folder, and ends up in a cloud workload has to be covered in all three places; miss one and the copy exists but the data does not come back whole.
Servers
Data center systems and workloads, with the frequency and retention policies each one calls for.
SaaS
Microsoft 365 and Google Workspace: mail, files, and sites. The provider guarantees the service, not your backup.
Cloud workloads
Whatever runs on cloud infrastructure, with copies isolated from the environment they protect.
Retention and compliance
Retention periods by data type, and evidence that the copy exists when someone audits it.
Backup is one piece of a broader data strategy.
The decision
Why managed rather than self-administered?
Because backup fails silently: nobody finds out until the day it is needed, and that day is no time to learn how to restore.
A copy that did not complete does not raise its hand. The nightly job dies, the policy leaves out a new folder, a machine has not connected in three months — and all of that coexists perfectly well with a console showing green. The fault does not surface when it fails; it surfaces when you restore.
And restoring under pressure is a separate skill. On the day of the incident you have to decide what comes back first, from which point in time, and to where, while the business is stopped and somebody asks every ten minutes. As a managed service that work is already done beforehand: verification is daily and the restore is tested, so the bad day means running a procedure instead of improvising one.
The operation
How does Lynxsource run your backup with Druva?
With continuous copies that need no backup windows, verification that each backup completed, restores tested in advance, and support on the day you have to recover.
The backup runs continuously and without stopping anyone’s work: there is no nightly window to meet and no machine to switch off. We define what is included, how often, and how long it is kept, and we adjust those policies when your operation changes — a new server, a department opening a new folder, a different retention obligation.
Verification sits on top of that. We check that copies completed and we test restores without waiting for an incident, which is the only way to know how long a recovery actually takes in your environment. And when it is time to recover, we do not send you a manual: we do it with you, deciding what comes back first and from which point.
The coverage
Which countries does Lynxsource operate in?
With in-house teams in Ecuador, Colombia, and Bolivia, and also in the United States and Canada.
In-house means the analysts, the automation, and the operations center belong to Lynxsource. In a reseller model your provider opens a ticket with another provider and passes the answer along when it arrives; here whoever answers is whoever decides.
The service is the same in all five countries, with the same SOC behind it and the same triage and response figures. What changes is who you have nearby, not the quality of the monitoring.
Questions about this service
Frequently asked questions
Does backup protect against ransomware?
Yes, when the copies are isolated and cannot be altered: an attacker who encrypts your systems does not reach a backup held outside your perimeter and protected from modification. That is the difference between paying and restoring.
How long does a recovery take?
It depends on the volume and on what comes back first. That is why we test restores before an incident: to give you times measured in your environment, not a promise.
Does it back up Microsoft 365 and Google Workspace?
Yes. The provider guarantees the service is available, not that your data returns after a deletion or an encryption; that is a separate backup, and it is the one we operate.
Does the data leave the country?
The region where the copies reside is chosen when the service is configured and is documented. If your operation requires a specific region, it is defined from the start.
What happens when an employee leaves?
Their data is kept according to the agreed retention policy, so their mailbox and files remain recoverable after the account is closed.
Do you see the content of my data?
No. We operate the protection — policies, verification, and restores — we do not read the content of what is backed up.
More from the site
Keep reading
Let us look at your case before moving anything.
We review what is backed up today, what was left out without anyone noticing, and how long a restore would actually take. Free and with no commitment.
Request a free assessment
We respond within one business day. Ecuador, Colombia, Bolivia, the United States, and Canada.