Day 2 of EMC World 2013 started off with a general session from the CEO of EMC, Joe Tucci. He talked about the software defined datacenter, the shift to even more users which are also mobile, and the ingress of large amounts of data which is influencing storage designs.
Hi and welcome to EMC World 2013. For those that are unaware what EMC World is: It’s an annual seminar covering all things new and improved that EMC has to offer. It’s hosted in The Venetian hotel in nothing less than … Las Vegas! Your ideal location to learn about the new products EMC is launching, to socialize with fellow EMC customers, partners or employees and of course… to have some fun! 😉
Yesterday we checked in to EMC World, got our access badges and goody bag. This being the first actual day of EMC World, we kicked it off by immediately leaving the premises! Continue reading
EMC has just announced a new version of RecoverPoint – 4.0. With this new version comes a truckload of new and exciting features. I will not cover all these features but will instead pick out a couple of features that score high on my list. But first of all: what is RecoverPoint and why should you consider replicating with it?
The RecoverPoint family replicates block data on a SAN/storage level. It can do both local replication inside an array or remote replication to another array. There are multiple flavours of RecoverPoint (SE, EX, CL): which one you need depends on the size of your environment and the storage systems you are using. The strong point of RecoverPoint is that it offers continuous replication instead of only the traditional asynchronous or synchronous replication.
Yesterday I received a call about a drive failure in a CLARiiON CX3-80 storage array. Since every system has at least a couple of hot spares configured, usually this does not pose a problem. But this drive failure happened on drive position 0_0_0: a vault drive failure.
The vault drives host (amongst others) the operating system and configuration of the storage array. They are also used to destage the write cache in case of an event that might threaten data integrity.