Plug-in the external USB drive to ESX Server directly to backup or copy
Sometimes you would like to use your external USB drive to backup (transfer) your VMDK files directly from your ESX Server external USB drive. VMDK files are files with extention *.VMDK and those files are virtual hard disks of your virtual machines. You can also mount VMDK files directly into your Windows PC.
When you plug-in external USB drive to ESX host you need to enter some commands at the console. For those of you who don’t really know linux, there is some commands to remember. But they are not many…. -:) .
First of all you should know that not all filesystems are supported. For the supported ones there are those here:
- FAT32 read/write.
- Ext3 read/write
- NTFS read only (that means that you can’t use NTFS formatted USB drives to copy your VMDK files, but you should create a partition with EXT3 or FAT32)
Now how-to copy data from Service Console to a USB device:
1. Plugin the external USB drive to your ESX host.
2. Run this command to find out to which device name the kernel assigned to it:
tail /var/log/dmesg
3. Now you will have to Run the following command to create a mount point (A mount point is a directory which a device or partition is attached to):
mkdir /mnt/usb

4. Run the following command to mount the drive ( When mounting, you must tell the mount command what is the device or partition you want to mount and what is the mount point. The mount point must be a directory that already exists on your system.:
mount /dev/[device_name] /mnt/usb -t [filesystem_type]
Please Note that you must:
* Replace [device_name] with your device name found in step 2
* Replace [filesystem_type] with vfat (FAT32) or ext3
5. After your copy(backup) you can type this command to unmount the device:
umount /dev/[device_name]
You might also want to export you VMDK files. Vmkstools is VMware ESX Server file system management tool. It is a program for creating and manipulating virtual disks, file systems, logical volumes and pyhsical storage device on the VMware ESX Server. Now what you need to do to export the VMDK (virtual disk)? You will use a command ‘vmfkstools’:
vmkfstools -i /vmfs/volumes/[datastore_name]/[vm_name]/[vm_name].vmdk /mnt/usb/[vm_name].vmdk -d 2gbsparse
And how-to import the VMDK (virtual disk):
vmkfstools -i /[path_to_USB_mount]/[vm_name].vmdk /vmfs/volumes/[datastore_name]/[vm_name]/[vm_name].vmdk
You might also want to copy the configuration files for a virtual machine. Those files are files with following extentions: *.vmx *.log *.nvram *.vmxf *.vmsd (you will not only copy the configuration files, but at the same time you will make a zip file in tar.gz format:
cd /vmfs/volumes/[datastore_name]/[vm_name]
tar -czvf [vm_name].tar.gz *.vmx *.log *.nvram *.vmxf *.vmsd
cp [vm_name].tar.gz /mnt/usb
Now you will be able to extract the configuration files of a virtual machine:
tar -xzvf [vm_name].tar.gz /vmfs/volumes/[datastore_name]/[vm_name]
Source: VMware Knowledge Base
Get some Top Free Whitepapers which you can download for free:
Top 5 VM Performance Problems.
In the Whitepaper you’ll first read the explanations where are the usual location of performance issues, and see that the resolution is not always evident in Virtual Infrastructure in general.
There are some caveats to know to find the problem first and then resolve.
Continuing to Reap the Rewards of Virtualization -
Balance and Efficiency. This illustrated e-book tells you more about interesting scenarios for sizing servers. With a clear examples. Also by using the monitoring solution bundled with Veeam One can show you exactly what’s going on in a real time or in what-if scenario.
If your RAM utilization is 4%, you have plenty of room to grow, but if you have no intention of growing that is a lot of expensive RAM going to waste. Bear in mind that more is not always better and the optimal strategy is to instead right-size your virtual environment. Download for Free
Analytics Required to Successful Manage Performance and Capacity in Cloud Environments- Managing Virtual Infrastructure instead of just physical servers one by one is challenging. One must make some decisions on where to best place the workloads or how much physical server and storage capacity to provision for new VMs…
What’s the best sizing for new VMs so they’re not oversubscribed with memory, disk or CPU…? Identify the “sleeping VMs” which do nothing, orphaned VMDKs, Snapshots, logfiles…
You can find more Free Whitepapers to download on my Free Resources page.
Enjoy… -:)
.
You may also like:
- Mounting your VMDK disks directly to your windows box – how to
- How-to find orphaned Virtual disks in your ESX server environement
- How to easy use ISOs during managing and installing VMs in ESX Server
- VMware Consolidated Backup 3.5 – new features
- Top freeware tools to manage ESX server
- VM Explorer – a free tool for ESX server
- Veeam Backup 3.0 supports ESXi without VCB















Pingback: Simple (probably local) backup options for ESXi | Resellernews.com.au