null

Backups That Work

Whether you utilize our native backup and replication utilities, Veeam, Commvault, or another off-the-shelf solution, jBASE works with them all and allows you to have a single backup strategy.

Online Backup and Restore

The Online Backup facility has been developed to enable system managers to perform necessary regular database backups while still allowing users the ability to perform updates on the database. The jBASE components used for this feature are jbackup and Transaction Journaling. jbackup is a far more powerful tool than your classic PICK backup utility, database archiving, full system backup capabilities and the only facility that may be used while the database is online. Using this facility enables the automatic restoration of the database including all updates up to the point of failure – without operator intervention or scripting. Following the restoration, the database will be left in a consistent state.

The functionality of the restore process, jrestore, has been extended to allow for the automatic roll-forward of log sets after a database restore has completed. This extension uses the Transaction Journal configuration (JediLoggerConfig) which was active at the time of the last backup along with the corresponding Transaction Journal Logfiles.

 

Transaction Journaling & Replication

Transaction Journaling on jBASE has been refined over many years to efficiently deliver the facility to log database updates to jBASE files. This module enables a log of updates that can be used to greatly reduce the time for database recovery in the event of a system or application failure. The “Transaction Journaling” product includes both transaction logging and transaction replication. Transaction logging (sometimes also called transaction journaling) is the normal logging of database updates to a transaction log file. These log files are typically used to restore changes made between backups.

Transaction Replication is a secondary process that takes transaction logs and commits them immediately to a second machine. For purposes of this documentation transaction logging will be used to discuss transaction logging/journaling while transaction replication will be used to describe updating a second machine (remote).

Want to learn more?