Bacula

After running the script which upgrades your Bacula database to version 14, there are a couple of fix-ups you may wish to run: alter table restoreobject owner to bacula; grant all on restoreobject_restoreobjectid_seq to bacula; grant all on restoreobject to bacula; You may or may not have to do this, depending on how you ran the upgrade script. Examine the following command output for your database: bacula=# \dt restoreobject List of relations Schema […]

I have been using Bacula since 2004. I started off on DDS tapes, then moved to DLT. Now I’m backing up to a ZFS array and the copying to tape. About a year ago, I obtained about 200 DLT tapes from a friend. They were no longer used at his place of work. He used Bacula and had written lots of 1s and 0s to the tapes to erase them. However, they still

Bacula is a backup and restore solution which I’ve been using and contributing to since 2004. Recently, I started backing up to disk and then copying to tape later. This approach, combined with a scratch pool, has proven to be very low maintenance, from a sysadmin point of view. I think all sysadmin will agree: the less you have to do, the better. At this time of year, I’m away running BSDCan and

I hate it when this happens: [root@kraken /usr/home/dan]# /usr/local/sbin/mtx-changer /dev/pass10 list mtx: Request Sense: Long Report=yes mtx: Request Sense: Valid Residual=no mtx: Request Sense: Error Code=0 (Unknown?!) mtx: Request Sense: Sense Key=No Sense mtx: Request Sense: FileMark=no mtx: Request Sense: EOM=no mtx: Request Sense: ILI=no mtx: Request Sense: Additional Sense Code = 00 mtx: Request Sense: Additional Sense Qualifier = 00 mtx: Request Sense: BPV=no mtx: Request Sense: Error in CDB=no mtx: Request

The new year started off poorly for my backups, and it is all my fault. Each of my remote servers is backed up utilizing Bacula’s TLS (Transport Layer Security) features. This requires an X.509 certificate which I obtain via CACert. These certificates have expired: 01-Jan 02:00 bacula-dir JobId 44464: Start Backup JobId 44464, Job=nyi_maildir.2011-01-01_02.00.00_07 01-Jan 02:00 bacula-dir JobId 44464: Using Device “MegaFile” 01-Jan 02:00 bacula-dir JobId 44464: Error: tls.c:92 Error with certificate at

I have an improvement on the original query. This one outputs ‘nil’ if the volume is empty. bacula=# SELECT mediaid, volumename, volstatus, slot, inchanger, pool.name, CASE WHEN volbytes < = 64512 THEN 'nil' else pg_size_pretty(volbytes) END FROM media, pool WHERE media.poolid = pool.poolid AND volumename LIKE 'ETU0%' AND inchanger != 0 ORDER BY slot; mediaid | volumename | volstatus | slot | inchanger | name | pg_size_pretty ---------+------------+-----------+------+-----------+---------------+---------------- 1328 | ETU021 | Append

With Bacula, a great piece of backup software [disclosure: I wrote the PostgreSQL module for Bacula], you can copy a Job after it has run. This is often used to backup first to disk, and then Copy that Job to tape. That is exactly what I’ve been doing recently. NOTE: You can also migrate a Job, which is very similar to a Job Copy. With a Job Copy, the original Job remains and