Paul Heinlein wrote:
> On Tue, 17 May 2016, m.roth@xxxxxxxxx wrote:
>
>> I'm hoping *someone* here has worked a bit with bareos. I've tried
>> posting to the google groups for it... and haven't even had one person
>> view my post....
>>
>> It was working fine, backing up windows boxes for months. Then, about
>> a week ago, the server got a regular yum update, and rebooted... and it's
>> broken. A job will start... and just keep running forever (as in, over
>> the weekend) and never end; normally, they were all done in a few
>> hours.
>>
>> I stopped bareos-dir, then -fd, then -sd, restarted, no joy. Then I
>> tried shutting them all down, and service restart postgres, and *then*
>> starting up -sd, -fd and -dir. I was starting them manually Friday, and
>> they'd run and finish. But the nightly b/u, a job started... and was
>> still running yesterday.
>>
>> Anyone have any ideas?
>
> Just one idea, and it's not a promising one:
>
> Any chance that the Windows client is spinning trying to backup cygwin
> files, specifically /var/log/lastlog?
Nope. I'm *explicitly* telling bareos to back up c:/Users/, and, in a
couple of cases, d:/ or e:/ - we don't care about the system or logs at
all. If something happens, desktop support will ghost reimage them.
And it was working with no trouble....
mark
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
