Hello everyone.
I have just installed the Bacula File Daemon on a windows 7 machine. I
did this on 3 other machines before and they are all being backed up.
For some reason i cannot start the file daemon service on this new (new
to the backup system) computer. I keep receiving error 1067 when
Le 08/10/2014 20:29, bacula-users-requ...@lists.sourceforge.net a écrit :
> 6. Communication issues with 7.0.5 (Bryn Hughes)
Hi,
I make a migration Ubuntu 12.04 / Bacula 5.2.5 to CentOs 7 / Bacula
7.0.5 ( 29/09/2014).
I reuse the old conf file with a little modification : /var/lib/bacula
-> /va
> On Tue, 07 Oct 2014 09:56:43 -0700, David Newman said:
>
> On 10/6/14, 9:20 PM, David Newman wrote:
> > On 10/3/14, 7:47 AM, Ana Emília M. Arruda wrote:
> >> Hi David,
> >>
> >> Have you tried to schedule the job at another time? Just for checking if
> >> the problem is at the scheduled time
Hi
Our backup schema is the typical:
Full on disk on first saturday every month
Diff on disk the rest of saturdays
Incr on disk every day
But we also generate a VirtualFull *on tape* every day, that is kept
offsite.
The default behaviour is that this VirtualFull becomes the last (more
recent) F
Hi,
You can pass config file as a parameter, i.e., bacula-fd.exe -c
path_to_config_file.
Regards,
Marius
On Thu, Oct 9, 2014 at 11:53 AM, Florian wrote:
> Hello everyone.
>
> I have just installed the Bacula File Daemon on a windows 7 machine. I
> did this on 3 other machines before and they a
Florian,
This is most likely a configuration error.
You can check more information starting the bacula-fd service on windows
command line:
net start bacula-fd
Regards,
Heitor Medrado de Faria
Precisa de treinamento Bacu
Hello.
I run this command:
list jobs
+---+-+---++---+---+++
| JobId | Name | StartTime|
Type
| Level
| JobFiles | JobBytes
I have used this command
*purge files 154
but the job with the id 154 still appears when I execute the command "list
jobs."
Le Jeudi 9 octobre 2014 17h56, ALI LARAB a écrit :
Hello.
I run this command:
list jobs
+---+-+---+
Hello!
If you want to delete all the information about a job/volume, you can use
the "purge volume=". This command will delete all job, files, etc.,
information from catalog, but it will not delete your volume. It will set
the volume status to "purged" and this way the volume will be available
Hi David,
Could you clarify some points?
1) your storage daemon is running on backups.networktest.com:9103.?
2) who is listening on the 3 ports bellow?
$ sudo netstat -an -f inet | grep 910
tcp4 0 0 *.9102 *.*LISTEN
tcp4 0 0 *.9103
10 matches
Mail list logo
