Loading...

Managing customer backups

Introduction

In the first part of this series, we explored how Bacula Community and Bacularis can provide a free and open-source foundation for building independent backup services.

Once a backup service has been established, service providers face everyday operational challenges. They need to organize backup resources for different customers, monitor backup operations, manage storage capacity, respond to problems, and restore customer data when needed.

Some service providers manage all backup and restore operations on behalf of their customers. Others also give customers access to selected backup resources and operations as part of their services.

Bacularis provides a web-based management interface for Bacula Community that can be used in both approaches. It helps administrators manage their backup environments while also providing mechanisms for controlled customer access.

In this article, we will look at backup management from two perspectives:

  • The MSP administrator who configures, manages, monitors, and maintains backup environments.

  • The customer who can access their own backup resources and perform selected operations as part of a self-service offering.

Throughout the article, we will use an illustrative MSP environment with two fictional customers to demonstrate how different Bacula Community and Bacularis capabilities can be used together in managed backup services.

Organizing customer backup environments

A managed service provider may be responsible for protecting many different systems belonging to different customers. Each customer may have its own infrastructure, applications, backup requirements, schedules, and retention policies.

Bacula Community provides a flexible resource-based configuration model that allows administrators to organize backup environments according to these requirements. Bacularis provides a web interface for configuring and managing these resources.

MSP customers and Bacula Clients

When managing backups for multiple customers, it is important to distinguish between an MSP customer and a Bacula Client.

An MSP customer is an organization or individual receiving backup services from the service provider. A Bacula Client is a configuration resource representing a Bacula File Daemon through which data can be backed up and restored.

A single MSP customer may have multiple Bacula Clients representing different servers, workstations, virtual machines, or other protected systems.

For example, consider a service provider managing backups for two customers:

Customer A

  • Server 1

  • Server 2

  • Server 3

  • Server 4

Customer B

  • Server 1

  • Server 2

  • Server 3

Although the MSP serves two customers, its Bacula environment contains seven Client resources in this example.

This distinction is particularly important when organizing backup resources and configuring customer access. An individual customer account in Bacularis can be configured to provide access to multiple Bacula Clients and their associated backup resources.

Organizing backup resources

Organizing backup resources

Bacula Community provides different types of configuration resources that administrators can use to define how customer systems are protected.

Some of the fundamental resources and concepts include:

  • Client – defines a connection to a Bacula File Daemon.

  • Job – defines a backup, restore, verification, or other supported operation.

  • FileSet – defines the files, directories, and backup options used to protect data.

  • Schedule – defines when Jobs are executed and can specify backup levels and other execution options.

  • Pool – defines a logical collection of backup Volumes and associated media management policies.

  • Volume – represents a backup medium, such as a disk-based backup file or magnetic tape.

  • Storage – defines access to storage resources used by Bacula for reading and writing backup data.

These resources can be combined to meet different customer requirements.

For example, one customer may require daily backups with a 30-day retention period, while another may require more frequent backups, longer retention, and additional off-site copies.

The MSP administrator can design the corresponding backup configurations and manage them through Bacularis.

Consistent resource naming

As the number of customers and protected systems grows, a consistent resource naming convention becomes increasingly important for everyday backup management.

One possible approach is to use a customer-specific prefix in the names of Bacula resources. This helps MSP administrators identify resources belonging to individual customers within their backup environments.

For example, Client resources can be named using a combination of the customer identifier and the hostname:

  • customer-a-server1-fd

  • customer-a-server2-fd

  • customer-a-server3-fd

  • customer-a-server4-fd

  • customer-b-server1-fd

  • customer-b-server2-fd

  • customer-b-server3-fd

Using host-based names allows Client resources to remain identifiable even when the applications or types of data protected on a particular host change over time.

Naming conventions for other Bacula resources should reflect their individual purpose. While a common customer prefix can help identify customer-specific resources, the remaining parts of resource names can follow different conventions depending on the resource type.

For example, Job names may identify the protected host and backup operation, while Pool names may reflect their intended usage, backup levels, storage policies, or association with specific protected systems.

Examples of Pool names include:

  • customer-a-pool-full

  • customer-a-pool-incremental

  • customer-a-pool-differential

  • customer-a-pool-offsite

