So im finally back with a new blog
i know i been sleeping during the corona pandemic, so lets get to it
i previously explain how to configure the DRS in VMware Level and now we will do it in the Storage level
so in my previous blog i show you how to install Storage
so the reason for Storage DRS is to move machine from an over utilized storage to a none busy storage
here i will show you only how to install it and the result is similar to the VMware DRS
similar to the VMware DRS i will create a new Cluster

Go to vCenter – Datacenter – New Datastore Cluster

Choose a name and check the box to Turn ON Storage DRS

Choose the DRS storage Automation to be Fully Automated

Leave this section as it’s but sometimes this I/O check box could cause Error but this is a lab so i would leave it as it’s
and  i played the thresholds a little bit so it triggered the storage automation

I selected the cluster here that need connecting to the Storage DRS

in this step i selected the 3 Storage that will be under this cluster  (ISCSI-A, ISCSI-B & ISCSI-C)

At the summary page press Finish

and now i can see all my storage is under the Datastore Cluster

now let me add a new Virtual Machine

Select Create a new Virtual Machine

Select the Datacenter

Choose the Cluster were you want to install the VM

Now the BIG Step, no need to choose a specific storage, i can select the Storage Cluster and automatically the system will choose the storage

Choose ESXi 5.5 and later

Select the Guest Machine

In the Customization page just press Next

Now in the summary page you can see under the Datastore
the Machine chooses the ISCSI-B as (Recommended) by the ESXi DRS Storage
Click Finish to start deployment

From Recent Task you can see the Task been Deployed

Finally the Machine created under the Cluster and in the Summary page you see the Storage (Storage Cluster)

;D

VMware vCenter Converter transforms your Windows- and Linux-based physical machines and third-party image formats to VMware virtual machines, So
Bayan Senur whom is the manager of Jaguar & Land Rover Contact Center have a recording server that almost crashing and there is no enough storage on server and she need that space so the best thing is to move it to Virtual environment were we can add space and back up the system without worrying any more

I have the EXE in my folder so lets get to it

Choose Next

Select agree to the terms

Choose the default folder to save the installation

I choose Local Installation

i checked the box to join the VMware which is optional

Now select Install to start the instalation

Select Finish to run the Converter
First step Select Convert Machine option

Now select the machine option
in my case my machine is powered on
then enter the detail of machine IP address (which is Jaguar Company Speechlog recording system ;D Sorry Bayan i had to test on something ) and username and password for the machine

The Agent will be deploy to the machine remotly

you can check if the Agent been deployed by going to Control Panel – Program and Feature

Now next step is select the Infrastructure that im using which is VMware infrastructure then Enter the IP Address of the vCenter with the admin login
Next step is to chose the Datacenter were you want the machine to be
then you choose the cluster and host that you will be installed on and the VM version

you can see there is an (X) error showing on the Data to Copy option and as you see the F: Drive have 368 G which bigger than our Host
Select Advanced
i made sure that i will not use the F drive in this process But in real life you need to have a bigger HD

and i made the C Drive as Thin

Also an optional i change the vCPU
In Advanced i made sure to remove any system restore point so it will not utilize more space

Press Finish

Converting process will start
and its completed

you can check the job process

Now Lets check our vCenter
Select Host and Cluster

and here under the Host that we choose earlier our Speechlog-PC Machine
i will use the credential to login 
;D

Thanks to an easy Converting

in the last blog “VMware DRS” i show you how to migrate machine automatically and this was the result, it moved my VM Machine “Windows 10-A” & “Windows 10-B” to the ESXi host “192.168.208.210”

but what if i do not want those two machines to be together and i want “Windows 10-A” & “Windows 10” to be together and “Windows 10-B” to be far away from “Windows 10-A” and not share the same host.
well there is one solution “Affinity and Anti-Affinity”
so if you go also to your Cluster – Related Objects -Virtual Machines

Okay lets adjust the component so we can see the host of each Machine
Add the Host Field

As you can see here
Windows 10 on host (192.168.208.209)
Windows 10-A on host (192.168.208.210)
Windows 10-B on host (192.168.208.210)
lets create first rule that will join Windows 10-A & Windows 10 Together
so lets go to Cluster – Manage – Settings – DRS Rules

Add a new Rule – Choose a Name
Select to Keep Virtual Machine Together
Now Add the Machine

I choose Machines:
Windows 10
&
Windows 10-A

Now Choose OK

as you can see if you highlight the rule it will show you the machine affected by that rules
Now if you go back to Cluster – Related Object – Virtual Machines
you can see that Machine Windows 10 Joined the other Machines and now become hosted by host 192.168.208.210
and you can see the Task Detail here
As i remembered we mention that we want “Windows 10-B” to be far away from “Windows 10-A”
so lets add another rule and this time we choose to (Separate Virtual Machines)

Lets choose Machines Windows 10-A & Windows 10-B
Now press OK

