Loading...

Why Bacularis for MSPs?

Introduction

Managed Service Providers (MSPs), hosting companies, and IT service providers have different approaches to protecting their customers' data. Some offer backup as a dedicated service, while others provide it as part of broader IT, hosting, or infrastructure services.

Regardless of the service model, building and operating backup services requires more than just software that performs backups and restores. Service providers also need tools to manage backup environments, organize their daily operations, integrate with existing systems, and adapt their services to changing customer needs.

Free and open-source software offers an interesting approach to these challenges. Instead of adopting a predefined service model, providers can select the technologies they need and build solutions around their own infrastructure, operational requirements, and business models.

Bacula Community and Bacularis can provide a foundation for building such backup services.

In this article, we will explore the benefits of using open-source backup software, the importance of maintaining control over your backup infrastructure, and the opportunities for building independent backup services around Bacula and Bacularis.

Why open source matters for MSPs

For managed service providers, choosing backup software is not only a technical decision. It can also influence how they develop their services, manage their infrastructure, and respond to changing business and customer requirements.

Free and open-source software gives service providers the freedom to make many of these decisions independently.

Some of the benefits of this approach include:

  • Freedom of use – use the software for both internal operations and commercial services without requiring a separate commercial-use license.

  • Access to source code – understand how the software works, review its implementation, and make modifications when needed.

  • Technology independence – maintain greater control over the software you use without relying entirely on the commercial decisions of a single vendor.

  • Customization and integration – adapt the software to existing infrastructure, tools, and operational workflows.

  • Long-term flexibility – develop and evolve backup services according to your own requirements and priorities.

These freedoms can be particularly valuable for service providers that want to build long-term services around technologies they can understand, control, and adapt.

Commercial use and licensing

Bacularis is free and open-source software released under the GNU Affero General Public License version 3 (AGPLv3), together with additional license terms pursuant to Section 7 of the Affero General Public License.

This license allows service providers to use Bacularis in their commercial activities, including offering paid backup services to their customers. There is no separate MSP license required for this purpose.

As with any open-source software, service providers need to comply with the applicable license terms. For example, if you modify Bacularis and allow users to interact with your modified version over a network, the AGPLv3 requires you to offer those users access to the corresponding source code of that version.

For more information, please refer to the Bacularis license documentation.

No capacity-based or per-client licensing

An important consideration for service providers is how software licensing costs change as their backup services grow.

Neither Bacula Community nor Bacularis imposes licensing fees or license-based limits on the number of backup clients or the amount of backup storage capacity used.

This means:

  • No software licensing fees per backup client or protected system.

  • No software licensing fees per terabyte of backup storage.

  • No license-based limits on the number of backup clients.

  • No license-based limits on backup storage capacity.

Service providers can expand their backup environments and onboard new customers without having to purchase additional software licenses based on these parameters.

The practical capacity and performance of a backup environment depend on its architecture, configuration, and available infrastructure resources rather than on licensing tiers.

Open source and operational costs

Using free and open-source software does not mean that providing backup services is free of costs.

Infrastructure, storage, network resources, administration, maintenance, security, and customer support are all part of operating a backup service. Optional paid services and software distribution channels may also have their own costs.

The value of open source goes beyond the absence of software license fees. It gives service providers greater freedom to decide how they build their solutions, where they invest their resources, and how they develop their services over time.

Bacula Community and Bacularis - a foundation for backup services

Bacula and Bacularis complement each other, providing different parts of a backup solution that service providers can use as a foundation for their own services.

Bacula Community is an open-source network backup system responsible for performing backup and restore operations. Its modular architecture allows service providers to protect systems across different networks, locations, and operating environments.

Bacularis provides a web-based management interface and a REST API for Bacula. It allows administrators to manage backup jobs, configure backup resources, monitor backup operations, perform restores, and control user access to selected resources and functions.

Together, these two projects provide a foundation on which service providers can build their own backup solutions.

An MSP can deploy Bacula and Bacularis on its own infrastructure, define how backup services are delivered, and decide how these technologies become part of its existing service portfolio.

