User Tools

Site Tools


bacula_manual:dealing_with_win32_problems

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
bacula_manual:dealing_with_win32_problems [2009/05/03 23:15]
gjz
bacula_manual:dealing_with_win32_problems [2009/05/04 09:43] (current)
gjz finished article and found problems and documented fix to get it working
Line 11: Line 11:
 When you start the bmx-console you will see a message "​Connection to the director lost. Quit Program?"​. When you check the services you will find that the Director Service is not running. This is very likely a configuration issue. When you start the bmx-console you will see a message "​Connection to the director lost. Quit Program?"​. When you check the services you will find that the Director Service is not running. This is very likely a configuration issue.
  
-<this article ​is not complete because ​it is pending results ​on the root cause>+There is lots of information added to the default installation that may affect the normal operation and a smaller version here is added to replace ​this to see this helps. First a reboot of the server may help as well when other services are not running. 
 + 
 +==== Not all services needed may be running ==== 
 + 
 +One service that could require extra attention ​is "​Removable Storage"​ service. This service may be disabled and not running. Programs like Windows Backup will not work when stopped. Because on every system boot this service is disabled ​it could mean that either Bacula or Yosemite ​is disabling it on system start. When manually set back to automatic and started, it will be disabled again on system reboot. Which of the programs that causes this is unknown at this moment. 
 + 
 +==== The configuration file of the Director ==== 
 +When you edit the "Edit Director Configuration"​ (bacula-dir.conf) areas likely needed your attention (paswords are replaces with *) : 
 + 
 +Default file storage: 
 +  # Definition of file storage device 
 +  Storage { 
 +  Name = File 
 +  # Do not use "​localhost"​ here 
 +  Address = fs3                # N.B. Use a fully qualified name here 
 +  SDPort = 9103 
 +  Password = "​********************************************"​ 
 +  Device = FileStorage 
 +  Media Type = File 
 +  } 
 +Reboot test fails so it may be smart to comment out with "#"​ everything that may not be needed to find when the director does not start. Before doing that please read the section below "Your database may not exist"​ 
 + 
 +==== Your database may not exist ==== 
 +SQL ports are not specified anywhere but if your server runs Microsoft SQL, Pervasive SQL, MySQL when the software is installed. It was not possible to find out if there are port conflicts with those packages. To go save the database default was chosen that may not interfer with those other services. 
 + 
 +When digging into this deeper I discovered that the database did not exist! Default location of the database is "<​drive>:\Documents and Settings\All Users\Application Data\Bacula\Work",​ name of the database is "​bacula.db"​. The best way is to add this manually to be certain it works. Open a DOS box (run, cmd) and go to the installation directory, this is default <​drive>:​\Program Files\Bacula\bin. From there run these commands sequentially:​ 
 +  - create-database 
 +  - make-tables 
 + 
 +Here is what you see and type in the DOS box: 
 + 
 +"<​drive>:​\Program Files\Bacula\bin>​create_database 
 + 
 +seq  name             ​file 
 + 
 +---  --------------- ​ ---------------------------------------------------------- 
 + 
 +0    main             ​E:​\Documents and Settings\All Users\Application Data\Bacul 
 + 
 + 
 +<​drive>:​\Program Files\Bacula\bin>​make_tables 
 + 
 +<​drive>:​\Program Files\Bacula\bin>​_"​ 
 + 
 +The odd part is that there is no visual feedback that the tables are really made. 
 + 
 +The database is created in a seperate folder, to locate it try this: 
 +<​drive>:​\Documents and Settings\All Users\Application Data\Bacula\Work 
 +The file bacula.db is created in that folder. 
 + 
 +You cannot start the directory service from the command line. To start it go to services (service.msc) and start the "​Bacula Directrory Service"​ from there. You should see that it starts. 
 ===== Bacula File Service is not running ===== ===== Bacula File Service is not running =====
-The standard installation works properly but it is better to set the file location to a controlled area on a different drive. +The standard installation works properly but it is better to set the file location to a controlled area on a different drive. ​See notes under "​Bacula Storage Service is not running"​ for more details. 
-===== Bacula Storage Service =====+ 
 +===== Bacula Storage Service ​is not running ​=====
 The standard installation works properly but no tape drives are configured. To assure this runs well it is better to configure this manually. The standard installation works properly but no tape drives are configured. To assure this runs well it is better to configure this manually.
  
-Open "Edit Storage Configuration"​ and set under "Archive ​Device"​ your intended location of where you would want to store the archive files: +Open "Edit Storage Configuration" ​(bacula-sd.conf) ​and set under "​Device"​ your intended location of where you would want to store the archive files: 
-Device {+ 
 +  ​Device {
   Name = FileStorage   Name = FileStorage
   Media Type = File   Media Type = File
Line 26: Line 79:
   AutomaticMount = yes               # when device opened, read it   AutomaticMount = yes               # when device opened, read it
   RemovableMedia = no   RemovableMedia = no
-  AlwaysOpen = no +  AlwaysOpen = yes 
-+  } 
-You may run tapes but the default installation also supports files and it is easier to test it with files before trying tapes. Why the "​AlwaysOpen"​ is set to "​no"​ is not clear when the drive is installed in the server. For hotplug devices it should be set to "​no"​.+ 
 +You may run tapes but the default installation also supports files and it is easier to test it with files before trying tapes. Why the "​AlwaysOpen"​ is set to "​no"​ is not clear when the drive is installed in the server. For hotplug devices it should be set to "no". For a fixed drive mounted in the server it should be set to "yes".
  
-Please stay tuned, I will try to add more details as soon as possible when finishing the review on the issues. 
bacula_manual/dealing_with_win32_problems.1241388933.txt.gz · Last modified: 2009/05/03 23:15 by gjz