Alternatively, if Pools are organized around individual protected systems, their names could follow a convention such as:

  • customer-a-pool-server1

  • customer-a-pool-server2

  • customer-a-pool-server3

These are examples of different naming approaches rather than recommendations for a particular Pool architecture. The actual organization of backup resources should follow the storage design and backup policies defined by the MSP.

Resource names should be meaningful not only to MSP administrators but also to customers who use the Bacularis self-service interface. Customers may encounter these names when browsing their backup resources, reviewing job logs, or selecting resources when running permitted backup operations.

Neither Bacula Community nor Bacularis automatically imposes a customer-specific naming convention. Service providers should establish their own naming standards and apply them consistently across their backup environments.

Consistent resource naming helps with identification, searching, filtering, and everyday administration. However, naming conventions do not provide access control or customer isolation. These require properly configured authorization mechanisms.

Reusable configurations with Configs and Patterns

Managed service providers frequently perform similar configuration tasks when adding new customers, protecting additional systems, or maintaining existing backup environments.

Instead of manually preparing each configuration from scratch, administrators can use the Configs and Patterns feature available in Bacularis to create reusable Bacula configuration templates.

The feature provides three mechanisms that are particularly useful in MSP environments:

  • Configs – reusable sets of configuration directives for individual Bacula resources, such as Clients, Jobs, FileSets, Schedules, or Pools.

  • Patterns – collections of Configs that can be applied together to the configuration of a Bacula component, such as the Director, Storage Daemon, or File Daemon.

  • Variables – placeholders for values provided by the administrator when applying Configs or Patterns.

Variables make reusable configurations particularly flexible. A single configuration template can be used for different customers and protected systems without requiring a separate template for each of them.

For example, an MSP can define variables representing a customer identifier, a server name, and a File Daemon address.

An example Client configuration template could contain the following directives:

Client {
    Name = "${customer}-${server}-fd"
    Address = "${fd_address}"
    ...
}

When applying the configuration, Bacularis prompts the administrator to provide values for these variables.

For example, using customer-a as the customer identifier and server1 as the server name results in a Client resource named customer-a-server1-fd.

The same variables can also be used in other Configs belonging to a Pattern. This allows administrators to prepare sets of related resources with consistent naming and references between them.

For MSPs, this approach can help:

  • Reduce repetitive configuration work when adding new customers or protected systems.

  • Maintain consistent resource naming conventions.

  • Reuse standardized backup configurations across customer environments.

  • Reduce the risk of manual configuration errors.

  • Apply common configuration changes to multiple selected resources.

Bacularis also provides configuration simulation, allowing administrators to review the expected configuration changes before they are written. Overwrite policies allow administrators to control how existing configuration directives are handled.

The Configs and Patterns feature is intended for Bacularis administrators and can support the technical provisioning and maintenance processes of a managed backup service.

Service providers remain responsible for designing, testing, and maintaining their configuration templates according to their own backup policies, security requirements, and operational standards.

For more information, please refer to the Configs and Patterns documentation and the documentation on configuration variables.

Bacularis patterns and configs - One pattern, many configurations

Shared and separate backup environments

Depending on their requirements, service providers can organize customer backup resources within a shared Bacula environment or deploy separate Bacula environments for individual customers or groups of customers.

Bacularis supports connecting to multiple Bacularis API hosts from a single Bacularis Web interface, allowing administrators to work with different Bacula environments from a common management interface.

The choice between shared and separate environments depends on factors such as customer requirements, security, administrative practices, infrastructure resources, and operational complexity.

We will explore these deployment approaches in more detail in the third part of this series.

In the following sections, we will focus on how administrators can manage customer backup resources and how controlled access to these resources can be provided to customers.

 

Day-to-day backup management

Once customer backup environments have been configured, MSP administrators need to manage and monitor their daily operations.

Bacularis provides a web-based management interface that brings together many of the tools needed for everyday administration of Bacula Community environments.

Administrators can work with backup jobs, protected systems, schedules, storage resources, job histories, and recovery operations through a common web interface.

Monitoring backup operations

Monitoring backup operations is an important part of maintaining a reliable managed backup service.

The Bacularis dashboard provides administrators with an overview of backup activity and job results. Administrators can also use the Jobs page to examine individual operations in more detail.

Bacularis for MSPs - dashboard main view

 

For example, in our MSP environment with Customer A and Customer B, the administrator can review backup jobs for all seven protected systems, identify unsuccessful operations, and investigate problems affecting individual customers.

Consistent resource naming, as described in the previous section, helps administrators identify customer-specific jobs and resources when searching and filtering backup information.

When investigating a backup job, administrators can review information such as:

  • Job status and execution time.

  • Backup level and associated Client.

  • Number of backed-up files and amount of data.

  • Storage and Pool used by the job.

  • Job error information.

  • Detailed job logs.

These details help administrators understand what happened during a backup operation and identify issues that require further investigation.

Bacularis for MSPs - job list
 

Managing backup jobs and schedules

Different customers may have different requirements regarding backup frequency, protected data, and recovery objectives.

Bacula Community allows administrators to define individual backup configurations using Jobs, FileSets, Schedules, Pools, and other configuration resources.

Bacularis provides a web-based interface for configuring and managing these resources.

For example, Customer A may require daily backups of all four servers, while Customer B may require more frequent backups of one of its three servers.

The MSP administrator can prepare different backup configurations to meet these requirements and adjust them as customer needs change.

In addition to scheduled operations, administrators can manually run backup jobs when needed, for example before system maintenance, application updates, or other important changes in customer environments.

Bacularis also allows administrators to monitor running jobs, cancel operations when necessary, and review the results of completed jobs.

Managing backup operations across multiple environments

An MSP does not necessarily need to manage all customer backups within a single Bacula environment.

Depending on the chosen deployment model, customer backup resources may be distributed across multiple independent Bacula environments.

By connecting Bacularis Web to multiple Bacularis API hosts, administrators can access and manage these environments from a common web interface without having to maintain a separate web interface for every installation.

This can be particularly useful for service providers managing backup infrastructures at different customer locations or data centers.

Restoring customer data

Data recovery is one of the most important operations performed by a managed backup service provider.

Bacularis provides web-based restore tools that allow administrators to browse available backups, select files and directories, and configure restore operations according to their requirements.

Depending on the backup type and the recovery scenario, administrators can restore selected files, directories, or larger sets of data.

Restores can also be directed to alternative locations or authorized destination systems when supported by the backup configuration and the recovery method.

For example, an MSP administrator may use Bacularis to recover an accidentally deleted file for Customer A or restore data to a replacement server belonging to Customer B.

Bacularis offers different restore modes, including Simple Restore, which provides a simplified way to perform common file recovery operations.

Bacularis for MSPs - restore file browser

 

Service providers can use these tools to perform restores on behalf of their customers or provide controlled access to selected restore capabilities as part of a customer self-service offering.

We will explore customer access and self-service in more detail in the following sections.

Managing backup storage, Pools and Volumes

Managing backup storage is an essential part of operating a reliable managed backup service.

As service providers add new customers, protect additional systems, and introduce different retention options, their backup storage requirements evolve.

Bacula Community provides flexible mechanisms for organizing backup media and controlling their lifecycle. Bacularis provides tools that help administrators configure, monitor, and manage these mechanisms through a web interface.

Organizing Pools and Volumes

In Bacula Community, Pools are used to organize backup Volumes and define policies associated with their management and lifecycle.

Service providers can organize Pools according to their own operational requirements, for example:

  • Individual MSP customers.

  • Individual protected systems or groups of systems.

  • Full, Differential, and Incremental backup levels.

  • Different retention requirements.

  • Primary and off-site backup storage.

  • Different storage technologies.

These approaches can also be combined when appropriate.

For example, an MSP may use separate Pools for Customer A and Customer B, or define additional Pools for customers requiring longer retention periods or off-site backup copies.

The appropriate Pool organization depends on the backup architecture, storage infrastructure, recovery requirements, and operational policies defined by the MSP.

Bacularis allows administrators to configure Pool resources and manage associated Volumes, including their properties, status, retention settings, and recycling options.

Bacularis for MSPs - pool list

 

Understanding retention and recycling

Bacula Community provides different retention mechanisms, including File Retention, Job Retention, and Volume Retention.

These mechanisms have different purposes and should not be treated as interchangeable.

The expiration of a retention period does not necessarily mean that backup data is immediately removed from storage or that the occupied disk space becomes available.

