On Fri, Apr 15, 2016 at 3:47 PM, Tony Schreiner
wrote:
>
>> I will increase
>> MaxBackups and MaxUserBackups from 2 to 6
>> to see if it makes any difference.
MaxBackups is the number that will be scheduled to run concurrently;
MaxUserBackups controls what you can start
On Fri, Apr 15, 2016 at 2:47 PM, terryls
wrote:
> Thank you very much!
> This all makes sense, although I don't know what caused the change.
> I will increase
> MaxBackups and MaxUserBackups from 2 to 6
> to see if it makes any difference.
>
> I think the
Thank you very much!
This all makes sense, although I don't know what caused the change.
I will increase
MaxBackups and MaxUserBackups from 2 to 6
to see if it makes any difference.
I think the WakeupSchedule setting was changed to [23]
a few years ago to prevent slowing the network down
Am 15.04.2016 um 16:06 schrieb tschmid4:
> Thank you for all of your help.
> -Copy the status line of your host:
> ? Selecting Host Summary from the WebGUI, I see a list of hosts. Providing
> User, #Full, Full Aga (days) Full Size(GB) etc...
> No exactly sure what you need here.
There are
Am 15.04.2016 um 17:01 schrieb Les Mikesell:
> On Fri, Apr 15, 2016 at 9:06 AM, tschmid4 wrote:
>>
>> Here is a link to the .PL files.
>>
>> http://pastebin.com/ZbQTMG7d
>>
>
> There may be more, but this looks wrong - and not the default setting:
> #
> $Conf{WakeupSchedule} =
On Fri, Apr 15, 2016 at 9:06 AM, tschmid4 wrote:
>
> Here is a link to the .PL files.
>
> http://pastebin.com/ZbQTMG7d
>
There may be more, but this looks wrong - and not the default setting:
#
$Conf{WakeupSchedule} = [
23
];
Normally that should be a list of hours when you
The log file lines you sent only cover the BackupPC_nightly job. This is a
housekeeping task that should run after the backups, so this information does
not really help to find your problems.
Please point your browser to your BackkupPC server, navigate to "Old LOGs" and
select "LOG.0.z" (or