There are no problems running the EQL HIT kit alongside the Nimble Windows Toolkit... the only incompatibility resides in VSS snapshots; if you're using EQL ASM for Exchange snapshots then installing the Nimble toolkit will conflict because you're installing a second VSS implementation on the same host.
Hope that helps in your planning & design.
Thanks for the reply.
I guessed that VSS would be a problem - we don't use scheduled Equallogic snapshots using ASM to protect Exchange or SQL databases due to the limitations of how many snapshots you can take and the related performance hits (hence the reason to go Nimble!), however the backup solution we implement uses the Equallogic VSS HW Provider, so this may be where we would encounter issues
Not sure if anyone has any best practices for performing online migrations of this kind (Exchange/SQL) from other storage providers to Nimble.
My high level plans would be something like this:
Install all pre-requisites for NWT on mailbox servers
Install and configure NWT on mailbox servers
Provision new volumes on Nimble in line with capacity plan
Present Nimble storage to each mailbox server in DAG
Create new mailbox databases using new storage
Configure protection policies etc.
Migrate mailboxes to new databases within Exchange
Remove Equallogic storage
Uninstall Hit Kit