For example, a service provider can use Bacularis as an internal management interface for its administrators, provide customers with controlled access to backup and restore operations, or integrate backup management into its own applications and customer portals using the REST API.

Bacula and Bacularis provide the underlying technology, while the service provider defines the service itself. This separation gives MSPs the flexibility to develop backup services according to their own operational requirements, customer needs, and business models.

Building backup services on an open-source foundation

Mobile-friendly web access

Bacularis provides a responsive web interface that adapts to different screen sizes, including desktops, laptops, tablets, and smartphones.

Administrators can access their backup management environment from different devices using a web browser, without installing dedicated client applications.

This capability can be particularly valuable for service providers offering customer self-service. Customers can access their backup resources, check backup job status, and perform permitted backup and restore operations from both desktop and mobile devices.

MSPs can therefore offer mobile-friendly access to backup services without having to develop and maintain a separate mobile application.

Where network access is provided by the MSP, customers can use mobile devices to access Bacularis under the same authentication mechanisms, resource restrictions, and user permissions as when using desktop computers.

Control over your backup infrastructure

Every service provider has its own infrastructure, operational practices, and customer requirements. A backup solution that fits one service provider may not necessarily be the right solution for another.

Using Bacula and Bacularis allows MSPs to retain control over many of the decisions involved in building and operating their backup environments.

Infrastructure, data location, and geographical flexibility

Both Bacula and Bacularis are network-based solutions. Their components do not need to be installed on the same server or operate in the same physical location.

Backup infrastructure, protected systems, backup storage, and management interfaces can be distributed across different locations, depending on the requirements of the service provider.

These locations can include:

  • Different servers within the same data center.

  • Multiple data centers in different cities or countries.

  • Different offices and branches of an organization.

  • Infrastructure located at customer premises.

  • A combination of on-premises and cloud environments.

This geographical flexibility allows MSPs to design backup services around their own infrastructure and the locations of their customers, rather than requiring all components to operate in a single location.

Service providers can also decide where backup data is stored, taking into account customer requirements, data residency, security policies, and available storage resources.

When designing geographically distributed backup environments, MSPs need to consider network connectivity, bandwidth, latency, secure communication, and applicable data residency requirements.

Backup policies and storage

Different customers may require different backup schedules, retention periods, storage arrangements, and recovery strategies.

With Bacula and Bacularis, service providers can define backup configurations according to these individual requirements rather than adopting a single predefined backup service model.

MSPs can also choose from the storage technologies supported by their Bacula environments and adapt their storage infrastructure as their services grow or customer requirements change.

Backup copies, migration, and storage flexibility

Bacula Community supports both disk and magnetic tape storage, giving service providers flexibility in designing their backup storage infrastructure.

Its Copy and Migration Jobs extend this flexibility by allowing existing backups to be copied or migrated between different storage resources and Pools, including storage managed by different Bacula Storage Daemons.

These capabilities can be particularly valuable for MSPs that want to offer backup services with additional storage options, such as:

  • Multi-site backup storage – maintaining backup copies in different data centers or geographical locations.

  • Off-site backup copies – storing additional copies outside the primary backup location.

  • Disk-to-Disk-to-Tape (D2D2T) – keeping backups on disk for convenient access while creating additional copies on magnetic tape.

  • Storage tiering – migrating backups between storage resources with different performance, capacity, or cost characteristics.

Multi-site Backup Storage

Copy and Migration Jobs operate on existing backup data without requiring the protected systems to perform another backup.

Bacularis supports the configuration, execution, scheduling, and monitoring of these Bacula Community operations through its web interface.

This allows service providers to design their own backup storage strategies and build service offerings that address different customer requirements for data protection, geographical redundancy, recovery, and long-term retention.

As with other backup operations, service providers need to carefully plan their storage configurations, retention policies, and recovery procedures, taking into account the compatibility of their backup workloads with Copy and Migration Jobs.

For more information about Copy and Migration Jobs, including transfers between different Storage Daemons, please refer to the Bacula Community documentation.

Bacula Disk-to-Disk-to-Tape (D2D2T)