and if you highlight the Rule you will see the affected Machines
and if we go to the Task we will see that Machine Windows -A is moving from host 192.168.208.210 and since there is a rule to keep Windows10-A and Windows 10 together in that case also Machine Windows 10 will be moving to the other host

and Yup both machine now faaaaaar away from Windows 10-B
and both of Windows 10 & Windows 10-A hosted on 192.168.208.209

Okay now we finish with VM to VM Relationship
what if i want to Keep a specific VM tagged to a specific Host
Here we go to a new thing called : DRS Group

Add a DRS Group and choose a name
and choose a Type should be VM DRS Group

First Select the VM Machine and i selected Windows 10-B
Note: make sure you dont select the wrong VM cause it will cause an issue since you have another rule that separate Windows 10-A from Windows10-B

and its added

Now Add another DRS Group and choose a name and Type should be Host DRS Group
and select the Host needed

and then press OK

Now go back to the DRS Rule and add a rule
Type: Virtual Machine to a Host
and select the VM DRS Group and Host DRS Group that you created

and if you highlight the rule you will see the affected Machine
Now you can see VM Windows 10-B moved to 192.168.208.209
an since there is an older rule that separate windows 10-A from Windows 10-B so the VM windows 10-A moved to host 192.168.208.210
also there is a rule that Join VM Windows 10-A & Windwos 10 together then the VM Windows 10 moved to host 192.168.208.210
i know that a really confusing but i suggest you read it couple of time and test it your self to get the matter

and that is the beautiful result

and you can go to the Cluster – Monitor – vSphere DRS – History to see the procedure

;D

Hello Again
So in my earlier blog i manually migrate VM Machine from my first host to the second one, what if i want for my virtual machine to be moved automatically??? the Answer is:
DRS (Distributed Resource Scheduler)

lets start by the configuration but first if you notice all my machine under Host [192.168.208.209] nothing under [10.1.1.32]or[192.168.208.210]
so before we start the earlier two blog is very important to be establish first for VMware DRS to work
VMotion
Shared Storage
Right Click my  Datacenter – New Cluster
Give it a name and check the box DRS [Turn on] and you can choose the Automation Level and here i will show you the Fully Automated. most of the admin prefer the Partially automated as the VMware will give you suggestion and you could follow or not or Manual were an admin give suggestion
Second step is i will drag my hosts under the Cluster
and it will ask me what to do with the VM and i choose my first option and press Ok
and automatically it start moving the VM from under my host 192.168.208.209 to other Hosts

and the end result as you can see my 3 Virtual Machine moved under my biggest host [192.168.208.210]

and if you go to the cluster – vsphere DRS tab – History
you see the time and date those machines moves
(Wow i cant believe i wrote this blog in 2018 and never shared it, dont blame me i was chasing pal alto certificate)
and also you can see the CPU Utilization
and select the VM to see each Utilization

;D

vMotion enables live migration of VM machines from one Host to another with no impact on the Daily operation But Let me tell you this
Before migrating a virtual machine with vMotion, ensure that your hosts and virtual machines have the same network card & share the storage believe me you don’t want your machine to come with different IP Address  ;D

So Similar to how we did earlier when we add a Storage in the last blog we need to add a VMkernel specific for vMotion
in your Home Dashboard go to Host and Cluster
Select your Host – Manage – Networking – Virtual Switches – Add Host Networking

Choose VMkernel Network Adapter

Choose a New Standard Switch

Click on the + Sign to add a network card
Select the card you want to use
Press Next
Here we will Check the Box for vMotion Traffic
Give a static IP Address to the VMKernel
Press Finish
Now it’s created we are ready to move to the next step

Now as you can see my VM Machine (Windows 10) is located under my Host 192.168.208.210 and using my ISCSI Storage (ISCSI-A)

Right CLick on the Machine and Select Migrate

Now i have the option either to change the Host of the Machine or Change the Datastore or Both
since in my last blog i added an External storage then i will change Both
I choose to move it to the Host and the compatibility check sign is successful
(the red sign Most of the time memory size give a red sign you have to take care about it but this is just a lab)
Now choose the storage you want to move to
It’s better to choose the Recommended option
Select Finish
and you can see your Machine is Moving in the Recent Task

And Walla your Machine Moved under host 192.168.208.209
and if you go down you can see the storage information  which show ISCSI-B

;D

okay i know
Same face, Different Hair style and Different dress
its like i created a copy of my self
Guess what!!
VMware have the same Capabilities called (Cloning)
Cloning Feature allow you to create a copy of your perfect Virtual Machine instead of repetitively creating a VM from scratch over and over

So this is how you can do it
Select your Perfect VM Machine
Right Click and choose – Clone to Virtual Machine

Select a name to your new machine and choose a Datacenter
Select which Host you want to put your VM in
Select the Storage
I will not go in detail of Edit the Machine file but for a better practice you need to do it
Press Finish
you can Monitor the recent task while the machine is been created

and just like that your machine is created
Of course you need to change the IP Address to save your self from Conflict IP Address and PC Name cause we did this clone without operation system customize

;D