[00:00] In this lesson, we'll learn how to configure sync services in Ignition Edge. This enables certain Edge services to connect with a standard Ignition gateway for long-term data storage. This helps to resolve the limitations of Edge historian's alarm journals and audit logs, only being able to store their data for a limited amount of time. I've created my own environment to walk us through configuring these services and I'll talk about what I needed to set up to do this. To start Sync Services requires two gateways to be connected to each other through the gateway network. Looking at my network diagram, my Edge spoke gateway is connected to a standard hub Gateway, which has a permanent database solution. Additionally, I've created a security zone in each gateway to allow remote connections to perform certain actions. On my Edge gateway, I have a zone for my Ignition Standard hub to perform tag writes, and on my standard gateway, I have a zone for my Edge spoke gateway to query and store tag history, alarm journal, and audit log data.

[01:04] Finally, back on my Edge gateway, I have a programmable device simulator connected, giving me the tag data I'll need for some of the services. We've covered in previous lessons in the gateway network topic, how to configure a gateway network and create the necessary security zones for remote connections. So I won't be covering how to implement these in this lesson. Now that we have an understanding of the environment, let's navigate to the Ignition Edge page on my Edge spoke gateway. Next, we'll click on the sync settings tab. Here, we can configure all of the services that we can sync with the standard gateway. Before enabling any of them we do need to provide the remote gateway's name here at the top. So I'll paste in Ignition Standard Hub. Next, we're able to turn on our history sync. With these settings, we can designate a historian on our standard hub to store the tag history data being recorded on our simulated tags in the Edge spoke. So we first need to pass in the name of the history provider we want to use. I'll paste in one from my standard gateway. Once we have the history provider we want, we can turn the service on by checking off the remote history sync enabled checkbox, and that's all you would need to do to enable the history sync.

[02:11] There are some additional options determining how much data gets sent and how often to send the data based on a schedule. Below this video, I've included a link to the user manual page for sync services where you can see how to configure these additional options. If we scroll down, we have more services for both remote audit and remote alarm journal storage. Configuring these is just about the same as a remote historian where you would pass in either the remote audit profile or alarm journal name and then check off their enabled setting. After you configure the services you want, you would then click on this save changes button in the top right. That covers all of the services for data synchronization, but you do also have access to create remote tag providers or remote alarm notification profiles with the Edge service product. We've covered how to create both of these on standard gateways in the Gateway Network topic, and creating them with an Edge gateway is the same exact process you would find in those lessons.

[03:06] One last important thing about sync services is that if you restore a gateway backup on your Edge gateway, there's a possibility to break the synchronization. These services all use a unique ID number and a restoration could have conflicting IDs preventing the system from working properly. If you run into the situation, you could fix the conflict by going back into this Ignition Edge page and clicking on the Sync reset tab. Here you can find all of the services that we have enabled. You can see the tag historian service we set up, and we can reset this by clicking on the reset button resolving any unwanted conflicts.