How does Enterprise Vault determine the last date a database was backed up
|Article:TECH195072|||||Created: 2012-08-16|||||Updated: 2014-02-04|||||Article URL http://www.symantec.com/docs/TECH195072|
In Enterprise Vault 8.0.4 and newer, the Enterprise Vault Console utilizes a critical alert monitor designed to provide a visual indicator of the last date Enterprise Vault is aware of it's databases and corresponding transaction logs being backed up.
Two primary alerts are provided regarding database backups. The first indicates the last date Enterprise Vault is aware of database backups.
"The SQL database 'Database Name' has not been backed up for 'X' days.
The seconds indicates the last date Enterprise Vault is aware of transaction log backups.
"The SQL database transaction log for Vault Store 'Vault Store Name' has not been backed up for 'X' days.
It has also been noted that the databases are not considered backed up when using SnapManager for SQL Server from NetApp. Using such a program bypasses the process to update the database correctly and therfore EV is not aware the databases have been backed up.
To validate the last date a database or transaction log has been backed up, Enterprise Vault executes a stored procedure that queries the MSDB - Backupset table. The Backupset table lists all the database and transaction log backups performed against all databases within SQL.
Database backups are marked in the Backupset table - "Type" column with either a 'D' or an 'I'.
Note: 'D' = Database backup. 'I' = Differential database
Transaction log backup are marked in the Backupset table - "Type" column with an 'L'.
Note: 'L' = Transaction log backup.
To determine the last date a database has been backed up, a simple query can be executed:
The result will be similar to the following:
Note: The query returns the last full backup and differential backup of the EnterpriseVaultDirectory database as well as the last date the transaction logs were backed up.
Article URL http://www.symantec.com/docs/TECH195072