Showing posts with label Server Migration. Show all posts
Showing posts with label Server Migration. Show all posts

Find Out Windows SID (Security Identifier) of a Windows Machine:


SID stands for Security Identifier; it is a security principle of the Microsoft Windows network. If you have
created a windows based network then each computer on the network will have a unique SID and that SID is used to identify an object, such as, a user or a group of users in the network. Whenever any specific user in the network tries to access any particular resource, the SID of the requesting user is checked to verify whether the user is authorized to access the resource or not.

Find out the SID of a Windows Computer:

It is very hard to find out the SID of the computer because you need to be a registry geek for this purpose. Instead, you can try out PsGetSid, a free command line utility which lets you view and change the SID.
Download it from the Micosoft website, and then open the command prompt in the administrator mode and run the following command to find out the SID of your machine.

Psgetsid



How to copy a VM host to host without vCenter


Login to both ESXi hosts that you are copying from and copying to and make sure SSH is enabled.

Make sure the SSH service is started and allowed in ESXi Firewall on both the hosts.

Now ssh into the esxi host 1 which has the VM that needs to be transferred.

Lets give that host ip 10.1.1.1 and the Host 2 that’s going to receive the file will be 10.2.2.2.

You can SSH into the host 1 using putty(win) or terminal (mac)

#ssh root@10.1.1.1
The authenticity of host '10.1.1.1 (10.1.1.1)' can't be established.
RSA key fingerprint is b2:d6:00:34:aa:cc:62:95:8f:d7:f3:1d:59:1e:c3:54.
Are you sure you want to continue connecting (yes/no)? yes

then it will prompt for Password: so enter that.

Start transferring folder:

nohup scp -rv /vmfs/volumes/data-store1/vm-folder-name root@10.2.2.2:/vmfs/volumes/data-store2/

For Multiple VMs (Folders)

First change directory to the Datastore folder

cd /vmfs/volumes/data-store1/

nohup scp -rv vm-folder-1 vm-folder-2 root@10.2.2.2:/vmfs/volumes/data-store2/

Then it’s better to enter multiple VMs leave just a single space between the VM folder name. No quotes or commas.
Now you will be prompted for “host 2” password. enter that and the file transfer will start. The flags used here are -rv, where r is for folder tranfer and v for verbos to watch the progress.

Note: Adding nohup before scp will allow the command to run in background even if you close Terminal/Putty window.

PROCEDURE TO MIGRATE WORKLOAD USING CLOUD ENDURE TOOL:

PHASE 1: Installing CE Agent on the Source Server

Step1:
Download the CE agent from Cloud Endure Website.

Step2:
Log-in to the source server and copy the CE Agent on it to run.

Step3:
Get the following details from the Source server:
i.                    CPU count
ii.                  Memory (RAM) count
iii.                OS type and version
iv.                 Number of disks attached to it
Ensure that Outbound Internet access is enabled in these servers.

Step4:
Run the Installer as administrator

Step5:
It will ask for the username and password. Provide the same.

Step6:
Once it accepts, it will connect to the Cloud Endure management console from the source server. (If there is no internet connectivity available then it would throw out an error)

Here it will show the number of harddisk drives it could recognize in the source server. Validate with your gathered data.

Step6:*
Note down the size and order of the disks properly. You need to create these disks in the Target VM in the same order as it has been in this screen.

Step7:
It will ask for port numbers and hostname. Generally we do not need to put anything manually and have to select the default value (by clicking the enter button).

Step8:
It will download and install the CE agent from the management console.

Step9:
It will successfully get registered in the CE database.

Step10:
Once the installation is finished it will show the message.

Step11:
You can verify it from the log file that gets generated as soon as you run the agent.

This completes your work on the Source Machine.
Next you need to get into the Target (Vmware) environment to create an empty VM which would be a replica of the source.


PHASE 2: Creating replica Target VM in the Vmware environment

In this phase, the replica target VM, once created, would be booted using the CE.iso file. The .iso file has been downloaded from the CE site and have been copied to our vCenter Datastores. The VM would not be having any Operating System on it and would be booted for the first time using this .iso image. This will help it to synchronize with the source VM under the monitoring of the CE management console.

Step1:
Log-in to the vCenter. Create a new virtual machine from the vCenter console.
Select the custom option.

Step2:
Name the hostname with a _CE extension to identify that it is a Cloud Endure based migration. It will not appear by default.

Step3:
Select the Cluster where you want the VM to be hosted and select the host accordingly.
A pre-requisite of it would be to get the details of the cluster capacity to select the ideal one based upon the target server resource requirement.

Step4:
Select the Datastore which has the sufficient free space to host the VM disks. You need to check it well in advance.


Step5:
Select the vm machine version based on your vSphere Environment.

Step6:
Select the guest OS as the source server.

Step7:
Select the number of CPU. It has two parts.
i.                    Number of sockets
ii.                  Number of cores/socket
You should try to get these information as much accurate as possible.

Step8:
Configure the memory (RAM) details as the source server.

Step9:
Selecting the network adaptor is an important step.
If you are creating a Linux VM, then select E1000.
For Windows VM it should be Vmxnet3 (for vSphere 6 and onwards).
If there is a back-up network available in the source then you need to create 2 vNICs.

Step10:
While selecting the storage SCSI controller adaptor we need to keep the following thing in mind:
1.      For Windows it should be LSI logic SAS
2.      For Linux it should be LSI logic Parallel
If not done properly, the target VM will not boot from the OS.

Step11:
Create the disks, as per the data you have gathered from the source server, and in the same sequence as of the CE agent.

Step12:
In Cloud Endure migration always select the disk file as Zero Thick.

Step13:
Keep the SCSI controller as 0:0. The count will increase by 1 for any additional addition of disk.

The VM will get created. Repeat step 11 and 12 to create additional disks as per requirement.

Step14:
Next, we need to assign the proper VLAN tag to the network interface from VM Edit settings .Please take a note of it from the team before doing this job.

Step15:
From VM Settings, we need to enable the CPU/RAM Hot Pluggable option.

Step16:
We have created a VM without an Operating System. To boot the VM with CE .iso file we need to mount it in the VM CD ROM drive. The cloud endure .iso file should be accessible from all the ESXi clusters.

Step 17:
Browse the appropriate datastore as per the requirement

Step18:
Select the .iso file as shown below. This will ask to assign a Temporary IP Address while you Power on the VM and log-in to it from console.

Step19:
Upon receiving the Temp IP Address,  based on the server name CE will identify any similar servers in its database and prompt for the CE ID to be entered. Enter the correct CE ID for the source server when prompted. This step maps the target to the source for replication, so make sure the server name matches exactly. Hit enter for the next few prompts, CE just verifies the disk mapping and IPs it has picked automatically here.

Step20: 
Logon to CE web console, type the server name in search box and check the progress. If the progress moves above 1.01% it means the replication has started.