Optimize Your Transaction Log Backups to Avoid Server Crashes, Part 1: The Essentials of a Good Backup Strategy

Ronny Henfling, IT Specialist, Deutsche Bahn AG

Jan Ofiara, IT Specialist, IBM Germany


July, 2010

Daily backups and transaction log backups recover files after a system failure or user error. But the best strategy is useless if the Domino transaction logging file system reaches full capacity and consequently causes the Domino server to stop. The result can be destroyed databases or corrupted transaction logs, not to mention dissatisfied users. Learn how to avoid the risk of your transaction log disk space reaching full capacity by basing your backup strategy on a clear understanding of all relevant factors and using the calculation-based method demonstrated here. In part 1, learn about the benefits of archive-style logging in making your Domino backups more efficient, gain insight into the relationship between transaction logging and backup intervals, and find out how to arrive at a backup strategy that makes sense for your environment. In part 2, learn the formulas to use in setting your backup strategy.

Domino administrators who work with archive-style transaction logging may recognize the problem: If the transaction logging file system is filled to capacity, the Domino server crashes. Often, your only option is to simply restart the server. You may also try shortening the backup interval. These measures usually solve the problem in the short term. However, if the situation reoccurs with some frequency, you will need to do something to solve the underlying problem.
Eliminating the risk of a file system reaching full capacity requires understanding the interrelationship of backup intervals, transaction logging data throughput rates, and thresholds for log archiving so that you can optimize your transaction logging system for stability. Find out how to improve the quality of your Domino transaction log backups based on what we’ve learned through our own implementation of archive-style Domino transaction logging in a large Domino server farm. We’ll share the approach that helped us to increase both system stability and the fail-safety of the Domino server infrastructure during transaction log backups.
Whether you are an administrator who manages archive-style Domino transaction logging, or an infrastructure specialist concerned with the planning of Domino transaction logging in conjunction with backup software, you can apply the principles and methods we share here, regardless of the backup software you use.

Would you like to see the full version of this article?

If you are an electronic license holder to THE VIEW, please log in to view this article.

If you would like information about becoming an electronic license holder — and having 24/7 unrestricted access to all articles and content in THE VIEW Online Knowledgebase — click here to see the available subscription options.

Or call 1-781-751-8813 to speak directly with a subscription and licensing specialist about customized access for you and your team.