Skip to Content

آرشیو دسته بندی ها:Uncategorized

vSphere 6.7 upgrade vSAN 6.6 to 6.7 – pt.4

vSphere 6.7 upgrade vSAN 6.6 to 6.7 – pt.4

 

If the virtual infrastructure in use is configured with vSAN, after completing the upgrade of both vCSA and ESXi hosts to version 6.7, also vSAN should be upgraded to latest version.

After the upgrade of vSphere components (vCSA and ESXi hosts), the vSAN cluster’s Summary tab displays a warning message related to Disk format version.

vsphere-67-upgrade-vsan-02

This warning is due to vSphere 6.7 that comes with the new vSAN version 6.7.

 

Blog Series

vSphere 6.7 install vCSA – pt.1
vSphere 6.7 upgrade vCSA 6.5 to 6.7 – pt.2
vSphere 6.7 upgrade ESXi 6.5 to 6.7 – pt.3
vSphere 6.7 upgrade vSAN 6.6 to 6.7 – pt.4

 

vSAN cluster checks before the upgrade

Before upgrading the vSAN cluster, some checks must be performed to avoid possible issues or data loss during the upgrade process.

Select the vSAN cluster and go to Configure tab. Click on Disk Management under vSAN area and verify that vSAN Health Status is reported as Healthy for all disks and disk groups configured.

vsphere-67-upgrade-vsan-03

Make sure that no rebuilding tasks are currently running in the vSAN cluster. From vSphere Client select the vSAN cluster and go to Monitor tab. Select Resyncing Objects option under vSAN section. In this area you can check running tasks or perform a synchronization before proceeding with the upgrade by clicking Resync Throttling.

vsphere-67-upgrade-vsan-04

From vSphere Client select the vSAN cluster and go to Configure tab. Click Pre-Check Upgrade button before launching the upgrade to ensure vSAN can be safely upgraded.

vsphere-67-upgrade-vsan-05

If the Pre-Check Upgrade process reports a green flag with Ready to upgrade – pre-check completed successfully, the system is ready to be upgraded.

vsphere-67-upgrade-vsan-06

 

Upgrade vSAN

When the pre-checks have been completed, from Configuration tab select Disk management option under vSAN section. Click Upgrade button to perform the upgrade of your vSAN cluster.

vsphere-67-upgrade-vsan-07

Based on your requirements select the Allow Reduced Redundancy option.

vsphere-67-upgrade-vsan-08

Click Upgrade to proceed with the upgrade.

vsphere-67-upgrade-vsan-09

The upgrade takes place and requires some minutes to complete depending on the disks size.

vsphere-67-upgrade-vsan-10

When the upgrade process has been completed successfully, the system reports a green flag with the status All <disks_number> disks on version 6.0.

vsphere-67-upgrade-vsan-11

The procedure to upgrade vSAN is now complete. The virtual infrastructure is now running vSphere 6.7 and you are able to take benefit of new features provided.

ادامه مطلب

vSphere 6.7 upgrade ESXi 6.5 to 6.7 – pt.3

vSphere 6.7 upgrade ESXi 6.5 to 6.7 – pt.3

After upgrading the vCSA, to take benefit of new features provided by vSphere 6.7 you have to upgrade also all ESXi hosts installed in your virtual infrastructure.

The procedure it’s pretty easy and rely on the Update Manager service provided with vSphere 6.7.

 

Blog Series

vSphere 6.7 install vCSA 6.7 – pt.1
vSphere 6.7 upgrade vCSA 6.5 to 6.7 – pt.2
vSphere 6.7 upgrade ESXi 6.5 to 6.7 – pt.3
vSphere 6.7 upgrade vSAN 6.6 to 6.7 – pt.4

 

Upgrade ESXi 6.5 to 6.7

To verify the installed ESXi version in the network, from the vSphere Client go to the host’s Summary section and check the Hypervisor field.

vsphere-67-upgrade-esxi-02

 

Create the upgrade baseline

new baseline must be created in the Update Manager service to easily upgrade all ESXi hosts in your network. Click Menu and select Update Manager.

vsphere-67-upgrade-esxi-03

From the Update Manager area, select the ESXi images section and click Import.

vsphere-67-upgrade-esxi-04

Click Browse button to select the ESXi 6.7 installer in ISO format downloaded from VMware website.

vsphere-67-upgrade-esxi-05

Selected the correct image version, click Import to import the image in the vCSA.

vsphere-67-upgrade-esxi-06

When the installer has been imported successfully, click New Baseline to create the baseline to apply to the hosts you need to upgrade.

vsphere-67-upgrade-esxi-07

Specify a Name and a Description to better identify the scope of the baseline. Click Next.

vsphere-67-upgrade-esxi-08

Select the previously imported ESXi image and click Next.

vsphere-67-upgrade-esxi-09

Click Finish to create the baseline.

vsphere-67-upgrade-esxi-10

In the Baselines section is now listed the new created baseline .

vsphere-67-upgrade-esxi-11

 

Attach the baseline

Created the baseline needed to upgrade the hosts, you have to attach this baseline to all ESXi you want to upgrade. Select the cluster with the hosts to process and go to Updates section. Click Attach.

vsphere-67-upgrade-esxi-12

Select the correct baseline to attach and click OK.

vsphere-67-upgrade-esxi-13

Click Check Compliance to verify hosts to upgrade.

vsphere-67-upgrade-esxi-14

 

Remediate hosts

Since the host upgrade cannot be staged, click Remediate to proceed with the upgrade.

vsphere-67-upgrade-esxi-15

The installation process begins. Accept the EULA and click OK.

vsphere-67-upgrade-esxi-16

Select the ESXi hosts to upgrade and click OK. You can safely proceed even if you have vSAN cluster configured in place.

vsphere-67-upgrade-esxi-17

The upgrade is being processed.

vsphere-67-upgrade-esxi-18

When the upgrade has completed successfully, all hosts are reported as Compliant.

vsphere-67-upgrade-esxi-19

 

Troubleshooting

After upgrading the first host, the vCSA was unable to reconnect the processed host displaying an error related to the Enhanced vMotion Compatibility mode. Not sure why this error, maybe Spectre/Meltdown CPU microcode fixes somehow may have affected the EVC cluster.

vsphere-67-upgrade-esxi-20

A work around used to continue with upgrade was disabling the VMware EVC feature in the processed cluster and renabling it after connecting all upgraded ESXi hosts.

vsphere-67-upgrade-esxi-21

Disabled the VMware EVC feature, right click the failed host and select Connection > Connect. This time the host was connected successfully to the cluster.

vsphere-67-upgrade-esxi-22

When all upgraded hosts are connected to the cluster, enable the vSphere EVC feature once again.

vsphere-67-upgrade-esxi-23

The ESXi hosts upgrade procedure is now complete. If you have a vSAN cluster configured, the cluster’s Summary section reports warnings related to vSAN since vSphere 6.7 comes with the new vSAN 6.6 version.

vsphere-67-upgrade-esxi-24

Final step of the overall upgrade procedure consists in the upgrade of the vSAN cluster if configured. Part 4 will cover vSAN upgrade to finalize the migration to the new version.

ادامه مطلب

vSphere 6.7 upgrade vCSA 6.5 to 6.7 – pt.2

vSphere 6.7 upgrade vCSA 6.5 to 6.7 – pt.2

If your vSphere environment is running version 6.0 or above, you can easily migrate the vCenter Server to version 6.7 with the migration tool provided with vSphere 6.7.

Compared to a fresh vCSA installation, the upgrade is the preferred method to use for complex environments or where time consuming settings have been configured in the original vCenter Server. Currently the direct vCSA upgrade to version 6.7 is supported from vCSA 6.0 or 6.5 U1 but it was already announced the upcoming vCSA 6.7 U1 update release will support the upgrade also from version 6.5 U2.

Although the upgrade process doesn’t delete the original vCSA, before proceeding with the upgrade make sure you have a working backup available to restore the original vCSA in case of problems.

 

Blog Series

vSphere 6.7 install vCSA 6.7 – pt.1
vSphere 6.7 upgrade vCSA 6.5 to 6.7 – pt.2
vSphere 6.7 upgrade ESXi 6.5 to 6.7 – pt.3
vSphere 6.7 upgrade vSAN 6.6 to 6.7 – pt.4

 

Pre-requisites

Before proceeding with the upgrade, the vSphere DRS feature in the source vCSA must be disabled or set to manual to avoid issue with the vCSA during the upgrade procedure.

From the vSphere Web Client, right click the cluster and select Settings. Access the vSphere DRS section under Services and set DRS Automation to Manual then click OK to confirm.

vsphere-67-upgrade-vcsa-02

When the vSphere DRS has been set to Manual you are ready to begin the upgrade procedure.

vsphere-67-upgrade-vcsa-03

 

Upgrade the vCSA

The upgrade to version 6.7 is a two stage process:

  • Stage 1 – Deployment of the new appliance
  • Stage 2 – Configuration of the vCSA

Stage 1 – Deploy the appliance

