We have turned nbackup off...
The problem with that is:
a. we want nbackup on!
b. we've been running for a year in the current configuration and only had the
issue once in the last month on one server, and twice in the last month on
another. I'm not convinced that if it doesn't happen
Hi Rob,
All access is through the server. Either localhost:/db_path/customer.gdb or
customer.server:/db_path/customer.gdb which are separate tcpsvd services but
using the same lock folder.
The nightly backup does 3 things:
1. backup using gbak
2. sweep using gfix
3. runs an sql
Hi Rob,
All access is through the server. Either localhost:/db_path/customer.gdb or
customer.server:/db_path/customer.gdb which are separate tcpsvd services but
using the same lock folder.
Ian
I had the same thing again on a completely unrelated database that doesn't do
the nightlySQL bit...so I know it isn't that.
Following on from the question from Alexey which made me think about
multi-file databases which we aren't using I've just disabled our regular
NBackups that we were
We shouldn't do. Just single big file in the first case, and a fairly small
500MB one in the second.
Hi FB Support!
We have been running FB since IB4.2 days and have only previously had any
database corruption when we've had hardware issues...until recently, when I've
seen this error on 2 different servers that I'm reasonably confident are both
fine! However, our setup is probably fairly