Deployment and integration

Bacularis supports working with multiple Bacula environments through a single web interface. This allows service providers to organize their backup infrastructure according to different customers, locations, or operational requirements.

Its REST API also provides opportunities to integrate backup management with existing tools, customer portals, and operational workflows.

Service providers can introduce these integrations gradually, according to their own needs and available resources.

Software lifecycle

Maintaining control over the software lifecycle is another aspect of infrastructure independence.

With a self-hosted solution, service providers can plan software updates, test new versions in their own environments, and decide when to introduce changes to their production infrastructure.

This freedom also comes with responsibility. Service providers need to maintain their environments, apply security updates, monitor their infrastructure, and ensure that their backup services continue to meet customer requirements.

Administrative expertise and infrastructure planning

Building and operating a reliable backup service requires administrative expertise. Service providers using Bacula and Bacularis need qualified administrators with a good understanding of both projects and their underlying technologies.

Bacularis simplifies many aspects of Bacula configuration and management, but it does not replace the administrator's knowledge, experience, or responsibility for designing the backup environment.

Some of the important areas that require careful planning include:

  • Backup infrastructure architecture and capacity planning.

  • Bacula Pool and Volume design.

  • Volume size and quantity limits.

  • Volume allocation, retention, recycling, and reuse policies.

  • Backup schedules and recovery requirements.

  • Storage capacity monitoring and future growth planning.

  • Security, authentication, and customer access restrictions.

Pool and Volume management deserves particular attention. Incorrectly designed storage and retention policies can lead to situations where backup storage becomes full or no suitable Volumes are available for new backup jobs. This can interrupt backup operations and affect the continuity of customer data protection.

Service providers must therefore design, test, monitor, and maintain these configurations according to their own operational requirements and expected service growth.

Bacularis provides tools that assist administrators in these activities, while the responsibility for infrastructure design, configuration, and operation remains with the service provider.

Having control over backup infrastructure does not mean that every operational challenge disappears. It means that service providers have the freedom and responsibility to make their own decisions about how these challenges are addressed.

Building services around Bacula Community

Bacula Community and Bacularis provide a flexible foundation that service providers can use to build different types of backup services.

Rather than being limited to a predefined service model, MSPs can combine the capabilities of both projects with their own infrastructure, administrative expertise, and existing services.

The following examples illustrate some of the service models that can be built around Bacula Community and Bacularis.

One open-source foundation, different service models

Backup as a service (BaaS)

Service providers can build and operate their own backup infrastructure and offer backup services to customers who do not want to maintain their own backup environments.

The MSP manages backup operations, storage resources, retention policies, monitoring, and recovery procedures, while customers benefit from the data protection service.

Depending on the service offering, backup data can be stored in one or more data centers operated or selected by the service provider.

Managed backup services

MSPs can also provide backup management services for customers who already have their own infrastructure or prefer to keep their backup data on their premises.

Bacula Community and Bacularis can be deployed within customer environments, while the service provider takes care of configuration, monitoring, maintenance, and backup and restore operations.

The network-based architecture of both projects allows administrators to manage geographically distributed backup environments without having to be physically present at each location.

Customer self-service

Service providers can extend their managed backup services by giving customers controlled access to selected backup resources and operations.

Depending on the permissions assigned by the MSP, customers can monitor their backup jobs, browse available backups, and perform restores without having to contact the service provider for every operation.

The responsive Bacularis web interface also allows customers to access these functions from desktops, laptops, tablets, and smartphones.

This approach can complement fully managed backup services by giving customers more flexibility while allowing the service provider to retain administrative control over the underlying backup infrastructure.

Extended data protection services

Bacula Community provides capabilities that allow service providers to develop additional data protection options for customers with different recovery, retention, and storage requirements.

Examples include:

  • Additional backup copies stored in geographically separated data centers.

  • Off-site backup copies for disaster recovery purposes.

  • Combined disk and magnetic tape backup storage.

  • Long-term backup retention.

  • Different backup storage tiers and retention policies.

MSPs can combine these capabilities to design service offerings that address different customer requirements.

