I have some bad news for folks running transactional logging. Items 1 and 2 cannot be used to help reduce file sizes without some very careful planning. You should not use copy style compacts with transactional logging. Doing so renders all prior log extents for that database useless since a copy style compact changes the DBIID. The rule is that you should take an immediate full backup after running a copy style compact on a transactionally logged server. I have seen people run a compact on Saturday night, and then take a full backup on Sunday. They were willing to risk the potential loss of data due to a crash/corruption for that short, off-hours timeframe. Only do this if you understand the risks and are willing to take them.Because I use the same strategy you mentioned here, I kind of got worried. Can you please advise what is the best strategy and command switches to use for compacting and backing up DBs on a transaction logging-enabled server?
Do you have comments on this Ask the Expert Q&A? Let us know.
Dig Deeper on Lotus Notes Domino Database Management
Related Q&A from Michael Lazar
Learn how to easily keep track of the numbers of incoming and outgoing Lotus Notes email messages to and from your Domino server each day. Continue Reading
Discover what steps you can take if your Lotus Domino server runs out of disk space and you have issues sending and receiving Lotus Notes email ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.