CPP is best known for the Myers-Briggs Type Indicator® assessment, they are a group of people committed to improving the performance of individuals and organizations around the world. Their story began more than 50 years ago with the pairing of two psychology professors—one from Stanford and one from U.C. Berkeley—with a common goal: to use research-based psychological assessments to give people the insight and guidance they need to develop in both their personal and professional lives. Their partnership resulted in the creation of CPP, Inc., the company formerly known as Consulting Psychologists Press.
That's how CPP brought two Reduxio HX550's
Key IT Trends that can affect CPP in the next 18 - 24 months
VMware's not the only player in the game anymore, and everybody else is trying to gain ground on VMware. You have Hyper-V. You have Xen. You have some other newer technologies out there as well. Although some of these other technologies have a lot of the rich feature set the VMware has, I don't see them really competing with the feature set that the VMware has. When I'm looking as a global organization, I want to be able to fail from one site over to another site within seconds to minutes.
How do I do that? Can I do that with these other providers and these other technologies out there? Well, after so many years in the industry, I've had an opportunity to piece together all the components I'd need to fail over from location to a secondary location, the seconds to minutes, without using Cloud resources, not just using my own private Cloud that I have, my MPLS network or software-defined networks.
Having the same stack of equipment on both sides, using some of the VMware replication tools, VMware site recovery manager. What needs to play well in that sandbox is the sand you have, because that's where your data resides at. Sometimes you can use backend sand replications. Sometimes it doesn't make sense to use backend replication. Whatever the component is, it needs to be able to play nice in that sandbox with all of the other technologies.
To Cloud or Not to Cloud
One of the biggest trends today is Cloud or no Cloud, right? What do you do? To Cloud or not to Cloud. I don't know how else to put it. When you make the jump to the Cloud solution, you have to take a look at the cost to go along with it.
What a lot of people don't understand is the cost of moving something into the Cloud, is the Opex expense, and it gets more expensive every year.
To where if you buy a functioning piece of equipment, you can depreciate that over time, and it costs you less the more and more you use it over time. Reduxio is positioned to where it will be able to take advantage of both the Cloud or local resources, so you could
These are some of the trends I'm seeing. Reduxio's positioned right now to where it makes cost sense to buy the Reduxio box and partnered with the right Cloud provider for storage, that's a pretty powerful combination. You could tier storage out to the Cloud. I think that the network
Seconds to minutes, that's really my RTO, my RPO, and that's what I'm focused on doing, is making sure I can recover within seconds to minutes and Reduxio allows me to do that.
Working with Reduxio
I think that the restore capabilities built inside of the box so I can just go back to a different point in time and grab that VM and bring it back into the pool again, or that LUN, for example.
That is probably one of the great benefits so when we're working in our development QA environment, they're breaking things all the time so we have a quick fix without having to go through and use the whole VMWare snapshot and recovery process, it just makes this much easier if we can do it from the sound side of things.
The performance is great for the VMs that are running, the ones that stay up in the upper SSD, that's giving us
As the VM is running, it takes a long time to actually take a snapshot. It could take a half hour, 45 minutes, but you have to really think ahead. Say, "Okay, I'm about to make changes to this environment, I want to think ahead, let's take a snapshot, okay then let's go ahead and do our work, we test. If it doesn't work then we revert to snapshot." It usually takes two or three people, resources, focused on making this happen right? To where now, we don't have to worry about it, somebody from our development team could move forward and say, "Okay, well we're going to make a bunch of changes. We don't have to take any snapshots."
It usually takes two or three people, resources, focused on making this happen right? To where now, we don't have to worry about it, somebody from our development team could move forward and say, "Okay, well we're going to make a bunch of changes. We don't have to take any snapshots."
We can go back and take a look at a granular level, it's called backdating, with Reduxio, go back to seconds a second time and just move forward from there, without having to take a snapshot and go through the whole preliminary process. So that takes one person. One resource instead of three, the time is anywhere from a half hour to two hours a time on top of it and it's ... So it does not slow down the development team or the QA team when they need to make changes to their environment.
One resource instead of three, the time is anywhere from a half hour to two hours a time on top of it and.