Search Results for: bacula

Bacula uses flat text files for configuration. From time to time, people, usually new to the project, ask: why isn’t the configuration in the database? Bacula uses the database to store information about what files were backed up, from what client, and when. This information is useful when you need to know how if you have a copy of a file from last Tuesday before you wrote crap into it but after you

Bacula is a backup system with three different retention periods: Volume Job File I set all three to the same value. It is important to note that these values affect only the Catalog. It determines how long a given record is held in the database. For example, if you set File Retention to be 45 days, it means that there are no records in the database for any files backed up in any

I noticed that one of our disk-based Volumes used a label name similar to that of our tape-based Volumes. To avoid confusion, I will rename that Volume. But, renaming a Volume is not simple, nor recommended if the Volume contains data. It is better to migrate the data instead. The Volume in question has MediaId = 42 (seriously!): | 42 | PEQ574L4 | Append | 1 | 4,144,705,431 | 0 | 31,536,000 |

Today, as I was writing up an invoice, I accidentally saved it over another. No worries!  Bacula to the rescue.  I managed to get the original files back from tape. One hint: include your pathnames in “quotes” so they are correctly parsed.  Like this: $ dir ———- 0 root wheel 0 1969-12-31 19:00:00 c:/ $ cd “c:/Documents and Settings/Dan Langille/My Documents/Technologies” cwd is: c:/Documents and Settings/Dan Langille/My Documents/Technologies/ $ dir -rwxrwxrwx 1 root wheel 63655 2006-10-05 14:32:49 c:/Documents and Settings/Dan Langille/My