Support Center

Self Hosted - basic configuration notes and requirements

Last Updated: Dec 18, 2015 11:18PM EST
The Self Hosted Solution allows customers to install our platform on their own infrastructure within their own facilities/locations.

The purpose of deploying our solution in this capacity is:
1) adhere to our "open" standards concepts, allowing the use of commodity hardware
2) adhere to customers existing infrastructure and management policies without introducing custom appliances into their environment
3) because of #1 and #2 above, reduce the costs to our customers for utilizing our solution

The hardware requirements/specifications are outlined on our website

- our solution does require SSH service to be enabled
- by default, when we install our solution, we setup the required SSH access list via IPTables. This includes access from various Bacula4 components (director/catalog/GUI) as well as Bacula4 VPN IP Ranges for basic management and licensing functions
- Customers are certainly able to install their own SSH keys if desired, or include their own IP ranges for SSH access. However, SSH service must be left enabled for the various components of our service to operate
- We do request that customers do not alter the default configuration we put in place. Custom firewalls and such can be used, but, the customer is responsible to ensure that all communication required for operation and management of the system remain in place
- Customers are free to perform typical OS updating and patching on their installs.  Major version upgrades of supported OS's are not recommended and typically would require migrations to new hardware, etc
- Customers are asked not to use automation systems such as puppet/chef as their configuration management may conflict with the installed application. Additionally, Bacula4 is already using such systems in various scenarios on our customers installs, and in the near future, it will be standard practice on all of our customers installs in order to assist with installations, troubleshooting, recovering failed installs and other day to day management practices of our self hosted install base

it is recommended that customers backup their pgSQL DB on their director/catalog server with whatever frequency they deem as adequate. In case a director/catalog is lost, the entire system can be easily restored to default, and all data associated with the install can be recovered as long as the pgSQL catalog backup is available.  Basic pgSQL dumps are typically sufficient (daily or x times per day depending on your requirements)
- it is recommended customers monitor their hardware and service health on their GUI, Director/Catalog, Storage Devices, etc

Contact Us
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found