DWHPro Insights

How to Migrate a Teradata Virtual Machine from VMware to Proxmox

By Roland Wenzlofsky ·

How to Migrate a Teradata Virtual Machine from VMware to Proxmox

This article outlines the procedure for migrating the Teradata virtual machine image from VMware to a level 1 hypervisor.

This historical workflow concerns a Teradata virtual machine image. Confirm current image availability, guest support and hypervisor compatibility in the vendor documentation.

To run Teradata virtual machine on a different server, you must install the operating system (such as Linux) and VMware Player or VirtualBox. However, this may not be optimal due to limited resources, particularly main memory.

Use private network connectivity to the guest for database access; port forwarding is only one optional topology and is not a migration prerequisite. Restrict database access to trusted clients. Hypervisor features and backup options vary by product and version.

Migration depends on compatible guest firmware, disk controllers, NIC drivers and target storage. Check the current vendor documentation and download availability; the historical procedure below was not rerun in this audit.

https://downloads.teradata.com/download/database/teradata-express/vmware

We will use Proxmox as our level 1 hypervisor, which is ideal for consumer hardware and is available for free. It can be installed on any old computer that is no longer in use. The Proxmox homepage provides the minimum system requirements. Here is the download link for Proxmox:

https://www.proxmox.com/en/downloads/category/iso-images-pve

Instructions for installing Proxmox on your computer are available on the Proxmox website. If you need further assistance, please leave a comment or email me.

Teradata Query Performance Tuning: The DWHPro Guide book cover

Get the complete Teradata tuning book, free

Teradata Query Performance Tuning: The DWHPro Guide
By Roland Wenzlofsky & Artemios Vogiatzis

206 pages on statistics and demographics, access paths and indexes, query execution plans, and joins. Get the full PDF and practical Teradata updates from DWHPro.

Confirm your email to receive your download link. Privacy policy. Unsubscribe in any newsletter.

About the free book

Prerequisites

The necessary software for this process varies depending on whether you use a Windows or Mac operating system. Fortunately, all required software is available at no cost.

For SSH access to the Proxmox server on Windows, I suggest using Putty. Mac users can simply use the default terminal.

https://www.putty.org/

Furthermore, you need an SFTP client. On Windows, I recommend WinSCP. On Mac, I use the Forklift File Manager, but that’s a matter of taste:

https://winscp.net/eng/download.php

That’s all you need. So let’s start with the migration.

The Migration Process

Before copying, stop the database and shut down the source VM cleanly, or use a documented application-consistent snapshot. Record firmware mode, controller type, disk order, boot disk and network configuration. Copy every required VMDK descriptor and extent to staging on Proxmox, verify the transfer, and preserve the source until the target is validated.

The destination directory on the Proxmox server is /var/lib/vz/images

Below this path, you must create a directory that will hold your files. 109 is the directory I want to use for my virtual machine on the Proxmox server. You can choose any other number, of course:

/var/lib/vz/images/109

In VMware Player, your Teradata virtual machine consists of 3 disks:

VantageExpress17.20_Sles12-disk1.vmdk
VantageExpress17.20_Sles12-disk2.vmdk
VantageExpress17.20_Sles12-disk3.vmdk

The following filenames are historical examples only. Import the complete source disks through a method supported by your Proxmox storage backend; renaming files alone does not register or convert a disk.

vm-109-disk-1.vmdk
vm-109-disk-2.vmdk
vm-109-disk-3.vmdk

Create a new, unused VM ID with memory and CPU sized to the database workload. Import disks using the Proxmox method supported by the selected storage backend; renaming VMDKs under /var/lib/vz/images is not a general import method. Preserve source disk order and firmware mode, identify the actual boot disk, and verify controller and NIC drivers before boot.

When creating the virtual machine, make sure that the option “Do not use any media” is selected under the “OS” tab, and of course, as the operating system, you need to choose Linux. The disk size must be large enough to accommodate your VMware disks. I have set 200GB. Depending on what you want to do with your Teradata, you can choose a larger or smaller amount. I would choose at least 8GB of memory. I chose 2 sockets and 4 cores for the CPU in my installation.

Configure a guest network adapter supported by its drivers, confirm the private IP and test authorized client connectivity. Use VPN/private networking for remote access rather than exposing the database port directly to the Internet.

Next, you need to log in to Proxmox using SSH. On Mac, you can do this with Terminal; on Windows, you can use Putty.

Go to the folder /var/lib/vz/images/109, where your vmdk files are located. We now need to convert them using the following command (local is the disk name in Proxmox where you store your images. Ensure that it is the correct name in your case by going to the Proxmox menu Datacenter/Storage where all disks are listed)

qm importdisk 109 ./vm-109-disk-1.vmdk local --format qcow2
qm importdisk 109 ./vm-109-disk-2.vmdk local --format qcow2
qm importdisk 109 ./vm-109-disk-3.vmdk local --format qcow2

Next, we must assign the new disks in qcow2 format to virtual machine 109 in the “Hardware Tab”. You have to assign all 3 disks.

Use a storage controller supported by the guest image and installed drivers. IDE worked in the historical setup, but is not a universal requirement; changing controllers may require guest-driver or boot configuration changes.

Set firmware and boot order from the source VM configuration. Identify the operating-system boot disk explicitly; disk size alone does not identify it. Preserve data-disk order and validate all expected devices after boot.

We are done. When you start up the virtual machine in Proxmox, you will have a fully functional Teradata system up and running with all the features Proxmox and level 1 hypervisors offer.

I know this was a lot of information, and you might get stuck during the process with some issues. Don’t hesitate to leave me a comment below this blog post, and I will help you.

If you want a video in which I show you this process step by step, then leave me a comment here and subscribe to my YouTube channel:

DWHPro YouTube Channel

Deciding what to change in your data platform?

Compare optimisation, modernisation and migration against your workload and business requirements.

Explore independent platform assessments

Teradata Query Performance Tuning: The DWHPro Guide book cover

Get the complete Teradata tuning book, free

Teradata Query Performance Tuning: The DWHPro Guide
By Roland Wenzlofsky & Artemios Vogiatzis

206 pages on statistics and demographics, access paths and indexes, query execution plans, and joins. Get the full PDF and practical Teradata updates from DWHPro.

Confirm your email to receive your download link. Privacy policy. Unsubscribe in any newsletter.

About the free book

Follow DWHPro in Google to see our articles more often in Search.

Leave a Comment

Teradata Query Performance Tuning: The DWHPro Guide book cover

Get the complete Teradata tuning book, free

Teradata Query Performance Tuning: The DWHPro Guide
By Roland Wenzlofsky & Artemios Vogiatzis

206 pages on statistics and demographics, access paths and indexes, query execution plans, and joins. Get the full PDF and practical Teradata updates from DWHPro.

Confirm your email to receive your download link. Privacy policy. Unsubscribe in any newsletter.

About the free book

Protected by Security by CleanTalk and CleanTalk Anti-Spam