This article is moved towards my new site:
« How to quickly discover a “VM to Resource Pool” mapping
Blog transferred to VirtualKenneth.com »
Good article as always!
Lately I run into the same problems while designing our new infrastructure, I don’t understand why HP doesn’t put pressure on the vCenter integrations. I hoped and expected they would release it with the new SANiQ 8.5 software.
What they do release are integrations for Microsoft Exchange 2010, so that’s cool but it would be perfect with vCenter integrations…! Missed change for HP!
In our solution I configured Microsoft DPM 2010 servers with the new HP P4500 G2 60TB MDL SAS solution, nice affordable solution with 60TB 2nd tier storage. When budget for a second 60TB MDL solution (on a second site..) you can also do offload/replica within DPM 2010, no more tapes anymore! 😉
Yeah, last year they told us that they would pressurize vCenter integration but last week unfortunately we heared that certain integrations were made but not for VMware which was shove backwards to Q4 or later.
[…] van Ditmarsch – Using LeftHand Snapshot techniques within a VMware EnvironmentWell, currently no integration exists between the LeftHand Snapshot technique and vCenter. If the […]
Hi good post, i agree HP need to move on this there are limatations even around VC intergration , see below
It may HP are looking at proprietary run time agents
Nice blog post Kenneth.
Funny you should post this as i have just been explaining to our sales guys the same thing.
How do you find snapshotting exchange and SQL Vms with much success?
Fill in your details below or click an icon to log in:
You are commenting using your WordPress.com account. ( Log Out / Change )
You are commenting using your Twitter account. ( Log Out / Change )
You are commenting using your Facebook account. ( Log Out / Change )
You are commenting using your Google+ account. ( Log Out / Change )
Connecting to %s
Notify me of new comments via email.
Error: Twitter did not respond. Please wait a few minutes and refresh this page.