compared with
Version 7 by Mario Heredia
on Aug 19, 2020 10:28.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (8)

View Page History
{color:#172b4d}{*}Enabling the InnoDB_force_recovery option for Control Panel users{*}{color}

{color:#172b4d}In this release, we have extended the ability of using additional options during a MySQL DB database restore, to control panel users. So, during a MySQL restore, control panel users will get an option, to select a value for InnoDB_force_recovery.{color}

{color:#172b4d}However, since this option can be destructive, we have made this a 2-Part process, for enabling and using this feature. a. Control Panel Admin needs to enable the option. To know more, visit the <<add link here>> page b Control Panel End users can then use the innodb_force_recovery option. To know more, end users can visit{color} {color:#172b4d}the <<add link here>> page{color}
{color:#172b4d}However, since this option can be destructive, we have made this a 2-Part process, for enabling and using this feature.{color}

{color:#172b4d}&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; a. Control Panel Admin needs to enable the option. To know more, visit&nbsp;{color}{color:#172b4d}[ServerBackupManager:Enabling the innodb_force_recovery option]{color}

{color:#172b4d}&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; b. Control Panel End users can then use the innodb_force_recovery option. To know more, control panel end users can visit the{color}&nbsp;[ServerBackupManager:Restore MySQL databases with innodb_force-recovery]&nbsp;page.

h1. {color:#172b4d}{*}Fixed Issues{*}{color}


{note:title=Important Upgrade Notice}
This fix requires a new version of&nbsp; cPanel plugin to be installed. Please review the <<add link here>>&nbsp;
This fix requires a new version of&nbsp; cPanel plugin to be installed. Please review the&nbsp;[Set up the cPanel plugin|ServerBackup:Set up cPanel plugin]&nbsp;page.
{note}
* {color:#172b4d}Fixed an issue with the DCC API documentation which was not being rendered correctly.{color}
* {color:#172b4d}Fixed issues with the DCC APIs where some of the APIs were not returning error or incorrect output.{color}
* {color:#172b4d}Fixed issues with the DCC APIs where some of the APIs were not returning incorrect output or returning an{color} {color:#172b4d}error{color}{color:#172b4d}.{color}