cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Enterprise Vault - SQL Logs never goes down

RenaudT_
Level 4
Partner Accredited

Hello,

We use Backup Exec 2010R2 to backup an EV9sp2 infra with one EV server and one SQL 2008 R2 server. We create a selection and selected the whole EV directory (Partitions, DBs, Indexes...). Then a policy with templates for daily, weekly,...

The EV infra is really small so we backup everything, all the time, with Full parameter. File, DBs, Enterprise Vault. 

The backup is OK (successfull), but when I look on the SQL side Logs stay really high (almost the same size as DBs). Is it normal? Logs should not be purged or flushed to the DB and then reduced of size after a full backup?

Thanks for your help.

Renaud

1 ACCEPTED SOLUTION

Accepted Solutions

sbora
Level 6
Employee Accredited Certified

No need to run SQL log backup to truncate the logs. You can run EV agent incremental backup from Backup Exec and that will truncate the logs.

However this will not reduce the physical size of the file on the disk. To resduce the size of the log file on the disk you will have to shrink the database file from SQL. Refer to following document for information:

http://www.symantec.com/docs/TECH82950

View solution in original post

2 REPLIES 2

ZeRoC00L
Level 6
Partner Accredited

This has nothing to do with Enterprise Vault, but more with Backup Exec.

See the BE forums here:

https://www-secure.symantec.com/connect/backup-and-archiving/forums/backup-exec

BTW:
you will need to create an SQL LOG backup to get the logs flushed:

http://www.symantec.com/business/support/index?page=content&id=TECH126063

sbora
Level 6
Employee Accredited Certified

No need to run SQL log backup to truncate the logs. You can run EV agent incremental backup from Backup Exec and that will truncate the logs.

However this will not reduce the physical size of the file on the disk. To resduce the size of the log file on the disk you will have to shrink the database file from SQL. Refer to following document for information:

http://www.symantec.com/docs/TECH82950