Mount the ISO file downloaded from VMware website and run the installer from the supported OSs (Windows, Linux, MacOS) by double clicking the installer.exe file.

vsphere-67-upgrade-vcsa-04

From the Deploy appliance wizard, click Upgrade.

vsphere-67-upgrade-vcsa-05

Click Next to begin the procedure.

vsphere-67-upgrade-vcsa-06

Accept the EULA then click Next.

vsphere-67-upgrade-vcsa-07

Enter the source Appliance FQDN or IP Address then click Connect to source.

vsphere-67-upgrade-vcsa-08

Specify the SSO User nameSSO password and the Appliance (OS) root password. Enter also the ESXi host where the source vCSA resides. Click Next.

vsphere-67-upgrade-vcsa-09

Click Yes to accept the certificate.

vsphere-67-upgrade-vcsa-10

Specify the target ESXi host where to deploy the new appliance and enter the credentials. Click Next.

vsphere-67-upgrade-vcsa-11

Click Yes to accept the certificate from the specified host.

vsphere-67-upgrade-vcsa-12

Enter the VM name and the root password. Click Next to continue.

vsphere-67-upgrade-vcsa-13

Based on your environment, specify the Deployment size and Storage size then click Next.

vsphere-67-upgrade-vcsa-14

Select the datastore to use and click Next.

vsphere-67-upgrade-vcsa-15

Configure the required network parameters. The Temporary IP address is used only during the deployment process, production IP address will be the same as the source appliance. Click Next.

vsphere-67-upgrade-vcsa-16

Click Finish to begin the deployment.

vsphere-67-upgrade-vcsa-17

The deployment of the new appliance is being performed.

vsphere-67-upgrade-vcsa-18

When the deployment has been completed successfully, click Continue to proceed with Stage 2. At this point you could stop the upgrade procedure and resume it later accessing the vCSA Management interface at the address https://IP_temp_address:5480.

vsphere-67-upgrade-vcsa-19

Take a snapshot of the new vCSA to resume the deployment from this point in case Stage 2 fails for some reasons.

 

Stage 2 – Configuration of the vCSA

Completed Stage 1, click Next to begin Stage 2 of the deployment procedure.

vsphere-67-upgrade-vcsa-20

Enter the required parameters to connect to source vCenter and click Next.

vsphere-67-upgrade-vcsa-21

Before migrating the configuration from the source vCenter Server, a pre-upgrade check is performed by the installer.

You may receive warnings about the following:

  • The cluster where the source vCenter Server is located must have the vSphere DRS feature not set to Fully Automated
  • Baselines not compatible with Update Manager 6.7 won’t be copied
  • Warnings about vCenter Server extensions that cannot be migrated
  • If the source appliance has multiple NICs configured, only the network information related to Eth0 will be preserved

Fix the detected issues that may prevent the upgrade (in the worse case you need to redeploy the vCSA). Click Close to proceed.

vsphere-67-upgrade-vcsa-22

Select the data to be migrated and click Next. Available data migration options are the following:

  • Configuration
  • Configuration + historical data (events and tasks)
  • Configuration + historical data (events, tasks and performance metrics)

vsphere-67-upgrade-vcsa-23

Optionally you can select the Join the VMware’s CEIP option. Click Next to begin data migration.

vsphere-67-upgrade-vcsa-24

Click OK to proceed with the upgrade.

vsphere-67-upgrade-vcsa-25

In step 1 data are copied from the source vCenter Server.

vsphere-67-upgrade-vcsa-26

During step 2 target vCSA is being configured and services are started.

vsphere-67-upgrade-vcsa-27

Final step import copied data to the new vCSA.

vsphere-67-upgrade-vcsa-28

Some messages are displayed to inform you about changes you should do in your environment after the deployment. Click Close.

vsphere-67-upgrade-vcsa-29

When the upgrade has completed successfully, click Close to exit the wizard. The new vCSA is now reachable at the same DNS name or IP address of the source vCenter Server.

vsphere-67-upgrade-vcsa-30

After logging to the new vCSA (the HTML5 client works more much better now and provides most of available features) you can notice the old vCenter Server still available and in a powered off state and of course the just deployed vCSA. The IP address didn’t change and it is the same as the source vCenter Server.

vsphere-67-upgrade-vcsa-31

The vSphere DRS feature in the cluster can be re-configured to Fully Automated, if you use this configuration.

vsphere-67-upgrade-vcsa-32

The vCSA is now running the new version 6.7. To take benefit of new features available in vSphere 6.7, next step to perform is the upgrade of the ESXi hosts present in the infrastructure. Part 3 will cover the ESXi hosts upgrade using VUM.

ادامه مطلب

vSphere 6.7 install vCSA 6.7 – pt.1

 

vSphere 6.7 install vCSA 6.7 – pt.1

starwind

vsphere-67-install-vcsa-01

When you plan the upgrade of your virtual infrastructure to latest VMware vSphere 6.7, first step to take is a new installation of the vCSA component.

The upgrade process must be planned carefully to avoid services disruption or data loss. Since the first vSphere component to configure is always the vCenter Server, you have the option to perform a fresh installation or an upgrade from a previous version. Currently the vCSA direct upgrade to version 6.7 is supported for the vCSA 6.0 or above with the exclusion of version 6.5 U2 but it was announced during VMworld 2018 US that migration from 6.5 U2 will be supported with the upcoming vCSA 6.7 U1 update release.

 

Blog Series

vSphere 6.7 install vCSA 6.7 – pt.1
vSphere 6.7 upgrade vCSA 6.5 to 6.7 – pt.2
vSphere 6.7 upgrade ESXi 6.5 to 6.7 – pt.3
vSphere 6.7 upgrade vSAN 6.6 to 6.7 – pt.4

 

Pre-requisites

Because VMware vSphere infrastructure strongly depends on DNS, before proceeding with the installation of the vCSA you have to configure the A record in your DNS Server that points to the new vCenter Server.

In your DNS Server (Windows version in the example) create a new A record.

vsphere-67-install-vcsa-02

Specify the DNS name and the associated IP address.

vsphere-67-install-vcsa-03

When the DNS entry has been created, you can begin the installation.

 

Install the vCSA

To perform a new install of the vCenter Server Appliance (vCSA), from the VMware website download the latest version of the vCSA in .ISO format. Mount the ISO and select the appropriate installer based on the OS from which the installation is executed. The installation can be launched from one of the supported OSs: Windows, Linux, and MacOS.

The installation of the vCSA is a two stage process:

  • Stage 1 – Deployment
  • Stage 2 – Configuration

Stage 1 begins deploying the vCenter Server.

 

Stage 1 – Deploy appliance

If your OS is Windows, access the vcsa-ui-installer > win32 directory and run the installer.exe.

vsphere-67-install-vcsa-04

From the installation wizard, click Install to proceed with the installation of a new vCenter Server.

vsphere-67-install-vcsa-05

Click Next.

install vcsa 1

Accept the EULA then click Next.

vsphere-67-install-vcsa-07

Select the deployment type. You can deploy a vCenter Server with an Embedded PSC suitable for medium to small environments or install a standalone PSC and vCenter Server for a more complex infrastructure. Click Next.

vsphere-67-install-vcsa-08

Specify the target ESXi host where to install the vCSA and enter the root credentials. Click Next.

vsphere-67-install-vcsa-09

Click Yes to accept the SSL certificate from the selected host.

vsphere-67-install-vcsa-10

Enter the VM name for the vCSA and type the password in the Set root password field. Click Next to continue.

vsphere-67-install-vcsa-11

Based on your environment, specify the Deployment size and the Storage size then click Next.

vsphere-67-install-vcsa-12

Select the datastore to use and click Next.

vsphere-67-install-vcsa-13

Configure the network settings and click Next.

vsphere-67-install-vcsa-14

Click Finish to start the installation.

vsphere-67-install-vcsa-15

The vCSA is deployed in the specified target system.

vsphere-67-install-vcsa-16

When Stage 1 has completed successfully, click Continue to continue the installation. You can also exit the wizard and continue the installation at any time by typing in your favorite browser the address reported in the window.

vsphere-67-install-vcsa-17

 

Stage 2 – Set Up the vCSA

When Stage 2 window is displayed, click Next to begin the configuration process.

vsphere-67-install-vcsa-18

Because the infrastructure must be time synced to avoid authentication issues, specify the NTP Server and optionally enable the SSH access. Click Next.

vsphere-67-install-vcsa-19

Select the Create a new SSO domain option and type the SSO domain name. Specify the SSO password then click Next.

vsphere-67-install-vcsa-20

Optionally join the CEIP then click Next.

vsphere-67-install-vcsa-21

Click Finish to finalize the deployment.

vsphere-67-install-vcsa-22

Click OK to proceed.

vsphere-67-install-vcsa-23

The setup process is being executed.

vsphere-67-install-vcsa-24

When Stage 2 has successfully run, the vCSA deployment is complete. Click Close to exit the wizard.

vsphere-67-install-vcsa-25

