However, this blog is about migrating my workloads from my old array to new with minimal downtime! So let’s do that 🙂 Non-Disruptive Data Migration Between Pools It’s possible to run my environment within a scale-out environment if required (the maximum we support is up to 4 arrays in a group).

Therefore, you can jump into your current Nimble array UI, head to the “ Hardware” tab, and click Actions->Add Array To Group. Once you’ve racked, cabled and powered on your new system, the array will start sending broadcast packets onto your network in order to be discovered. If you’ve done all of the above, then we’re ready to get going. This is a critical part, and should not be overlooked. Nimble Connection Manager should also be installed on your Windows, VMware or Linux servers.Both systems need to run the same NimbleOS software release.Both old and new platforms are residing on the same data network – ie iSCSI or Fibre Channel.Let’s Scale-Out!īefore you start, it’s important to ensure: Most importantly, I want to do this as easy as possible, with the most minimal amount of application disruption! Typically, storage array data migrations are the bugbear of the enterprise IT industry.Īnd this is exactly what we can use Nimble Scale-Out technology to do for us, with minimal app disruption or downtime.

Perhaps I want to migrate my environments to All Flash, or perhaps I want to repurpose my older Nimble array to Disaster Recovery, or even for another project elsewhere. Whilst this array has done a fantastic job, I now wish to replace my older Nimble array with a newer Nimble platform. Array UI showing vnmbl-group with a single array

Nimble san storage replication