Bacula-users

Re: [Bacula-users] Failure Backing Up Windows Client Machine

2014-03-03 11:38:37
Subject: Re: [Bacula-users] Failure Backing Up Windows Client Machine
From: Larry Kemp <Larry.Kemp AT usmetrotel DOT com>
To: Kern Sibbald <kern AT sibbald DOT com>, Larry Kemp <Larry.Kemp AT usmetrotel DOT com>, Greg Woods <greg AT gregandeva DOT net>
Date: Mon, 3 Mar 2014 16:31:37 +0000

Can you tell me the URL to the specific manual? I am searching through this manual right now: http://www.bacula.org/5.2.x-manuals/en/main/main.pdf. This links shows August 18th 2013 as the date.

 

Also this Windows server is part of an Active Directory Domain and I log in via RDP as my username on the Domain which is a member of the Domain Admins group.

I have never logged in via RDP as a domain or local account named Administrator.

 

From: Kern Sibbald [mailto:kern AT sibbald DOT com]
Sent: Saturday, March 01, 2014 3:44 AM
To: Larry Kemp; Greg Woods
Cc: bacula-users AT lists.sourceforge DOT net
Subject: Re: [Bacula-users] Failure Backing Up Windows Client Machine

 

Hello,

I wrote an email on this exact subject just a week or so ago.  If you simply follow the instructions in the Windows chapter of the manual and install the FD using an Administrator account directly on the machine in question (no remote login), Bacula will be automatically started and will restart after a reboot, and you should not have any of the problems with finding the conf file that you report.  Of course, it is possible the conf file can be broken by things such as @monitor@, in which case you will need to edit/remove the error.

The service panel that you show below indicates that the fd will start automatically.

Best regards,
Kern

On 02/27/2014 12:16 AM, Larry Kemp wrote:

Kern/All,

 

I was able to get the Bacula file daemon to start manually on my Windows Server 2003 32bit system by using the following exact command:

Command to start File Daemon:

C:\Program Files\Bacula>bacula-fd.exe -c ./bacula-fd.conf

 

To see if the Bacula-FD is running I entered the following at the command line:

netstat -na | more

Then I looked for socket 9101 listening.

 

Then I wanted to kill the daemon I entered:

bacula-fd.exe -kill

 

Then I wanted the daemon to start as a service at boot so if the server was ever rebooted it would startup just like my Linux systems at bott/reboot without me having to manually go to each Windows Server 2003/2008/2012.

I read about Creating A Service at this Microsoft link: http://technet.microsoft.com/en-us/library/cc990289.aspx

Entering this command:

sc create Bacula-FD binpath= "C:\Program Files\Bacula>bacula-fd.exe -c ./bacula-fd.conf" type= share start= auto

 

....produced a named service but it will not start at boot and will not let me edit it from the services.msc module.

 

Manully trying to click “Start Service” gives this graphical error:

 

Services: Could not start the Bacula-FD service on Local Computer. Error 2: The system cannot find the file specified. OK?

 

 

 

Anyone know how to make it behave and start up at boot without human intervention? I’m almost there! Whoo hoo!

 

LK

 

-----Original Message-----
From: Kern Sibbald [mailto:kern AT sibbald DOT com]
Sent: Sunday, February 23, 2014 5:47 AM
To: Greg Woods; Larry Kemp
Cc: bacula-users AT lists.sourceforge DOT net; Larry Kemp
Subject: Re: [Bacula-users] Failure Backing Up Windows Client Machine

 

You simply ensure that Bacula is not installed, login at the main console (not a remote console) as Administrator and execute the bacula-fd .exe file, and if it finishes without error, it should be installed as a system program and running.  There is no need to start it manually, unless the bacula-fd.conf file needs changed, and in that case, you always start it through the System Services panel.

 

Best regards,

Kern

 

On 02/22/2014 08:30 PM, Greg Woods wrote:

> On Sat, 2014-02-22 at 14:16 -0500, Larry Kemp wrote:

>> I will check to see if fd is running at all...I assumed it

>> was...maybe it is not at all.

> At least with the version of the Windows bacula-fd that I have on my

> VM, installing the daemon doesn't automatically create a startup entry

> for it. I usually start it from a command prompt window (running as

> Administrator, otherwise bacula-fd doesn't have permission to read all

> the files). I'm sure there's a way to put it into the system startup,

> but I haven't figured out how to do that on Windows 7 yet.

> --Greg

> ----------------------------------------------------------------------

> -------- Managing the Performance of Cloud-Based Applications Take

> advantage of what the Cloud has to offer - Avoid Common Pitfalls.

> Read the Whitepaper.

> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.

> clktrk _______________________________________________

> Bacula-users mailing list

> Bacula-users AT lists.sourceforge DOT net

> https://lists.sourceforge.net/lists/listinfo/bacula-users

 

 

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users