WEBVTT 00:00:00.000 --> 00:00:06.700 Welcome back to vSphere 8 in the real world. Now we're going to discuss storage policies. 00:00:06.700 --> 00:00:16.459 So storage policy-based management is just a way for us to use our storage policies to align our vSphere environment with all the other aspects of our vSphere environment. 00:00:16.459 --> 00:00:25.559 For example, we have network I.O. control so we can make sure that certain virtual machines have the necessary bandwidth for that application to perform correctly, 00:00:25.559 --> 00:00:31.760 that lower-priority virtual machines don't overwhelm the more important higher-priority virtual machines. 00:00:31.760 --> 00:00:40.160 We have ways of making sure that our storage I.O. control, which we don't really need that for storage policy-based management, 00:00:40.160 --> 00:00:47.360 but we have storage I.O. control to make sure that we can give VMs the right amount of I.O. to storage. 00:00:47.360 --> 00:01:01.160 We also have things like resource groups, right? We can use our resource groups or resource pools to allocate a certain amount of resource, CPU, and memory to VMs to make sure they have all the CPU they need, 00:01:01.160 --> 00:01:05.360 they have all the memory they need, they have a certain number of shares, and they have reservations. 00:01:05.360 --> 00:01:08.919 And we have all these tools to ensure our virtual machines' performance. 00:01:08.919 --> 00:01:15.959 Well, this will help us to ensure our virtual machines' performance from the storage side as well as other things besides performance. 00:01:15.959 --> 00:01:21.720 We can also ensure things like recoverability. We can configure – say we want things like replication. 00:01:21.720 --> 00:01:28.360 We can also ensure security because we can say we need encryption. We can say we need deduplication. 00:01:28.360 --> 00:01:37.760 So we can create policies that express the needs of this VM, and then when we assign that VM to a policy and then we want to put on a certain piece of storage, 00:01:37.760 --> 00:01:41.760 we'll say, nope, that storage doesn't have the things that you said you needed. 00:01:41.760 --> 00:01:50.160 You said you needed replication, and that storage array you're trying to put it on and that data store doesn't have replication configured, so you can't put that VM there. 00:01:50.160 --> 00:01:54.559 So it can help us to ensure that we are meeting the needs of our virtual environment. 00:01:54.559 --> 00:02:02.160 And maybe it's our performance needs, maybe it's our security needs, maybe it's with deduplication something like our efficiency needs. 00:02:02.160 --> 00:02:11.160 So storage policy-based management will just help us to automate that to make sure that people aren't like, well, yeah, this is supposed to be encrypted. 00:02:11.160 --> 00:02:16.559 I'm going to put it here for a minute while I do something so I can do some maintenance over here and then forget to put it back, 00:02:16.559 --> 00:02:23.759 and this very critical, highly sensitive information isn't encrypted on your storage or something like that, right? 00:02:23.960 --> 00:02:32.160 So it helps us to align all the different needs from our businesses, our security needs and performance needs and budgetary needs, right? 00:02:32.160 --> 00:02:34.759 Maybe we don't want – it says it cannot be on Flash. 00:02:34.759 --> 00:02:41.759 These VMs are really not that big a deal and their performance is really not that important, and I do not want them going to Flash. 00:02:41.759 --> 00:02:47.759 I only want them on an inexpensive spinning disk, right, so I can help my budgetary needs line up. 00:02:47.759 --> 00:02:50.960 I don't want to put those VMs on Flash, fill up that Flash array. 00:02:50.960 --> 00:02:57.960 I'm like, oh, I've got to buy more storage, I need more Flash, I've got to spend big dollars again when I have less expensive storage available, 00:02:57.960 --> 00:03:00.960 or I could buy more less expensive storage if that's what's getting full. 00:03:00.960 --> 00:03:01.960 All right. 00:03:01.960 --> 00:03:05.960 I have a unified control panel so I can go into vCenter and I can manage all these things through vCenter. 00:03:05.960 --> 00:03:12.960 I can go and manage all my policies the same way I manage my networking, the same way I manage creating my data stores and creating VMs. 00:03:12.960 --> 00:03:15.960 That's also how I manage my storage policy-based management. 00:03:16.960 --> 00:03:23.960 I don't have to be a SAN admin and go in there to the SAN and make sure that these things are happening, right? 00:03:23.960 --> 00:03:25.960 The SAN side will need to be set up, of course. 00:03:25.960 --> 00:03:29.960 I'm not trying to say it won't have to be anything, but my SAN admin can give me my storage 00:03:29.960 --> 00:03:33.960 and I can make sure things are assigned to the right place through my policies. 00:03:33.960 --> 00:03:37.960 And the SAN will tell vCenter whether or not those things are on that data store. 00:03:37.960 --> 00:03:40.960 It will know if it's true or not, okay? 00:03:40.960 --> 00:03:45.960 Make sure I can build policies, define capabilities of the storage array, all right? 00:03:45.960 --> 00:03:48.960 So we'll show you how to do that in our demo. 00:03:48.960 --> 00:03:49.960 And interpret your requirements. 00:03:49.960 --> 00:03:53.960 So basically you've gone in, you tell it what it needs, and then when you go to put a VM somewhere, it says, 00:03:53.960 --> 00:03:57.960 well, here's the things you said you need and here are the things the SAN says this can do. 00:03:57.960 --> 00:03:59.960 It lines up, you're good. 00:03:59.960 --> 00:04:03.960 Go ahead. 00:04:03.960 --> 00:04:05.960 So some storage policy components. 00:04:05.960 --> 00:04:09.960 Policy can include, for example, we can define services that are going to be available to the VM, right? 00:04:09.960 --> 00:04:12.960 We can define, you know, we want replication available. 00:04:12.960 --> 00:04:14.960 We want things to be encrypted. 00:04:14.960 --> 00:04:16.959 We can define all these different components in there, right? 00:04:16.959 --> 00:04:20.959 We can say what are the future needs of the VM going to be? 00:04:20.959 --> 00:04:21.959 Are we going to end up needing more space? 00:04:21.959 --> 00:04:24.959 Are we going to end up needing more I.O. and things like that? 00:04:24.959 --> 00:04:26.959 And then we can associate these things to a policy. 00:04:26.959 --> 00:04:30.959 So some of the different things we can define in that policy, we can define compression. 00:04:30.959 --> 00:04:33.959 We can say caching, encryption, replication. 00:04:33.959 --> 00:04:38.959 So compression basically is like going in kind of like a way of zipping the different blocks. 00:04:38.959 --> 00:04:41.959 It's not exactly that, obviously, but a way of, you know, 00:04:41.959 --> 00:04:47.959 basically reducing the amount of space that is used by a block so we can get more data into a block. 00:04:47.959 --> 00:04:51.959 So if we have a file that normally would take up, without compression, eight blocks, 00:04:51.959 --> 00:04:55.959 maybe with compression it only takes up six blocks so we can save space. 00:04:55.959 --> 00:04:59.959 Of course, that means there's a lot of overhead with using that when you're writing it, 00:04:59.959 --> 00:05:02.959 so hopefully you're probably only doing that with maybe like archive data. 00:05:02.959 --> 00:05:05.959 You're not going to be doing that with data that is accessed often. 00:05:05.959 --> 00:05:10.959 And so your policy can say, this machine over here is, you know, an older machine. 00:05:10.959 --> 00:05:12.959 We don't access that data hardly ever. 00:05:12.959 --> 00:05:15.959 It takes up a lot of space for data that's hardly ever used. 00:05:15.959 --> 00:05:16.959 Let's compress that. 00:05:16.959 --> 00:05:20.959 But this other VM, even though it's equally large, it uses the same amount of space, 00:05:20.959 --> 00:05:24.959 this is data that's used every day by a lot of people. 00:05:24.959 --> 00:05:27.959 We need it to be fast, and compression would slow that down. 00:05:27.959 --> 00:05:29.959 We need it to be readily available, 00:05:29.959 --> 00:05:34.959 and we don't want a lot of overhead on the system to try and compress and decompress that data. 00:05:34.959 --> 00:05:36.959 So we're not going to compress this often used data. 00:05:36.959 --> 00:05:39.959 We're going to compress this rarely used data. 00:05:39.959 --> 00:05:42.959 Kind of think about if you're familiar with like AWS 00:05:42.959 --> 00:05:46.959 and they have those different levels of storage and one's Glacier where it takes, you know, 00:05:46.959 --> 00:05:48.959 days to get your data back from them. 00:05:48.959 --> 00:05:51.959 So that's what they would put over there. 00:05:51.959 --> 00:05:55.959 That data you put over there is what you're going to rarely, rarely ever use. 00:05:55.959 --> 00:05:57.959 So compression is going to be for less used data 00:05:57.959 --> 00:06:00.959 and you're not going to want to compress more often used data. 00:06:00.959 --> 00:06:02.959 Caching, if you want to enable caching, 00:06:02.959 --> 00:06:06.959 we want to help make our slower disks a little faster, 00:06:06.959 --> 00:06:09.959 our spinning disks a little faster by putting cache in front of them, 00:06:09.959 --> 00:06:12.959 and that could help improve their performance. 00:06:12.959 --> 00:06:14.959 But, again, if this is a machine that I don't care a lot about 00:06:14.959 --> 00:06:18.959 and I'm not really worried about performance that much on this one, 00:06:18.959 --> 00:06:21.959 a small number of users use it, not high priority. 00:06:21.959 --> 00:06:26.959 So we're not going to waste the money on giving them that cache for those VMs. 00:06:26.959 --> 00:06:29.959 So we won't put that VM on a data store cache. 00:06:29.959 --> 00:06:33.959 I will put these, you know, higher priority, much more often used, 00:06:33.959 --> 00:06:37.959 more critical to the business, and we need really great performance, 00:06:37.959 --> 00:06:42.959 that will go on a LUN or data store that has caching. 00:06:42.959 --> 00:06:46.959 Encryption, if we have financial data, if we have HR data, 00:06:46.959 --> 00:06:48.959 some companies have a policy that we encrypt everything, 00:06:48.959 --> 00:06:49.959 and that's a great policy. 00:06:49.959 --> 00:06:50.959 That's a great policy. 00:06:50.959 --> 00:06:53.959 If you have the resources to do that, that's great. 00:06:53.959 --> 00:06:55.959 But maybe we don't have those resources. 00:06:55.959 --> 00:06:59.959 And encryption, you know, is an additional overhead for us, 00:06:59.959 --> 00:07:04.959 and we don't want to necessarily worry about, you know, 00:07:04.959 --> 00:07:08.959 spending that overhead on data that is just not that critical 00:07:08.959 --> 00:07:10.959 and it's not that sensitive. 00:07:10.959 --> 00:07:11.959 It's not HR related. 00:07:11.959 --> 00:07:12.959 It's not finance related. 00:07:12.959 --> 00:07:17.959 It's not, you know, business secrets to help my business run. 00:07:17.959 --> 00:07:20.959 So maybe we'll put that on unencrypted storage, right, 00:07:21.959 --> 00:07:23.959 and not worry about the processor overhead that we have 00:07:23.959 --> 00:07:24.959 encrypting that data. 00:07:24.959 --> 00:07:25.959 Okay. 00:07:25.959 --> 00:07:27.959 Replication, what are we going to replicate? 00:07:27.959 --> 00:07:30.959 Maybe there's certain data we want to replicate once every 24 hours, 00:07:30.959 --> 00:07:32.959 certain data we replicate once a week. 00:07:32.959 --> 00:07:35.959 Some data we're going to replicate every five minutes. 00:07:35.959 --> 00:07:38.959 We're going to replicate this constantly and keep it always up to date 00:07:38.959 --> 00:07:41.959 because this is a mission critical business application, 00:07:41.959 --> 00:07:43.959 and if there's a failure somewhere, 00:07:43.959 --> 00:07:46.959 I need this back up and going and to be current within the last five 00:07:46.959 --> 00:07:49.959 minutes, and that's what I have told the higher ups that we are going 00:07:49.959 --> 00:07:52.959 to deliver, that this application will be within five minutes of 00:07:52.959 --> 00:07:53.959 whenever it failed. 00:07:53.959 --> 00:07:55.959 You won't lose more than five minutes worth of data. 00:07:55.959 --> 00:07:58.959 So I can set, you know, replication targets like that, 00:07:58.959 --> 00:07:59.959 and I can, again, 00:07:59.959 --> 00:08:03.959 say this application needs this five-minute replication storage policy, 00:08:03.959 --> 00:08:06.959 and if I try moving it somewhere that doesn't have five-minute 00:08:06.959 --> 00:08:08.959 replication, it has one-day replication, 00:08:08.959 --> 00:08:10.959 it will fail and not go over there. 00:08:10.959 --> 00:08:11.959 All right. 00:08:11.959 --> 00:08:14.959 And then we can also enable, you know, storage I.O. control. 00:08:14.959 --> 00:08:16.959 So some best practices. 00:08:16.959 --> 00:08:18.959 Components can only have one rule set. 00:08:18.959 --> 00:08:23.959 What they're saying there is in a rule set, we can add something. 00:08:23.959 --> 00:08:24.959 In the policy, 00:08:24.959 --> 00:08:28.959 we can add a rule that says what storage array that I want this VM on. 00:08:28.959 --> 00:08:32.960 I want this on my really high-end enterprise storage array that has all 00:08:32.960 --> 00:08:34.960 these bells and whistles so I can do all these things like compression 00:08:34.960 --> 00:08:35.960 encryption. 00:08:35.960 --> 00:08:39.960 And I've tried moving it to an older storage array that isn't in that 00:08:39.960 --> 00:08:41.960 policy, then it will fail. 00:08:41.960 --> 00:08:44.960 Well, if I try to add storage array twice and I put both of them there, 00:08:44.960 --> 00:08:46.960 then which one do I need, right? 00:08:46.960 --> 00:08:47.960 So I can only add that once. 00:08:47.960 --> 00:08:49.960 Things like that. 00:08:49.960 --> 00:08:52.960 If a component is referenced by a VM, 00:08:52.960 --> 00:08:54.960 if I have a policy and it's referenced by a VM, 00:08:54.960 --> 00:08:56.960 I can't delete that until I remove it from that VM. 00:08:56.960 --> 00:08:58.960 That's what they're trying to say there. 00:08:58.960 --> 00:09:01.960 So one component for, you know, for a category, 00:09:01.960 --> 00:09:04.960 when you're adding things to a policy, again, 00:09:04.960 --> 00:09:06.960 we only want to add certain types of things once. 00:09:06.960 --> 00:09:12.960 So to create this, we're going to go into our vSphere client. 00:09:12.960 --> 00:09:14.960 We can go into our storage policies. 00:09:14.960 --> 00:09:16.960 We're going to say we want to create a new, 00:09:16.960 --> 00:09:18.960 hit the create button to create a new policy. 00:09:18.960 --> 00:09:20.960 We're going to give it a name, right? 00:09:20.960 --> 00:09:22.960 And then we're going to go ahead and say next. 00:09:22.960 --> 00:09:24.960 We're going to set what category we're going to put this in. 00:09:24.960 --> 00:09:26.960 So, for example, it's going to be like our pure storage. 00:09:26.960 --> 00:09:28.960 I keep saying pure storage, that's what we're going to do in our demo. 00:09:28.960 --> 00:09:30.960 Pure storage, you know, 00:09:30.960 --> 00:09:33.960 storage policy for our pure storage storage arrays. 00:09:33.960 --> 00:09:37.960 And then we can start going in and adding additional services, right? 00:09:37.960 --> 00:09:43.960 So what storage we're going to provide the service and what features of 00:09:43.960 --> 00:09:44.960 that do I want? 00:09:44.960 --> 00:09:48.960 I want replication and I want encryption or something like that. 00:09:48.960 --> 00:09:50.960 You can specify those things. 00:09:50.960 --> 00:09:53.960 And you can also say for replicating, what do you want replicated to? 00:09:53.960 --> 00:09:55.960 I want it replicated and I want it replicated to over there. 00:09:55.960 --> 00:09:56.960 I want the target to be this. 00:09:56.960 --> 00:09:59.960 I can say replication and not also add target, 00:09:59.960 --> 00:10:02.960 or I can add target and say I want it replicated 00:10:02.960 --> 00:10:04.960 and I want it replicated to this other SAM. 00:10:04.960 --> 00:10:09.960 All right. 00:10:09.960 --> 00:10:12.960 So let's go ahead and go in and do a quick demo. 00:10:12.960 --> 00:10:13.960 In our demo environment, 00:10:13.960 --> 00:10:16.960 I'll show you how to actually create a storage policy 00:10:16.960 --> 00:10:18.960 and apply it to a virtual machine. 00:10:18.960 --> 00:10:23.960 So here we are in VMware's hands-on lab environment. 00:10:23.960 --> 00:10:25.960 So you can get to here by going to hol.vmware.com. 00:10:25.960 --> 00:10:27.960 So you also, yourself, from home, 00:10:27.960 --> 00:10:30.960 can do the same exact demo all on your own. 00:10:30.960 --> 00:10:35.960 Now I'm jumping to Section 4, which talks about the storage policies. 00:10:35.960 --> 00:10:39.960 But there is actually, it has, I think, five sections. 00:10:39.960 --> 00:10:41.960 So you can do one through three yourself, 00:10:41.960 --> 00:10:43.960 and that will have you create VVols and some other things 00:10:43.960 --> 00:10:45.960 and also do replication policies. 00:10:45.960 --> 00:10:47.960 So a lot of great stuff on here. 00:10:47.960 --> 00:10:55.960 The first thing it will want us to do is to log into the storage array. 00:10:55.960 --> 00:10:58.960 And right over here, it actually has all the step-by-step, you know, 00:10:58.960 --> 00:10:59.960 actions you're going to take. 00:10:59.960 --> 00:11:03.960 So it's saying to log into storage array A, right, 00:11:03.960 --> 00:11:05.960 tells you what the, you know, that's what the screen is going to look like. 00:11:05.960 --> 00:11:07.960 It will give you the name and password for it. 00:11:07.960 --> 00:11:08.960 And then once you're in, 00:11:08.960 --> 00:11:10.960 it's going to show you what it wants you to look at. 00:11:10.960 --> 00:11:13.960 So, for example, it wants me to go to this protection group. 00:11:13.960 --> 00:11:19.960 And here I have, I'm sorry, not protection group, but protection. 00:11:19.960 --> 00:11:21.960 And here I see what array I'm connected to. 00:11:21.960 --> 00:11:22.960 I'm in array A. 00:11:22.960 --> 00:11:26.960 If I go down here, I see I'm in array A. 00:11:26.960 --> 00:11:29.960 And I'm connected to array B. 00:11:29.960 --> 00:11:32.960 So if I click on this little icon here, 00:11:32.960 --> 00:11:37.960 it will show me that I'm connected to array B, right. 00:11:37.960 --> 00:11:40.960 This is the controller for array A's controller address. 00:11:40.960 --> 00:11:44.960 And then this is array B's controller address, right. 00:11:44.960 --> 00:11:46.960 And I see that the connection is up. 00:11:46.960 --> 00:11:49.960 If I go over to array B and log in. 00:11:59.960 --> 00:12:01.960 Again, I go to protection. 00:12:01.960 --> 00:12:04.960 I'll show that array B, which is the one we're looking at, 00:12:04.960 --> 00:12:06.960 is connected to array A. 00:12:06.960 --> 00:12:09.960 And, again, I can look at this little map icon. 00:12:09.960 --> 00:12:14.960 And it will show me that here's the address for array B 00:12:14.960 --> 00:12:17.960 and the address for array A. 00:12:17.960 --> 00:12:18.960 And, again, that connection is up. 00:12:18.960 --> 00:12:20.960 So I have a connection from A to B. 00:12:20.960 --> 00:12:23.960 They both see each other and they see each other's B up. 00:12:23.960 --> 00:12:24.960 All right. 00:12:24.960 --> 00:12:28.960 So next what we're going to do is go into vSphere. 00:12:28.960 --> 00:12:33.960 And from here, we're going to go to policies and profiles. 00:12:34.960 --> 00:12:37.960 And we're actually going to create a storage policy. 00:12:37.960 --> 00:12:39.960 Now, I do want to jump to that part in the labs 00:12:39.960 --> 00:12:41.960 because I want to make sure I get all the names correct, 00:12:41.960 --> 00:12:44.960 all the spelling and things like that because it does matter. 00:12:49.960 --> 00:12:51.960 So here I'm going to say create. 00:12:53.960 --> 00:12:57.960 And the first thing I want to do is to name that policy. 00:12:57.960 --> 00:13:00.960 So one really cool thing is we can type this in 00:13:00.960 --> 00:13:02.960 or we can just copy it. 00:13:05.960 --> 00:13:07.960 Wipe that out of there. 00:13:07.960 --> 00:13:10.960 And right up here in the HOL toolbar, 00:13:10.960 --> 00:13:13.960 I can paste it in there and say send it. 00:13:13.960 --> 00:13:17.960 And I just now made sure I got it typed in exactly correct. 00:13:17.960 --> 00:13:19.960 I'm going to say next. 00:13:19.960 --> 00:13:22.960 Now, it's going to want me to enable this rule for pure storage. 00:13:22.960 --> 00:13:24.960 So I'm going to say next. 00:13:24.960 --> 00:13:27.960 Next thing I'm going to do is I'm going to add a rule. 00:13:28.960 --> 00:13:32.960 And I'm going to say do I want this to be a pure storage FlashArray? 00:13:32.960 --> 00:13:34.960 I'm going to say yes. 00:13:34.960 --> 00:13:36.960 Now, I'm just going to catch up real quick here 00:13:36.960 --> 00:13:38.960 so I don't get too far ahead. 00:13:42.960 --> 00:13:45.960 So I went to placement, right, add a rule, pure storage FlashArray. 00:13:45.960 --> 00:13:47.960 That's the step I just did. 00:13:48.960 --> 00:13:49.960 So yes. 00:13:49.960 --> 00:13:53.960 And now I'm going to add another rule and FlashArray group. 00:13:54.960 --> 00:14:00.960 And here what I'm going to do is it says make sure you type this in 00:14:00.960 --> 00:14:04.960 and it needs to be exactly like this and it is case sensitive. 00:14:04.960 --> 00:14:16.960 So let's say I come over here and I'm going to say pure Flash. 00:14:16.960 --> 00:14:20.960 And I'm going to forget the word array and just say A, right. 00:14:20.960 --> 00:14:21.960 So I'm not going to copy and paste it in. 00:14:21.960 --> 00:14:25.960 I'm going to just type it in there and I accidentally typed it in wrong. 00:14:25.960 --> 00:14:27.960 So I got my FlashArray group. 00:14:27.960 --> 00:14:29.960 Okay, that's great. 00:14:29.960 --> 00:14:31.960 I think it's correct, right. 00:14:31.960 --> 00:14:34.960 And I'm going to go ahead and go to replication. 00:14:34.960 --> 00:14:36.960 I'm going to say custom. 00:14:36.960 --> 00:14:39.960 My provider is pure storage. 00:14:39.960 --> 00:14:41.960 Add a rule. 00:14:41.960 --> 00:14:47.960 And I want to say target, right. 00:14:48.960 --> 00:14:50.960 Oh, I'm sorry. 00:14:50.960 --> 00:14:54.960 Replication capable is supposed to be the first one. 00:14:54.960 --> 00:14:56.960 There we go. 00:14:56.960 --> 00:14:58.960 That one. 00:14:58.960 --> 00:15:00.960 Then I'm going to say yes to this. 00:15:00.960 --> 00:15:06.960 And then the next thing it wants me to do is say target. 00:15:06.960 --> 00:15:10.960 So let's say target. 00:15:10.960 --> 00:15:12.960 And now it's going to add a new rule. 00:15:12.960 --> 00:15:16.960 So let's say target. 00:15:16.960 --> 00:15:21.960 And now it's going to ask me to send it to my storage array B. 00:15:21.960 --> 00:15:24.960 I'm going to go ahead and just do this one correctly. 00:15:24.960 --> 00:15:25.960 All right. 00:15:25.960 --> 00:15:29.960 So I said I want to replicate, right. 00:15:29.960 --> 00:15:31.960 I want this to go from storage array A. 00:15:31.960 --> 00:15:33.960 I want it to be placed on storage array A. 00:15:33.960 --> 00:15:36.960 And I want to make sure that storage array A is replicating to storage array B. 00:15:36.960 --> 00:15:40.960 But I accidentally mistyped the names for storage array A. 00:15:40.960 --> 00:15:43.960 I'm going to say next. 00:15:43.960 --> 00:15:46.960 And then from here it's going to tell me to just go next and next, right. 00:15:46.960 --> 00:15:50.960 And just verify everything's right. 00:15:50.960 --> 00:15:55.960 I missed the fact that I spelled the storage array A's name wrong. 00:15:55.960 --> 00:15:58.960 But I do see that I got everything else right, right. 00:15:58.960 --> 00:16:01.960 But this is wrong. 00:16:01.960 --> 00:16:02.960 And we know what's wrong. 00:16:02.960 --> 00:16:04.960 We'll come back and fix it after I show you what I'd like to show you. 00:16:04.960 --> 00:16:08.960 But let's just say, again, double-checking myself, I missed it here too. 00:16:09.960 --> 00:16:11.960 And we're going to say finish. 00:16:11.960 --> 00:16:16.960 Now what it wants me to do is go over to this vCenter. 00:16:16.960 --> 00:16:20.960 This is vCenter B versus the vCenter A that I'm currently in. 00:16:20.960 --> 00:16:25.960 And I'm going to go to policies and profiles. 00:16:25.960 --> 00:16:29.960 And I'm going to create. 00:16:29.960 --> 00:16:33.960 And I've got a name for this one. 00:16:33.960 --> 00:16:39.960 And what we're doing is we're basically setting up a policy that says if it's 00:16:39.960 --> 00:16:42.960 running on A, replicate it from A to B. 00:16:42.960 --> 00:16:46.960 And if it's running in vCenter B, replicate it from B back to A. 00:16:46.960 --> 00:16:48.960 I'm just creating that reverse policy there. 00:16:48.960 --> 00:16:52.960 So that way if there is a failure and it does fail over to B, 00:16:52.960 --> 00:16:57.960 the changes from B get replicated back to A automatically so that then I can 00:16:57.960 --> 00:16:59.960 do a fail back if I'd like. 00:16:59.960 --> 00:17:01.960 And all my data's been replicated. 00:17:02.960 --> 00:17:04.959 I'm just going to type this one in. 00:17:04.959 --> 00:17:05.959 There we go. 00:17:05.959 --> 00:17:06.959 Got it that time. 00:17:06.959 --> 00:17:08.959 For some reason it wasn't copying from there. 00:17:08.959 --> 00:17:09.959 I created that policy. 00:17:09.959 --> 00:17:13.959 This clip here is saying it wants me to do it from vCenter B. 00:17:13.959 --> 00:17:15.959 And I'm in vCenter B. 00:17:15.959 --> 00:17:22.959 So I'm going to say I want to do a peer storage array. 00:17:22.959 --> 00:17:25.959 And I'm going to add a rule. 00:17:25.959 --> 00:17:27.959 And I want to do a flash array. 00:17:27.959 --> 00:17:41.959 I'm going to say yes, right, for replication, custom, 00:17:41.959 --> 00:17:47.959 my provider's peer storage, replication capable, yes. 00:17:48.959 --> 00:17:55.959 And what is the target site? 00:17:55.959 --> 00:17:58.959 It works this time. 00:17:58.959 --> 00:18:00.959 If not, I'll start typing it in. 00:18:00.959 --> 00:18:04.959 Okay, that's how it works. 00:18:04.959 --> 00:18:05.959 Cool. 00:18:05.959 --> 00:18:06.959 All right. 00:18:06.959 --> 00:18:08.959 So we have those set there. 00:18:08.959 --> 00:18:10.959 Compatible there. 00:18:10.959 --> 00:18:11.959 All right. 00:18:11.959 --> 00:18:12.959 All right. 00:18:12.959 --> 00:18:17.959 So here I see that I did say I want the storage array to be flashed, 00:18:17.959 --> 00:18:19.959 but I forgot to put in the group. 00:18:19.959 --> 00:18:23.959 So I can just hit back, back, go back to here, 00:18:23.959 --> 00:18:28.959 say what do I want my array group to be. 00:18:28.959 --> 00:18:34.959 And I want it to be B because B is the primary one for this vCenter. 00:18:34.959 --> 00:18:39.959 So now if I go and look at this, yes, I want a flash array. 00:18:39.959 --> 00:18:44.959 I want my group to be B, and I want to replicate, yes, 00:18:44.959 --> 00:18:46.959 and I want to replicate to A. 00:18:46.959 --> 00:18:50.959 So I did the exact same thing in vCenter 2 that I did in vCenter 1, 00:18:50.959 --> 00:18:54.959 or I should say vCenter B that I did in vCenter A, except in reverse. 00:18:54.959 --> 00:18:56.959 So B is the primary. 00:18:56.959 --> 00:18:59.959 The replication target is A for vCenter B. 00:18:59.959 --> 00:19:03.959 For vCenter A, it was the primary was A and the failover was B. 00:19:03.959 --> 00:19:05.959 So I just set that all up. 00:19:05.959 --> 00:19:09.959 So now it's saying to go to A over here, back to A. 00:19:09.959 --> 00:19:12.959 What we're going to do now is we're going to set up replication. 00:19:12.959 --> 00:19:13.959 Okay. 00:19:13.959 --> 00:19:19.959 So back in Pure Storage A array, right, I'm going to go to protection, 00:19:19.959 --> 00:19:22.959 protection groups, all right, 00:19:22.959 --> 00:19:28.959 and we're going to look for that vFault 04 group, 00:19:29.959 --> 00:19:35.959 and we're going to go to targets, add, 00:19:35.959 --> 00:19:41.959 and I'm going to add B to A as replication, right, 00:19:41.959 --> 00:19:44.959 and I need to create a schedule next. 00:19:44.959 --> 00:19:50.959 So I created the replication target, right, added that, 00:19:50.959 --> 00:19:54.959 and I said I checked B and added it. 00:19:55.959 --> 00:20:00.959 So now under my replication schedule, I'm going to go to here, 00:20:00.959 --> 00:20:03.959 and I'm going to change how often it replicates. 00:20:03.959 --> 00:20:06.959 It's going to want me to replicate, I think, every five minutes. 00:20:06.959 --> 00:20:08.959 Just to make sure, though, replicate every five minutes. 00:20:08.959 --> 00:20:13.959 And how many do I want to retain? 00:20:13.959 --> 00:20:16.959 I want to retain 30 of these guys. 00:20:16.959 --> 00:20:19.959 I'm sorry. 00:20:19.959 --> 00:20:23.959 I want to retain all of these guys for 30 minutes. 00:20:23.959 --> 00:20:24.959 I'm sorry. 00:20:24.959 --> 00:20:26.959 I want to retain all my snapshots for 30 minutes. 00:20:26.959 --> 00:20:29.959 So once it becomes 30 minutes old, it just dumps them. 00:20:29.959 --> 00:20:31.959 I make them every five minutes, so if you think about it, 00:20:31.959 --> 00:20:34.959 that's a lot of snapshots, you know, being created, 00:20:34.959 --> 00:20:38.959 and so that means that each one's going to be 30 minutes old and then dump, 00:20:38.959 --> 00:20:41.959 and I will still have a lot of snapshots there, right. 00:20:41.959 --> 00:20:48.959 I'm going to go ahead and say save, leave all the other settings alone. 00:20:48.959 --> 00:20:49.959 All right. 00:20:49.959 --> 00:20:50.959 So now I'm going to go back to my inventory, 00:20:50.959 --> 00:20:52.959 and I'm going to create a virtual machine. 00:20:52.959 --> 00:20:54.959 So I'm going to go back to vCenter A. 00:20:54.959 --> 00:20:58.959 I'm in A. That's the correct one. 00:20:58.959 --> 00:21:03.959 Go back to my inventory here, here. 00:21:03.959 --> 00:21:09.959 On this region here, I can say I want to new virtual machine. 00:21:09.959 --> 00:21:12.959 And I'll say create a new virtual machine, X. 00:21:12.959 --> 00:21:14.959 We're going to give it a name. 00:21:14.959 --> 00:21:18.959 This is the name that VM they want us to use. 00:21:18.959 --> 00:21:23.959 And we want it to be correct because we're going to see it later on in the lab. 00:21:23.959 --> 00:21:27.959 So we want to know what we're looking for. 00:21:27.959 --> 00:21:29.959 Send. 00:21:29.959 --> 00:21:30.959 All right. 00:21:30.959 --> 00:21:35.959 Gave it a name. 00:21:35.959 --> 00:21:36.959 We've got to pick a VM for it. 00:21:36.959 --> 00:21:39.959 We're going to say put it on ESX-501. 00:21:39.959 --> 00:21:41.959 Next. 00:21:41.959 --> 00:21:44.959 So now here is where that mistake I made earlier, 00:21:44.959 --> 00:21:46.959 that storage policy is going to come around. 00:21:46.959 --> 00:21:49.959 So this is the storage policy I created. 00:21:49.959 --> 00:21:53.959 And I'll say, okay, I want to put it on this datastore. 00:21:53.959 --> 00:21:55.959 And it says this datastore doesn't work for that VM. 00:21:55.959 --> 00:21:56.959 I'm like, well, why not? 00:21:56.959 --> 00:21:57.959 Why doesn't this datastore work? 00:21:57.959 --> 00:22:00.959 That's my policy, and that's the datastore, 00:22:00.959 --> 00:22:01.959 and I know it's on that storage array. 00:22:01.959 --> 00:22:03.959 So what's wrong with my policy? 00:22:03.959 --> 00:22:11.959 So I'm going to get out of here and go back to policies and profiles. 00:22:11.959 --> 00:22:15.959 And I'm going to find that policy I created. 00:22:15.959 --> 00:22:18.959 And there's the policy I created. 00:22:18.959 --> 00:22:21.959 I'm going to edit that. 00:22:21.959 --> 00:22:24.959 And this time I'm going to pay really close attention to what I did, 00:22:24.959 --> 00:22:29.959 and I'll be like, oh, I typed that name wrong, right? 00:22:29.959 --> 00:22:39.959 That should have been named pure flash array. 00:22:39.959 --> 00:22:41.959 Did I spell it right? 00:22:41.959 --> 00:22:43.959 Okay. 00:22:43.959 --> 00:22:47.959 And then say next, next. 00:22:47.959 --> 00:22:48.959 And finish that. 00:22:48.959 --> 00:22:51.959 Like, okay, yeah, see, now this is right. 00:22:51.959 --> 00:22:52.959 I'm paying more attention now. 00:22:52.959 --> 00:22:54.959 I didn't really, I kind of went next, next, next, finish, 00:22:54.959 --> 00:22:55.959 thinking I did it right. 00:22:55.959 --> 00:23:01.959 But obviously I made a mistake, and now I see that this name is correct. 00:23:01.959 --> 00:23:04.959 I'll hit finish. 00:23:04.959 --> 00:23:05.959 All my tasks are completed. 00:23:05.959 --> 00:23:06.959 I'm good. 00:23:06.959 --> 00:23:09.959 So I'm going to go to inventory again. 00:23:10.959 --> 00:23:21.959 And I'm going to create a new VM, a new virtual machine, create a new VM. 00:23:21.959 --> 00:23:29.959 And this is the name I want to use there. 00:23:29.959 --> 00:23:32.959 And I'm going to put it on ESXY1. 00:23:32.959 --> 00:23:34.959 Okay, that's good. 00:23:35.959 --> 00:23:40.959 I'm going to choose that policy. 00:23:40.959 --> 00:23:42.959 I'm going to choose a data store. 00:23:42.959 --> 00:23:43.959 Now it checks out. 00:23:43.959 --> 00:23:44.959 Now it's good. 00:23:44.959 --> 00:23:45.959 Okay. 00:23:45.959 --> 00:23:48.959 So you need to make sure that everything's typed out exactly right. 00:23:48.959 --> 00:23:50.959 You know, even if you're doing it in your own environment, 00:23:50.959 --> 00:23:52.959 you want to make sure you have the names for the arrays, you know, 00:23:52.959 --> 00:23:53.959 exactly right. 00:23:53.959 --> 00:23:55.959 They are case sensitive. 00:23:55.959 --> 00:23:57.959 You want to make sure you're matching all that up. 00:23:57.959 --> 00:23:58.959 Okay, perfect. 00:23:58.959 --> 00:23:59.959 Now that's good. 00:23:59.959 --> 00:24:01.959 This also shows you that my policy is working, right, 00:24:01.959 --> 00:24:02.959 because it was saying, well, 00:24:02.959 --> 00:24:08.959 I can't put that VM on that policy because I can't connect to that array. 00:24:08.959 --> 00:24:10.959 The array you specified, I can't connect to. 00:24:10.959 --> 00:24:12.959 I'm going to go ahead and say next. 00:24:12.959 --> 00:24:15.959 ESXI is great. 00:24:15.959 --> 00:24:16.959 Windows is great. 00:24:16.959 --> 00:24:20.959 I'm going to go ahead and just reduce this. 00:24:20.959 --> 00:24:22.959 I'm not taking up too much resource on here. 00:24:22.959 --> 00:24:28.959 I think 16 megs of RAM is plenty nowadays. 00:24:28.959 --> 00:24:32.959 We do not need to overfeed these guys, right. 00:24:32.959 --> 00:24:37.959 And I'll say 64 megs of RAM. 00:24:37.959 --> 00:24:40.959 This is going to be a really small operating system. 00:24:40.959 --> 00:24:44.959 Say next and finish. 00:24:44.959 --> 00:24:45.959 All right. 00:24:45.959 --> 00:24:49.959 So now it should create that virtual machine for me. 00:24:49.959 --> 00:24:52.959 And while that's being created, there it is. 00:24:52.959 --> 00:24:58.959 Let's go ahead and just go forward in our lab guide. 00:24:58.959 --> 00:25:03.959 And it wants us to go back to our pure storage A array and to verify that it 00:25:03.959 --> 00:25:10.959 actually did create that virtual machine and that snapshot. 00:25:10.959 --> 00:25:14.959 So let's go ahead and go back to array A. 00:25:14.959 --> 00:25:18.959 We're going to go to storage. 00:25:18.959 --> 00:25:21.959 We're going to go to volumes. 00:25:21.959 --> 00:25:27.959 And there is my VM4, my pure replication VM4. 00:25:27.959 --> 00:25:29.959 I see I have it configured here. 00:25:29.959 --> 00:25:33.959 That's the size on the disk there, right. 00:25:33.959 --> 00:25:43.959 And I can also go to B and go to storage and volumes. 00:25:43.959 --> 00:25:48.959 I need to go to protection, sorry, and protection groups. 00:25:48.959 --> 00:25:53.959 And there's that VM, right, or my group. 00:25:53.959 --> 00:25:54.959 All right. 00:25:54.959 --> 00:26:01.959 If I go back to A and go to protection and protection groups, right, 00:26:01.959 --> 00:26:10.959 now I'm starting to see stuff coming up. 00:26:10.959 --> 00:26:11.959 All right. 00:26:11.959 --> 00:26:13.959 So we did go in. 00:26:13.959 --> 00:26:14.959 We created that VM. 00:26:14.959 --> 00:26:16.959 We created a policy first, right. 00:26:16.959 --> 00:26:23.959 We created our storage policy. 00:26:23.959 --> 00:26:25.959 And we created a VM at that storage policy. 00:26:25.959 --> 00:26:27.959 We configured replication on our storage array, 00:26:27.959 --> 00:26:30.959 and we saw the VM creating snapshots on there. 00:26:30.959 --> 00:26:31.959 All right. 00:26:31.959 --> 00:26:34.959 So that was a pretty good demo of how storage policies work. 00:26:34.959 --> 00:26:39.959 Again, remember, you can run through the same thing yourself by going to HOL, 00:26:39.959 --> 00:26:42.959 which is hands-on labs, HOL.VMware.com. 00:26:42.959 --> 00:26:47.959 Just log in with your VMware account and start checking this out.