Welcome to this demonstration of Dell EMC, Appsync and Power Store.
There are numerous ways they can integrate and today we will showcase a few of them. Appsync is a software that enables integrated copy data management with Dell EMC primary storage systems. Appsync simplifies and automates the process of generating and consuming copies of production data. It is able to orchestrate all of the activities required from copy creation and validation through mounting at the target host and launching or recovering the application. This video will show how appsync integrates with Dell E MC Power Store, vmware and Microsoft's sequel. First, we will go over the power store X configuration. Next the production SQL server configuration.
Then we will discuss the absent configuration and we'll run a power store remote silver service plan. Lastly, we will show how the remote power store T configuration looks and how to unmount a copy. If we navigate to the power store X Gooey, we see the dashboard. By default. If we click on the storage button in volume groups, you can see that we have a sequel volume group created that has 10 gigabytes of provision storage as well as two volumes or members created within it. We click into the sequel volume group and look at the members. You can see that we have two lungs associated with this volume group SQL data and SQL logs. They're each five gigabytes and they each have one host mapping. If we click on the host mappings, you can see that this volume is mapped to a windows host via the I Scuzzy Protocol. We go back to the volumes and click on the other volume mapping.
You can see that it is also mapped to the same windows host via scuzzy. If we navigate back to volume groups and click within it and look at the protection, click on the replication tab, you will notice that we have replication configured between two power store arrays. The one on the left is an X and the one on the right is A T and currently this volume group is involved in the replication. Since this is a power store X, we have embedded ESX hypervisors running within the appliance. If we click on compute and VCENTER server connection and then launch Vsphere and launch Vsphere client were directly brought into the vmware vsphere client. Here, you can see that we have two ESX I servers running as well as a appsync windows VM running and a sequel server for absynth copy management.
Additionally, there are two power store VMS running the power store software running virtual machines or VMS within the power store is known as apps on functionality. If we navigate back to the power store X Gooey and click on compute again and look at the virtual machines tab, you can see here we also show the virtual machines running within the power store. X. Next, we will navigate to the Microsoft sequel server host that will be used for copy management with appsync. Here is the Microsoft Sequel server and you can see that there is a, a sync power store DB one database created within Microsoft SQL server. And this is comprised of the E and F drives coming from the power store appliance. The drive has the database data files and the FRI has the database log files. We also have another instance of SQL running on this host called appsync instance where we will mount a copy taken with appsync to this same server in a different instance.
Next, we will navigate to the A sin gooey. Here we start out on the dashboard if we navigate to copy management and then select view service plan and select our application, which in this case is Microsoft SQL server. We see that we have all of the service plans that come out of the box, bronze, silver and gold. And we also have a couple of service plans created for Power Store and sequel. So we have a bronze one and a silver one. Today, we will be focusing on the silver plan, which is a remote service plan meaning that we can take a copy from one power store appliance and replicate it over to the secondary remote power store appliance. So in this case, we're going from a power store X to a power store T as we showed in the power store Gooey. If we edit the service plan, you can see that we gave it a name, Power Store Silver sequel service plan.
The service plan is enabled, it's set up to do remote copies. Since this is a remote service plan, we've also configured it to mount the copy. Once we take the sequel copy, we'll actually mount it to another instance and we're keeping seven copies we go to next. We'll also see that the SQL server backup type is set to fall and our copy priority is set to snapshot on the mount settings. We've set appsync to do a mount and recover. So in this case, we're going to take the copy of the SQL server database and then we're going to mount it up to the appsync instance that I showed earlier in this video and then we're going to recover it and we're gonna append a different suffix called appsync in front of the database name. And then if we go next, we don't have any scripts configured for this service plan.
So we'll go on to the next part of the wizard. And the last step, we're just gonna say that we want to run the service plan on demand and not set it to be on a regular schedule. If we wanted it to run at a certain time every day, you would just select schedule and pick your frequency. So we'll just leave it on demand. Click next and finish. You can also see that we've subscribed the service plan to our AB sync power store database. So when we run the service plan, it's going to run against this database. So the next step is to run the service plan. So I'll click run and then here we'll go through all of the different statuses of the service plan running. You can expand out the details and see all the different steps that we're going to go through. So now we can see that the recovery of the copy completed successfully. We scroll down here, we see that the running database recovery, unmounted application finished.
So now we can close out and if we look at the copies in appsync, go under Microsoft sequel server, click on our sequel incense and our specific AB sync power store DB one, we can see now that we have a copy that is mounted. So now if we go over to our SQL server, now on the instance that we mounted to, we need to refresh. And if we expand the databases, we can see that appsync automatically mounted the database copy to this other instance that happens to be on the same host, we still have our original production volumes. And if we look at absent mos directory, we can see that we have the, the mounted copy here. If we now navigate to the remote power store T Gooey and go into host groups and select our SQL server and click on map to volumes.
You will see that appsync has taken the snap and created a thin clone from it in order to map and mount the lungs and file systems through to the SQL server allowing us to mount to the other sequel instance as shown earlier. Now, if we want to come back to a sync and unmount the copy, simply select the copy and hit on mount and hit. Ok. And we'll see the unmounted copy status. We can expand out the details. Now, the unmount of the copy has completed successfully, we can minimize the window.
And now if we go back to our SQL host, you can see that the mount point has been removed. And if we refresh our mount instance, you can see that the database is no longer mounted. So this completes the service plan run and the mounting and un mounting automatically through a sync.
Thanks very much for watching today's demonstration of Dell EMC appsync and power store integration. Please visit the links below for more technical documentation and videos.
