Cross-vCenter vMotion with SRM and Pure Storage ActiveCluster

Video Statistics and Information

Video
Captions Word Cloud
Reddit Comments
Captions
hi my name is Cody hos Furman and I'm the technical director here at pure sword for VMware Solutions today I'm going to be demonstrating a technical preview of integration with V Center set Recovery Manager and purity active cluster our active active replication so here I have a set Recovery Manager environment and in the second look at my virtual machines so I have two data stores each one of these data stores has eight virtual machines running on so you can see the second one has an additional eight in my other V Center these data stores are also presented the same data source but there's no virtual machines currently running on these data stores in my other V Center if we take a look at my flasher right and go to storage and then pods click and look at my active cluster pod called SRM this is essentially an asynchronous replication consistency group both of those data stores those volumes are in that pod and on my first array you can see they are indeed connected to my cluster and on my second array where these volumes also exist where this pod is stretched to we can see those volumes are indeed here and they are connected to the cluster on my other V Center so now let's actually take a look at the VMware configuration so the next thing we want to do is look at our policies so our Recovery Manager uses vm storage policies to control failover of active active replication you can see all my V ends are added to this particular storage policy and these are based on tags you can tag the data stores you want to include together now in site Recovery Manager let's set it up so first let's take a look at our array managers in my array manager for my flasher right you can see if a variety of replicated volumes here and indeed supports stretch storage and both of my VMware data stores are recognized as stretched storage volumes so let's create a protection group with stretch storage protection groups are based on storage profiles and so it allows you to include data stores that have a certain profile in a protection group so I'll choose storage policies I'll choose my storage policy that I showed before that all my VMs are assigned to if a data store has that policy and is total is said to be replicated by a test array it's a valid data store this will lay all VMs on these data stores are automatically added to this protection group furthermore you can see they are vMotion eligible I'll talk a little bit more about what that means in a second now let's create a recovery plan a recovery plan is what you actually run to say I want to fail over these virtual machines allowing you to fail over one or more Site Recovery Manager protection groups so I'll choose my recovery site and then I'll choose my protection group and here's my storage policy protection group I'll confirm the remaining details and click finish this creates my recovery plan so it's take a deeper look at the configuration of my recovery plan under related objects we can take a look at the virtual machines in this recovery plan let's take a look at the first one under configure recovery there's a variety of options and the one thing you can importantly note here is it allows you to choose I want to fail this over using a cross vCenter vMotion or not the default is yes I do if it's available and so I'll keep it that way so now let's actually run a failover so we'll kick off the recovery process I understand what's going to happen and I'll keep playing migration and enable vmotion checked if this is checked if it can vmotion a VM that has that enabled as I showed before it will vmotion the VM and so this is going to start this process once we get to the live migration it'll start be motioning the virtual machines this actually moves the VM from one V Center to the other V Center non-disruptive Li if we take a look at my hosts in clusters view we can see the VMS or moving over there it creates kind of a shadow VM on the other side move the state of that VM over and it's automatically running this allows you to move the VMS non-disruptive lee using set Recovery Manager orchestrating the cross V Center of emotions it's also fairly speeds up the recovery process if it cannot do AV motion what's going to happen instead is it's going to just register and power on the VMS on the other site since it's a plan migration and V motion is enabled we can do this so the V motioning of all my protected virtual machines is complete and the recovery process will finish itself if there are certain VMs it couldn't be v motioned or there's other types of storage that needs to be failed over this so this a recovery plan will complete that now now since all the other VMs have been failed over via V motion there's nothing to power on or really complete other than finishing up some of the related kind of metadata tasks that SRM needs to do to finish the recovery plan the process is now pretty much complete and now we can run a Reaper TechEd and this will finish up the process allowing you to fail back if needed so this kind of swaps the protection groups and the recovery plans and so I start Recovery Manager allowing you to then take those and fail them back to the other V Center so this has been a technical preview demonstration of using purity active cluster on the flash ray with V Center Site Recovery Manager thank you you
Info
Channel: Cody Hosterman
Views: 1,524
Rating: 5 out of 5
Keywords: VMware, vCenter, SRM, ActiveCluster, Pure Storage, Site Recovery Manager, vMotion
Id: 5KfAkDIILTI
Channel Id: undefined
Length: 6min 24sec (384 seconds)
Published: Wed Mar 28 2018
Related Videos
Note
Please note that this website is currently a work in progress! Lots of interesting data and statistics to come.