As Paul says every block with data in it must be read - even for an incremental backup. Which is why an incremental backup takes about as long to run as a full backup.

-Bp 10 helps to prevent the entire -B buffer pool getting flushed as a result of a backup running and the follow-on impact that that will have to the hit ratio. During the backup itself though you will still almost certainly see a poor hit ratio.

@mlb3820 Thanks Mark. That's fixed it.

@nickw still getting the dbanalys msg too? Or just the "cannot find drive" msg?

Can you email to me log\dbmonitor.log and tmp\dbmonitor.debug and err please?

$PROTOP/etc/NOTES_*.

tick, tick, tick...

The time for pre-release feedback is drawing to a close!

@tom said in Installation Instructions:

Would be a better error message?

Sure

if ( not _Connect-device matches "*batch*" ) and _connect-batch <> "yes" then tt_Dashboard.con_self = tt_Dashboard.con_self + 1.

So "self" is counted for non-batch self-service connections. It (mostly) equates to local interactive connections.

Somehow I suspect that you are going to suggest that that might be sub-optimal 😉

@tom Sorry... off to the coffee machine...

Looks like it dates back to pt3.3n.

It is fixed now.

@tom said in Alert re lkHWM near lkTableSize:

Regarding the specific alert: there is a lkTblPct field which I use for a similar purpose. Rather than the HWM it reflects the locks in use at that moment. In some ways that is better -- the HWM sticks around until you restart and if something went bump in the night is going to keep alerting once you hit the threshold.

Good to know, thanks.

Nope. You're right -- that's a bit more difficult to calculate and it seems much less likely.

But I'll add it to the "think about it" list 🎣

Portal v4 has a lot of enhancements to stuff like this. Real Soon Now.

Which reminds me of another needed alert "not having audit archive db" 😉

I think I probably need more visuals. I'm not forming a picture in my head of what you are describing.

Should be fixed in pt3.141x. I decided to simply use the first part of the device name unless the device name is "batch" and only if the name is otherwise blank. If that fails then use the usr#.