Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

reducing db size in backup exec 10d?

Created: 30 Jan 2012 | 6 comments
michael.t.anderson@pepsico.com's picture
0 0 Votes
Login to vote

Is there a techdoc on how to reduce the size of a be 10d database.  I have two that are causing space issues.

 

thanks

Comments

VJware's picture
30
Jan
2012
0 Votes 0
Login to vote

try clearing all alerts from

try clearing all alerts from alert history...

Delete aged data from Tools - Options - db maintenance

try compacting database using BE Utility.exe

Ken Putnam's picture
30
Jan
2012
1 Vote +1
Login to vote

RE: reducing db size in backup exec 10d?

Is it the size of the BEDB itself, or is it the \Catalogs directory that is causing problems?

If this response answers your concern, please mark it as a "solution"

Striker 303's picture
31
Jan
2012
1 Vote +1
Login to vote

The Size of the BEDB (Backup Exec Database) Log file BEDB_LOG.LD

 

Refer: The Size of the BEDB (Backup Exec Database) Log file BEDB_LOG.LDF becomes very large

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

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

michael.t.anderson@pepsico.com's picture
31
Jan
2012
0 Votes 0
Login to vote

Catalog Folder

The catalog folder is five gb, on other servers it is just under one half a gb.  So I suspect the size of the catalog folder is the culprit in this case.

 

What are my options?

VJware's picture
31
Jan
2012
1 Vote +1
Login to vote

Either you move the Catalogs

Either you move the Catalogs to a different location OR you may choose to truncate catalogs

KB - http://www.symantec.com/docs/HOWTO23126

Ken Putnam's picture
31
Jan
2012
0 Votes 0
Login to vote

RE: Either you move the Catalogs

if you choose to truncate the catalogs, be aware that you will need to re-catalog any affected media before being able to restore from them.

Not a deal killer by any means, but something to bear in mind

If this response answers your concern, please mark it as a "solution"