Restore Backups more than 30 Days, Big Problem
Hello,
I have search at the forum and find many topics how to restore backups more than 30 days, I read many topics and see that I have to change options at Database Maintenance and Security, I configure these options on last 2 weeks like the picture here, but it´s not take effect, I see the Backup Sets older than 30 Days, buit is only possible to restore backups until 30 Days.
It´s possible to anyone help me to find where I have to configure IT ?
Instead of, I Change Audit logs today to 182 days. But I only see the effect tomorrow, if it´s possible to restore my backup from 08/28/2017.
This Backup Job are running more than 6 months.
I Use backup Exec 2014.
You should probably log a formal support case
Also note: Backup Exec is not designed to run with an incremental forever strategy and as such you should run a full backup more often than you appear to be doing.
1) The job history is JUST the information in the console (or reports) about whether the job ran on a certain date - it has nothing directly to do with being able to restore. Although it can be handy as references for what media (tapes etc) were used by a specific job
2) The availability for restore selection to be visible is linked to catalogs (and possibly catalog truncation) where:
- Catalogs are only deleted for tape based jobs, when the tape is overwritten (which is loosely linked to media set protection settings but also requires a new backup to run after the protection dates end)
- Catalogs for disk or deduplication based jobs are deleted when the backup set is expired and reclaimed
- Catalog truncation reduces the details we keep a record of in restore selections to just the whole of the backup set instead of the individual items (files etc) so should be used with care if you want the ability to restore individual files going back any length of time
- As catalogs can get large over time- it is recomended that you make sure that the catalogs folder is stored on a volume with plenty of disk space (and therefore almost certainly not the C: drive of the server itself)
- For tapes you can overwrite a full backup before the chain of incremental backups are overwriteable - but should plan it so that you do not do this as this as it will mean not being able to restore from the incremental chain back to the full, so you should use longer overwrite protection settings for the full and/or make sure the full tapes are not online in the library (or are only online with the correct media set or physical overwrite protection) until you know you no longer need the backup set
- For disk and deduplication backup, BE removes the backup sets and the catalogs as background operations but will ONLY do this when the complete incremental chain is expired AND addtionally when it is NOT the last complete backup chain of a specific set of data.
As these above concepts are complicated you should research catalog handling as well as use of media sets (for tapes) and data lifecycle management (for disk and deduplication). We cannot possibly describe all the details in a forum post as it woud more or less means writing the admin guide again.