To access the Appliance Management, type the address https://IP_vCSA:443 in your favorite browser and enter the root credentials. Click Login.

vsphere-67-install-vcsa-26

The Appliance Management dashboard.

vsphere-67-install-vcsa-27

To access the vCSA through the vSphere Client (HTML5 based), type the address https://IP_vCSA/ui in your favorite browser and enter the administrator@ssodomain.local credentials. Click Login.

vsphere-67-install-vcsa-28

The vSphere Client 6.7 dashboard.

vsphere-67-install-vcsa-29

When the vCSA deployment procedure has been completed, you can start configuring your environment by creating vSphere objects such as datacenters, clusters, and so on.

A fresh install is a suggested option if you are managing a small environment or if the vCenter Server in use is pretty messed upPart 2 will cover the upgrade from an existing vCSA 6.5 to the new 6.7 version.

 

ادامه مطلب

Physical to Virtual Migration – Part 3

Physical to Virtual Migration – Part 3

  • Physical to Virtual Migration

This is the last part of the article on the Migration of physical machines to the VMware virtual environment.

In the first part of the series, we looked at the basics that need to be understood before migrating your workloads from physical to virtual. In the second part, we looked at VMware’s free migration tool – VMware vCenter Converter Standalone, and how to perform P2V migration using it.

In this last & third part of the series, we’ll look at a powerful solution – Vembu BDR Suite that offers data protection as well as ensures seamless cross-platform migration.

Vembu BDR Suite Overview:

Vembu BDR Suite is a comprehensive backup & DR solution designed to protect the data across physical, virtual and cloud workloads.

Vembu BDR Suite offers:

  • Agentless Backup & Replication for VMware VMs
  • Host-level backups for Hyper-V VMs on the cluster, SMB & CSV
  • Disk-Image Backup for Physical Windows Servers & Workstations
  • FIle & Application Backup for Windows, Linux & Mac
  • Disaster Recovery – Backup to offsite, cloud & tape

Vembu BDR Suite is available in different editions (Free/Standard/Enterprise) to make it ideal for businesses of all sizes and types.

Vembu BDR Suite Free Edition, exclusively for businesses that couldn’t spend on data protection expenses due to budgetary constraints. This edition contains all the basic features that are necessary for complete data protection and is free forever.

Vembu also offers an exclusive package – Vembu BDR Essentials, specifically for small & medium businesses who wish to protect their data with enterprise-level features but don’t want to spend extravagantly. This package is suitable for businesses with VMware & Hyper-V environments having upto 10 Sockets or 100 VMs.

Along with Backup & Disaster Recovery features, Vembu BDR Suite also supports the migration of your workloads across different hypervisors and platforms. The best thing is, cross-platform (P2V, V2P) and cross-hypervisor (V2V) migration feature is available in all the editions of Vembu BDR Suite.

Now, let’s look at the step by step process of how to perform P2V migration (Physical to VMware environment) using Vembu BDR Suite.

P2V migration with Vembu BDR Suite

Using Vembu BDR Suite, you can download the image of your backed up physical machines in different virtual formats – VHD, VHDX, VMDK, Flat-VMDK and RAW. These file formats are used to convert a physical as a virtual machine.

I’ve tested this by converting one of my physical 2012 SQL servers to VMware Platform and it worked perfectly.

Let’s look at this process in a detailed manner:

Step 1: Download and Install Vembu BDR Suite

Step 2: Perform the image-backup of your physical machine

  • Add your physical host providing administrative credentials
  • Choose disk/volumes
  • Enable App-Aware process, if you have any VSS aware applications – Exchange, SQL.
  • Set the scheduling & retention Policies

Check out this video tutorial for a detailed backup configuration.

Step 3: Once the backup is complete, navigate to the Recovery tab, Here you can view the available backups.

Click on the restore icon alongside the physical machine backup that you would like to convert as a VM.

Physical to Virtual Migration
Step 4: Select the restore option – Download and Click Next

Physical to Virtual Migration
Step 5: Choose the version of backup data you want to download for the migration from the listed restore points and Choose the disks that you want to download, then Click Next

Physical to Virtual Migration
Step 6: Choose the virtual format based on the target hypervisor where you are going to migrate your physical machine. Also, provide the restore location where to download the virtual disk format and Click Next

Note: Here we are migrating to VMware vSphere platform, so choose the Flat-VMDK format

Physical to Virtual Migration
Step 7: Review the restore configuration and Click Restore Now

Physical to Virtual Migration
Step 8: Click OK to confirm and start the download

Physical to Virtual Migration
Step 9: From the recovery option, you can monitor the progress of the restore by clicking the Job Status option

Physical to Virtual Migration
Physical to Virtual Migration
Also, you can verify the downloaded file from the path you have provided earlier.

Physical to Virtual Migration
Step 10: Next, Browse the Datastore on the ESXi host and Upload the Flat-VMDK and VMDK file.

Physical to Virtual Migration
Step 11: Login to the ESXi host. From Virtual Machines option, click on create/register VM for new VM creation

Note: If your ESXi host is part of vCenter you can perform this from vCenter Server also.

Physical to Virtual Migration
Step 12: Select the Creation type – Create a new virtual machine and Click Next

Physical to Virtual Migration
Step 13: Provide a Name to the Virtual Machine, Select Guest OS compatibility, OS Family, Guest OS version and Click Next

Physical to Virtual Migration
Step 14: Select the Datastore and click Next

Physical to Virtual Migration
Step 15: From here you can remove the default 40 GB Hard Disk1 and add the downloaded vmdk file using add hard disk.

Physical to Virtual Migration
Physical to Virtual Migration

After Removal of Default Hard Disk 1
Step 16: Click on Add hard disk and select the Existing hard disk

Physical to Virtual Migration
Step 17: Browse the uploaded file and Select

Physical to Virtual Migration
Once the Drive is attached, Click Save

Physical to Virtual Migration
Step 18: Verify all the details and click on Finish

Physical to Virtual Migration
Step 19: Now the physical server is migrated as a virtual machine and you can Power ON.

Physical to Virtual Migration
After powering on the server it will be the same as your physical server, IP, Hostname and the application will be running perfectly.

Physical to Virtual Migration
Step 20: Open the Console and Login now to the server.

Physical to Virtual Migration
Follow our Twitter and Facebook feeds for new releases, updates, insightful posts and more.

ادامه مطلب

Physical to Virtual Migration – Part 2

Physical to Virtual Migration – Part 2

  • v2p

In the first part of the series, we looked at the basics that need to be understood before migrating your workloads from physical to virtual – the difference between Physical and Virtual infrastructure, Pros and Cons of Virtual environment, and considerations that need to be checked before migration.

In this second part, we will take a look at the overview of the VMware free migration tool – VMware vCenter Converter Standalone, and how to perform P2V migration using it.

VMware vCenter Converter Standalone

VMware’s vCenter Converter Standalone is a free tool that lets you easily automate the process of creating VMware virtual machines from physical machines (running Windows and Linux) and other virtual machine formats.

vCenter Server Converter has a centralized management console where you can perform multiple simultaneous conversions quickly, consistently without any interruptions or downtime and monitor the progress from the same console.

vCenter Server Converter Standalone Components

vCenter Server Converter Standalone consists of four components:

  1. Converter Standalone server
  2. Converter Standalone worker
  3. Converter Standalone client
  4. Converter Standalone agent

Converter Standalone server

The standalone server enables and performs the import and export of virtual machines.
The Converter Standalone worker service is always installed with the Converter
Standalone server service.

Converter Standalone agent

The Converter Standalone server installs the agent on Windows source machines to import
them as virtual machines. There are two options available, you may choose to remove
the Converter Standalone agent from the source machine automatically or manually after the
import is complete.

Converter Standalone client

The Converter Standalone server works with the Converter Standalone client. The client
component consists of the Converter Standalone user interface, which provides access to
the Conversion and the Configuration wizards and lets you manage the conversion and the
configuration tasks.

VMware vCenter Converter is designed for converting physical machines and virtual machines for use in VMware hosted and managed products. You can use vCenter Converter Standalone to perform various types of conversion tasks.

  • Converting a physical machine as a virtual machine to standalone ESXi hosts or to ESXi hosts managed by vCenter Server
  • Converting a virtual machine as a virtual machine to standalone ESXi hosts or to ESXi hosts managed by vCenter Server
  • Convert a virtual machine from VMware Workstation or Microsoft Hyper-V Server to ESXi hosts managed by vCenter Server
  • Export virtual machines managed by vCenter Server hosts to other VMware virtual machine formats
  • Configure virtual machines managed by vCenter Server so that they are bootable and install VMware Tools or customize their guest operating systems
  • Customize guest operating systems of virtual machines in the vCenter Server inventory
    Migrate legacy servers to new hardware without reinstalling operating systems or application software
  • Perform migrations across heterogeneous hardware
  • Modify the volume sizes and place volumes on separate virtual disks

VMware vCenter Converter Installation

vCenter Converter Standalone can be installed on a physical or a virtual machine. There are a few methods available to install the VMware vCenter Converter.

Local Installation on Windows

The local setup installs the Converter Standalone server, Converter Standalone agent, and
Converter Standalone client for local use.

Client-Server Installation in Windows

Perform a client-server installation so that you can create and manage conversion tasks
remotely. With this option, you can select the Converter Standalone components that you
want to install on your system.

Command-Line Installation in Windows

Use this option to install Converter Standalone from the Command Prompt or by writing a
Windows batch file (.bat) to automate the installation process.

Refer the VMware Documentation for CLI based installation details

Prerequisites of vCenter Server Installation

  • Verify whether your system meets the Converter Standalone system requirements. Refer the VMware Documentation for System Requirements
  • Verify that you have Administrator privileges
  • If you have an earlier version of Converter Standalone agent on the system, uninstall Converter Standalone agent
  • Required Ports are opened in the network for HTTPS, HTTP, Agent services

vCenter Server Installation procedure

Download the vCenter Converter Standalone from the VMware Web site. Double-click/Right Click and run the VMware-converter file you have downloaded.

From the Welcome Screen, click Next.

p2v
Read the End-user Patent Agreement and click Next

p2v
Select I agree to the terms in the License Agreement and click Next.

p2v
From Destination Folder page, select the location to install Converter Standalone and click Next.

p2v
On the Setup Type page, choose the required option and Click Next

p2v
Note: We have already discussed the components, refer that for planning Client-server installation method

From User Experience Settings page, if you like to join the Customer Experience Improvement Program, select the checkbox else deselect and click Next.

p2v
From the Ready to Install page, click on Install.

p2v
It will take few minutes to complete installation and you can view the progress over there

p2v
On the Installation Completed page, click Finish.

Note: – A prompt might ask you to restart your system. Also there is an option Run Converter Standalone Client now available, select the checkbox if you want to start the application after click Finish. if you like to Run the application later manually, deselect the checkbox and click Finish

p2v
VMware vCenter Server Console is opened and you can start the P2v or V2V migration

p2v

PHYSICAL TO VIRTUAL (P2V) MIGRATION USING VMWARE vCENTER CONVERTER

Prerequisites

  • Microsoft Windows version of the machine is supported form the VMware Docs
  • Check the Source Type Support From VMware Docs
  • Converter Standalone server machine has network access to the source machine
  • Turn off windows firewall /any other firewall application on the source machine
  • Disable or Stop anti-virus software temporary on the Source
  • Disable simple file sharing on the source machine
  • Local Administrator Access
  • Windows Vista and later, either use an administrator account for Converter Standalone or Turn off UAC
  • For Windows 8 or later the source machine, turn off Remote UAC
  • Make sure that no other conversion job is running on the source
  • Remove / Uninstall previous installations of vCenter Converter

Physical to Virtual (P2V) Migration

Open the VMware vCenter Converter and Click on Convert Machine

p2v
Select the source as Powered on and Remote Machine Windows/Linux or this Local Machine

Here we are selecting the source type as “Powered on” and “Remote Windows Machine. Since we are performing the conversion of Remote windows machine.

p2v
Note:– Power Off option for powered off VMware Infrastructure virtual machine, VMware Workstation , VMware Virtual machine backup images and to convert Hyper-V virtual machine to vSphere Virtual Machine

Provide the remote power on machine IP address and Administrator credentials and Click Next

p2v
VMware Converter will install the “Converter standalone agent” on the remote windows machine.

Then, you can choose one of the options to uninstall Converter agent. Here we choose “automatically uninstall the files when import succeeds.” Click on Yes

p2v
Once converter agent is successfully installed on the remote windows machine, you will get option to choose the destination system.

Select “VMware Infrastructure virtual machine” from the destination type and specify the vCenter Server or ESXi server hostname or IP address along with the admin credentials and Click Next

p2v
You may ignore the Certificate Warning by Clicking Ignore.

p2v
If you choose the destination as VMware Workstation you will get screen as shown below

p2v
Once Converter connected to vCenter Server the current inventory will be visible. Destination VM name will be automatically generated, name will be FQDN as default and you may modify that. Select the data center location or folders to deploy the virtual machine and Click next.

p2v
Select the ESXi host or cluster and datastore to place the converted virtual machine. Also, you may choose the virtual machine hardware version from the drop-down.

Click on Next to continue.

p2v
Modify the current configuration of the remote machine with available options and settings and click Next. You can click on Edit option to modify the parameters for the conversion task, below are the available options

  • Data to Copy – From this option you can copy all disks to the destination or select the volumes to be copied, also you can configure the destinations with multiple datastores
  • Devices – To modify the number of processor Sockets, Cores, and Memory for the Destination Virtual Machine. And configure a Disk Controller for the Destination Virtual Machine
  • Networks – Modify Network Adapter Type and VLAN settings of the Destination Virtual Machine
  • Services – Configure the Source and Destination services status, you can stop the required services form source and destination select startup mode as Manual, Automatic or Disabled
  • Advanced Options – You can perform below operation from advanced settings
    • Customize the Windows Guest Operating System with below option
      • Enter the Windows License Information
      • Set the Time Zone for the Destination Virtual Machine
      • Configure the Network Adapters
    • Install VMware Tools on the Destination Virtual Machine
    • Remove System Restore Checkpoints
    • Throttling
    • Configure the Network for the Helper Virtual Machine
  • Throttling – Control the CPU resources and network bandwidth

p2v
From Summary page review all the conversion parameters and click on Finish to start the P2V conversion.

p2v
Once the conversion started, you can monitor the progress from the VMware converter Client. Based on the amount of data and network transfer speed, the client will display the estimated time to convert the virtual machine.

p2v
Once the P2V Migration is completed successfully check the conversation status .

As per our migration it took 1 hour 45 minutes and the average transfer rate is 10.7 MB\s.

p2v
Now you can shut down your physical server and login to your vCenter Server and power on the converted machines.

Conclusion

Thus, we have successfully converted the physical machine as a virtual machine to a VMware vSphere environment using vCenter Converter.

In our next article – the last part, we’ll look at a powerful solution that offers data protection as well as seamless cross-platform migration across multiple hypervisors (V2V), and across different workloads (P/V).

Follow our Twitter and Facebook feeds for new releases, updates, insightful posts and more.

ادامه مطلب

Physical to Virtual Migration – Part 1

Physical to Virtual Migration – Part 1

  • P2V

This article on the migration of physical machines to the VMware virtual environment will be a three-part series.

In this first part, we will take a look at the following:

  • Difference between Physical and Virtual infrastructure
  • Benefits of migrating to a virtual environment
  • Pros and Cons of Virtual environment
  • How to move from physical to virtual
  • Considerations to be checked before migration

In the second part, we will take a look at the overview of VMware free migration tool – VMware vCenter Converter, and how to perform P2V migration.

In the third part of this series, we’ll look at a powerful solution that provides data protection and also ensures seamless cross-platform migration across multiple hypervisors (V2V), or across different workloads (P/V).

Difference between the Traditional Physical & Virtual infrastructure

Traditional Physical Infrastructure

In this, the resources and components of a physical server are not shared between multiple users. Each physical server includes own memory, processor, network connection, hard drive, and an operating system (OS) for running programs and applications.

Typically, in the physical infrastructure, the servers don’t have a sufficient amount of resources or they don’t completely utilize the allocated resources such as CPU, RAM, Storage. This is because many of the servers sit idle as the workload is distributed to only a few servers on the network. In addition to that, the physical servers also consume a lot of power and require separate maintenance.

Virtual Infrastructure

Virtualization means the creation of virtual resources such as a server, desktop, operating system, file, storage or network. Virtualization allows you to utilize the computing resources completely by partitioning a physical server into multiple virtual servers, defining each server a specific OS and application. These virtual servers look and act like a physical server but are highly scalable and resources can be used efficiently.

Benefits of migrating to a virtual environment

Infrastructure Footprint Reduction

Consolidation of servers with virtualization will reduce the overall footprint of your infrastructure with minimal energy utilization, efficient utilization of resources, less networking gears and of course only a smaller number of racks is needed. All these valuable points will result in good savings for the company.

Break Hardware Aging

Nowadays technology is evolving much faster and it demands higher infrastructure requirements when it comes to processor speed, energy efficiency, RAM size which often leads to buying new servers or replacing existing. All your applications running need to be based on the current hardware specifications and technology advancements which will obviously be a challenge in your IT budget.

Aging infrastructure brings additional costs as it results in performance degradation, rising maintenance costs, energy inefficiencies, an increase of unplanned downtime and more. Virtualization abstracts the underlying hardware and gives more flexibility, better performance, right resource allocation & utilization when compared to physical servers.

Test and Development Environment

Using virtualization you can easily build an isolated test and dev environment which drastically reduces the investment for building an infrastructure for testing and development purposes. Traditional physical infrastructure to virtual infrastructure migration will free up many servers which you can utilize to build a test and dev environment.

Ease of Management

Comparing to traditional physical infrastructure, virtual infrastructure is very easy to manage. In the traditional way, you must access individual servers to access the operating system and application whereas in a virtual environment from a single logon you can access all virtual machine console. Virtualized environment is not limited to maintenance and access, it has also other great capabilities like disaster recovery, security, server provisioning, monitoring, and automation.

Legacy Applications Support

Legacy Applications will not run in modern operating systems or hardware. Due to hardware failures or any other issues, companies face challenges to run the application. In such a case, moving to VMware Virtualized environment will be the best option to keep running the legacy application. Virtualizing your infrastructure and migrating the application to a virtual environment will extend the use of the application with higher uptime.

Moving to Cloud

From past years, we all know about virtualization and many organizations are moving their infrastructure from Physical to Virtual. And Cloud is the next journey of virtualization and moving to a virtualized environment from physical infrastructure is the first step to move into the cloud.

From Virtual infrastructure, you can easily move to a private cloud environment or you can migrate directly to public clouds like Azure, AWS, etc. Organizations should prepare for the new technology and be ready for the transformation, so it’s very important to convert your physical infrastructure to Virtual.

Pros and Cons of Virtualization or Virtual environment

Pros

Lower CAPEX

By virtualizing the Infrastructure, organizations will have great cost savings in the area of 50 percent on hardware, power, and cooling. Consolidating multiple applications by migrating from physical servers to one virtualized host will reduce the hardware cost on the server and its components also. The number of application servers reduced will lead to more savings on server/storage hardware, rack space, power & cooling, network, cables, and parts like keyboard, mouse and finally, your capital expenses will be reduced.

Lower OPEX

Virtualizing the Infrastructure will reduce the number of servers and equipment used, which will help to reduce the OPEX. Also, you can automate several routine tasks such as reporting, applying patches, etc. Finally, it reduces the need for hands-on management and reduces your business’s operational costs. The IT staff can provide high-quality service instead of spending servers hours to keep the systems up to date.

Increase Infrastructure & Application Availability

By utilizing Virtualization, organizations can manage their infrastructure easily and efficiently with increased uptime. Virtualization allows to take regular backup and replicate all your servers as a complete virtualized image into separate storage or location. If any failure occurs, the backup virtual server can be used instantly.

Business Continuity

Another benefit of moving to virtualization is disaster recovery. Using solutions like VMware vSphere replication, Site Recovery Manager you can execute the fastest and most reliable recovery of the entire production infrastructure to a secondary site. Also, all data can be encrypted and kept safe on your secondary site with inbuilt encryption mechanisms.

Green IT with Energy Savings

As we mentioned earlier, lowering the size of the infrastructure there will be huge savings on energy because of less consumption. Energy efficiency and the reduction of a company’s carbon footprint is one of the significant benefits of using Virtualization.

Right Resource Utilization

Hosting an application to a physical server is really wasting almost 80 % of the resources of the server. With virtualization, you can consolidate multiple servers to a single server which helps the right utilization of the resources. And your business is getting the most out of your hardware and resource investments with efficient resource management.

Flexible and Scalable

Virtualized infrastructure is easy to manage, it provides a centralized view and access to Infrastructure. The same way you can scale up the infrastructure by adding new hosts or upgrade the resources without impacting any business operations. And, if there is a new application requirement you don’t need to buy a complete physical server and wait for the normal long process; you can provision in virtualized infrastructure easily.

Cons

Upfront Cost

You have to invest in the virtualization software and maybe new hardware required for the virtualization platform. Most organizations have enough resources to move to virtualization without demanding more money. If you have an infrastructure that is very old and not compatible with virtualization software, then you must consider an initial budget that may be a pain area.

Application Compatibility

There are some applications that are not supported in virtualized environments. So, we need to perform an assessment of existing physical infrastructure before migration.

Expert Virtualization Skill

To manage a virtualized environment, need virtualization expert engineers in an organization. For the application team or end-user, the virtualized environment is like a traditional physical environment.

How to move from Physical Infrastructure to Virtual Infrastructure?

You can easily migrate your physical Infrastructure to VMware Virtual environment using VMware free tools and other third-party tools.

P2V conversion

You can turn your Windows and Linux physical machines into VMware virtual machines which act as a physical machine with all your saved data hosted application without any issue. This migration process generally referred to as physical to virtual (P2V) conversion.

VMware has its own VMware vCenter Converter to perform this migration, which is free of cost. vCenter Converter supports many source physical machines, including Windows and Linux desktop and server editions. It also supports the conversion of third-party virtual machines like Hyper-V and KVM. VMware vCenter Converter converts local and remote physical machines into virtual machines without any downtime.

Considerations to be checked before migration

When planning to migrate to virtual infrastructure, the first thing to do is migration assessment.

Migration assessment is collecting complete infrastructure details of the existing environment which includes Network, Servers, Storage, Operating System, and Applications.

Check the below points before starting the migration:

    1. Create a checklist for collecting the existing infrastructure details, you may collect the details to an excel sheet based on category for easy management

Server Details

      • Fully Qualified Server Name
      • Operating System Type
      • Server Make and Model
      • Number of CPU sockets
      • Number of CPU cores
      • Amount of physical memory installed
      • Current CPU & Memory usage
      • Any hardware dongles connected to server and details
      • Any server application licenses are binding to a MAC or IP address?
      • Prior to migration, any defragmentation performed
      • Antivirus Installed on the Server or not
      • Antivirus Name and Version
      • Any Network Share configured, collect the details (Share Name & Path )

Network

      • Number of Network Interface Cards
      • VLAN’s associated with each NIC including trunk or access mode
      • Complete IP address which can obtain from ipconfig or all for each NIC
      • Remote Management IP Address for the server (ILO /iDRAC etc.)

Storage

      • Physical disk capacity with Driver Letters, Raid, and Disk Type
      • Current physical disk usage with a drive letter
      • Storage Make and Model
      • Storage Management IP Address
      • Any NFS or CIFS Configured and details
      • iSCSI or SAN storage Connected with Server
      • iSCSI Server IP Addresses
      • IQN (iSCSI qualified name) of Physical Server and associated IP Address
      • iSCSI LUN Name, Size, type, and configured server details
      • iSCSI LUN is shared with more than one server or not
      • iSCSI shared servers Name
      • FC Storage Make and Model
      • FC Storage management IP address
      • FC Switch Name and IP address
      • FC LUN Name, Size, type, and configured server details
      • FC LUN is shared with more than one server or not
      • LUN shared servers Name
      • WWN Number of Server HBA’s
      • WWN Number of Storage HBA’s
      • Zoning Information

Operating System

      • Server Operating System
      • Operating System Licensed or Not
      • Operating System has full Updates

Application

      • Application Name
      • Serve Name where Application installed
      • Application installed on which Drive of Server (Driver Letter)
      • Application is Clustered or not
      • Any Shared Storage is Presented for the Application
      • Any Dependency with additional Hardware devices like USB dongles
      • Any application licenses are binding to the MAC or IP address of the server?
      • Server Name / IP and MAC binding details of the Application
      • Application Owner Information
      • Compatibility of the Application in Virtualized Environment
      • Application Downtime

License

Necessary License details of Operating System and Application, which is very much required for licensing compliance.

Access Details

      • Local administrator credentials for the server
      • Remote access types like RDP or any other tools
      • Remote management access information (ILO, iDRAC, etc.)
      • Active directory domain admin details

Based on the above details you can plan how resources should be allocated for the servers after migration. For smooth migration, we recommend modifying the resources setting after the migration and verify whether the Operating system and application is working perfectly. The checklist will help you assign resources properly and save the cost of infrastructure.

    1. Create a checklist for collecting the VMware vSphere environment details to plan the migration smoothly. We need this information very accurate for configuring the servers and applications in a virtualized environment after migrationM

Virtual Infrastructure

      • vCenter Name
      • vCenter Access details
      • Datacenter, Cluster and ESXi Name
      • ESXi IP Address
      • Port Group Name and VLAN ID’s
      • Configured (FC / iSCSI) LUN Name, Type and name and IP of connected ESXi hosts
    1. Verify VMware Infrastructure configuration is standard and followed the best practices
      For better performance, proper management and easy maintenance and migrations, virtualized Infrastructure should be configured with standards followed by VMware best practices

Let’s check a few points which help to create standard VMware Infrastructure

    • VM Name and Guest OS Name should be the same
    • VMware Tools should be updated
    • VM Hardware Version should be Latest
    • Unwanted Virtual Hardware’s can be removed, example – Floppy Drive
    • ESXi and vCenter with N-1 version, where N is the Latest Supported Version for Hardware
    • If there is no IPV6 in the environment, disable in guest OS and ESXi
    • ESXi Local Datastore Naming – ESXI Name_LOCAL, example VMARENA-ESXI-01_LOCAL
    • Shared Storage Naming – Storage Array Model-VMDATASTORE-XX, example VMAX-VMDATASTORE-01 for Dell EMC VMAX Storage LUN
    • For placing some Application in Specific Datastore, better use naming Storage Array Model – APPLICATION NAME DATASTORE-XX, example VMAX-EXGDATASTORE-01 for Exchange
    • Port Group Name – VLAN_VLANID, example VLAN_191
    • Separate vmdk’s for each logical volume in VM, example C-drive, D-drive should be in separate VMDK
    • Virtual Machine Network Card Model – VMXNET3
    • Separate vSwitch for Management, vMotion and VM Network with redundant network adapters, Management Network – 1G, VMotion and Production 10G network will be best options, applicable for Standard and Distributed
    • For SMB Management and vMotion can be on Single vSwitch with 1G connection and VM network in Sperate vSwitch 10G or multiple 1G Connections
    • Separate vSwitch for iSCSI Configuration in ESXi
    • Place the Virtual machines in Separate Folders with application or Department names for better management and Access control
    • Configure LDAP / Active Directory Authentication with vCenter & ESXi hosts
    • NTP Configuration with NTP Server
    • Separate domain accounts for operations like backup, monitor, etc
    • Provision LUN in thin mode from Storage to vSphere environment
    • Create virtual Machine VMDK in such manner Thin – For less write IO and utilization, Thick
    • Lazy – Minimal write IO and Utilization, Thick Eager – High write IO, example – For OS thin, Application and Databases Thick Lazy / Eager based on application type
    • Configure multipathing policy on all Luns, refer Storage Vendor recommendation
    • Configure VAAI Configuration as per vendor guidelines
    • Add the Annotation with required details such as VM creation date, owner, etc. for VM’s
    • Application Cluster Setup Configuration – SCSI bus sharing type define

As an initial setup for physical to virtual migration above-mentioned points will help. Also, there are many more options available that help to create Infrastructure more secure, you can refer to VMware’s best practice guide for the same. After collecting all these details, prepare a migration plan and discuss with respective owners for downtime and other details.

In this article, we looked at the basics that need to be understood before migrating your workloads from physical to virtual as well as its pros & cons.

In our next article, we will look at how the P2V migration is done using VMware vCenter Converter.

Follow our Twitter and Facebook feeds for new releases, updates, insightful posts and more.

ادامه مطلب

همه چیز درباره گرافیک NVIDIA GRID vGPU

همه چیز درباره گرافیک NVIDIA GRID vGPU

در این مقاله قصد داریم به صفر تا صد گرافیک NVIDIA GRID vGPU بپردازیم. با‌ توجه به حجم کاری سرور ها در سال‌ های قبل، وعده مجازی‌ سازی‌ دسکتاپ قابلیت انعطاف و مدیریت بیشتری را داشت. ابتدا مجازی‌ سازی‌ دسکتاپ درجایی استفاده شد که انعطاف و امنیت، نقش اساسی و مهمی را بر اساس ملاحظات هزینه‌ ای و مالی ایفا می‌کردند.

از پنج سال گذشته، با‌توجه به پیشرفت در ذخیره‌سازی و پردازنده‌ های چند هسته‌ ای، هزینه‌ های مجازی‌ سازی دسکتاپ خیلی سریع سیر نزولی را به خود گرفته‌ اند اما در‌ گذشته تکنولوژی‌ های گرافیکی مانند CPU و ذخیره‌ ساز ها پیشرفت زیادی نداشته است. به‌ همین دلیل در کاربرد های مجازی‌ سازی‌ دسکتاپ که نیاز به گرافیک بالا بوده استفاده از مجازی‌ سازی دسکتاپ از نظر مالی مقرون به صرفه به نظر نمی‌ رسد.

چرا انتخاب گرافیک NVIDIA GRID vGPU

تلاش‌ های زیادی برای حل این مشکل، با به اشتراک‌ گذاری تکنولوژی GPU انجام‌ شده است که می‌توان به vSGA اشاره کرد که از نظر مالی، مقرون‌ به‌ صرفه بوده است. ولی این تکنولوژی‌ ها برنامه‌ های حرفه‌ ای را پشتیبانی نمی‌کنند چرا که نیاز به موفق‌ شدن و حصول اطمینان کار از طرف کاربر نهایی محقق نشده‌ است. این موضوع با GPU اختصاصی و مجزا که از‌طریق vDGA که ارائه‌ کننده تطبیق و سازگاری ۱۰۰٪ با برنامه‌ ها است، مقایسه می‌شود. اما تنها برای بالاترین موارد استفاده نهایی با توجه به هزینه‌ های بالای با تراکم محدود از ماشین‌ های‌ مجازی در هر سرور میزبان می‌ باشد.

شما با نرم‌ افزار Horizon View، قادر به متمرکز ساختن و مدیریت آسان شبکه‌ هایی هستید که به‌ صورت سنتی پیچیده، گران و دارای ایستگاه و دسکتاپ‌ های چند قسمتی می‌ باشند. در شکل زیر از سمت چپ به ترتیب نحوه کارکرد سه روش VMWare vSGA، NVIDIAGRID vGPU و GPU Pass-through NVIDIA GRID را مشاهده می‌نمایید که در شرح هرکدام به تفصیل بیان شده‌است.

معرفی انواع کارت گرافیک NVIDIA GRID

NVIDIA GRID vGPU از کارت‌ های‌ گرافیکی‌ GRID K1 NVIDIA و NVIDIA GRID K2 پشتیبانی می‌ کند. در شکل زیر یک کارت گرافیک GRID K2 را مشاهده می‌ نمایید. همانطور که می‌بینید این مدل دارای دو GPU بر روی برد خود می‌ باشد. اگر برای شما عملکرد و کارایی بیش از تعداد کلاینت‌ های مجازی اهمیت دارد، باید از این مدل استفاده نمایید.

چرا انتخاب گرافیک NVIDIA GRID vGPU

در زیر نیز یک مدل دیگر یعنی GRID K1 را مشاهده می‌نمایید. این مدل دارای ۴ GPU برروی برد خود می‌باشد. اگر برخلاف GRID K2 تعداد کلاینت‌های بیشتری را نیاز دارید و تعداد کلاینت‌ها نسبت به کارایی و عملکرد از اهمیت بیشتری برخوردار است، این مدل کارت گرافیک، مناسب‌ تر می‌باشد.

در جدول زیر ویژگی‌های سخت‌ افزاری دو مدل کارت‌ گرافیک GRID K1 و GRID K2 را مشاهده می‌نمایید. از ویژگی‌ های مهم این دو مدل کارت‌ گرافیک، می‌ توان به موارد زیر اشاره کرد.

  • GRID K1 دارای ۷۶۸ هسته(CUDA) و GRID K2 دارای ۳۰۷۲ هسته(CUDA) می‌ باشد.
  • GRID K1 دارای ۱۶ گیگابایت حافظه و GRID K2 دارای ۸ گیگیابایت حافظه می‌ باشد.


چرا NVIDIA GRID VGPU را باید انتخاب کنید

همانطور که در جدول زیر مشاهده می‌نمایید، هر GPU فیزیکی می‌تواند چندین نوع vGPU متفاوت را پشتیبانی کند. هر نوع از vGPU دارای یک ‌میزان ثابت از حافظه رم، تعداد صفحه‌ نمایش قابل پشتیبانی، بالاترین میزان رزولوشن و همچنین استفاده از چندین کلاس متفاوت حجم‌کاری می‌ باشد.

به‌ عنوان مثال اگر کارت گرافیک GRID K1 را برروی حالت GRID K160Q قرار دهید، می‌تواند در قالب ۴ گرافیک مجازی(VGPU) با ظرفیت رم ۲۰۴۸ مگابایت عمل کند.

چرا از کارت های گرافیک Grid برای مجازی سازی استفاده می شود.

پروتکل‌های گرافیکی قابل پشتیبانی در این کارت‌گرافیک از قرار زیر می‌باشند.

  • Full DirectX 9/10/11, Direct2D
  • (DirectX Video Acceleration (DXVA
  • OpenGL 4.4
  • (NVIDIA GRID SDK (remote graphics acceleration

موارد زیر در این نسخه از vGPU پشتیبانی نمی‌شوند.

  • CUDA
  • OpenCL

برای CUDA و OpenCL، استفاده از vDGA پیشنهاد می‌شود که البته در این کتاب به آن اشاره‌ای نشده‌ است.

ادامه مطلب

مجازی سازی دسکتاپ

مجازی سازی دسکتاپ

VMware Horizon بهترین راهکار مجازی‌سازی دسکتاپ

Horizon 7 با استفاده از بهترین‌ امکانات Mobile و Cloud توانسته است تحول بزرگی را در VDI یا مجازی‌سازی دسکتاپ ایجاد نموده و مزایایی همچون سادگی، امنیت، سرعت و مقیاس‌پذیری را با حداقل هزینه برای کاربران به ارمغان آورد. علاوه بر آن سرعت عملکرد را تا 30 برابر افزایش و در عین حال هزینه‌ها را نسبت به راهکارهای سنتی تا 50% کاهش داده است.

VMware Horizon مجازی سازی دسکتاپ

این تکنولوژی به عنوان یک راهکار Hybrid Cloud واقعی با یک کنسول واحد مدیریتی (single pane of glass)، تمام برنامه‌های کاربردی و دسکتاپ‌های مجازی را به سرعت و سادگی یا از سرویس Cloud یا به صورت On- Premise ارائه و مدیریت می‌نماید.

شرکت مهندسی امن پایه ریزان کارن APK با مطالعه و بررسی نیاز سازمان ها این تکنولوژی را راهکاری بسیار مناسب برای کاهش هزینه های خرید سخت افزار PC برای کاربران و همچنین مدیریت هر چه سادتر سیستم عامل های آنها معرفی نموده و این تکنولوژی با کاهش بارکاری مدیران شبکه برای نصب برنامه های کاربردی و همچنین وصله های امنیتی و … راهکاری بسیار موثر برای مدیریت یکپارچه کاربران از سوی شرکت مهندسی APK به سازمان ها پیشنهاد می گردد. شرکت مهندسی APK با تجربیات متعدد در پیاده سازی این تکنولوژی، در ادامه به تشریح بخشی از قابلیت های منحصر به فرد این تکنولوژی می پردازد.

ارائه دسکتاپ و برنامه کاربردی به عنوان سرویس

دسترسی به این سرویس‌های برنامه‌ کاربردی و دسکتاپ شامل برنامه‌های کاربردی RDS-Hosted، برنامه های کاربردی SaaS، برنامه‌های کاربردی مجازی‌سازی شده‌ی Citrix و همچنین برنامه‌های کاربردی Package شده با ThinApp از طریق یک فضای کاری یکپارچه برای کاربران نهایی فراهم شده و تمامی منابع مورد نیاز را با سرعت مورد انتظار و کارایی لازم در کسب‌و‌کار برای در اختیار آنها قرار خواهد گرفت.

Desktopها و برنامه‌های ارائه شده از طریق یک پلتفرم مجزا

Desktopها و برنامه‌های مجازی یا Hosted از طریق یک پلتفرم جداگانه برای مدیریت آسان ارائه می‌گردند و بسیار آسان و سریع در تمامی موقعیت‌ها و تجهیزات در اختیار کاربر قرار می‌گیرند.

فضای کاری یکپارچه دیجیتال

تکنولوژی Virtual Desktop Infrastructure و یا VDI از فرآیندهایی همچون تایید اعتبار به صورت Real-Time و مدیریت احراز هویت در تمام منابع مرتبط با آن از قبیل Active Directory و LDAP پشتیبانی نموده و برای کاربران نهایی دسترسی زمینه‌ای و سفارشی به منابع  را از یک فضای کاری واحد و یکپارچه امکانپذیر می‌نمایند.

شرکت APK (امن پایه ریزان کارن) نخستین شرکت دانش محور در اجرای پروژه های انفورماتیکی کشور    تماس با کارشناسان021-88539044-5

دسکتاپ‌های Just-in-Time با استفاده از تکنولوژی Instant Clone

Horizon با بهره‌مندی از تکنولوژیInstant Clone  همراه با App Volumes‌ می‌تواند نیاز به مایحتاج مربوط به زیرساخت را تاحد زیادی کاهش داده و در عین حال امنیت را بهبود ‌بخشد.

دو تکنولوژی فوق این امکان را فراهم می‌نمایند تا سرویس‌های برنامه‌های کاربردی و دسکتاپ شخصی‌سازی‌ شده‌ی جدید در هر بار ورود (Log In شدن) برای کاربران نهایی ارائه‌ گردد.

مجازی سازی دسکتاپ VDI

ایجاد تحول در تجربه کاربران با Blast Performance

مدیریت جامع فضای کاری (Workspace)

می‌توان گفت تنها VMware این قابلیت را داراست که مدیریت برنامه‌های کاربردی و فضای کاری را به صورت End-to-End و با ویژگی‌های زیر ارائه نماید:

  • تفکیک برنامه‌های کاربردی از سیستم عامل با برنامه‌های کاربردی Containerشده
  • ارائه‌ی بلادرنگ برنامه‌های کاربردی به دسکتاپ‌های فیزیکی یا مجازی
  • مدیریت Policy و Policy‌های هوشمند برای ارائه یک سیستم‌ Real-Time و مبتنی‌بر Policy همراه با مدیریت زمینه‌ای هوشمند و مبتنی بر Role
  • مدیریت فضای کاربری برای ایجاد یک تجربه مشابه، شخصی‌سازی شده‌ و پویا از دسکتاپ در تمامی تجهیزات
  • مدیریت تصویر با قابلیت Disaster Recovery به صورت Built-In

مدیریت محیط کاربری و شخصی‌سازی برای کاربر

قابلیت شخصی‌سازی و تنظیم پویای ‌Policyها در تمام محیط‌های مجازی، فیزیکی و مبتنی بر Cloud توسط User Environment Manager ایجاد می‌شود.

ارائه برنامه‌های کاربردی و مدرن سازی مدیریت چرخه عمر با App Volumes

App Volumes با ایجاد دسترسی به دسکتاپ‌های مجازی و برنامه‌های کاربردی انتشار یافته از قبیل برنامه‌های کاربردی RDS-Hosted و Citrix XenApp، از کاربران نهایی پشتیبانی می‌نماید. بنابراین مدیریت برنامه‌های کاربردی از یک فرآیند کند و طاقت‌فرسا به یک مکانیسم چابک با قابلیت مقیاس‌پذیری بالا تبدیل می‌شود که علاوه بر عرضه‌ و مدیریت سریع‌تر برنامه‌های کاربردی، موجب کاهش هزینه‌‌های IT تا %70می‌گردد.

ارائه و مدیریت برنامه‌های کاربردی به صورت Real-Time

  • ارائه‌ی برنامه‌های کاربردی در قالب Package به منظور اجتناب از مشکلات تطبیق‌پذیری
  • آماده‌سازی سریع برنامه‌های کاربردی در مقیاس مورد نیاز
  • اختصاص برنامه‌های کاربردی به کاربران، گروه‌ها یا تجهیزات حتی در هنگام ورود کاربران به دسکتاپ شخصی
  • آماده‌سازی، ارائه، به‌روز‌رسانی و کنار گذاشتن برنامه‌های کاربردی به صورت Real Time

زیرساخت مجازی سازی دسکتاپ Horizon

  • تفکیک و جداسازی برنامه کاربردی
  • Policyهای هوشمند با دسترسی آسان
  • مدیریت Image
  • فرایند تجزیه و تحلیل و خودکارسازی

حالات مختلف پیاده‌سازی VMware Horizon به صورت On Premise، Off Premise و یا hybrid

  • بهره‌مندی از یک کنسول مدیریتی قدرتمند در Cloud با هدف مدیریت زیرساخت و کلیه سرویس‌های برنامه‌کاربردی و دسکتاپ Horizon به صورت On Premise یا بر روی Cloud
  • ارتقا و توسعه آسان در مقیاس مورد نیاز با ارائه فوق‌العاده سریع زیرساخت فوق همگرا و از پیش تعریف شده همراه با تکنولوژیInstant Clone

افزایش قدرت دیتاسنتر مبتنی بر نرم افزار شامل مجازی سازی شبکه، ذخیره‌سازی و سرور

VMware Horizon در ترکیب با سایر انواع مجازی سازی و پشتیبانی از آن‌ها، باعث بهینه سازی عملکرد و امنیت دیتاسنتر شده و در نتیجه به کاهش هزینه‌های IT، بهبود تجربه کاربران و چابکی بیشتر کسب و کار می گردد.

مثلا به همراه NSX می توان خیلی سریع و آسان policyهای امنیتی شبکه را برای کاربران نهایی (با هر ابزار و از هرمکان) ایجاد نماید، بدون اینکه نیازی به انجام تغییرات در زیرساخت فیزیکی وجود داشته باشد.

مجازی سازی NSX

شرکت APK (امن پایه ریزان کارن) با تکیه بر دانش مطالعاتی و حضور در پروژه های متعدد و همچنین استفاده از راهکارهای گوناگون مطابق با تجهیزات و نیاز سازمان ها در قالب کارگروه های تخصصی، خدمات طراحی، مشاوره و اجرای مجازی سازی را در بالاترین سطح از دانش عملیاتی برای سازمان های محترم ارائه می نماید و سازمان ها را در ارائه هر چه پویا تر خدمات خود یاری می رساند.

ادامه مطلب

مجازی سازی سرور

مجازی سازی سرور

مجازی‌سازی سرور موجب بهبود کارایی و دسترس‌پذیری منابع و برنامه‌های IT می‌گردد. این فرآیند به مدیران در کاهش انجام امور تکراری برای مدیریت سرور منجر شده و زمینه نوآوری در ساختار کسب‌و‌کار را برای آنان فراهم می‌نماید. بازار مجازی سازی سرور با توجه به سادگی، صرفه‌جویی قابل توجه در هزینه‌ها به دلیل کاهش نیاز به سخت‌افزار و بهبود کارایی سرور، به سرعت گسترش یافته است.

مزایای مجازی‌سازی VMware

  • عدم پراکندگی و پیچیدگی سرور به دلیل استفاده از بیش از 75% از ظرفیت سرور
  • مدرن سازی سیستم‌های قدیمی (re-hosting)
  • کاهش هزینه‌های سرور با استفاده از تکنولوژی مجازی‌سازی و تجمیع سرور
  • کاهش زمان خرابی و بهبود قابلیت اطمینان با ویژگی‌های تداوم کسب‌وکار و Disaster Recovery به صورت Built-In
  • ارائه سرویس‌های IT بر حسب نیاز و به صورت مستقل از سختافزار، سیستم عامل، ارائه‌دهندگان زیرساخت یا برنامه‌های کاربردی
  • کیفیت سرویس، افزایش کنترل و متمرکزسازی روند مدیریت سرور
  • دسترس پذیری بالا (HA)
  • مدیریت کلیه منابع و مانیتورینگ کل زیرساخت به صورت متمرکز و یکپارچه
  • 50 تا 70% تسریع زمان آماده‌سازی (provisioning)
  • چابکی
  • افزایش ظرفیت برحسب نیاز
  • خودکارسازی در راستای ساده‌سازی روند مدیریت، فراهم نمودن سطوح دسترس‌پذیری، عملکرد و مقیاس‌پذیری، به حداقل رساندن زمان خرابی، اختصاص منابع IT به صورت پویا و سیاست-محور و حذف وظایف نگهداری و پیکربندی‌های تکراری
  • ارائه سرویس‌های عملیاتی مهم برحسب نیاز و ایجاد دیتاسنتری با به کارگیری بیش از 80% ظرفیت خود
  • حفظ و نگهداری سخت‌افزار بدون نیاز به برنامه‌ریزی برای زمان خرابی یا قطع عملیات‌های کسبوکار

مجازی سازی سرور

دلایل انتخاب VMware برای مجازی‌سازی سرورها

هم اکنون چندین پلتفرم مجازی‌سازی در دسترس کاربران قرار دارد اما VMware در بین این پلتفرم‌ها با ارائه یک پلتفرم ایمن و معتبر، امکان دستیابی به شرایط SLA برای اکثر برنامه‌های کاربردی مهم در کسب‌و‌کار به همراه منابع فراوان را با کمترین هزینه کلی مالکیت (TCO) میسر می‌نماید.قابل اطمینان‌ترین

پلتفرم مجازی‌سازی به واسطه‌ی معماری ایمن و معتبر Hypervisor

ویژگی‌های مهم امنیتی و  معماری VMware vSphere به همراه Operations Management

ویژگی‌های مهم مجازی‌سازی VMware vSphere
Hypervisor Architecture مقیاس‌پذیری Host:320, 4TB RAM√VM: 64 vCPUs, 1TB vRAM
Hypervisor  هدفمند √بدون اتکا بر سیستم‌های عامل چندمنظوره
فرآیند Patching  ساده √بدون Patching غیرمرتبط، قابلیت خودکار، مبتنی بر تصویر با قابلیت‌های Rollback
مدیریت پیشرفته حافظه Ballooning√، اشتراک گذاری صفحات Transparent، فشرده‌سازی حافظه و تعویض با دیسک و SSD
امنیت پلتفرم فضای کوچک برای حملات √فضای دیسک کمتر از 200 مگابایت
مدیریت متمرکز امنیت √رویکرد یکپارچه‌ی سیاست‌محور که از طریق vCenter  مدیریت می‌شود.
محافظت ماشین مجازی به صورت Agentless √وجود vShield Endpoint  به صورت Built-In، آنتی ویروس به‌صورت Offload و Antimalware   برای ایمنی تجهیزات
امنیت مبتنی بر نرم‌افزار √امنیت و شبکه‌بندی vCloud* به صورت Built-InEdge، vNIC-Level Firewall،NAT و SSL VPN

 

vSphere به همراه Operations Management بهترین پلتفرم برای برنامه‌های حیاتی کسب‌و‌کار

  • ارائه یک محیط کاملا انعطاف‌پذیر، مقیاس‌پذیر، ایمن و با عملکرد بالا را جهت پشتیبانی از اصلی‌ترین برنامه‌های مهم در کسب‌و‌کار که مستلزم حداکثر دسترس‌پذیری و انعطاف‌پذیری، بالاترین سطح خدمات و دستیابی به سطح مطلوبی از SLA می‌باشند
  • ارائه مجموعه گسترده‌ای از برنامه‌ها به همراه راهکارهای جامع مدیریتی برای حداکثرسازی عملکرد برنامه‌ها
  • کامل‌ترین و قدرتمند‌ترین راهکار در مقابل Downtimeهای برنامه‌ریزی شده/نشده و خرابی‌های مهم:

مجازی سازی VMware

تداوم کسب‌و‌کار

ویژگی‌های مهم مجازی‌سازی VMware vSphere با Operations Management 5.5
تداوم کسب و کار بدون Downtime برای اکثر برنامه‌های مهم Fault Tolerance
دسترس‌پذیری بالا یا HA دسترس‌پذیری بالای با یک کلیک، مقاومت در برابر خرابی چندین Host
پشتیبان‌گیری Agentless محافظت داده‌ها: قابلیت De-Dupe به صورت Built-In
توسعه منابع در لحظه Hot-Add vCPUvRAM Hot-Plug

توسعه دیسک مجازی

Replication  مبتنی بر Host vSphere Replication
پشتیبانی و انتخاب گسترده سیستم‌عامل‌های مختلف 96 سیستم عامل مختلف شامل اکثر نسخه‌های ویندوز در مقایسه باHyper-V
ارائه‌دهندگان سرویس سازگار بیش از 7200 ارائه‌دهنده سرویسVMware
پشتیبانی ارائه‌دهندگان نرم‌افزارهای مستقل (ISV) بیش از 3600 برنامه مستقیما توسط بیش از 2000 ارائه دهنده نرم‌افزار پشتیبانی می‌شوند

 

بالاترین سطح انعطاف‌پذیری و انتخاب جهت برگزیدن سخت‌افزار و اجزای برنامه مطابق با نیاز کاربران

راهکار مجازی سازی سرور VMware vSphereمقایسه رویکرد کلی بار کاری برای VMware  با رویکردهای رقبا

  • ارائه یک پلتفرم برای پشتیبانی تمامی برنامه‌های مهم و حیاتی در کسب‌‌و‌کار به جای مدیریت Siloهای چندگانه
  • همکاری نزدیک با اکوسیستم بزرگ شرکای خود (ارائه دهندگان نرم‌افزار، تولیدکنندگان تجهیزات اصلی سیستم (OEM) و تولیدکنندگان فرعی) و درنتیجه مورد استفاده قرار گرفتن این تکنولوژی در مجموعه گسترده‌ای از محیط‌های IT  است. از جمله این شرکت‌های مهم می‌توان به موارد زیر اشاره کرد:

Adobe , IBM , Apple , Juniper Networks , Avaya , McAfee , BMC Software , Microsoft , Cisco Systems , Oracle , Computer Associates, Red Hat, Dell , SAP, EMC , Symantec, HP , TIBCO

به حداقل رساندن هزینه کلی مالکیت (TCO)

  • vSphere به همراه Operations Management، به ارائه کارایی بهینه برای سخت‌افزار، مدیریت ساده منابع و همچنین تاثیر‌گذاری بیشتر مدیریت مدیران پرداخته و موجب کاهش هزینه‌های سرمایه (CapEx) و هزینه‌های عملیاتی (OpEx) می‌گردد.
  • علاوه بر این، خودکار‌سازی هوشمند با کاهش ضرورت انجام کارهای دستی معمولا باعث کاهش هزینه کلی مالکیت می‌گردد.

افزایش کارایی دیتاسنتر بواسطه وجود vSphere به همراه Operations Management

  • 40% بهبود استفاده از ظرفیت و 37% بهبود نسبت Consolidation
  • خودکارسازی هوشمند و مدیریت ذخیره‌سازی به صورت Built-In در vSphere همراه با Operations Management و سایر راهکارهای مرتبط مانند vCenter Site Recovery Management
  • پاسخگویی سریع به مشکلات ظرفیتی یا عملکردی

شرکت APK (امن پایه ریزان کارن) با مطالعه دقیق برروی پلترفرم های مجازی سازی مختلف و همچنین پیاده سازی لابراتوارهای گسترده مجازی سازی سرور، دانش نوینی را در اجرای این زیرساخت ها در اختیار داشته و تجربه تیم اجرایی/مطالعاتی این شرکت همواره راهکارهای پیشرفته و متفاوتی را برای اجرا و بهینه سازی زیرساخت مجازی سازی ارائه می نماید. این شرکت با تجربیات موفق در این حوزه همراه آماده خدمت رسانی به سازمان ها بوده و افتخار خود می داند تا گامی درجهت پیشرفت دانش و تکنولوژی سازمان های محترم برداشته و موجبات پیشرفت علمی کارشناسان را فراهم آورد.

ادامه مطلب