<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic MySQL Replication NetApp and NFS in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/MySQL-Replication-NetApp-and-NFS/m-p/66520#M6064</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We're currently setting up a new MySQL 5.5 replicated database using NFS mounts for the database.&amp;nbsp; The standard configuration for MySQL replication includes setting "innodb_flush_log_at_trx_commit=1" and "sync_binlogs=1" to make sure database updates are saved and replicated properly in the case of a server crash, or power outage.&amp;nbsp; My question is regarding NFS.&amp;nbsp; If we store the databases for the replicated servers on NetApp NFS mounts, are we still guaranteed that the updates are saved properly even with "innodb_flush_log_at_trx_commit=1" and "sync_binlogs=1"?&amp;nbsp; I've read two NetApp documents "Best Practices Guidelines for MySQL" and "MySQL 5.0 Performance Protocol Comparision", but there is nothing I can find that talks specifically about NFS and MySQL Replication.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 06:55:01 GMT</pubDate>
    <dc:creator>MIKEA0730</dc:creator>
    <dc:date>2025-06-05T06:55:01Z</dc:date>
    <item>
      <title>MySQL Replication NetApp and NFS</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/MySQL-Replication-NetApp-and-NFS/m-p/66520#M6064</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We're currently setting up a new MySQL 5.5 replicated database using NFS mounts for the database.&amp;nbsp; The standard configuration for MySQL replication includes setting "innodb_flush_log_at_trx_commit=1" and "sync_binlogs=1" to make sure database updates are saved and replicated properly in the case of a server crash, or power outage.&amp;nbsp; My question is regarding NFS.&amp;nbsp; If we store the databases for the replicated servers on NetApp NFS mounts, are we still guaranteed that the updates are saved properly even with "innodb_flush_log_at_trx_commit=1" and "sync_binlogs=1"?&amp;nbsp; I've read two NetApp documents "Best Practices Guidelines for MySQL" and "MySQL 5.0 Performance Protocol Comparision", but there is nothing I can find that talks specifically about NFS and MySQL Replication.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:55:01 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/MySQL-Replication-NetApp-and-NFS/m-p/66520#M6064</guid>
      <dc:creator>MIKEA0730</dc:creator>
      <dc:date>2025-06-05T06:55:01Z</dc:date>
    </item>
    <item>
      <title>Re: MySQL Replication NetApp and NFS</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/MySQL-Replication-NetApp-and-NFS/m-p/66524#M6065</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey Mike, I'm keen to know which settings you came up with? Or maybe you didn't go any further with NFS?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Vladimir&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 May 2012 21:03:57 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/MySQL-Replication-NetApp-and-NFS/m-p/66524#M6065</guid>
      <dc:creator>vladimirzhigulin</dc:creator>
      <dc:date>2012-05-25T21:03:57Z</dc:date>
    </item>
  </channel>
</rss>

