Converting MSSQL transaction logs to full backup - how to hold/block this option.

Hello Kamil , 

Thank you for reach out. As you have mentioned that SQL T-log backup is getting converted to full due to communication with the media agent was interrupted. It is best advised to look and resolve the communication failure between SQL client and MA rather implementing a work around. 

Regards

Karthick.C.R

Hello @karthickcr 
 

I fully understand it and thanks for the advice, but in case it would not be possible, are there workarounds for such situations?
 

Thanks,
Kamil

@Kamil 

There are certain situation a SQL tlog backup will convert that is not preventable. Unchecking those conversion rules would not matter. In this case if a log backup was processing data and then a failure occurred, Commvault does not have complete data so the conversion is required to be able to restore. Without conversion all tlog backups after that would not be restorable since each one if required.

Hello @Scott Reynolds 
 

Of course, I realize that in the case of a broken chain, until there is a conversion, it will not be possible to recover the data from that moment, but this would be a conscious action.

One of the Customer would like to have the option that a job that has been converted to full should be treated by blackout window configurations as regular full, and not as a transaction log - in the event that this happens, the job should be stopped according to this blackout window - it's probably one more "if" in the code, and at this point the blackout window in such a scenario is useless, because the only time it's useful is if a normally scheduled full will process much longer than usual. It seems to me that it should be used just in case of unforeseen situations, such as this conversion to full, which someone may not want in a specific blackout window.

Do you think that creating a CMR in Commvault support may result in the acceptance of such an application, or will it be rejected for some specific reason?

Thanks,
Kamil

@Kamil I am not certain on what the requirement or difficulty on implementing this however I think that is a valid CMR.

If you want to go ahead and open a support case, you can reference myself and this thread and share the case number with me and I will follow-up with dev and CMR creation.

Scott

@Scott Reynolds 

Thanks Scott for the hint on this topic, I escalated the thread to CV support as CMR - Incident 230816-271

If you would be so kind, you can also speak up on this matter to put additional pressure on creating such a solution for the Blackout Window configuration.
 

Thanks for the help!

Kind Regards,
Kamil

Thanks for your help @Scott Reynolds Scott on this topic!

Kind Regards,
Kamil

Hello ​@Kamil ​@Scott Reynolds 

I saw this CMR has been resolved but in which release? I have 11.36 and I’m not sure it’s already there.

Hello ​@mateusznitka ​@Kamil 
The MSSQL conversion method changed in 11.38+
Now it starts a new backup job if a database converts for just that specific DB which honors the blackout windows.

Hi, today I have a case on 11.40 when log for some reason convert to full. Transcational log job was completed and “Converted full” job started. But I have blackout window on “Full Data Managament” and this setting was not resepected (converted full is still working, but should be stopped by blackout window). Any hints?