Due to the way Bacula manages backup Volumes, their reuse depends on Volume status, pruning and recycling policies, Volume limits, and other relevant configuration settings.

When a Volume becomes eligible for recycling and is selected for reuse, Bacula can reuse it for new backup data.

Bacula's approach is to preserve backup data on Volumes for as long as possible, according to the configured retention and recycling policies. Backup data is not immediately overwritten simply because its retention period has expired.

For service providers, it is important to understand these mechanisms when designing retention policies and planning storage capacity.

Volume limits and storage capacity

The physical capacity of backup storage is not the only factor determining whether a new backup job can write its data.

Bacula configuration settings can also affect the availability of suitable backup Volumes.

Examples include:

  • Volume limits.

  • Volume retention settings.

  • Volume recycling policies.

  • Volume availability and status.

  • Storage capacity and growth.

These settings need to be considered together.

For example, a backup Pool may reach its configured maximum number of Volumes even when physical disk space is still available. Alternatively, backup storage may become full before existing Volumes become eligible for recycling.

Both situations can prevent new backup jobs from continuing normally.

Pool and Volume configuration is one of the most important aspects of designing and maintaining a Bacula backup environment. It requires particular attention and solid administrative experience with Bacula.

For this reason, MSP administrators should carefully design and test their Pool and Volume configurations in a test environment before introducing them into production. They should also regularly review these configurations as backup requirements and storage usage change.

Monitoring backup media

Bacularis provides administrators with access to information about backup Pools and Volumes.

Administrators can use this information to review the state of their backup media, identify available and occupied Volumes, examine retention and recycling information, and investigate media-related problems.

This information can support everyday storage management and help administrators identify situations requiring further investigation or configuration changes.

However, Volume usage information alone does not provide a complete picture of physical storage capacity.

Service providers should also monitor their underlying storage infrastructure, including available filesystem capacity, hardware health, and storage growth.

Combining Bacula media management information with infrastructure-level monitoring helps MSPs maintain a more complete view of their backup storage environments.

Bacularis for MSPs - volume list

 

Managing Copy and Migration Jobs

As described in the first part of this series, Bacula Community supports Copy and Migration Jobs that operate on existing backup data.

Service providers can use these mechanisms as part of their storage management and data protection strategies, including:

  • Maintaining additional backup copies in another location.

  • Creating off-site backup copies.

  • Copying disk-based backups to magnetic tape.

  • Migrating backups between different storage tiers.

Bacularis provides web-based tools for configuring, executing, scheduling, and monitoring these operations.

For example, an MSP may configure scheduled Copy Jobs to create additional backup copies for customers who have selected an off-site backup service.

The administrator can then monitor the results of these operations alongside regular backup jobs.

Copy and Migration Jobs also introduce additional storage capacity and media management requirements. Their source and destination Pools, retention settings, Volume availability, and recovery procedures need to be carefully considered.

Service providers should test recovery from their additional backup copies and ensure that their storage strategies meet customer recovery requirements.

Maintaining storage availability

Reliable backup services require ongoing attention to the availability of backup storage and suitable Volumes.

Bacularis provides management and monitoring tools that assist administrators in these activities, but it does not automatically design storage policies or determine the appropriate capacity for a managed backup service.

These decisions remain the responsibility of the MSP and require a good understanding of Bacula storage and media management mechanisms.

Proper storage planning, monitoring, and maintenance help reduce the risk of interrupted backup operations and support the long-term reliability of customer data protection.

For more information about Pool and Volume configuration, retention, pruning, and recycling, please refer to the Bacula Community documentation.

Customer access and permissions

Managed service providers may want to give their customers access to selected backup resources and operations without providing full administrative access to the backup infrastructure.

For example, a customer may need to check the status of backups, run permitted backup jobs, or restore files from their own protected systems. However, they should not be able to change the MSP's storage configuration or access backup resources belonging to other customers.

Bacularis provides several access control mechanisms that can be combined to support these requirements.

User accounts and authentication

Each customer can have their own Bacularis user account, allowing them to sign in to the web interface and access the resources and functions assigned by the MSP administrator.

Bacularis supports local user accounts and integration with external authentication systems. This allows service providers to choose an authentication approach that fits their operational and security requirements.

