Deployment and training in Bacula & Bareos
The world’s most established open-source backup solutions, deployed, optimized and migrated by a global Bacula reference — with official training and certification so your team takes control of your backup.
What Bacula and Bareos are
Bacula and Bareos are the two most established and mature open-source enterprise backup solutions on the market. Both were born from the same original project and share the same modular client-server architecture, capable of protecting anywhere from a few servers to tens of thousands of heterogeneous clients — Linux, Windows, macOS, databases, virtual machines and applications.
The architecture is organized into three independent daemons: the Director, which orchestrates all jobs, schedules and policies; the Storage Daemon, which writes and reads data to and from media (disk, tape or cloud); and the File Daemon, the lightweight agent installed on each client to be protected. All metadata — which files were saved, on which volume, at what moment — lives in a relational catalog, typically PostgreSQL or MySQL.
This robustness explains why governments, universities, providers and large companies have used Bacula and Bareos in production for more than two decades to protect their most critical data, without depending on a proprietary vendor and without a scale ceiling imposed by licensing.
The modular architecture of Bacula / Bareos
What makes Bacula and Bareos so scalable is the clear separation of responsibilities: each component does one thing and can grow independently. On the left, the components that orchestrate and process the backup; on the right, the media and targets where the data actually rests.
The daemons and the catalog
Four decoupled pieces that talk over the network: orchestration, writing, collection on the clients and the metadata persisted in a relational database.
Where the data rests
The Storage Daemon abstracts the target: the same job can write to fast disk, long-retention tape or object cloud, according to the retention and cost policy.
Why this modularity scales
- Each component grows on its own — add Storage Daemons for more throughput, or File Daemons for more clients, without rewriting the environment.
- Geographic distribution — a central Director can command Storage Daemons in different branches and data centers, writing close to where the data is born.
- Media independence — disk, LTO tape and S3 cloud coexist; policies move data between tiers according to age and cost.
- Relational catalog — in PostgreSQL or MySQL, it enables granular restores, auditing and reporting over millions of files.
How OpenTechs delivers Bacula / Bareos
Deployment from scratch or professionalization
We install and configure Bacula or Bareos in a new environment — Director, Storage Daemon, File Daemons, catalog and console — or we take over a poorly configured legacy environment and bring it up to a professional standard, with reliable jobs, correct retention and tested restores.
Performance tuning
Slow backup or overrunning window? We optimize jobs, schedules and the Storage Daemon: job concurrency, spooling, block size, pools and volumes, catalog indexes and incremental/differential/full strategies to fit the window and restore fast.
Migration between versions and solutions
We carry out migrations between Bacula/Bareos versions, from Bacula to Bareos (or vice versa) and from proprietary solutions to open source — preserving history, catalog and media where possible, with a cutover plan and end-to-end validation.
Official training with certification
We train your team with official training, in-person or in-company, with certification. From architecture to daily operation, from tuning to disaster recovery — so your team operates the backup with real autonomy, without depending on third parties.
Three ways to work with OpenTechs
You can engage OpenTechs to deploy and audit the environment, to upskill your team with certified official training, or for ongoing support with an SLA. All three combine — many clients deploy, train the team and keep a backup support contract.
Deployment / Health-check
- Complete installation of Bacula or Bareos from scratch
- Director, Storage Daemon, File Daemons and catalog
- Audit and optimization of an existing environment
- Restore test and delivered documentation
Official Training
- Official training, in-person or in-company
- Certification of the team at the end
- From architecture to operation, tuning and recovery
- Content in English, by instructors who are a global Bacula reference
- Material and hands-on labs
Ongoing Support
- Support with an SLA
- Assisted operation and job monitoring
- Managed updates and patches
- Incident response and disaster recovery
- Periodic health and capacity reviews
Bacula / Bareos vs. NG Backup — which to choose?
| Criterion | Bacula / Bareos (open source) | NG Backup (enterprise) |
|---|---|---|
| License cost | No license per data — you do not pay per protected terabyte | Enterprise licensing, with vendor support included |
| Team required | Requires its own skilled team to operate and tune | Operable with a lean team; the vendor handles the complexity |
| Global dedup | Available, with manual configuration and fine-tuning | Global dedup out of the box, optimized and supported |
| Vendor support | Community + OpenTechs services (under contract) | Vendor support with an SLA, guaranteed |
| Advanced immutability | Possible (S3 Object Lock, tape), but manual | Immutability and anti-ransomware integrated and managed |
| Best for… | Those who have (or want to build) their own team and seek total independence | Those who want vendor support and the least operational effort |
When to reach out to us
Start from scratch
You need a reliable backup strategy and want to start right, with Bacula or Bareos well architected from day one.
Professionalize a legacy environment
You already have Bacula/Bareos, but poorly configured, with failing jobs and restores never tested. We bring it up to a professional standard.
Upskill the team
You want full autonomy: official training with certification for your team to operate, tune and recover without depending on third parties.
Migrate from a proprietary solution
Moving away from expensive proprietary backup toward open source, with a cutover plan, history preservation and validation.
Audit and optimize
Slow backup or overrunning window: health-check, tuning of jobs and storage, and a review of the retention policy.
Integrate tape and cloud
Combine fast disk, long-retention LTO tape and off-site S3 cloud into a tiered media strategy.
Why deploy and train with OpenTechs
- Global Bacula reference — based in Brasília, with internationally recognized standing in the community.
- Training with certification — official, hands-on training that generates real autonomy for your team.
- Support in English — deployment, tuning and assisted operation with an SLA, in your language and time zone.
- Real tuning — job, storage and catalog performance tuned for your window and your volume.
- Total independence — no lock-in: the goal is to put your team in command of its own backup.
- Community — we contribute and stay at the frontier of Bacula and Bareos, passing that on to you.
Frequently asked questions
Bacula or Bareos — which should I use?
Do I need my own team to use open source?
Do you train with certification?
Do you migrate from my current backup?
When does NG Backup make more sense than open source?
Shall we deploy or train your team in Bacula / Bareos?
Get a proposal for deployment, tuning, migration or official training with certification — tailored to your environment. No obligation.
Request a proposal
Disponível em: 
Português (Portuguese (Brazil))
English
Español (Spanish)