In environment, What is your network speed or speed needed for SnapMirror Sync?
Since all of the data written to the source system must be replicated to the destination system as it is written, write throughput to the source system cannot generally exceed the bandwidth available between the source and destination system devices. It is important not to look at average write performance, but in order to avoid undesired performance impact, it is necessary to plan for the peaks in write performance.
In general, the configuration guideline is to configure the network between the source and destination system with two times the peak write throughput at the source system.
How can SnapMirror Sync ensure database consistency?
It does this by making sure that CPs are not written to disk until the writes are in NVRAM of the source and the destination filers. The storage does not acknowledge the write until the data has been written to both the source and destination systems. An example is below.
- A user saves some information in the application.
- The client software communicates with a server and transmits the information.
- The server software processes the information and transmits it to the operating system on the server.
- The operating system software sends the information to the storage.
- The source storage sends the information to the destination system.
- The destination system acknowledges receipt of the data.
- The source system acknowledges receipt of the data.
- The operating system tells the application server that the write is complete.
- The application server tells the client that the write is complete.
- The client software tells the user that the write is complete.