Authentication identifies the user, but it does not by itself determine which backup resources or operations that user is allowed to access.

These permissions need to be configured separately.

Roles and access to web interface pages

Bacularis provides role-based access control (RBAC) for defining which areas of the web interface are available to individual users.

For example, an MSP administrator can prepare a role that gives customers access to backup job information and the Restore wizard, without granting access to administrative pages used for configuring Bacula components, Pools, or Storage resources.

Roles can be defined according to different responsibilities, such as:

  • Backup monitoring.

  • Running selected backup jobs.

  • Performing permitted restore operations.

  • Access to selected administrative functions.

A user can have one or more roles assigned, with the permissions of those roles combined.

This allows MSPs to create different levels of access depending on the services offered to their customers.

However, roles control access to areas of the Bacularis interface, not automatically to individual Bacula resources.

Access to selected Bacula resources

Bacula Community provides Console Access Control Lists (ACLs), which can be used to restrict access to specific Bacula resources and operations.

Bacularis supports these mechanisms and provides web-based tools to help administrators configure restricted resource access.

For example, consider our two customers:

Customer A has four protected systems:

  • customer-a-server1-fd

  • customer-a-server2-fd

  • customer-a-server3-fd

  • customer-a-server4-fd

Customer B has three protected systems:

  • customer-b-server1-fd

  • customer-b-server2-fd

  • customer-b-server3-fd

The MSP administrator can configure access so that Customer A uses only its assigned backup Jobs, Clients, and other required resources, while Customer B has a different set of available resources.

Bacularis provides a Set access function that allows administrators to select the Jobs available to a user and generate a corresponding Bacula Console ACL containing those Jobs and their related resources.

In Bacularis, restricted access to Bacula resources is configured through Bacularis API hosts. For customer self-service, the MSP administrator needs to prepare a separate API host definition for each restricted Bacularis user. These API host definitions can all point to the same Bacularis API installation and Bacula Director. They do not require separate physical servers or separate API installations.

Each user-specific API host definition uses its own access configuration and corresponding restricted Bacula Console, so the Bacularis API accesses Bacula with the permissions assigned to that user. This is different from Bacularis Web roles, which control access to pages and functions in the web interface. Together, these mechanisms allow an MSP to provide different users with different views of the same underlying Bacula environment.

Administrators can also configure Console ACLs manually when more specific access rules are required.

For customer self-service, properly configured Console ACLs are an essential part of restricting access to backup resources. These restrictions should be combined with appropriately configured Bacularis roles and API access.

Bacularis for MSPs - set access to resources

 

Permissions for configuration resources

Bacularis also supports permissions for accessing Bacula configuration resources.

Depending on the resource type and the assigned permissions, access can be configured as:

  • Read-only – the user can view the permitted configuration without modifying it.

  • Read-write – the user can view and modify the permitted configuration.

  • No access – the user cannot access the corresponding configuration through the relevant Bacularis functionality.

These permissions can be useful when MSPs have operators or administrators with different responsibilities.

However, regular customer self-service accounts usually do not need permission to modify Bacula configuration resources.

MSPs should also treat access to backup media information, including Volumes, as an administrative capability. Restricting access to a Pool does not automatically restrict access to Volume information in Bacularis.

Designing and verifying customer access

When providing access to customers, service providers should follow the principle of least privilege: each user should receive only the access required to use the service.

For example, a customer who only needs to view backup results and restore files should not receive permissions to modify retention policies, manage storage resources, or perform unrelated administrative operations.

MSPs should also verify the resulting permissions by signing in with the corresponding customer accounts.

This is particularly important in environments where multiple customers share a Bacula Director, Catalog, or other infrastructure components.

Bacularis provides the mechanisms for configuring controlled access, but the service provider remains responsible for designing, testing, and maintaining the security of the customer environment.

For more information, please refer to the Bacularis documentation on restricted access, web interface roles, and Bacula resource access.

Customer self-service

Customer self-service is one of the ways MSPs can extend their managed backup services using Bacularis.

Instead of requiring customers to contact the service provider for every backup-related operation, MSPs can give authorized users direct access to selected functions through the Bacularis web interface.

Depending on the assigned permissions and the service model, customers may be able to check backup results, run permitted backup jobs, and restore data from their own protected systems.

