Bobcares

How to access VMFS Datastore from Linux, Windows and ESXi

by | Dec 14, 2020

Wondering how to access VMFS datastore from Linux, windows, and ESXi? You’re at the right place.

Here at Bobcares, we have seen several such VMWare related queries as part of our Server Management Services for web hosts and online service providers.

Today we will take a look at how to access VMFS datastore.

 

How to access VMFS Datastore from Linux, Windows, and ESXi

Now let’s take a look at how our Support Engineers access the data stored on the VMFS database of the ESXi host.

If the ESXi host crashes, but the local disk (disks) of the server are still functional, then it is always possible to copy the virtual machine files (both data drives and configuration files) from VMFS datastore and run VM on a different server (even on VMware Workstation or Hyper-V). The main problem is that the common operating systems (Windows and Linux) by default do not recognize the partition with the VMFS file system, because they do not have a VMFS driver.

Let’s see the different ways of accessing data on the VMFS datastore.

 

How to Mount VMFS file system on Linux (Ubuntu)

First, we connect to a physical disk with the VMFS file system to the computer (server) with Ubuntu.

In order to access the data on the VMFS volume, we have to install a special third-party vmfs-tools package. This package allows accessing VMFS from non-ESXi hosts. It is possible to access data on this partition in read-only mode.

We run the below command to install the package.

#apt-get install vmfs-tools

Next, to install package dependencies, we run the below command.

#apt-get install vmfs-tools

After the package is installed, we need to create a mount point in which the VMFS partition will be mounted:

#mkdir /mnt/vmfs

The next step is to look into the partitions on the disks. Creates a number of service partitions when installed in addition to the partition for virtual machine files (VMFS partition).

If the ESXi version is 4 or earlier, or a VMFS storage has been updated from VMFS 3 to VMFS 5, and its size doesn’t exceed 2TB, then we can display the list of disks and partitions by executing below command.

#fdisk -l

As a result of the above command, we found VMFS partition is /dev/sdb3

Now we only have to mount a partition with the VMFS storage:

#vmfs-fuse /dev/sdb3 /mnt/vmfs

Then list the contents of the mounted partition:

#ls -all /mnt/vmfs

Now we see all the virtual machine files on the VMFS storage that is available in read-only mode. It means that we can now copy the directories and/or individual files of the necessary virtual machines to a separate drive and run them on another ESXi host.

 

Access VMFS Volume from Windows

In order to connect the VMFS volume and access virtual machine files from Windows, we’ll need a special Java driver – Open Source VMFS Driver. This driver requires Java version 6 or later. It allows mounting VMFS volumes in read-only mode.

  • First, we download Open Source VMFS Driver (fvmfs_r95_dist.zip and unpack it to any directory (e.g., C:\vmfs).
  • Next, we can check the operation of the java-application fvmfs.jar by running the below commands.
    cd \vmfs
    java -jar fvmfs.jar
  • Next, we determine the number of HDDs containing VMFS storage that is connected to the Windows computer. We can find the disk number in the Disk Management Console or using diskpart (in our example, the connected disk has the index 1 – Disk1. For fvmfs driver, this disk has the following name: \\.\PhysicalDrive1).
  • Then we try to get information about this disk:
    java -jar fvmfs.jar \\.\PhysicalDrive1 info
  • After that, we share this disk with WebDAV:
    java -jar fvmfs.jar \\.\PhysicalDrive1 webdav
  • Then mount the shared disk:
    net use * http://localhost:50080/vmfs
  • A new disk that contains VMFS datastore available for reading should appear in the system;

However, we don’t close the console window while working with files on the VMFS storage.

 

Mounting an existing VMFS Datastore on a new ESXi host

As we saw earlier in both of the above cases, third-party VMFS drivers for Linux and Windows do not allow working with VMFS 6.0. Therefore, the best way to access data on a VMFS partition of a failed server is to connect its disks to a new ESXi server.

The new ESXi host must correctly identify the attached VMFS datastore and then we will be able to access the files on it.

Here are the steps that we follow to connect an existing VMFS storage to a new ESXi host without formatting it:

  • First, we connect to the new ESXi server using the vSphere Web Client;
  • Next, we connect the drive to the new server and run Storage rescan;
  • Then we go to the Configure >> Datastores section and select Create a new datastore item;
  • After that, we select the storage type: Disk or LUN;
  • In the list of available devices, we select the connected drive (LUN) with the VMFS storage;
  • Then we select the connection mode. Select Keep the existing signature item;
    how to access VMFS datastore from linux, windows and esxi
  • We click the Finish button.
  • We go to the host’s storage section. Here we select the connected storage. Its contents can be displayed by clicking on the
  • Datastore browser button;
  • Finally, now we can find the necessary vmx files, register them on the host, and immediately start the critical virtual machines.

[Need any further assistance in fixing VMWare queries? – We are here to help you]

 

Conclusion

Today, we saw how our Support Engineers how to access VMFS datastore from Linux, Windows, and ESXi.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF