This sounds interesting, maybe i can do a mixed solution with the script for
triggering the job with this additional parameters.
Thank you all
ganiuszka wrote:
> marco zanca:
>
> >
> > terryc wrote:
> >
> > > manually -> bconsole -> run ->
What about a script that ping the specific ip or name (e.g. 192.168.1.2 or
client1.work) and then, when the first ping response, start the backup with the
command bconsole etc?
I think this could work, but i'm not happy with this solution. Too much
overhead maybe? And potentially too much ICMP
terryc wrote:
>
> manually -> bconsole -> run -> choose appropriate job -> check parametrs
> -> yes
>
Ok, but what if i can't be present all the time and do it manually?
I need a way to automate this. It is possible to modify the number of retry?
It is possible to run a job with a bash scri
Well, i don't no why, but i step back into the 2.4.4 version and now all works
fine.
+--
|This was sent by marco.za...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+
I try to set the permission even to 777 but with no luck.
And now i have some problem with some backup job that hangs in the same waiting
status ...
I've no idea what to check, the database work fine, the configuration file is
almost similar to the default provided with the installation.
+
Ok, thank you for helping, i'm using bconsole, but i also tried with the bat
gui. I do this step:
1. run a backup job in /tmp, wich ends with no error. i check the volume in
/tmp and seems to be alright
2. give a restore command in bconsole, select 5: Select the most recent backup
for a client