The MSP continues to manage the underlying backup infrastructure, storage configuration, retention policies, and other administrative aspects of the service.

One account, multiple protected systems

A single MSP customer may have multiple servers or other protected systems.

Bacularis allows a customer account to access multiple Bacula Clients and their associated backup resources, according to the restrictions configured by the administrator.

Consider Customer A from our example.

This customer has four protected servers:

  • customer-a-server1-fd

  • customer-a-server2-fd

  • customer-a-server3-fd

  • customer-a-server4-fd

The MSP can configure one Bacularis account that provides access to the selected backup Jobs and Clients associated with these systems.

After signing in, the customer can use the available pages and operations without needing a separate Bacularis account for every protected server.

At the same time, Customer B can have its own account with access to a different set of resources.

This approach can make backup self-service more convenient for customers managing several protected systems.

Bacularis for MSPs - restricted user panel self service

 

Monitoring customer backups

Customers may want to check whether their backups have completed successfully without contacting the MSP administrator.

With appropriately configured permissions, Bacularis can provide access to backup job information, allowing customers to review the results of their permitted operations.

For example, Customer A can check recent backup jobs associated with its four servers and investigate whether an expected backup has completed.

This gives customers more visibility into their own data protection operations while allowing the MSP to retain control over the configuration and operation of the backup infrastructure.

The exact information and operations available to a customer depend on the permissions and Bacula resource restrictions configured by the MSP.

Running permitted backup jobs

Some MSPs may want to allow customers to start selected backup jobs manually.

For example, a customer preparing an important software update may want to run an additional backup before making changes to a protected server.

Bacularis can provide access to this operation through its web interface, provided the customer has the necessary permissions.

The MSP determines which Jobs are available and whether customers are allowed to run them.

This can provide additional flexibility without giving customers unrestricted access to Bacula configuration.

Self-service data recovery

Restoring data is another important self-service capability.

For example, suppose a user at Customer A accidentally deletes an important document stored on Server 2.

Instead of submitting a request to the MSP and waiting for an administrator to perform the restore, an authorized customer user can open the Bacularis Restore wizard and select an available backup containing the required data.

The user can then select the files or directories to restore and configure the permitted recovery options.

Bacularis provides different restore modes, including Simple Restore and the advanced mode based on Bacula Virtual File System (BVFS).

These modes offer different ways to select data for recovery, allowing administrators and users to choose the approach appropriate to their environment.

The possibility of restoring data to a selected destination depends on the configured Bacula permissions, available restore resources, and recovery options.

MSPs should carefully configure and test these permissions, particularly when customers are allowed to perform restore operations without administrator assistance.

Bacularis for MSPs - restricted user restore capability

 

Self-service as part of a managed service

Customer self-service does not mean that the MSP gives up responsibility for the backup environment.

The service provider continues to design and maintain backup policies, manage storage capacity, monitor infrastructure health, apply security updates, and provide the services agreed upon with its customers.

Self-service simply gives customers more direct control over selected day-to-day operations.

Different MSPs may choose different approaches. Some may provide access only to backup monitoring and restore operations, while others may allow customers to run selected backup jobs.

The scope of customer access should match the service model, security requirements, and operational policies defined by the MSP.

For more information about configuring restricted user access, please refer to the Bacularis access examples.

Mobile-friendly access

Customers increasingly use different devices to access their applications and IT services. Backup management does not have to be limited to desktop computers.

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

For MSPs offering customer self-service, this means that customers can access their permitted backup resources and operations through a web browser without installing a dedicated mobile application.

Backup access from different devices

Consider Customer A from our example.

An authorized user may check backup results from an office computer, review backup activity on a tablet, or access the Restore wizard from a smartphone when working outside the office.

The same Bacularis account can be used across these devices, with the available functions and Bacula resources determined by the permissions assigned to the user.

Responsive web access can also be useful for MSP administrators who need to check backup operations while away from their regular workstations.

Bacularis for MSPs - desktop and mobile view

 

Mobile access as part of customer self-service

A mobile-friendly interface can make managed backup services more convenient for customers.

For example, a customer who notices a missing file while away from the office may be able to sign in to Bacularis, browse the available backups, and initiate a permitted restore operation.

