cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Critical Status messages after Backup Exec differential backups

Using EV agent for BE 2010 R3, we do weekly Full backups and daily Differentials. All backups complete succesfully. A couple of days after the full backup, we get the following warnings in the EV10 console.

 It is more than 2 days since backup or replication was detected for one or more open partitions.

Open partitions with unsecured items scanned: 1
Total open partitions: 1

List of partitions:
    VaultStore 1 Ptn1


The fingerprint database 'EVVSGVaultStore1_1_1' transaction log for Vault Store Group 'Vault Store 1' has not been backed up for 3 days. The information in this database is at risk until the database has been backed up.



The SQL database transaction log for Vault Store 'VaultStore 1' has not been backed up for 3 days. The information in this database is at risk until the database has been backed up. 

The weekly Full backup crears these warnings. According to http://www.symantec.com/business/support/index?page=content&id=HOWTO23612, diff backups should a full backup of the the databases, so I believe these messages should not appear.

Anyone come across the same, or know how to stop the warnings appearing?

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Differential backup ideally

Differential backup ideally backup the chages from the last full backup ..you need to run incremental backup to avoid the errors you are getting .

Enterprise vault would know the backup is done only when the archvie bit is reset for a vault store partition .

eg if you perform the full backup the archvie bit on the files get reset. Next time when you run the differential backup it will just backup the files chaged from last full bakup but will not touch the archvie bit . and these files would get baked up each time you run the differential backup . whereas if you are running  incremental backup it would backup the changes from last full or incremental backup . Incremental backup resets the archive bit . so when performing next backup it would only backup the file with the arhive bit on it .

View solution in original post

3 Replies
Highlighted
Accepted Solution!

Differential backup ideally

Differential backup ideally backup the chages from the last full backup ..you need to run incremental backup to avoid the errors you are getting .

Enterprise vault would know the backup is done only when the archvie bit is reset for a vault store partition .

eg if you perform the full backup the archvie bit on the files get reset. Next time when you run the differential backup it will just backup the files chaged from last full bakup but will not touch the archvie bit . and these files would get baked up each time you run the differential backup . whereas if you are running  incremental backup it would backup the changes from last full or incremental backup . Incremental backup resets the archive bit . so when performing next backup it would only backup the file with the arhive bit on it .

View solution in original post

Highlighted

monitoring

EV checks if a FULL has been done.

Change the monitoring schedule to warn you on the database backup after 8 days.

Because:

you write you make a full backup once a week

sunday backup full = day 1

sunday next backup full = day 7

monday check. if last sunday succesfull, then no warning, if last full failed, warning. More realistic.

Regards. Gertjan
Highlighted

I would also suggest that you

I would also suggest that you do transaction log backups, so you keep the t-logs at a good size.

At least if you use Full recovery model in SQL.

As far as I remember the differential only do a differential of the DB, it doesn't do anything with the T-log.

NBU work that way anyway and I believe it's a SQL thing since most backup software use the internal SQL methods to trigger backups but redirecting the data stream through the agents.