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