The actual recovery destination and available restore options depend on the configuration and access permissions established by the MSP.

Bacularis does not require a separate native mobile application to provide these web-based capabilities.

Secure mobile access

Access from mobile devices should follow the same security requirements as access from desktop computers.

The MSP decides how the Bacularis web interface is made available to its customers. Depending on the service architecture, this may involve secure HTTPS connections, VPN access, or other protected network access methods.

Mobile access does not bypass Bacularis authentication, web interface permissions, API access restrictions, or Bacula resource permissions.

The service provider remains responsible for securing the web interface, protecting customer accounts, and configuring the network access appropriate for its services.

Maintaining reliable backup services

Operating a managed backup service involves more than configuring backup jobs and checking whether they have completed successfully.

Service providers also need to maintain the availability of their backup infrastructure, respond to operational problems, and ensure that customer data can be recovered when needed.

Bacula Community and Bacularis provide tools that support these activities, while the service provider remains responsible for the overall reliability of the service.

Regular monitoring and maintenance

MSP administrators should regularly review the state of their backup environments and investigate problems that may affect customer data protection.

Important operational activities include:

  • Reviewing backup job results and investigating failed or incomplete operations.

  • Monitoring backup storage capacity and Volume availability.

  • Maintaining Pools, retention policies, and recycling configurations.

  • Checking the availability of Bacula components and protected systems.

  • Applying relevant software and security updates.

  • Reviewing customer permissions and access restrictions.

  • Maintaining documented recovery procedures.

The frequency and scope of these activities depend on the number of customers, the size of the infrastructure, and the service requirements defined by the MSP.

Bacularis provides a common web interface for many Bacula management and monitoring operations. Additional infrastructure monitoring tools may also be needed to provide a complete view of service availability.

Testing data recovery

A successfully completed backup job is an important result, but it does not guarantee that the required data can be successfully recovered.

For this reason, MSPs should regularly test their restore procedures and verify that their backup strategies meet customer recovery requirements.

Recovery tests can include restoring individual files, directories, complete backup sets, or application data, depending on the systems being protected.

Tests should also cover relevant recovery scenarios, such as restoring to an alternative system or recovering data from an off-site backup copy.

The scope and frequency of recovery testing should be defined by the service provider according to customer requirements and operational priorities.

Automated Restore Verification

Bacularis provides a Restore Verification feature that helps administrators automate selected restore tests.

Restore Verification can perform an actual restore to a configured test destination and verify the restored data using predefined rules or supported verification methods.

Administrators can use Restore Tests, Restore Policies, Restore Destinations, and Verification Rules to define what should be tested, how the data should be checked, where it should be restored, and when the test should run.

For MSPs, this feature can support internal backup quality assurance processes by helping administrators regularly check selected recovery scenarios.

Restore Verification is an administrative capability that requires proper configuration and suitable test infrastructure. It does not replace comprehensive disaster recovery planning or guarantee that every possible recovery scenario will succeed.

For more information, please visit the Bacularis Restore Verification page.

Operational responsibility

Reliable backup services require both suitable technology and experienced administrators.

MSPs need to define their own operational procedures, responsibilities, support arrangements, and recovery commitments.

They should also regularly review their backup environments as customer requirements, protected data volumes, and infrastructure resources change.

Bacularis helps administrators manage Bacula Community environments and perform many everyday operations through a web interface. However, the service provider remains responsible for designing, operating, monitoring, and maintaining the complete backup service.

This combination of software capabilities, administrative expertise, and operational discipline is essential for providing dependable backup services to customers.

Moving forward

Managing customer backups requires a combination of reliable backup technology, suitable administration tools, and clearly defined operational procedures.

In this article, we explored how Bacula Community and Bacularis can help MSPs organize customer backup resources, manage everyday backup operations, control access to selected functions and resources, and provide customer self-service.

We also looked at the importance of backup storage management, regular recovery testing, and maintaining the infrastructure needed to deliver dependable backup services.

Bacularis makes many of these activities available through a web interface, helping administrators manage complex Bacula environments while providing customers with controlled access to their own backup operations.

In the third and final part of this series, Architectures and integrations for MSPs, we will explore different deployment models, customer separation, security considerations, and integration possibilities for building managed backup services around Bacula Community and Bacularis.