Log Backup Activity To Database

Top Previous Next

In addition to knowing that the backup didn't work, it is still desirable to log backup activity to some sort of log file, e.g. to a database. That way the backup history will still be available even when the event log is cleared.

As of version 2.70, EventSentry supports the following databases:

•	Microsoft Access: This database is only recommended when you have a single host or a very small number of computers (e.g. 1-3 computers) in your network.

•	Microsoft SQL Server: This is the recommended database for small, medium and large networks and has thus far shown the best performance with the web reports.

•	MySQL: This database is recommended when you have a small or medium size network and do not have Microsoft SQL Server available.

•	Oracle: We only recommend Oracle for customers who already have an Oracle database server they need to integrate EventSentry with.

Since this guide focuses only on one computer we will use a Microsoft Access database for our example. In order to log all backup (or all event log activity for that matter) to the database you will need to do the following:

1.	Install the EventSentry Access database (automatically done during installation)

2.	Create a database notification target (automatically done during installation)

3.	Create a filter forwarding NTBackup events to the database

4.	Optionally create a custom Access query

5.	Setup the web reports using IIS