Question: Truncating Catalogs and when it takes affect

MacLEOD's picture
MacLEOD
July 16th, 2010

Hello there,

We have the Backup Exec 11D and I have recently check the catalog retention period on our Server (was set to 4 months).
I have have the following note http://seer.entsupport.symantec.com/docs/229528.htm
to change this setting form 4 months to 3 months before truncating.

My question is when/if the Backup Exec will tidy up the month of Catalogs?

Is it a scheduled process, or is it something internal to Backup Exec?  Can it be manually started/checked?

Thanks

Filed under: , , , ,
0 votes

AmolZeroCool's picture
AmolZeroCool
7 weeks 4 days ago

Ideally the old catalogs should disappear after recycling the services.

I have noticed that the old catalogs still appear in the catalogs folder even after restarting the services.

As per my experience the catalogs will start truncating as soon as you run any backup or restore job.


Regards
Amol
__________________________________________________________________________________________
If this response answers your query, please mark it as a solution

+1 (1 vote)
AmolZeroCool's picture
AmolZeroCool
5 weeks 4 days ago

Any update on the issue ?


Regards
Amol
__________________________________________________________________________________________
If this response answers your query, please mark it as a solution

0 votes
Colin Weaver's picture
Colin Weaver
5 weeks 1 day ago

The remove catalogs timing only starts for new catalogs i..e

You start with no Catalog Truncation and then decide one day to turn on Truncate after a Month - nothing will happen to the existing catalogs, but in a months time new catalogs will start to get deleted.

Not 100% sure what would happen if you started with 4 months truncation and then changed it to 3 months EDIT: On a quick chat with a colleague though we believe it will still truncate the 4 month data on the 4 month anniversary

This is because we set the truncation date as calculated from teh job date and the current truncation settings when the job runs - instead of saving the job run date and having the truncation date dynamically calculated from the current truncation settinbgs.

+2 (2 votes)