Category / SysAdmin

A quick fix for a weird issue that in Proxmox unprivileged container fails to install filesystem update on Centos 7 : [[email protected] ~]# yum install filesystem Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: ftp.belnet.be * extras: ftp.belnet.be * updates: ftp.belnet.be Resolving Dependencies –> Running transaction check —> Package filesystem.x86_64 0:3.2-21.el7 will […]

Read More

Today, I had a new issue, a server blankly refused to reboot/shutdown. [[email protected] ~] reboot -h now Failed to start reboot.target: Connection timed out See system logs and ‘systemctl status reboot.target’ for details. Failed to open /dev/initctl: No such device or address Failed to talk to init daemon. I first tried : [[email protected] ~]# systemctl […]

Read More

When a Client job fails and reports : Error: VSS API failure calling “BackupComplete”. ERR=Object is not initialized; called during restore or not called in correct sequence. Try to start the Service : VSS manually; This solved the issue for a few Clients;

Read More

After adding a bunch of clients, we realized that a good naming convention was required and that some funny names, where not the best choice after all. So we changed them. However, Bareos will remember those Jobs ran against the old Client. The ‘new’ name will be seen as a new client; Some of the scripts […]

Read More

Doesn’t happen often that I need Windows tools, but this worked nicely, so I though I share it with the future me that will have forgotten about this method; On the domain server open a “Windows Powershell”; Import the module : Import-Module ActiveDirectory Then create the list of “enabled” users : Get-ADComputer -Filter {enabled -eq […]

Read More

A simple issue, but can be tricky nevertheless ! bareos-sd JobId 265: Warning: stored/mount.cc:270 Open device “FileStorage3” (/storage/block1) Volume “Full-0015” failed: ERR=stored/dev.cc:731 Could not open: /storage/block1/Full-0015, ERR=No such file or directory While experimenting I had made the owner of /storage/block1 different from the Bareos user; This resulted in the storage deamon (bareos-sd) not able to […]

Read More

Surprisingly perhaps for newbies such as myself; Bareos will only start one backup job at once; meaning if you got 100 clients, there will be a serieus delay between the first and last job. So why is this happening ? Bareos is a fork off Bacula and this was originally developed for the use of […]

Read More

Bareos uses FileSets to decide what to backup and what not to backup. While the documentation is extensive, the approach is mostly include everything and exclude parts (include all, exclude after).  While this is the way average people want to backup. If you work around non-IT minded people, you know that they will store EVERYTHING, […]

Read More

By default the device used by Bareos for data archival/storage is FileStorage. Meaning data stored is stored in images on spinning disks in the file structure: /var/lib/bareos/storage While this might be a good place for you, its tricky with this location is in root … (full root and whatnot) You can change this in : […]

Read More

When installing Bareos client on Centos 7, I could not start the service with the following “cryptical error” : [[email protected] ~]# systemctl restart bareos-fd A dependency job for bareos-fd.service failed. See ‘journalctl -xe’ for details. [[email protected] ~]# systemctl status bareos-fd ● bareos-fd.service – Bareos File Daemon service Loaded: loaded (/usr/lib/systemd/system/bareos-fd.service; enabled; vendor preset: disabled ) […]

Read More