Barry Burke

"Now that we've formally announced the rest of the functionality included in the Enginuity 5874 update that delivered FAST v1 for V-Max, I'll be happy to discuss Zero Page Reclaim.Perhaps best to start with my blog post on the subject: http://bit.ly/784kuT" - Barry Burke

"Now that we’ve formally announced the rest of the functionality included in the Enginuity 5874 update that delivered FAST v1 for V-Max, I’ll be happy to discuss Zero Page Reclaim. Perhaps best to start with my blog post on the subject: http://bit.ly/784kuT" - Barry Burke

"The Enginuity code release you refer to has not yet been formally announced. This week was all about FAST..." - Barry Burke

"Your impression about the I/O flow in V-Max (and CLARiiON, actually) is incorrect. First off, all the processors in both are active/active, not active passive. With both, any I/O can be serviced by any port and destined to any disk. V-Max scales out using the Virtual Matrix. V-Max engines are not “loosely” coupled with RapidIO - RapidIO plays the same inter-process(or) communications role as does the Direct Matrix in DMX. The one ASIC in the V-Max manages the interface to the RapidIO fabric, as well as providing numerous data manipulation services to the local nodes. The simplest way to explain it, since you seem to have a better grasp on the DMX architecture is this: V-Max assigns specific tasks to each core in each director (there are 8 cores per node). These “tasks” are analguous to prior Symm FA, DA, RA (etc.) ports. Incoming I/O requests are received by an FA, and queued to the appropriate DA pair. The DA pair could be local (the two nodes in an Engine), or they could in fact be..." - Barry Burke

"Test post - will you accept comments from me?" - Barry Burke

"This post includes numerous technical inaccuracies. For example, both Symmetrix and CLARiiON are in fact multi-processor based, with each processor providing multiple cores. V-Max scales to multiple closely-coupled engines to form a larger cluster by adding processor, memory, ports and drives to a running system (non-disruptively). The FAST management interface is inherently simple, scalable and intuitive, with wizards to help storage admins to jump-start the implementation and management. The operation of FAST is highly automated, inherently managing performance impact of both analysis and relocation operations while adapting to changing workloads. FAST (and VLUN) can relocate LUNs far, far faster than can a USP-V, and it can relocate LUNs without any impact to running applications or to dependent/active replication sessions (local or remote). V-Max inherently allows for numerous config changes to occur concurrently, redically reducing the frequency and impact of the “lock-out” you..." - Barry Burke