<div id="docs-body">
 <div class="section">
  <div class="titlepage">
   <div>
    <div>
     <h3 class="title">
      <a name="backup-strategy-summary">
      </a>
      9.3.3 Backup Strategy Summary
     </h3>
    </div>
   </div>
  </div>
  <p>
   In case of an operating system crash or power failure,
   <code class="literal">
    InnoDB
   </code>
   itself does all the job of recovering
        data. But to make sure that you can sleep well, observe the
        following guidelines:
  </p>
  <div class="itemizedlist">
   <ul class="itemizedlist" style="list-style-type: disc; ">
    <li class="listitem">
     <p>
      Always tun the MySQL server with binary logging enabled
            (that is the default setting for MySQL 8.4).


            If you have such safe media, this technique can also be good
            for disk load balancing (which results in a performance
            improvement).
     </p>
    </li>
    <li class="listitem">
     <p>
      Make periodic full backups, using the
      <a class="link" href="mysqldump.html" title="6.5.4 mysqldump — A Database Backup Program">
       <span class="command">
        <strong>
         mysqldump
        </strong>
       </span>
      </a>
      command shown earlier in
      <a class="xref" href="backup-policy.html" title="9.3.1 Establishing a Backup Policy">
       Section 9.3.1, “Establishing a Backup Policy”
      </a>
      , that makes an online,
            nonblocking backup.
     </p>
    </li>
    <li class="listitem">
     <p>
      Make periodic incremental backups by flushing the logs with
      <a class="link" href="flush.html#flush-logs">
       <code class="literal">
        FLUSH LOGS
       </code>
      </a>
      or
      <a class="link" href="mysqladmin.html" title="6.5.2 mysqladmin — A MySQL Server Administration Program">
       <span class="command">
        <strong>
         mysqladmin flush-logs
        </strong>
       </span>
      </a>
      .
     </p>
    </li>
   </ul>
  </div>
 </div>
 <br/>
</div>
