commvault.com commvault.com
Solved

Missing some Full backup jobs

  • 5 October 2022
  • 3 replies
  • 117 views
E
Rank
Userlevel 2
Badge +9

Hi, We noticed that some Full backup jobs are missing for one of our PostgreSQL clients.

Those are the Full backup jobs for the months: February, March, April, May and August. 

 

Doing another query including aged data we have:

These Full backup jobs with one or more errors completed with errors that our DBA team recognized as harmless, but Does the Commvault software not honor extended retention time for backup jobs completed with errors? 

This may explain why we didn't find the Full backup jobs for the months mentioned above and, In this case, the backups jobs for the months of April and August will expire soon.

 

 

 

icon

Best answer by Mike Struening RETIRED 5 October 2022, 20:35

View original

3 replies

Mike Struening RETIRED
Rank
Userlevel 7
Badge +23

Depends on the agent:

https://documentation.commvault.com/2022e/expert/11965_impact_of_jobs_that_completed_with_errors.html

However, PostgreSQL is not there.

The next thing to check is in Control Panel > Media Management.

Can you see what this is set to?

Ignore Completed With Errors job option for Extended Retention calculations

Definition: Specifies whether or not to ignore the Completed With Errors job option for Extended Retention calculations.

Default Value: 0

Range: 0 (No) or 1 (Yes)

When the value is set to '1', the current value set for the Completed with Errors job in the agents' database is ignored for extended retention calculations. When the value is set to '0', the current value set for the Completed with Errors job is honored for extended retention calculations.

Usage: Administrator may hold extended retention Jobs to a higher standard than those used to determine normal media/retention cycle.

https://documentation.commvault.com/2022e/expert/11019_media_management_configuration_data_aging.html

https://www.linkedin.com/in/michael-struening
E
Rank
Userlevel 2
Badge +9

Depends on the agent:

https://documentation.commvault.com/2022e/expert/11965_impact_of_jobs_that_completed_with_errors.html

However, PostgreSQL is not there.

The next thing to check is in Control Panel > Media Management.

Can you see what this is set to?

Ignore Completed With Errors job option for Extended Retention calculations

Definition: Specifies whether or not to ignore the Completed With Errors job option for Extended Retention calculations.

Default Value: 0

Range: 0 (No) or 1 (Yes)

When the value is set to '1', the current value set for the Completed with Errors job in the agents' database is ignored for extended retention calculations. When the value is set to '0', the current value set for the Completed with Errors job is honored for extended retention calculations.

Usage: Administrator may hold extended retention Jobs to a higher standard than those used to determine normal media/retention cycle.

https://documentation.commvault.com/2022e/expert/11019_media_management_configuration_data_aging.html

Mike,

In our case the parameter is set to 0

When the value is set to '0', the current value set for the Completed with Errors job is honored for extended retention calculations.

And How do I know the current value set for the Completed with Errors job? 

Mike Struening RETIRED
Rank
Userlevel 7
Badge +23

If you change that setting to a 1, then Extended Retention will ignore CWE and keep jobs as if they completed just fine.

Leaving it as 0 means that any CWE jobs will not be kept for Extended Retention.

The reason is that the component of the backup that failed (hence, the CWE) might bar this backup from doing a full restore.  Better to err on the side of caution and not keep that job (by default).

You can change it to a 1 and (going forward) all CWE jobs will be eligible for Extended Retention.

Conversely, you can find out why they are CWE and address that directly.

Let me know if that helps, @Eduardo Braga !

https://www.linkedin.com/in/michael-struening

Reply


Terms & ConditionsCookie settings