Ask the Community
Groups
Hot Copy or restore failures may result from Hyper-V synthetic backups when non-default deduplication block size is used - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Hot backup copy failures may result from invalid synthesized backups.</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p>This issue is exceedingly rare. To encounter this issue, one first must be using a non-standard Hyper-V deduplication block size setting. <br>If in the appliance master.ini file the value maxSubfileBytes_Hyper-V is not present, then the default values are being used and this issue issue does not apply. <br><br><br><br><br> </p> <h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p>If you are using a custom hyper-V backup block size for deduplication set using [fileDedup] maxSubfileBytes_Hyper-V, upgrade your appliance to version 10.1 and perform new Hyper-V full backups of any effected synthetic backup. </p> </article> </main>