#1 Global Leader in Data Resilience

DD replication causes panic error on the target Data Domain server

KB ID: 2244
Product: Veeam Backup & Replication
Version: 9.5
Published: 2017-02-15
Last Modified: 2020-08-13
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

You have configured a Data Domain Storage Unit as a Veeam backup repository using MTree replication. Data Domain replication results in PANIC on the target Data Domain storage. 

Cause

Veeam Backup & Replication leverages the Virtual Synthetic (VS) feature of the DD Boost library for building Grandfather-Father-Son (GFS) restore points or when applying retention policies to backup chains. As part of the Veeam workflow, overwrites can occur over sections of the file being replicated that have already been processed. This behavior will trigger the recipe tracking process to remove all recipes on the disk, but not any invalid in-memory recipes. This may result in a corrupted recipe to be recalled and lead to an incorrect recipe replication process later (because of a checksum mismatch) so that recipe replication will be confused and target EMC Data Domain may PANIC.

Solution

Turning off the recipe processing feature on the source Data Domain system source for MTree replication will resolve the issue. A later DDOS 6.x release will fix the underlying issue, and recipe processing can then be re-enabled for performance reasons.

Customers should first verify their system matches the criteria for overcoming the issue:

1. Confirm that the system configured for VEEAM backups is also configured for Data Domain MTree replication: 
# replication show config
In the output look for "mtree://"

2. Confirm if managed file replication (MFR) or backup replication via DD Boost) is being used, on the Data Domain you can use this command: 
# ddboost file-replication show active all

Also verify in the backup application configurations. Once confirmed through the commands above your system may be a configuration where this issue applies, please do following or contact Dell/EMC support for assistance:

3. Disable running replication contexts and MFR tasks, if any.

4. Run command
#se sysparam set RECIPE_REPL_ENABLED=FALSE

5. Enable replication contexts and resume MFR tasks, if any.

Note the workaround to be performed by a Dell EMC TSE will require disabling Data Domain replication and MFR replication jobs, and will require downtime for the workaround to be completed.

More Information

This fix was made into DDOS 6.0.1.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.