The underlying backup configurations, storage policies, recovery procedures, and service commitments are defined and maintained by the service provider.

Backup as part of existing IT services

Backup services do not necessarily have to be offered as a standalone product.

Hosting companies, infrastructure providers, system administrators, and other IT service providers can use Bacula Community and Bacularis to introduce or extend data protection capabilities within their existing service portfolios.

The REST API provided by Bacularis also allows service providers to integrate backup management into their own applications, customer portals, and operational workflows.

These integrations can be developed gradually, allowing providers to extend their services as their business and customer requirements evolve.

These service models are not mutually exclusive. A service provider can combine them and develop its own approach to delivering backup services using the same open-source technological foundation.

Your services, your business model

Every service provider has its own approach to delivering services, working with customers, and developing its business.

Bacula Community and Bacularis provide technology that MSPs can use to build their backup services. How these services are designed, operated, offered, and priced is up to the service provider.

Freedom to define your services

MSPs can independently decide how to structure their backup service offerings, including:

  • The types of systems and environments they protect.

  • Backup schedules and retention options.

  • Available storage capacities and locations.

  • Additional off-site backup copies.

  • Customer access and self-service capabilities.

  • Recovery options and support arrangements.

  • Service pricing and billing models.

Neither Bacula Community nor Bacularis imposes a predefined commercial service model on the service provider.

Since the software does not require per-backup-client or capacity-based licenses, MSPs can also decide how to structure their own service pricing independently of such software licensing fees.

Independence in customer relationships

Service providers maintain their own relationships with their customers.

They define the scope of their services, establish service agreements, provide customer support, and decide how backup capabilities are presented within their own service portfolios.

There is no separate Bacularis MSP edition, commercial-use license, or MSP program required to start building backup services with Bacularis.

Building the complete service

Bacula Community and Bacularis provide the backup technology and management capabilities, but they do not constitute a complete, ready-to-use managed backup business platform.

Depending on the service model, MSPs may need additional systems and processes for:

  • Customer onboarding and service provisioning.

  • Subscription management and billing.

  • Customer support and incident management.

  • Infrastructure and service availability monitoring.

  • Service-level agreement (SLA) management.

  • Usage reporting and service accounting.

Some of these processes can be integrated with Bacularis using its REST API, while others can be handled independently using the service provider's existing tools and procedures.

This gives MSPs the freedom to choose the systems that best fit their business rather than requiring them to adopt a predefined business management platform.

Freedom and responsibility

The freedom to design and operate independent backup services also comes with responsibility.

Service providers need to ensure that their backup infrastructure is properly designed, securely configured, adequately monitored, and regularly maintained by administrators with the necessary Bacula Community and Bacularis expertise.

This includes planning storage capacity, managing Pools and Volumes, reviewing access permissions, testing recovery procedures, and preparing for infrastructure failures.

The service provider is also responsible for meeting its contractual commitments to customers, including backup availability, recovery requirements, security, and customer support.

Bacularis is an open-source project and does not provide guaranteed technical support under a service-level agreement (SLA). MSPs should make their own arrangements for the technical expertise and support they require to operate their services reliably.

The role of Bacula Community and Bacularis is to provide an open technological foundation. The service provider remains in control of the service, its operation, and its business model.

Getting started

Bacula Community and Bacularis provide a free and open-source foundation for building independent backup services. They give service providers the freedom to design their own backup infrastructure, adapt it to customer requirements, and develop services according to their own business models.

If you are considering using Bacula Community and Bacularis in your managed backup services, a good starting point is to set up a test environment. This will allow you to explore the available capabilities, become familiar with both projects, and evaluate how they fit your operational and business requirements before deploying them in production.

The following resources can help you get started:

  • Online demo – explore the Bacularis web interface without installing the software.

  • Quick start guide – learn how to install and start using Bacularis.

  • Documentation – explore the available features, configuration options, and integration capabilities.

In the next part of this series, we will take a closer look at the practical aspects of managing customer backups with Bacularis, including everyday backup operations, customer access, resource management, roles, and permissions.