Prev Pervasive Backup Agent Guide (revision 1) Next


Backup Agent Components

Show this topic in Library frames

This section discusses the components that make up Pervasive Backup Agent. The two utility components along with the Software Developer's Kit (SDK) give you three ways to easily incorporate the agent into your backup routine, depending on your business needs.

Command-line Utility

The command-line interactive (CLI) utility (pvbackup.exe) is one access method Backup Agent offers. For implementation with any of the popular backup products on the market, simply add the executable commands into pre and post command settings. With this implementation, your backup software automatically starts the agent prior to backup and stops the agent after the backup completes. Using this method ensures that your regularly scheduled backups include consistent and reliable Pervasive.SQL data.

GUI Utility

Another access method for Backup Agent is the graphical user interface (GUI) utility (pvbackupgui.exe), which is available from the Start menu or from within the Pervasive Control Center. In this interface you can start and stop the agent at the touch of a button - without having to recall commands or parameters required for the command-line interface. Using this method allows you the flexibility to perform ad-hoc backups of your Pervasive.SQL data quickly and almost effortlessly.

Controller

The Controller component of Pervasive Backup Agent consists of a DLL which provides a common interface for the agent utilities. The Controller handles all communications with the Event Handler.

Durable File List

The Durable File List (dfl.txt) is located in the program's data path and is generated by Pervasive Backup Agent. The default location for the data path is set at installation as <Pervasive.SQL install directory>\PBA\Data. This file contains a list of all the files in Continuous Operations at any given time. When a file goes into Continuous Operations, it is automatically added to the list. Similarly, when the file is taken out of Continuous Operations, it is then removed from the list.

Event Handler

The Event Handler is the workhorse inside Pervasive Backup Agent. The primary purpose of this component is to intercept files as they are opened so that they can be placed in Continuous Operations. Backup Agent uses the MicroKernel hook interface to work with the Controller to handle all the operations, or events, requested through the Backup Agent interfaces. As the name implies, the Event Handler handles all the events going on inside Backup Agent.

Log File

Pervasive Backup Agent maintains a log file (baevent.log) which reports informational and warning messages from the event handler. The log file resides at <Pervasive.SQL install directory>\PBA\Logs, and this location cannot be modified.

Software Developer Kit (SDK)

Pervasive Backup Agent includes an application programming interface (API) so that developers can embed the Backup Agent directly into a software application. The API, along with the necessary header and library files, make up the SDK developers need for this type of implementation. Integrating Backup Agent directly into your application using the SDK provides the highest level of backup data assurance.


Chapter contents
Publication contents

Prev topic: Pervasive Backup Agent Overview
Next topic: Licensing