Subscribe to Blog via Email
Follow me on TwitterMy Tweets
While chatting on slack the other day, one of my peers asked if I’d seen that ESG Global had done a write up on Veritas Velocity. Velocity is a product that won’t be available until the end of 2016 and is considered “Alpha”. I was surprised that anyone allowed to participate in Alpha was able to publish a description on the product, but that’s not my call to make.
What I found interesting about the article, written by ESG, discusses how Veritas Velocity, “… is combining its sophisticated approaches to data management with its broader ability to deliver superior data protection and information availability in order to offer something revolutionary.”
I found this statement to be quite odd, as what they’re doing is simply using the same technology that Delphix has utilized for years to perform what Delphix has implemented at our customer sites since 2008. They are simply hopping on the bandwagon, (along with a number of other companies) in an attempt to take advantage of the newest buzz word, “Copy Data Management”.
There’s nothing revolutionary about what we do. It was revolutionary back in 2008 and may be seen as revolutionary to the customers who haven’t embraced the power of virtualized environments yet, but to say what they’ve created is revolutionary isn’t true.
If we inspect (at a high level) what Veritas Velocity does:
I can replace the lead into the above list with Delphix and that describes the Delphix Engine, as well. We also offer a mature User Interface, advanced scripting capabilities and heterogenous support.
There are a lot of companies out there making claims that they have revolutionized new capabilities like “data virtualization”, “copy data management “ and “test data management”. Delphix has been in this space since the beginning and as the Gartner reports prove, will continue to be the driving force behind what other companies are striving to achieve in their products.
Want to learn how many solutions Delphix virtualization can provide for your company’s data? Try out Delphix Express, a simple Virtualbox or VMware open source version for your workstation to check out who’s been doing it right all along and before it was cool!
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!
Delphix Express offers a virtual environment to work with all the cool features like data virtualization and data masking on just a workstation or even a laptop. The product has an immense offering, so no matter how hard Kyle, Adam and the other folks worked on this labor of love, there’s bound to be some manual configurations that are required to ensure you get the most from the product. This is where I thought I’d help and offer a virtual hug to go along with the virtual images…:)
If you’re already set on installing and working<– (Link here!!) with Delphix Express, you will find the following Vimeo videos- importing the VMs and configuring Delphix Express quite helpful. Adam Bowen did a great job with these videos to get you started, but below, I’ll go through some technical details a bit deeper to give folks added arsenal in case they’ve missed a step or challenged just starting out with VMWare.
Note- Delphix Express requires VMWare Fusion, which you can download after purchasing a license, ($79.99) but well worth the investment.
Not enough memory to run all three VM’s required as part of Delphix Express or after an upgrade, the Delphix Express uses over 6Gb.
Different laptops/workstations have different amounts of memory, CPU and space available. Memory is the most common constraint with today’s pc. Although the VMs are configured for optimal performance, the target and source environments can have the memory trimmed to 2Gb each and still perform when resources are constrained.
The VM must be shut down for this configuration change to be implemented. After stopping or before starting the VM, click on Virtual Machine, Settings. Click on Processors and Memory and then you can configure the memory usage via a slider option as seen below:
Move the slider to under 2G for the VM in question and then close the configuration window and start the VM. Perform this for each VM, (the Delphix Engine VM should already be at 2Gb.)
Issue- Population of sources and targets is empty after successful configuration.
After starting the target and source VMs, a UI interface with command line is opened and you can login right from the VMWare. Virtualbox would require a terminal opened to the desktop, but either way, you can get to the command line interface in such a way without using Putty or another desktop terminal from your workstation.
On the target VM command line, login as the delphix user. The target VM has a python script that runs in the background upon startup that checks for a delphix engine once every minute and if it locates one, will run the configuration. You can view this running in the cron:
crontab -l @reboot ..... /home/delphix/landshark_setup.py
It writes to the following log file:
You can view this file, (or tail it or cat it, whatever you are comfortable doing to view the end of the file…) I prefer just to view the last ten lines, so I’ll run a command to look at JUST the last ten lines:
tail -10 landshark_setup.log
If the configuration is having issues locating the Delphix engine, it will show in this log file. Once confirmed, then we have a couple steps to check:
VMWare issue with the one of the virtual machines not visible to another. Each VM needs to be able to communicate and interact with each other. When importing in each VM, the ability for the VM to be “host aware” with the Mac may not have occurred. If you the delphix engine VM isn’t viewable to the target or the source, you can check the log and then verify in the following way.
Click on Virtual Machine, Settings and then click on Network Adapter. Verify that the top radio option is selected for “Share with my Mac”:
Verify that this is configured for EACH of the three virtual machines involved. If this hasn’t corrected and the configuration doesn’t populate the virtual environments in the Delphix interface, then it’s time to look at the configuration for the target machine.
Get IP Address
While SSH connected to the target machine, type in the following:
Use the IP address shown, (inet address) and open a browser on your PC, adding the port used for the target configuration file, (port 8000 by default):
You should be shown the configuration file for your target server that is used to run the delphix engine configuration. There are options to update the values for different parameters. The you should focus on are:
linux_source_ip= make sure this matches the source VM’s ip address when you type in “ifconfig”.
engine_address= ip address for the delphix engine VM when you type in ifconfig on the host
engine_password= should match the password that you updated your delphix_admin to when you went through the configuration. Update it to match if it doesn’t, as I’ve seen some folks not set it to “landshark” as demonstrated in the videos, so of course, the setup will fail when the file doesn’t match the password set by the user.
oracle_xe = If you set Oracle_xe to true, then don’t set the 11g or 12c to true. To conserver workstation resources, choose only one database type.
Once you’re made all the changes you want to the page, click on Submit Changes.
You need to run the reconfiguration manually now. Remember, this runs in the background each minute, but when it does that, you can’t see what’s going on, so I recommend killing the running process and running it manually.
From the target host, type in the following:
ps -ef | grep landshark_setup
Kill the running processes:
Check for any running processes, just to be safe:
ps -ef | grep landshark_setup
Once you’ve confirmed that none are running, let’s run the script manually from the delphix user home:
Verify that the configuration runs, monitoring as it steps through each step:
This is the first time you’re performed these steps, so expect a refresh won’t be performed, but a creation will. You should now see the left panel of your Delphix Engine UI populated:
Now we’ve come to the completion of the initial configuration. In my next post on Delphix Express, I’ll discuss the Dsource and Target database configurations for different target types. Working with these files and configurations are great practice to learning about Delphix, even if your Delphix Express even if you are amazed at how easy this all was.