Our Sponsors

Articles

Backup ESXi from Windows

Like many others that work with the free version of ESXi, I think VMware should have included an easy way to backup virtual machines even if it was just a copy to another Datastore.

Knowing that backups are extremely important, I have looked all over trying to find a simple and free way to backup the free version of ESXi Server. I finally found one that works well and was not that difficult to setup.

Backups can take a lot of time so to avoid any downtime it is best to schedule them to run at night.

Requirements:

  • This backup solution requires that the backup computer have the VMware VI Remote CLI for Windows installed
  • Enough hard drive space on the target backup PC to store the virtual machine backups
  • ESXi-backup.pl - I found the backup script on the VMware Communities site.

You must modify ESXiBackkup.pl to work in your environment. It's not hard to do, it can be opened with any text editor, I used Notepad. I had to remove some extra lines from the script that caused problems for me so hopefully they won’t cause any problems for you.

Below I’m going to take you through the configuration portion of the script. I'm only going to show you the pertinant information. To help with any formatting issues I'm going to have the script information surrounded in blue. The changes will be in standard text.

Change "IP-Address:Port" to the IP address or hostname of your Server

 

my $username = "user";

Replace "user" with the root user for your ESXi Server.

 

my $password = "pw";

Replace "pw" with the root password for your ESXi Server

 

my $DSPath = "[datastore]";   

[datastore] needs to be replaced with the name of the datastore you want to backup. You need to include the brackets [] or the script will not work.

 

$VMNames[0] = "ServerDisplayName";               

