Subscribe to Blog via Email
Follow me on TwitterMy Tweets
I love technology- ALL TECHNOLOGY. This includes loving my Mac Air and loving my Microsoft Surface Pro 4. I’ve recently went back to a Mac when I joined Delphix, trimming down the power I had on my Surface Pro 4, knowing the content I was providing would be required to run on hardware with lesser resources.
With the release of Microsoft SQL Server 2016 on Linux, I jumped in with both feet and wanted to install it on one of my Linux VMs that I have “discovered” with my Delphix engine and its Oracle environment. To accomplish this, the OS version was CentOS, which wasn’t a supported OS, but did work with the yum commands with a few changes and with an upgrade from CentOS 6.6 to 7.
After upgrading and installing SQL Server 2016, I became aware that the memory requirements, once trimmed down on the VM to less than 1.5Gb, now required at least 3.5G to run. My Mac Air has only 8G of memory on it and to run a Delphix environment, you have the stand alone Delphix engine, (a simple software appliance) VM, a “Source” environment and a “Target” environment. To run three environments with that much of an increase in resource demands for the source and target was a bit too much for the little machine.
Moving a VM from a Mac to a PC is easy by copying the .ova file and importing it on the new PC. Upon doing so, I noted that it was from the original version and didn’t include my OS upgrade or the MSSQL installation.
I was able to quickly see this by comparing the images with the following command:
I took a new snapshot, brought the new file over and imported again, but no change occurred. I then decided to do some testing of how robust and how dependent VMs are.
Ensuring the VM was DOWN, I copied the actual VM’s folder on my Mac Air to a jump drive. It was almost 18 GB.
I then switched over to the Surface and with the VM down, renamed the original folder and copied the one from my MAC into the same directory. I then renamed it to be the same as the original, (I had to remove the .vmwarevm extension on the folder) which then mimicked the original it was replacing. Here’s the folder with the .vmwarevm extension on the jumpdrive-
And here’s how I renamed the original folder to “old” and then copied the Mac version to the same directory and removed the extension. Notice that the name now matches what it would have been for the original, which will also match what is in the Windows registry:
I restarted the VM and then checked that everything came up and verify that the image contained the correct OS and MSSQL installation:
Ahhh, much better…. 🙂 Now my upgraded VM with the addition of MSSQL 2016 has some room to move and grow!
A number of emails I received about trying out Delphix Express was regarding VMWare. Many of my followers had used Virtualbox for a long time and we all know, no one likes change, (OK, maybe me, but we know how abnormal I am anyway… :))
Importing an OVA is pretty simple in VMWare. In the VMWare Fusion application, click on File, Import and accept the defaults. Depending on the size of the VM, the process will take the time needed to import and if anything happens to the VM you imported in, the great thing about a VM, you just have to DELETE AND IMPORT AGAIN to erase that which you have destroyed. 🙂
Open the VM Control Console, click on the VM you want to delete, then click on Remove. Remember to click on delete files if you’d like that space back on your hard drive, too! The utility will take just a moment to clean up the VM and you can then proceed with work or re-import in the OVA file.
I know, if using Delphix Express, the IP address for the machine is displayed when it’s first started, but I also know that we DBAs are a curious lot and known for snooping around every chance we get. Due to this, you may not have noted the IP address and now need it to log into a terminal windows or want a second terminal to run or check items.
Knowing how to return the IP address is a good thing to know, so here are all the ways depending on what OS you’re on:
Linux- type in ifconfig from the terminal and you’ll see the IP address listed for the inet address for the eth0 configuration, (commonly setup as the eth0.)
Windows- ipconfig -a from the Command prompt or Click on the Window Icon, type in “Network” to go to Network and Ethernet and then click on ethernet. Your IP Address is listed in in the IPv4 Address setting.
Mac- ifconfig from terminal of click on the Apple up at top left corner of screen, click on System Preferences, click on Network, then if you’re using WiFi, click on it and then TCP/IP to view your actual IP Address listed for the IPv4 address.
If the VMware screen is blank, (no test or image on the screen or you’ve lost your cursor, the best way to get control back is to click Ctrl/Command on Mac to retrieve cursor control or make return your screen to active.
Every software has updates and just like the other software we support, updates to VMware is important. We may not utilize our VMs as often as we think, so it’s good to get into the practice to check for updates when you first log into VMware by clicking on VMWare Fusion and Check for Updates. If only takes a moment and hopefully you’ll see the following after it’s gone out to check:
By that, I mean to remember that you’re on one PC and you’re running virtual PCs on it. Don’t take up so many resources to your VMs that your PC doesn’t have enough to do its job. A VM should be pretty conservative on its resources and its important to look at the configuration and see if you can dial down any usage that isn’t necessary.
To do this, the VM must be shutdown, (not just suspended) and click on Virtual Machine, Settings. In your settings, there are a couple areas that need to be considered for resource usage:
The first, obviously, is to look at Processors & Memory. Ensure you’ve left enough memory for your PC and as PCs come with quad-core or higher processors these days, a single core is often sufficient for the processing on a VM.
The amount of space that is being used by a VM is a consideration, too. If a VM is so large that you need to purchase an external drive to run it on, then that’s a better choice vs. using up all your local disk or it may be time to build out Delphix just to virtualize the environment to start! 🙂
Verify that all disks for the VM are actually in use. I’ve seen where their are drives created for future growth, but never used or extra space that was allocated that just needs to be shrunk down. This can be accomplished by clicking on Virtual Machine, Settings and then from there, click on each of the disks in use by the VM, shrinking any that may have been over-allocated to. This is another task that can only be performed when the VM is shutdown.
Well, there’s a start to getting comfortable with VMWare Fusion. Do you have any tips or tricks that you can add to this? Comment and let use know and have a great Monday!
For those of you that downloaded and are starting to work with Delphix Express, (because you’re the cool kids… :)) You may have noticed that there is an Express Edition Oracle 11g database out there you could use as a Dsource, (source database for Delphix to clone and virtualize…)
If you’d like to work with this free version with your Delphix Express environment, these are the steps that I performed to allow me to utilize it. My setup is as follows:
Although we start the environment from the Delphix Engine VM, the Target VM contains the discovery scripts/configuration files and the Dsource VM has the 11g XE environment we wish to add.
Log into a terminal session to your DSource VM. You can login as the delphix user, (default password is delphix) and then ‘su’ over to the oracle user. You now need to check to see if the XE environment is running:
ps -ef | grep pmon
If the database is up and running, you’re done over here on you’re Dsource, but if it isn’t, then you need to start it.
First, you’ll need to set the environment, which is just standard for any database administrator:
Check each of the environment settings for the following:
$ORACLE_HOME=/u01/app/oracle/product/11.2.0/xe $ORACLE_BASE=/u01/app/oracle $ORACLE_SID=XEXE
Once these check out as set to those, you should be able to start the database without any errors, (if you followed my last post, you set it up to configure it as part of the setup.
Now, by default, these aren’t configured as Dsource or Targets to deter the Dsource and Target VMs from consuming too much space by default. Needless to say, you’ll need to tell the Delphix engine that it’s alright now to use them.
Open up a terminal to the Target for your Delphix Express and get the IP Address:
Take this address and type it into a web browser window and add the port to it:
The the landshark configuration file will come up and you’ll need to check the following to ensure they are set to true:
We need to tell the Delphix discovery script that we want to enable the Dsources, (Source VM) and VDBs, (Target VM) to configure/discovery and then which ones we will be working with, (the oracle_xe, which is the XEXE database we checked out on the Dsource VM.)
Remember to submit your changes before existing out of the configuration, otherwise you’ll just have to do it all over again and you know how much I hate it when anyone does things more than once! 🙂
Return to the terminal window for the Target VM. Check and see if any setup scripts are attempting to run:
ps -ef | grep setup
You should only see the the following running from the startup and you’re good-
Run the setup to configure the new Dsources and VDBs to your Delphix Express environment as the delphix OS user on the Target VM:
You’ll note that some of the configuration was completed previously and skipped, but that there’s also some additions to your environment now that you’ve requested these areas be configured. It doesn’t take a long time, (note the time in the output from the landshark_setup.log):
And by Grabthar’s hammer, you’ll have those Dsources now in your Delphix Express environment to work with:
Next post I’ll talk more about the actual cloning and VDBs- I promise… 🙂 Have a good week!
Maximum manageable storage per VM by ESX version
Note that the 60TB limit for 5.0 and 5.1 requires Update 1. Without this the limit is 24TB.
|Component||ESX 3.5 *||ESX 4.0||ESX 4.1||ESX 5.0||ESX 5.1||ESX 5.5|
|Disk Size (VMDK)||2TB||2TB||2TB||2TB||2TB||62TB|
|Number of Disks||60||60||60||60||60||60|
|Max Storage per VM (VMDK)||32TB**||32TB**||60TB**||60TB**||3.63PB|
|Max Storage per VM (RDM)||120TB||120TB||3.75PB||3.75PB||3.75PB|
|* VMware has EOL support for 3.x|
|**See limits related to VMFS heap at http://dlpx.co/1004424|
|#RDM size is based on physical-mode RDMs. Virtual-mode RDM limits match VMDKs.|
ESX 5.0, 5.1 VMFS addressable storage limit is 60TB when patches are applied
ESX5.5 VMFS addressable storage limit is 3.63PB, performance max is 100TB
Note: MaxAddressableSpaceTB sets pointer-block cache for performance: default 32TB, max 128TB. Threshold where PB cache eviction starts is 80%: so 100 TB is maximum for performance. Details in this blog post.
Posted in VMWare