Use periodic
incremental live backups to prevent transaction logs from growing too large. Databases can
remain online while this type of backup is generated. You can then apply incremental backups
against the full backup on the recovery server.
Note: Incremental
backups must be simultaneously indexed (renamed and a new output file started),
particularly for the cache database. This prevents open-ended growth of the
transaction log, while maintaining information about the old transactions.
Using dbbackup to Create Incremental Backups
Use the dbbackup utility to create an incremental live backup that also resets transaction logs on completion. Each backup uses a unique name that acts as a method of versioning each file.
Using dbtran to Validate the Backup
Validation allows you to check the integrity of incremental backups and to ensure that you can safely apply these increments to the offline backup. This is a vital step and cannot be bypassed, without risking the viability and integrity of your backup data.