My Nimble Wish List

[BenLoveday]

Thanks Mitch!

Unfortunately the arrays I have are physically separate and on different management networks. Is there any specific network requirement around using this feature?

Cheers!

Ben

[mgram128]

Ben,

In your scenario, I am assuming that one array is production and the other is for DR and they replicate to each-other?  In this case, you will not be able to join them into a single group for management (even if you were able to get them on the same management subnet).  Mitch

[ccolht99]

My wish list:

Multi-tenant support

     Destination end space and bandwidth control

     Source and destination volume and collection name difference allowed

     Replication controlled at the destination rather than the source

     Solid segregation of network traffic between customers

     Pools below the array level (customer buys 5T, they only can grow to 5T)

AIX support

NAS support

I think we need something like IBM's SAN Volume Controller that sits in front of a bunch of arrays providing services like this.

[m_chadwick]

Some small pieces of my wishlist (mostly with the vCenter plugin)

1) When creating a datastore with the vCenter plugin, it always adds 4 0's to the end of the datastore name in the Nimble management console and plug-in view

     - Also allow the underscore in the name

2) Be able to choose performance policy when creating a datastore

Definitely agree with the Veeam support and FC support as well.

[BenLoveday]

Thanks Mitch, in our case they are two completely separate arrays for separate clusters :-(

Cheers anyway!

Ben

[sgalbincea137]

*Whistles*

[jliu79]

"2. With Exchange running as a vm, do Exchange VSS snaps that clear the exchange logs."

Doesn't Nimble already have this feature?

[sgalbincea137]

Jason Liu wrote:

"2. With Exchange running as a vm, do Exchange VSS snaps that clear the exchange logs."

Doesn't Nimble already have this feature?

Yes it does. 

[mandersen81]

Jason Benway wrote:

2. With Exchange running as a vm, do Exchange VSS snaps that clear the exchange logs.

This is supported in the 2.1.4+ code release.   Providing you are doing iSCSI attached volumes from within the guest OS.

[sgalbincea137]

We're on 2.1.4 here and it does not seem to require in-guest iSCSI for Microsoft VSS. Ours are all on vmdk.