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 durin
Increasing the
WakeupSchedule to 1, 2, 3, 4, 20, 21, 22, 23,
MaxBackups to 4
and
MaxBackupPCNightlyJobs to 4
Allows all 12 servers to backup every night.
The previous admin loaded this BackupPC install on a primary database server so
it's fairly important to
have the backups complete overnight
A few days ago, I posted an issue pertaining to backups not running on schedule.
The problem was identified and resolved by increasing the
WakeUpSchedule and MaxBackup settings.
for 2 days, the backups worked without any problems.
This morning, I opened the WGUI and all of the Windows servers had
I'm getting positive results by checking the network share settings.
Apparently windows updates changes the share settings.
This is the only thing I can think of
and the only thing that appears to be resolving this issue.
SSDP Discovery needs to be a running service
also, google 'network discov
Yes,
This is an interesting issue. I just started to have this problem a few days
ago.
There isn't much history about this error on line.
Here's what I know.
It appears to be affecting Windows machines, my Linux machines backup fine.
I had a previous issue with scheduling which was resolved just
I've tried removing Windows updates from 4/18/16 and had no change.
A couple of the servers don't have updates running automatically so they
weren't installed anyway.
I am running Samba version 3.4.7 so the Debian Samba bug report
doesn't appear to be the issue.
+
Update,
I started 3 of the previously failing Windows servers on a full backup and
they've been running for well over an hour. Usually when an incremental backup
is started, the failure occurs within a few minutes.
+--
|This wa
Update,
I started 3 of the previously failing Windows servers on a full backup and
they've been running for well over an hour. Usually when an incremental backup
is started, the failure occurs within a few minutes.
+--
|This wa
What could cause Windows servers to suddenly fail backups while Linux servers
continue to backup?
Windows servers have a mix of firewall off/on, have a mix of updates on/off...
I have restored the configuration files on the backup server from a date prior
to the issue,
I can get different results
I'm willing to try this but the server doesn't appear to have samba loaded on
it.
when I issue smbstatus --version,
The server returns smb is currently not installed.
I'm at a loss at this point.
Thank you for responding.
I'm looking forward to keeping my job!
+
I have tried making the suggested changes to these files:
> $Conf{SmbClientFullCmd} = '$smbClientPath $host\\$shareName
> $I_option -U $userName -E -N -d 1 -c tarmode\\ full\\ verbose -Tc$X_option
> -
> $fileList';
>
> {SmbClientIncrCmd} = '$smbClientPath $host\\$shareName
> $I_option -U $
Correct. I issued the SMB status command on the backuppc server.
I was able to locate the Smb.pm file and make the adjustments to the file
according to the link mentioned in this post, however, I have a couple of
backups running and wait to see what this outcome is.
If this works, I can cancel my
After making changes to the Smb.pm and Browse.pm files, I have 2 Windows
servers backing up and 4 in the process of backing up.
The only change I made was that indicated in this post:
https://bugzilla.redhat.com/attachment.cgi?id=264&action=diff
Browse.pm changed this:
From:
if ( !defined
I can't change the status of the post to indicate resolved, but here is what
resolved my BackupPC Windows client failure:
After making changes to the Smb.pm and Browse.pm files, I have 2 Windows
servers backing up and 4 in the process of backing up.
The only change I made was that indicated in
14 matches
Mail list logo
