Skip to main content
Solved

Failed to replicate snapshots for subclient [default] using DDR

  • February 10, 2022
  • 5 replies
  • 1500 views

Forum|alt.badge.img+1

Hi,

we are getting a number of failed backup jobs for SQL default subclient with the following error:
Failed to replicate snapshots for subclient [default] using DDR

As I was not able to find any viable explanation for this error message on CommVault support site, I would be glad if someone can explain what this error message actually means.

Sincerely,

Vladimir

Best answer by Scott Reynolds

@Marc Poncet Correct that is same as my response “Check to see if you have a separate schedule set for the SQL clients to run a full backup. You should only see transaction log schedule for all those VMs that are configured for appaware.”

This error can occur on appaware when running from the SQL subclient level.

I will also note that we changed the job pending reason to be clearer on the failure and the error in latest version of Commvault.

Glad we could assist you!

View original
Did this answer your question?
If you have a question or comment, please create a topic

5 replies

Mike Struening
Vaulter
Forum|alt.badge.img+23

@Marc Poncet , can you confirm this SQL instance is running on a VM?  this error usually indicates that a SQL backup is running via the SQL iDA, not the app ware configured VSA iDA.


Forum|alt.badge.img+14

@Marc Poncet  Check to see if you have a separate schedule set for the SQL clients to run a full backup. You should only see transaction log schedule for all those VMs that are configured for appaware.

The full can only start/run from the VSA subclient which launces the full on the SQL side.

This is all assuming you meant to enable appaware backups?

 


Forum|alt.badge.img+1
  • Author
  • Bit
  • 2 replies
  • February 11, 2022
Mike Struening wrote:

@Marc Poncet , can you confirm this SQL instance is running on a VM?  this error usually indicates that a SQL backup is running via the SQL iDA, not the app ware configured VSA iDA.

Hi Mike, thank you for your reply. SQL instance is running on a VM where backup is configured as a VSA AppAware backup. The problem with this error is because it is random as next backup jobs after the one that failed are performing successfully.


Forum|alt.badge.img+1
  • Author
  • Bit
  • 2 replies
  • February 11, 2022

I think I found the rights answer to my question:
https://kb.commvault.com/article/64049
Thanks guys for your willingness to help me.

Best regards,

Vladimir


Forum|alt.badge.img+14

@Marc Poncet Correct that is same as my response “Check to see if you have a separate schedule set for the SQL clients to run a full backup. You should only see transaction log schedule for all those VMs that are configured for appaware.”

This error can occur on appaware when running from the SQL subclient level.

I will also note that we changed the job pending reason to be clearer on the failure and the error in latest version of Commvault.

Glad we could assist you!


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings