Tag:

VMware

Getting Started with Tanzu Kubernetes in vSphere 8

by Philip Sellers January 20, 2023

This post is the first in a series of creating Tanzu Kubernetes on vSphere 8. I’m doing this my home lab, which I have decided to create with an Orange theme, because its not an Apple lab. (Yes, that’s cringy dad-joke territory.)

So what is done up to this point in the lab?

Purchased a Ubiquiti Dream Machine Pro as my core switch & router
Setup several VLANs for vSphere use
- Management VLAN
- vMotion VLAN
- FT VLAN
- Storage VLAN for iSCSI
- VSAN VLAN (for later)
- Servers VLAN for VM workloads
Purchased 3 x HP Z640 workstations with Xeon processors, RAM and an SSD boot disk
Setup iSCSI from a Synology NAS
Added dual 10Gb NICs to each host and added a Ubiquiti 8 port 10Gb Switch
Used 1 0 G t e k b r a n d TwinAx/DAC 10Gb cables to connect things up
Installed ESXi 8.0.0 on each host
Deployed vCenter 8.0.0
Configured a Standard vSwitch and Distributed vSwitch
Setup iSCSI software adapters, configured, connected and provisioned 2 x 1TB VMFS datastores

Deploying TKG

Tanzu Kubernetes Grid (TKG) with vSphere 8 has gotten significantly simpler, in my eyes. The wizards in vCenter 8 are great and walking a novice through the deployment of TKG in a simplistic way, however, there are somethings that flow better with the workflow if you’ve completed prep before hand.

Checklist of items to complete before the Workload Management wizard

vSphere Enterprise Plus licensing is required because DRS (and vSphere Distributed Switch) is required. HA also needs to be enabled.
You will need to make some basic network decisions around load balancing.
- You will either need to use native vSphere Distributed Switches (VDS) or NSX
- For vSphere Distributed Switches, you need a load balancer. Either deploying NSX Advanced Load Balancer or HAProxy load balancer are you two options.
- For NSX, you’ll use their internal load balancing features of NSX.
- NSX-T is supported and you can use a vSphere Distributed Switch (a converged distributed switch) but not a NSX Distributed Switch/N-DVS). You must migrate if you use N-VDS.
You need to setup and define vSphere Zones or your Tanzu is limited to a single vSphere cluster. Personally recommend setting up a zone (see below).
A storage policy is required.
Management Network – control plane VMs to the Supervisor cluster
Workload Network – traffic to the Kubernetes API, workloads, and services

vSphere Zones

Most customers are probably not leveraging vSphere Zones. This feature in vSphere is for multiple zone deployments when a customer scales to multiple colocation datacenters or clouds. I would recommend that even as you start your Tanzu journey, even if you only have a single zone – go ahead and create a single zone. This is one step in future-proofing your Tanzu installation. The whole idea of Kubernetes is enabling your cloud-native applications to be deployed across multiple clouds for resiliency. By creating your first zone, you create your first step in this journey. For more detail, see this article.

If you choose not to use vSphere Zones, you’ll need to choose a cluster to assign your Tanzu deployment onto.

New Networks for Tanzu and HAProxy (or NSX)

I created 3 new networks for Tanzu and HAProxy. The first is a Kubernetes Control Plane network. The second is a Load Balancer network. The third is a Kubernetes workload network.

The Kubernetes Control plane will be used for the HAProxy management network. This is where Tanzu will talk to HAProxy to configure and programmatically setup external access to your Kubernetes workloads. “Programatically” is the key here. Kubernetes will reach out to HAProxy and make all the magic happen automatically. While I’m talking about HAProxy – the same is true with NSX Advanced Load Balancer (aka AVI Networks) or NSX-T’s built-in load balancer.

The Load Balancer network is where your external endpoints for your workloads are going to be exposed. It is a range of IP addresses. For your production workloads, this is the network that should scale with the number of workloads you plan to have. Keep in mind, this is for the single zone (back to the previous concept) – so enough external IP addresses

HA Proxy Download and Config

Review the requirements of HAProxy Load Balancer from VMware. You can obtain the current OVA from VMware’s GitHub for HAProxy – https://github.com/haproxytech/vmware-haproxy.

As you deploy, take note of the following things that you will need during the configuration. Network settings and some backend network configuration for the HAProxy configuration is definitely required.

HAProxy Load Balancer Controller Endpoint – this is the API endpoint that Tanzu will call to configure HAProxy. This is the primary integration point of HAProxy with your Kubernetes and vSphere clusters.
Username and password configured during the HAProxy deployment
Virtual IP Address Ranges
TLS Certificate from the HAProxy appliance

I loaded the HAProxy OVA into my Content Library (aka The Barn) and then cloned a VM out from this location. It is a standard OVA deployment and you’ll be prompted for configuration to deploy. This guide does a great job of walking you through the HAProxy deployment.

Wizard, wizard

Welcome. The pre-requisites are listed and linked to documentation.

Decisions, decisions – What vCenter Server and what network technology will you use? The wizard adjust based on your choices. For a base level in the lab, I’m deploying VDS.

Next step is choosing where to deploy your Supervisor cluster – the Kubernetes cluster that controls all workload Kubernetes clusters in your deployment. This is where you can choose and associate a vSphere Zone to allow for scale and multi-zone resiliency.

You’ll choose a storage policy – easy peasy.

Next, your load balancer configuration – as noted from above for HAProxy, will be required to input and associate the stand-alone HAProxy or HAProxy cluster.

Next, you’ll use your planned management network

Lastly, your workloads will need a place to run. This is where the Kubernetes API, workloads and services will run – but the API needs to be accessible to interact with other services. Behind the covers, the Kubernetes cluster will run in its own private IP space, that is not of real concern.

Deploy.

Monitor.

Done.

January 20, 2023 0 comment

Kubernetes VMware

Error deploying VMware’s demo Tanzu Kubernetes Cluster on vCenter 8

by Philip Sellers January 6, 2023

written by Philip Sellers

For users getting started on vSphere 8 and Tanzu, after you get everything setup and configured, you’ll likely hit a snag. VMware’s GitHub hosts a quick start guide and YAML manifest for deploying your first Tanzu workload cluster. It will fail with the following error:

Error from server (unable to find a compatible full version matching version hint "1.18" and default OS labels: "os-arch=amd64,os-name=photon,os-type=linux,os-version=3.0".

vCenter and Kubernetes Versioning

Why does this error? This is a brand new cluster, after all? The answer is a versioning issue.

Tanzu Kubernetes Grid is tied to the vCenter version and since we are running vSphere 8 and vCenter 8, the release has specific Kubernetes releases it supports. K8s 1.18 is not compatible. vCenter 8.0.0.10100 releases with Tanzu Kubernetes Grid 1.6.1. The compatible versions for vCenter 8.0.0.10100 are Kubernetes 1.21, 1.22 and 1.23. The supervisor cluster deployed with vCenter 8.0.0.10100 is Kubernetes 1.23.10.

My VMware team has told me that each vCenter will ship with a specific K8 release and upgrading vCenter is the way to upgrade your Tanzu Kubernetes versions. In addition to the vCenter and Tanzu Supervisor Cluster being tied at the hip, VMware will support the current and two prior K8 releases on each vCenter version.

VMware, for its part, doesn’t do much to help the confusion of versioning – as Tanzu has its own versioning, separate from vCenter and separate from the Kubernetes releases. Tanzu Kubernetes Grid version 1.6.1 has K8 version 1.23.10 as its release. TKG 1.5.4 was K8 1.22.9, TKG 1.4.2 was K8 1.21.8.

Demo YAML File

Source: https://raw.githubusercontent.com/vsphere-tmm/vsphere-with-tanzu-quick-start/master/manifests/tkc.yaml

apiVersion: run.tanzu.vmware.com/v1alpha1
kind: TanzuKubernetesCluster
metadata:
  name: tkc-1
spec:
  distribution:
    version: v1.18
  topology:
    controlPlane:
      class: guaranteed-small
      count: 1
      storageClass: kubernetes-demo-storage
    workers:
      class: guaranteed-small
      count: 1
      storageClass: kubernetes-demo-storage
  settings:
    storage:
      classes: ["kubernetes-demo-storage"]           #Named PVC storage classes
      defaultClass: kubernetes-demo-storage          #Default PVC storage class

Troubleshooting the Issue

The first thought is, can my supervisor cluster see the library of Kubernetes images? How can I verify that? Google results point me to a post from Anthony S p i t e r i w i t h s o m e h e l p f u l t r o u b l e s h o o t i n g c o m m a n d s . After verifying that my content library was linked correctly, I ran the following command:

kubectl get virtualmachineimages

This output is a good sign. I can see that I have a LOT of images that are available to this namespace. That’s promising, but no silver bullet why I’m getting this error. Digging a bit further into Google results, I hit another kubectl command:

kubectl get tanzukubernetesreleases

BINGO. In the output, I noticed that the version I requested in the YAML was not “READY” or “COMPATIBLE” in the list.

What needs to be altered to allow this to run on vCenter 8 and Tanzu Kubernetes Grid 1.6.1?

Its a simple change – just adjust the distribution version number to 1.21, 1.22, or 1.23. The error is very helpful, in that it says it can’t find a compatible version.

Working YAML

apiVersion: run.tanzu.vmware.com/v1alpha1
kind: TanzuKubernetesCluster
metadata:
  name: tkc-1
spec:
  distribution:
    version: v1.23
  topology:
    controlPlane:
      class: guaranteed-small
      count: 1
      storageClass: kubernetes-demo-storage
    workers:
      class: guaranteed-small
      count: 1
      storageClass: kubernetes-demo-storage
  settings:
    storage:
      classes: ["kubernetes-demo-storage"]            #Named PVC storage classes
      defaultClass: kubernetes-demo-storage           #Default PVC storage class

Further assumptions – for this file to work, you need to have created a “kubernetes-demo-storage” storage policy and assigned it to the namespace where you’re running this YAML. You also need to have the default VM Class of “guaranteed-small” assigned to the namespace and available for consumption. If that’s in place, run kubectl from the same directory as the YAML file and voila, you will get a working Tanzu Kubernetes Cluster for workloads!

kubectl apply -f ./tkc.yml

Happy clustering!

January 6, 2023 0 comment

VMware

VMUG is (still) donating proceeds of Advantage Memberships to Girls Who Code

by Philip Sellers January 4, 2023

written by Philip Sellers

The holidays may be past, but goodwill and charity don’t need to end. VMUG members who subscribe or extend their VMUG Advantage membership will get a 10% discount on the membership and enfuse a contribution Girls Who Code. All that is needed is to to check out with code GIRLSWHOCODE.

VMUG is offering an extra charitable benefit to members who subscribe to VMUG Advantage through Jan 14, 2023. It is a new year, new budget – save 10% plus feel good helping young women learn to code!

VMUG members selected one of four nonprofits by a Twitter poll, with beneficiary being Girls Who Code.

Members who subscribe to Advantage still have some time to get in and help this non-profit while also getting great benefits of your own. VMUG Advantage membership gives members evaluation licenses of many VMware products for use in your home lab and for learning, it gives training discounts and a discount to VMware Explore conferenc events. Advantage also gives members access to TestDrive by VMware.

January 4, 2023 0 comment

Home Lab

Why invest in a home lab in 2022?

by Philip Sellers November 29, 2022

written by Philip Sellers

A decade ago, home labs were all the rage in my Twitter circle. I had home lab envy – I’m not gonna lie. Visions of Synology and servers dancing in my mind.

Thinking back to that time, it was also when Dell and others were shipping truckloads of hardware onsite to conference to run hands-on-labs. It was BC. You know, Before Cloud.

Cloud changed much of this for IT professionals. Instant, on-demand resources for learning and exploring are common. I can spin up a demo environment and take a test drive on most solutions quickly and easily. Many of those solutions are Cloud-native today.

After moving in 2016, I never rebuilt my home lab. For the last 6 years, I have had tons of hardware at my disposal to tinker, until I had no time to tinker.

But then, a change.

Last month, I started buying hardware components on eBay and Amazon to rebuild my lab. But, why did I decide to revive a home lab in 2022?

Not everything is cloud. I’m working with a lot of customers in a hybrid stance and there’s a lot of traditional IT that still needs to be maintained, lifecycled and upgraded.

Sometimes the cloud labs are missing core pieces of the process. While I could leverage vendor provided lab environments, most of these demos don’t start at square one. Some don’t even allow you to do the installs and instead simulate the screens. I believe there is value and lessons to be learned starting from the bare metal.

I am a hands-on learner. It is a byproduct of years of being hands-on-keyboard as an administrator and engineer. Classes and online learning modules are good for me, but never as good as simply installing a product, configuring it, breaking it, fixing it and eventually mastering it.

Goals

In terms of goals, I would say first is learning and gaining the knowledge to pass certifications. Second, is a place to try things and vet ideas.

I recently started a new role at XenTegra as a Solutions Architect. While I’m a long-time VMware SME, there’s a lot of technologies I want to learn and experiment with. I also need time to get into the weeds of the products to attain certifications, proving and certifying my knowledge through accreditation. I need to brush off those VMware Horizon skills, since it was called View when I last ran it.

One of the best parts of my job is trying things – coming up with strategies and then making sure that they work. To tinker. I feel like I need a place where I can make that happen without interrupting others and their work. My teammates are doing similar lab builds on hosted resources, but those environments are built not just for learning, they are also for show and demo. The environments have different goals – the shared should always be ready for show.

When the time comes, to be able to demo functionality. While I don’t expect my home lab to be ready to demo at any given time, I do want the ability to log in remotely and check something or show off a UI or concept when my shared lab environments aren’t available. As with anything shared, I don’t have full control – but for this little nugget, its all mine. (Insert some sort of bad cartoon villain here. I heard a cackle as I wrote that line.)

Bottom Line

I’d argue that for many, it may not make sense to build a home lab in 2022. For me, maybe call me old-school. I’m looking forward to what I learn on the way and how I can use this tiny little cluster of goodness. I think that is one of my differentiators – while I can talk strategy and architecture all day long with you – I can also run the tech and know that it’ll live up to what I’m selling you. I love having both perspectives, and the ability to translate between the two.

November 29, 2022 0 comment

Graphical user interface, text, application, email Description automatically generated

vExpert Virtualization VMware vSphere

VMware vSphere ESXi 8.0 Certificate Replacement via SSH

by Roger Lund October 29, 2022

written by Roger Lund

Today, I had an Interesting one. As this was a new install of VMware vSphere ESXi 8.0, or at least within a few days. And low and behold, it has a expired Certificate!? This is a technical write up, with the steps I performed to fix it in my own lab.

When I logged into the Host I Saw the following.

Graphical user interface, text, application, email

Description automatically generated

That isn’t good, lets go fix it.

Step 1. Google.

I found this write up by Jesus Vigo in Security

”

How to regenerate certificates on VMware host servers

https://www.techrepublic.com/article/how-to-regenerate-certificates-on-vmware-host-servers/

“By default, VMware host servers, like ESXi hosts typically generate new certificates when the hypervisor is installed on bare-metal hardware. Through the process of configuring the host and allocating resources, it is common for the server configuration to undergo many settings changes as you harden your device.

Must-read security coverage

Among the hardening steps your organization may employ, joining an Active Directory (AD) domain helps administrators to simplify management of underlying hypervisor used to host virtual machines (VM) by centralizing the management of user accounts and groups allowed to access to the server, as well as what changes they are authorized to make.

SEE: Information security policy template download (Tech Pro Research)

However, while the process to join the server to AD may be straightforward, it can and certainly will consistently fail if the SSL certificates used by the VMware host are expired, invalid, or otherwise corrupted. These all pose a difficulty in getting the server to authenticate domain accounts, which will leave users unable to maintain the server until it is resolved. But how can you fix this once it’s happened? Or worse yet, if you’ve never been able to join it to the domain in the first place?

“

Ok, lets get to it!

First lets enable SSH, Go to Manage , Services.

Graphical user interface, text, application

Description automatically generated

Select TSM-SSH, Name SSH and Click start

Graphical user interface, text, application

Description automatically generated

next, lets login via ssh. I used Putty.

Text

Description automatically generated

Lets move to the dir that has the SSL keys to back up the keys. Per the above write up.

cd /etc/vmware/ssl

Then run the following.

mv rui.crt rui.crt.bak mv rui.key rui.key.bak

But I got the following error.

Text

Description automatically generated

So we are going to move on.

Next type /sbin/generate-certificates

Then /etc/init.d/hostd restart

Text

Description automatically generated

Looks like that worked, lets see!

Log back into the VMware Host via the web interface.

Ta da!

Graphical user interface, text, application, email

Description automatically generated

Make sure to disable SSH, or reboot to do so.

Thanks for reading

Roger L

October 29, 2022 0 comment

Cloud News Software Virtualization

DH2i Closes 2021 As Another Year of Record Sales Growth, Product Innovation, and Strategic Partnership Development

by Phil Marsden February 11, 2022

written by Phil Marsden

DH2i Closes 2021 As Another Year of Record Sales Growth, Product Innovation, and Strategic Partnership Development

Strengthened Foothold Across Key Verticals and Transitioned to 100% Software as a Subscription Model

DH2i today announced that 2021 marked another year of record growth, with a 44% percent sales growth year-over-year, across both its DxEnterprise multi-platform smart availability software and DxOdyssey software defined perimeter (SDP) security software solutions.

“2021 was a transformative year for DH2i,” said Don Boxley, CEO and Co-Founder of DH2i. “In addition to our enviable sales growth, DH2i strengthened its foothold across key verticals, such as financial services – making strong gains in the multinational investment banking segment – as well as technology, healthcare, and media.” He continued, “We also continued to build-out a market leadership product feature set, transitioned to a 100% software as a subscription model, and strengthened and entered into new highly strategic channel and technology partnerships.”

DH2i’s 2021 Milestones:

Product Innovation

– DH2i Launched Free DxEnterprise & DxOdyssey Developer Editions – Database, System, and Network Administrators now able to ensure instance level workload and SQL Server Availability group high availability (HA) and build secure zero trust connections between on-premises, remote, edge, IoT, and cloud environments — without a VPN.

– DH2i Launched DxEnterprise (DxE) Smart Availability Software for Containers – Enables cloud-native Microsoft SQL Server container Availability Groups (AGs) in Kubernetes (K8s).

– DH2i Launched DxEnterprise v20 Improving Microsoft SQL Server High Availability (HA) and Disaster Recovery (DR) Performance – Improves the performance and resilience of transaction processing workloads found in financial services, as well as other sectors, running on top of Microsoft® SQL Server.

New Customers

– Docler Holding Selected DH2i’s DxEnterprise To Help Maintain Operations Uptime and Minimize Business Disruption Across Multinational Conglomerate – ICT, media and entertainment leader deployed DxEnterprise software and is now achieving near-zero planned and unplanned downtime for its SQL Server on Linux cluster.

Strategic Channel Partnerships and Global Expansion

– DH2i and Nubelity Entered into Strategic Channel Agreement — Expanding DH2i’s Latin America Footprint – Announced First Joint Customer, a premier Latin American Digital Bank.

Market Education and Thought Leadership

– Microsoft’s Amit Khandelwal and DH2i’s Connor Cox Presented “How to Deploy Highly Available AGs Across Containers in Azure” at PASS Data Community Summit 2021 – Webinar explained how to improve performance, scalability, and portability of IT environments with highly available SQL Server Availability Groups (AGs) that span containers in Azure.

– Pythian and DH2i Presented Live Webinar, “Highly Available SQL Server AGs in Google Kubernetes Engine” – Webinar explained how to set up and configure highly available SQL Server Availability Groups (AGs) between containers in Google Cloud Platform.

– Microsoft’s Amit Khandelwal Joined DH2i’s Connor Cox to Discuss, “How to Achieve Peak Availability for Containerized SQL Server in Kubernetes” – Webinar explained how to create hybrid AG clusters across SQL Server containers, achieve near-zero RTO, and avoid SQL Server HA/DR configuration and networking challenges.

– DH2i Joined Microsoft Azure Webinar to Discuss “How to Unlock Free SQL Server Licenses and Hybrid DR with DH2i” – Webinar explained how to use DxEnterprise, SDP-enhanced clustering software, to take advantage of free replica benefits while unlocking easy hybrid cloud, advanced fault detection/auto-failover, and superior performance.

– Microsoft and DH2i Presented, “Paving the Way to SQL Server HA on Linux in Azure” – Webinar explained how to achieve peak high availability with unmatched management simplicity, infrastructure and platform flexibility, and advanced fault detection with automated failover for nearest-to-zero downtime.

These and additional DH2i webinars are archived and available on-demand here: https://dh2i.com/webinars/.

Market Intelligence

– DH2i Pre-Pandemic State of Virtual Private Networks (VPNs) Survey Revealed Inadequate Security Number One VPN Pain Point – Premier Virtual Private Network (VPN) survey of IT professionals across small-, mid-, and enterprise-sized organizations revealed almost 40% of respondents believed their network had already been breached by bad actor(s).

Tweet this: @DH2i Closes 2021 As Another Year of Record Sales Growth, Product Innovation, and Strategic Partnership Development https://dh2i.com/press/ #SQLServer #Kubernetes #Containers #HA #SDP #Data #Security

About DH2i: https://dh2i.com/

February 11, 2022 0 comment

News

Install Microsoft Windows Server 2022 on vSphere 7 Update 3

by Roger Lund November 16, 2021

written by Roger Lund

Welcome! Today we will install Server 2022 on VMware vSphere 7 Update 3.

We will go ahead and Create a New Virtual Machine.

As you see, I have added more ram and disk space. And Importantly changed the network adapter to VMXNET3, but I also change the disk type to Paravirtual.

Edit your Virtual Machine and edi your CDROM and browse to your ISO.

Click Save.

Power on

Open console.

Hit a key.

Tab to Next, and then hit Enter.

Select the edition, and version you want, and hit tab to Next and then hit Enter.

Accept, and tab to Next, and hit Enter.

Tab over to Custom and hit Enter.

Tab to new, and hit Enter.

Tab to apply and hit Enter

And hit ok.

Tab to Next, and hit Enter.

Go ahead and set your password, and tab to Finish and hit Enter.

Once it’s booted up, make sure you install VMware tools.

Welcome to Server 2022!

November 16, 2021 0 comment

News

Installation of VMware vSphere 7 Update 3

by Roger Lund November 15, 2021

written by Roger Lund

Install vSphere 7 U3

Today I will be Installing VMware vSphere 7 Update 3 via workstation to walk you through the installation.

Lets go ahead and press F11

Select your disk, and Press Enter.

Select your language and Press Enter.

Enter your password and Press Enter.

Here it is saying my I7 is old, imagine that, normally you will not get this unless it’s an older cpu. Press Enter to continue.

Hit F11 to install.

W00t, Time to reboot, Press Enter.

Lets go build some VM’s! Until next time.

November 15, 2021 0 comment

Datacenter Software VMware

VMware vRealize Automation bring infrastructure as code

by Philip Sellers June 22, 2020

written by Philip Sellers

In April 2020, VMware released vRealize Automation 8.1 – an incremental upgrade to vRealize Automation 8 – which includes a number of new features. Kubernetes support has been enhanced, Red Hat Openshift support has been introduced, approval policies have been added, support for Powershell in ABX and in vRealize Orchestrator, NSX and networking updates, RBAC enhancements and a slew of other new features.

Let me be honest – calling vRealize Automation 8.0 or 8.1 the same name as the previous product is actually a disservice. This is an entirely new product and way of automating infrastructure for VMware. The new product is modern and itself containerized and modular in the way that VMware built and distributes the software. It introduces modern concepts like code pipelines, continuous delivery and infrastructure as code definitions.

Components

vRealize Automation 8 is made of 3 major components – Cloud Assembly, Code Stream & Service Broker. Also packaged is Orchestrator, which has been closely coupled with the legacy vRA for many years.

Cloud Assembly is the portion of the product used to create blueprints and workflows. This is the section that allows us to create infrastructure as code definitions for templates that can be deployed. Cloud Assembly allows for common definition of deployments through the abstraction of infrastructure. This allows the IaC definitions to be normalized while allowing the specifics to be mapped back for operational purposes. For instance, in AWS or Azure, you have a specific VM image and sizing to be determined. In vSphere, those options are a combination of choices of vCPU, RAM and disk space. Cloud Assembly allows you to setup definitions – t-shirt sizes, if you like – that defines small on vSphere as 2 vCPU, 8GB of RAM, 40Gb of Disk space and maps that to a specific SKU for a matching cloud instance.

Code Stream is a code pipeline allowing for continuous delivery. It is a DevOps tool with integrations to other tools that developers will be using to create software.

Service Broker is the catalog or portal for users to access and request services. This is the primary interface for non-infrastructure users. Governance is also built into Service Broker. In addition to blueprints created in Cloud Assembly, some services can be surfaced directly into Service Broker, like AWS Cloud Formation Templates.

Architecture Diagram

The new vRealize Automation is made up of Kubernetes orchestrated containers.

June 22, 2020 0 comment

Datacenter Storage

DobiMigrate Now Fully Integrated with New Dell EMC PowerStore for Migration off Legacy Systems

by Philip Sellers June 17, 2020

written by Philip Sellers

News Release

Dell Technologies announced Dell EMC PowerStore to the market back in May. The headlines ranged from ‘breaks ground in storage infrastructure’, ‘PowerStore is untouchable’ through to ‘Dell simplifies mid-range storage portfolio.’ It made a strong impression.

PowerStore is a revolutionary infrastructure platform built from the ground up with Dell’s superior technology. Up to seven times faster and three times more responsive than previous Dell midrange storage arrays, PowerStore is built to handle any workload, traditional or modern, without compromising efficiency or performance. It’s also the only purpose-built storage array that includes a built-in VMware ESXi Hypervisor, allowing administrators to deploy applications directly on the array for greater flexibility. This capability is ideal for data-intensive workloads in core or edge locations and infrastructure applications.

Whenever any new storage array is launched by Dell the market gets excited, but once the dust settles and users start to discuss the practicalities of using this new solution, migration becomes a key priority. Today, Datadobi is excited to announce that their industry-leading DobiMigrate software is fully tested and compatible with Dell EMC PowerStore. It will enable users from non-Dell EMC arrays to migrate their data to PowerStore technology and enjoy a more efficient platform with far less risk and a better return on investment.

DobiMigrate is used in the world’s largest and most complex migration projects. It is ideally suited to mid-market organizations adopting PowerStore to optimize their storage strategy across today’s varied and complex use cases. Datadobi has a long-standing and successful history with the Dell team, and the launch of PowerStore will enable organizations to modernize their infrastructure to meet demanding storage requirements.

At the end of the day, Datadobi customers migrating data to PowerStore can have peace of mind and confidence that DobiMigrate can help quickly and effectively roll out this ground-breaking new platform.

June 17, 2020 0 comment