On 7/21/2016 11:09 AM, philhu wrote:
> ok, that def explains it.
>
> Is it possible to force bacula to ignore, but save, current ctimes, for one
> incr run?
Doubtful. I don't think file records are updated for files that are
skipped; only records for the files that are selected for the job.
>
ok, that def explains it.
Is it possible to force bacula to ignore, but save, current ctimes, for one
incr run?
Usinf mtimeonly, it could use mtime to backup incr of nothing, but save the new
ctimes it finds.
After the 'special' incr run, take out the mtimeonly line and everything is
back to
On 7/21/2016 9:31 AM, philhu wrote:
> Something is wrong here
>
> I moved 48TB from one NAS to the other, rsync -avz --numeric-ids
>
> All dates/times were identical between the two, but when I mounted new at
> same mount points, every other application pointing at the NAS was happy,
> EXCEPT BA
Something is wrong here
I moved 48TB from one NAS to the other, rsync -avz --numeric-ids
All dates/times were identical between the two, but when I mounted new at same
mount points, every other application pointing at the NAS was happy, EXCEPT
BACULA which proceeded to do incrementals, selectin
Thanks.
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor sup
It's now resolved!
The Fedora DNF update picked up Bacula 7.4.2 yesterday and today all the
servers did their first daily backup for nearly 3 weeks - no changes on my part
were needed.
Thanks all.
+--
|This was sent by bill.da
