Welcome to this demonstration on how appsync integrates with S RDF Metro technology. There are many use cases available with this integration and we will step through a few of them today. Now for a quick overview of appsync. AB sync is a software that enables integrated copy data management or ICD M with Dell EMC primary storage systems. Absynth simplifies and automates the process of generating and consuming copies of production data. It is able to orchestrate all the activities required from copy creation and validation. We are mounting at the target host and launching or recovering the application. This video will explain how absent can automatically create copies with S RDF Metro technology.
Today's agenda will include how AB sync is configured to work with S RDF Metro. It will also show how the Absynth service plans are defined. The video will lastly step through running a gold service plan for SDF Metro and viewing and mounting a copy. And now we'll get into the demo. If we navigate to the Dell EMC Appsync dashboard and then navigate to settings, you can see that under infrastructure resources and storage systems, we have three storage systems added to AB sync. We have two power max 2000 arrays, 691 and 692. These make up the synchronous Metro replication and then we have a V max 250 F array 859 which makes up the third leg which is SRD asynchronous. We navigate to the servers item.
You can see that we have a 60.181 host running sent OS and this has two extent four volumes coming from the Power Maxes. This is what we will use for creating copies in a sync. Now we navigate to copy management service plan and file systems. You can see we've created three service plans for SDF Metro use cases. We have a bronze one, a silver and a gold. These were all created from the original bronze, silver and gold templates to be specific for SDF Metro. If we edit this bronze plan, you can see that the copy location defaults to local. This is because a bronze plan with S RDF Metro allows you to choose which leg of the Synchronous Metro replication that we create the copy on. So if we navigate to next, you can see here under the Metro one. AB sync knows that 691 and 692 arrays are involved in S RDF Metro synchronous replication.
You choose here which array either 691 or 692 you want the copy to be taken on. If you want to create copies on both sides, you need to create two bronze S RDF Metro service plans. If we look at the Silver S RDF Metro service plan and hit edit, you can see here the copy location defaults to remote. This is because a Silver SDF Metro service plan will snap the DR leg or the leg that is being updated via SRD or asynchronous replication. In many cases, this is called the third site. Because of this, you don't have to choose which site to create the copy on absint. Just knows that the link that is being updated via SRD is the one that will be copied in this instance. Lastly, if we look at the gold Srdf Metro service plan, you can see that the copy location defaults to local and remote.
This will allow you to take a copy on either of the synchronous legs. You pick like with a bronze plan. Plus, you get that Dr leg, both the local and the remote copies will both be at the same point in time. Here, we've chosen the 691 leg of the Synchronous Metro replication to take a copy on. And we've also chosen the 859 Dr leg for the SDF asynchronous copy to be taken on. So now that that gold service plan has been configured, we can run it. So we just check the box next to the gold Sr DF Metro service plan and click run. This will run the service plan against the two Power Store Metro volumes. The extent four volumes that are presented to the Linux host that I showed earlier. So here you can see the plant is running now that the service plan has completed running.
You can see that we've created both a local and remote copy and now we can close this out. And if we navigate to copies file systems and click on to our 181 host and then click into one of the disks. You can see now that we have both a local and a remote dr leg copy. If we pull up the host, you can see here, we have disc one and disc two that are already mounted. Those are our production lines. So now if we select the local copy that was taken and hit mount, choose the local copy, also mild duct disc two in addition to disc one mount to our 181 host, and we'll take the default mount path which is a sync mounts and then click finish and we'll let this run. Now, we can see the mount has completed if we close this window and then look back at our host.
You can see we now and have an AB sync mounts directory. And if we look in here, we can see that both disc one and disc two are now mounted. This demo has shown how easy it is to take copies with appsync in an SDF Metro environment. Please visit the links below to download a free 90 day trial of appsync or to learn more about the product through documentation videos, et cetera. You can also learn more about S RDF Metro by reviewing the numerous white papers and documentation available on our website.
Thank you for viewing today's video.
