3 %% The following characters must be preceded by a backslash
4 %% to be entered as printable characters:
11 \index[general]{Bimagemgr }
13 {\bf bimagemgr} is a utility for those who backup to disk volumes in order to
14 commit them to CDR disk, rather than tapes. It is a web based interface
15 written in Perl and is used to monitor when a volume file needs to be burned to
19 \item A web server running on the bacula server
20 \item A CD recorder installed and configured on the bacula server
21 \item The cdrtools package installed on the bacula server.
22 \item perl, perl-DBI module, and either DBD-MySQL DBD-SQLite or DBD-PostgreSQL modules
25 DVD burning is not supported by {\bf bimagemgr} at this
26 time, but both are planned for future releases.
28 \subsection{bimagemgr installation}
29 \index[general]{bimagemgr!Installation }
30 \index[general]{bimagemgr Installation }
32 Installation from tarball:
33 % TODO: use itemized list for this?
34 1. Examine the Makefile and adjust it to your configuration if needed.
35 2. Edit config.pm to fit your configuration.
36 3. Do 'make install' as root.
37 4. Edit httpd.conf and change the Timeout value. The web server must not time
38 out and close the connection before the burn process is finished. The exact
39 value needed may vary depending upon your cd recorder speed and whether you are
40 burning on the bacula server on on another machine across your network. In my
41 case I set it to 1000 seconds. Restart httpd.
42 5. Make sure that cdrecord is setuid root.
43 % TODO: I am pretty sure cdrecord can be used without setuid root
44 % TODO: as long as devices are setup correctly
46 Installation from rpm package:
47 % TODO: use itemized list for this?
48 1. Install the rpm package for your platform.
49 2. Edit /cgi-bin/config.pm to fit your configuration.
50 3. Edit httpd.conf and change the Timeout value. The web server must not time
51 out and close the connection before the burn process is finished. The exact
52 value needed may vary depending upon your cd recorder speed and whether you are
53 burning on the bacula server on on another machine across your network. In my
54 case I set it to 1000 seconds. Restart httpd.
55 4. Make sure that cdrecord is setuid root.
57 For bacula systems less than 1.36:
58 % TODO: use itemized list for this?
59 1. Edit the configuration section of config.pm to fit your configuration.
60 2. Run /etc/bacula/create\_cdimage\_table.pl from a console on your bacula
61 server (as root) to add the CDImage table to your bacula database.
63 Accessing the Volume files:
64 The Volume files by default have permissions 640 and can only be read by root.
65 The recommended approach to this is as follows (and only works if bimagemgr and
66 apache are running on the same host as bacula.
68 For bacula-1.34 or 1.36 installed from tarball -
69 % TODO: use itemized list for this?
70 1. Create a new user group bacula and add the user apache to the group for
71 Red Hat or Mandrake systems. For SuSE systems add the user wwwrun to the
73 2. Change ownership of all of your Volume files to root.bacula
74 3. Edit the /etc/bacula/bacula startup script and set SD\_USER=root and
75 SD\_GROUP=bacula. Restart bacula.
77 Note: step 3 should also be done in /etc/init.d/bacula-sd but released versions
78 of this file prior to 1.36 do not support it. In that case it would be necessary after
79 a reboot of the server to execute '/etc/bacula/bacula restart'.
81 For bacula-1.38 installed from tarball -
82 % TODO: use itemized list for this?
83 1. Your configure statement should include:
84 % TODO: fix formatting here
85 --with-dir-user=bacula
86 --with-dir-group=bacula
90 --with-fd-group=bacula
91 2. Add the user apache to the bacula group for Red Hat or Mandrake systems.
92 For SuSE systems add the user wwwrun to the bacula group.
93 3. Check/change ownership of all of your Volume files to root.bacula
95 For bacula-1.36 or bacula-1.38 installed from rpm -
96 % TODO: use itemized list for this?
97 1. Add the user apache to the group bacula for Red Hat or Mandrake systems.
98 For SuSE systems add the user wwwrun to the bacula group.
99 2. Check/change ownership of all of your Volume files to root.bacula
101 bimagemgr installed from rpm > 1.38.9 will add the web server user to the
102 bacula group in a post install script. Be sure to edit the configuration
103 information in config.pm after installation of rpm package.
105 bimagemgr will now be able to read the Volume files but they are still not
108 If you are running bimagemgr on another host (not recommended) then you will
109 need to change the permissions on all of your backup volume files to 644 in
110 order to access them via nfs share or other means. This approach should only
111 be taken if you are sure of the security of your environment as it exposes
112 the backup Volume files to world read.
114 \subsection{bimagemgr usage}
115 \index[general]{bimagemgr!Usage }
116 \index[general]{bimagemgr Usage }
118 Calling the program in your web browser, e.g. {\tt
119 http://localhost/cgi-bin/bimagemgr.pl} will produce a display as shown below
120 % TODO: use tex to say figure number
121 in Figure 1. The program will query the bacula database and display all volume
122 files with the date last written and the date last burned to disk. If a volume
123 needs to be burned (last written is newer than last burn date) a "Burn"
124 button will be displayed in the rightmost column.
126 \addcontentsline{lof}{figure}{Bacula CD Image Manager}
127 \includegraphics{./bimagemgr1.eps} \\Figure 1
128 % TODO: use tex to say figure number
130 Place a blank CDR disk in your recorder and click the "Burn" button. This will
131 cause a pop up window as shown in Figure 2 to display the burn progress.
132 % TODO: use tex to say figure number
134 \addcontentsline{lof}{figure}{Bacula CD Image Burn Progress Window}
135 \includegraphics{./bimagemgr2.eps} \\Figure 2
136 % TODO: use tex to say figure number
138 When the burn finishes the pop up window will display the results of cdrecord
139 % TODO: use tex to say figure number
140 as shown in Figure 3. Close the pop up window and refresh the main window. The
141 last burn date will be updated and the "Burn" button for that volume will
142 disappear. Should you have a failed burn you can reset the last burn date of
143 that volume by clicking its "Reset" link.
145 \addcontentsline{lof}{figure}{Bacula CD Image Burn Results}
146 \includegraphics{./bimagemgr3.eps} \\Figure 3
147 % TODO: use tex to say figure number
149 In the bottom row of the main display window are two more buttons labeled
150 "Burn Catalog" and "Blank CDRW". "Burn Catalog" will place a copy of
151 your bacula catalog on a disk. If you use CDRW disks rather than CDR then
152 "Blank CDRW" allows you to erase the disk before re-burning it. Regularly
153 committing your backup volume files and your catalog to disk with {\bf
154 bimagemgr} ensures that you can rebuild easily in the event of some disaster
155 on the bacula server itself.