hello and welcome to the second part of the flexpod hybrid cloud data center build out the first video is focused on the infrastructure build out including aws and netapp cloud manager in this video we will focus on the power of automation provided by cisco inter site to build our custom workflows through which we can set up the necessary data replication relationships between the flexpod on-premises environment and cloud volumes on tap in awsand while we go through that we will also look at the data integrity that is being maintained when the data replication happens over the wire from the on-premises environment to the public cloud let's begin with cisco intersight so we'll pick a workflow that's going to create a volume and also export it so all these operations are going to happen uh on the ontap system that is part of our flexpod environment on clicking execute into site throws up a wizard which collects some more additional details about the user input parameters that are required like the name of the volumethe mount path for the volume that will be created and also the volume size with this the workflow is now triggered and the execution is in process the execution is completed successfully so we should now be able to see our volume being created in theontab storage system that is part of our on-premises flexpod environment and there is the volume you can see that the volume also has an export policy and the volume is not protected by a snap mirror at this point so it's an unpredicted volume let us now mount this volume to a vm that is running on our flex pod first we are going to create a directory and mount the volume using an nfs lift ip and the mount path to this directory that we have just createdwe shall also verify the mount as we can see here the volume has been mounted using the nfs lift ip to the directory that we have created the available size is 95 gb we can confirm the same from system managerin this demonstration we will use a sample data set of size 2gb that will be replicated to the cloud before we start the replication let's generate a checksum of this data set this checksum will be used at a later stage to verify the integrity of data transferback in cisco into site we shall use another workflow to set up the snapper relationship between flexpod and cloud volumes ontap so this is the workflow and we're going to execute it into site is going to present us with another form that we will be filling out with our user input parameters or environment specific inputsthat include the aws specific details like the region subnet vpc etc and also details regarding our on-premises volume from where the data set is going to be replicated over to cvothe name of the svm in flexpod and then the details of the destination which is going to be cloud volumes on tap in aws so we will provide the name of the destination volume that needs to be created and then the replication intervaland also the name of the cvo cluster and finally we can execute this workflow it takes a couple of minutes for the workflow to finish execution once completed successfully we can head over to cloud manager and the timeline view for a detailed update on the replication statuswhen the snap mirror has been initiated successfully we can head over to the replication tab and view the replication relationship it's currently uninitialized we can get into information for additional details a visual representation of the replication relationship is available in the canvas view and the data transfer is right now in progress once the data transfer has been successfully completed we shall stop the source storage virtual machine that is the svm that is in flexpod to simulate a disaster the svm is now stopped we'll head back to cloud manager and navigate to the on premises on tap working environment you can see that cloud manager loses visibility to all the volumes that were running out of the storage virtual machine that we just stopped so at this point we break the replication relationship and promote the destination cloud volumes on tap volumeas production so the relationship has now been broken we go back to timeline to ensure that the replication break is successful we now navigate to the cvo working environment we can see that's our destination volume with 2.3 gig of data roughly that's been replicatedwe can edit the volume and make it accessibleusing a custom export policy and now this volume can be mounted to an ec2 instance so we can go and get a ready to use mount command let's copy thatgo to aws connect to an ec2 instancewe'll create a directory within the within this ec2 instance and use the mount command that we just copiedand updated with the directory that we just created and the volume is now mounted so we'll quickly verify the mount that is our mount and you can see that the use size is roughly 2.4 gig and when we go inside we can see the sample data set now to verify the integrity of data transfer we'll run the checksum at the ec2 instance the checksum is availableandon comparing both checksums from cloud volumes ontap and from flexpod we can see that both the checksums are matching indicating that the data transfer has been successful with absolute integrity to summarize we started off by replicating a sample data set from the on-premises flexbot environment to cloud volumes on tap by leveraging the cisco inter-site workflows inter-site workflows inter-site workflows and once the data transfer was completed we broke the relationship of the snap mirror and promoted the destination volume in cloud volumes on tap to production and it was a seamless operation with just a click of a button and lastly we also verified the integrity of data transfer by running the checksums at both the source and destination and comparing each other we hope you enjoyed the content in this video and thank you for watching