What does JobManager Event 19:1962 mean? "Redirecting to the data storage policy[String] of the online full backup[Number]."

@tigger2 

When I research that message, I get given a link to this article: https://documentation.commvault.com/2023/expert/selective_online_full_backups.html

This states:

• The data and archive logs use the data storage policy that you define on the subclient. Selective online full backups ignore the log storage policy that you define on the instance.

So I believe that this event appears to be notifying you that this is happening (as it may be unexpected as it’s technically running a ‘full’ now and not just an incremental/archive log backup), however I find it strange this is showing as ‘major’ event… 

It’s not necessarily an error in my opinion (if my understanding is correct), moreso an FYI.

Are you able to confirm if this appears to be the case (as in, it’s done a full not an incremental/t-log)?

Regards,

Chris

No issues @tigger2, 

Good to know! Was the event not for Oracle? 

If it was SQL and not Oracle, I’d say it’s major because it’s SQL… and if T-LOG backups continue to fail or hang, you could run out of disk space on the SQL Server as the log isn’t being truncated.

https://learn.microsoft.com/en-us/sql/relational-databases/backup-restore/back-up-a-transaction-log-sql-server?view=sql-server-ver16

If a database uses either the full or bulk-logged recovery model, you must back up the transaction log regularly enough to protect your data, and to prevent the transaction log from filling. This truncates the log and supports restoring the database to a specific point in time.

CV article for reference: 

https://documentation.commvault.com/2024/expert/backing_up_sql_transaction_logs.html

Each time a transaction log is backed up, the transaction log is truncated to the exact time of the backup operation and releases the inactive virtual log files for reuse. However, the truncation does not reduce the size of a physical log file.

​​​​​​​Regards,

Chris