VMware

ESX on the IBM System i

This is all about my experiences running ESX on IBM BladeCenter and System x integration with IBM System i

2 Posts tagged with the bladecenter tag
0


So I finally have this prefected - I had to do a lot of CL Programming, and had to do a lot of tweaking to get this working. I will try and put everything in here that I went through to get it working. What I can do is post everything I have in place today. I hope you're a good CL programmer, or know one :)

First, make sure all the VM's have the VMware Tools with the "Volume Shadow Copy Services Support " selected. This doesn't get installed by default.

Second, on the Integrated Server that will be your VCB Proxy do the following.

  • Install the VMware Consolidated Backup Framework
  • Created a secondary drive (I call mine the V:\ drive) We'll talk about the size of this drive later - so read this whole thing before you do anything
  • create a folder in the V:\ drive called mnt and share it
  • Create a Batch program to do the mounting, and another to do the unmounting - this is for file level backups
  • I put these in a directory called c:\vcb
    • mount.bat - your vCenter Server probably isn't called vcenter.acme.com and the uid and pwd probably need to be changed too
      • "C:\Program Files\VMware\VMware Consolidated Backup Framework\vcbmounter" -h vcenter.acme.com -u Adminaccount -p adminspassword -a name:%1 -r v:\mnt\%1 -t file -m nbd
    • unmount.bat - same rules apply here
      • "C:\Program Files\VMware\VMware Consolidated Backup Framework\vcbmounter" -h vcenter.acme.com -u Adminaccount -p adminspassword -U v:\mnt\%1
  • I also created a bacth program to do image level backups - use the same unmount program
    • imount.bat
      • "C:\Program Files\VMware\VMware Consolidated Backup Framework\vcbmounter" -h vcenter.acme.com -u Adminaccount -p adminspassword -a name:%1 -r v:\mnt\%1 -t fullvm -m nbd
  • now we're ready to go to the green screen

Create a CL on the green screen, if I've lost you already, please PM me and we can talk, or go to your application group.

I called mine vmbackup

The VMNAME is the name of the virtual machine on the esx host and it is case sensitive. The NWSD, is the name of the integrated server.

/**MOUNT VMNAME TO THE VCB PROXY SERVER*******************************/

SBMNWSCMD CMD('"C:\VCB\MOUNT VMNAME"') SERVER(NWSD)

on the vcb proxy server, go to v:\mnt and you will see a folder with the same name as your Virtual Machine. Open it, you will see the folder letters, keep going, and you see the drive letters. Now just figure out what you want to save, and put that into the path you see below.

/**SAVE THE FILES YOU WANT TO SAVE***********************************/
SAV DEV('/qsys.lib/TAP02.DEVD') +
OBJ(('/qntc/nlcvcb/mnt/VMNAME/letters/*path*')) ENDOPT(*LEAVE)

/**UNMOUNT VMNAME FROM THE PROXY SERVER*****************************/
SBMNWSCMD CMD('"C:\VCB\UNMOUNT VMNAME"') SERVER(NWSD)

Now just repeat for all the VM's you want to backup. I like to do an *UNLOAD on my last save, that way I know everything worked ok.

This is very basic code, you may want to put a lot more logic in your code. And please test this. I like tesing mine to a save file.

Now, if you want to do an image level backup of a VM, it's all the same, but you call the IMOUNT

And for sizing, let me first explain that doing a file level backup doesn't copy files over the vcb proxy. Doing an image backup does. The files do get compressed a little, but I always say this, you should make your v:\ drive as big as your largest VM that you are going to backup.

Please let me know if you have any questions.

0 Comments Permalink
0

Welcome the IBM System i

Posted by dave@NLC Sep 27, 2008

Any idea what the IBM System i is? Ever heard of the System i5? How about the AS/400? If not, you should know about it. You've probably heard the numbers about how all the fortune 100 companies and fortune 500 companies are using VMware right? Well guess what, they all have one of these old green screen machines too! And guess what, it's more than just some Warehouse Inventory system. There is a reason that all these companies have one, it can do just about everything, and I am going to make you a believer :8}.

Now I'm not about to write an essay on why the System i is so great, but if you keep reading my posts, you will get why I'm so excited right now.

So how does VMware fit in with the System i? Well in a nut shell - The System i (which a lot of big companies have) can act as an iSCSI SAN, and you can boot IBM BladeServers and IBM System x Servers from this SAN, and have your shared storage too! Why is that so great? Because the IBM System i is one of the most reliable pieces of hardware on the planet! Because your company probably already has one! Because you can have a great backup and recovery platform! I could keep going, and trust me I will on subsequent posts, but I want to keep you interested, and move on for those people who already are experiencing the joy of this technology.

The big news - IBM announced during VMworld that ESX 3.5 is now supported on System i Integration. Here is the link to the site that explains it all. Starting with i5/OS version V5R4 ESX could be installed but only 3.0.1 and 3.0.2 were supported. It looks like this is still the case and as of this second, I am running ESX 3.0.2 build 52542 on one HS20 Blade and ESX 3.0.2 build 61618 - I'm just testing stuff, that's why I have 2 builds. I got all this going when we were at V5R4, but we have since upgraded to V6R1 - YAY!!!:D Shared storage is supported! And while I was in Vegas at fabulous VMworld 2008, ESX 3.5 is now supported. So now I need to upgrade to ESX 3.5 and build my HA and DRS Cluster. I can't wait! I'm glad to see IBM making the commitment to support VMware on this platform, the next step is for VMware to run natively on a Power System LPAR.

So here is a quick rundown of the hardware and software:

IBM System i5: Model 520 - 0595 Expansion Unit with 6 146GB 15k drives. 1 iSCSI HBA (soon to be 2). O/S V6R1

IBM BladeCenter S Chassis

2 - IBM BladeServer: HS20 Blade - 2 Dual Core 2.66 Ghz Intel Proc. 8 GB RAM. QLogic iSCSI HBA. O/S ESX 3.0.2 (soon to be 3.5)

I have VirtualCenter Server 2.5 running in a VM

That's all pretty basic stuff, but when I need to back everything up, the i5 does it for me. We have an LTO3 attached to it, and it backs up everything running on the i5 (Domino, Content On Demand, WebSphere, and now VMware)

Next weekend I am hoping to do the upgrade to ESX 3.5 - wish me luck! I'll be posting after the upgrade.

0 Comments Permalink
Click to view dave@NLC's profile Member since: Aug 22, 2008

This is all about my experiences running ESX on IBM BladeCenter and System x integration with IBM System i

View dave@NLC's profile

Communities