Replace ServerDisplayName with the name the way it is Displayed in the VI Client. If you want to backup more than one VM put the name between the quotes of the next openVMNames[#]

 

my $RCLIPath = "C:/Progra~1/VMware/VM9270~1"; 

You must add the path the the VI Remote CLI Path. This can only be in the Windows short file name format. The default should work but if it does not you can type "dir /x" from a command window in the c:\program files\vmware directory.

 

my $DestPath = "D:/esxi-backups"; 

 Here is where you fill out the directory where the backups will be copied to. Again, make sure you are using windows short filenames.

 

The last step before running the backup script is to make sure you have all of the directories created that you may need. In the destination path you need to create directories for each VM that you wish to backup. In the case of this example we need to make sure we have a directory called "ServerDisplayName" in D:\esxi-backups. If we don't the backup will fail.

 

 

 

 

Last Updated (Thursday, 05 March 2009 15:48)

 

Connect ESXi to Windows Based NFS

Many people are looking for a low cost solution for external storage for their free ESXi server. In this article, I will describe how to use a Windows machine and Windows Services for UNIX (WSFU) version 3.5 to create an NFS share that can be mounted on an ESXi host for storage of Virtual Machines, ISOs, or backups. There are a lot of articles like this out there but none of them worked as advertised for me so I decided to write my own.

Because I’m thinking about using my NFS storage for backup purposes my NFS share is called esxi-backup. Call your share what you will.

There are 6 main steps in the process:

  1. Installing WSFU
  2. Enable SSH on the ESXi Server
  3. Obtaining copies of the ESXi Server passwd and group files to the WSFU server
  4. Configuring WSFU for accepting ESXi connections
  5. Sharing the Windows folder to NFS clients
  6. Creating an ESXi Datastore to mount the Window NFS Share.

 


1. Install WSFU

  • To install WSFU you must first download it from Microsoft. SFU Download
  • Install WSFU on the desired machine
  • Select Custom Install
  • Add NFS + Server for NFS and Authentication tools for NFS + user name mapping
  • After installation, open the windows services control panel applet and verify the service ‘User Name Mapping’ is setup to startup automatically and that the services is started.


Windows Services Screen

 

2. Enable SSH on the ESXi Server

  • Please note that enabling SSH on ESXi is not supported on production servers. Follow the instructions here

 

3. Copy the ESXi Server passwd and group files to Windows

  • Using a program like WinSCP or Veem fastSCP you need to navigate to the /etc directory on your ESXi server and copy passwd and group files to the WSFU server.
  • I copied the files to c:\SFU\esxi-files, that way I won’t forget what the file is for.


Windows Services Screen

 

4. Configure WSFU to accept connections from the ESXi Server.

  • On the Windows platform where WSFU was installed Click Start, Programs, Windows Services for UNIX, Services for UNIX Administration
  • Select User Name Mappings on the left hand side then configuration on the right had side.
  • Windows Services For Unix User Screen

  • Select the Password and Group files radio button
  • Then select browse for both the password and group files that you copied from the ESXi server
  • Select apply
  • Now Select Maps
  • Once the Maps window opens, select “Show User Maps”
  • Under Windows domain name, Select the windows PC where the users are located and then select List Windows Users, then select list Unix users
  • Select a local administrator user from the Windows Users on the left.
  • Under the Unix users Select the root account
  • Select Add
  • Then click apply (upper right)

Windows Services For Unix Maps Screen

 

5. Sharing the Windows folder for NFS compatibility

  • Right click the local folder you wish to share via NFS (mine is c:\VMware esxi backup)
  • Select NFS sharing
  • Type in the name for the share
  • Make sure allow anonymous access is NOT selected.
  • Windows NFS Sharing

  • Select permissions
  • Change type of access to “Read+Write” then select allow root access.
  • Windows NFS Sharing Permissions

 

6. Configure the ESXi Server to mount the Window NFS Share as VMFS

  • Open the VI client and select your ESXi Server
  • In the Configure tab choose Storage
  • Add storage, Network File System
  • In the Server Field enter the NFS server IP address or hostname.
  • In the Folder field enter the share name you created above (mine is esxi-backup)
  • I used esxi-backup for the Datastore name.

 

VI Add NFS

6a. Alternate NFS Configuration
This is an advanced configuration that requires the NFS server is on a separate IP network. I would only suggest this is you know what a separate subnet is and have one configured.

  • Open the VI client and select your ESXi Server
  • In the Configure tab choose Networking
  • Select Add networking
  • A new window will open, select VMKernel then select a vSwitch, then give the VMkernel an IP that is accessible via the NFS host.
  • Now open the storage option for this host
  • Click add storage, Network File System
  • In the Server Field enter the NFS server IP address or hostname.
  • In the Folder field enter the share name you created above (mine is esxi-backup)
  • I used esxi-backup for the Datastore name.

 

Last Updated (Friday, 04 December 2009 00:22)

 

Scanning

Anyone that has ever put a document in a copy machine and pressed start has scanned an image. Scanning is that easy, what you do with the scan is how you can improve your business.

Scanning is the process of taking a hardcopy document and converting it to a digital format. Instead of keeping the hardcopy documents in metal file cabinets, the scanned images can now be stored electronically in electronic file cabinets. This save space and if setup correctly it can be found quickly and easily by anyone with access to the location where the file is stored.

Scanning can be accomplished in a number of ways.

  • Scan to email - The document is scanned from a MFD, using the MFD internal mail client the scanned document is then sent by email to the recipient. In most cases the file is sent in a image only PDF format. That means that the scan looks just like the original hardcopy document but it can not be searched for keywords.
  • Scan to folder - With scan to folder the document is scanned to a folder on the network. From there it can be accessed by anyone.
  • Scan to desktop - Building on scan to folder, an application like Nuance PaperPort watches the network folder for scanned document. Once it sees a new scan it takes the scan out of the network folder and puts into the PaperPort desktop. At this point the user can convert the document to a text searchable PDF. A text searchable PDF looks just like the original image and it can be searched for keywords. Once it is in a text searchable PDF it can easily be found in PaperPort.
  • Middleware scanning applications - Middleware scan applications like NSI Autostore, Xerox SMartSend, and xSolutions Scan Flow Store,  can take scanned images and convert them to almost any file format and send them to a number of locations with little or no intervention from an end user. A common use of a middleware scanning application would be to scan to a document management system like Microsoft SharePoint or Xerox DocuShare. 

That brings us back to the how can scanning benefit you? With scanning you can take all of your hardcopy documents that are sitting in the file cabinet and make the readily accessible for anyone that needs them. This can save you space, time, and money.

 

 

What is a MFD?

What is an MFD?

MFD stands for Multi-Function Device. The MFD contains a Printer, Copier, Scanner, and Fax machine in one device replacing the separate devices. This saves your company space, electricity, and consumables like toner. MFDs can be either inkjet or laser and have the ability to print in color.

The MFD is the cornerstone of any small business and its purchase should not be taken lightly. Inkjet MFDs can be purchased for as low as $70, but will it suit your needs?

When purchasing a MFD you need to ask yourself several questions. What functions do you need? I don’t know of any small business that does not need printing, copying, and faxing.

If you are doing less than 100 prints a month, you can make do with an inkjet but if you are printing more than that, you should really go with a laser-printing engine; it’s faster and normally has better print quality.

More advanced MFD features include:

  • Scan to email – Scanning a hardcopy document and automatically emailing it to a recipient.
  • Scan to desktop – Once scanned to your desktop you can OCR the electronic image to convert it to another format.
  • Scan to repository – This includes network shares or a document management system such as Microsoft SharePoint or Xerox DocuShare.

Check out our scanning section for more information on how scanning can benefit your business.  

Last Updated (Saturday, 07 March 2009 00:36)

 

Choosing the Correct OS

Which Operating System is right for your business?

There are three basic choices, Windows, Mac, or Linux. What you really need to focus on is compatibility.

In most cases, I recommend a Windows based PC  with Vista. The majority of PCs out there today are based on Windows and that ensures application compatibility. It is also easy to find an IT consultant or PC technician that can help with your issues. Windows PCs can be purchased new for under $700 and that includes most of the software needed to run your business.

I’m not trying to disparage you from going with a Mac or Linux PC, if you want to go with them great. They both have there place and can easily fit in a business environment.

The Mac has a lot of the same applications as the PC does but in my opinion they are still more suited to the graphics environment. If I were running a graphics house or a print shop, I would not hesitate from purchasing a Mac.

I am a Linux fan and do all of my web development on a Linux box. I have found that there are a lot of resources online to help with Linux support but there is not as much support locally unless you live near a college or university with an IT program.

When it comes to Network Operating Systems, you there are a lot of decisions to make.

You can stay with a peer to peer network that is built into all of the new operating systems or if you require more scalability you need to look into a client server model.

I use Windows Small Business Server 2003 (SBS2003) for my SOHO network. It has served me well for many years and it is easy to administer. It’s inexpensive for most small business and there is plenty of local and on-line support for it. SBS2008 is out now but for many business the difference in cost may keep them at SBS2003.

IBM has a new offering called Lotus Foundation server. Like SBS it is cost effective and easy to manage.

If you have an older PC that can function as a server, you have some technical ability, and you don’t want to spend any money on a Server OS I would suggest you look into Linux. Several builds and distributions are available to give you similar functionality to SBS and Lotus Foundations but at no cost. I used SME Server for many years prior to moving to SBS2003

Last Updated (Monday, 29 December 2008 16:23)

 
More Articles...