Hyper-V Nimble configuration #nimble #storage #news


#

Hyper-V Nimble configuration

The best practise guide or this KB should clarify: KB-000036 SQL Integration

Format the NTFS with 64KB.

Issues are only caused if the block size of the Nimble volume (defined with the performance policy) is larger then the blocksize the application is using. Volume blocksize for a SQL volume is typically 8KB. If it’s a CSV I wouldn’t bother and just set it to a “Hyper-V” Policy. (4KB blocksize, caching and compression enabled)

However, if SQL or another database is virtualized, there’s still some meaningful tuning you can do. I always recommend the following to my customers:

1. Create a new performance policy for Hyper-V/VMware with caching disabled

2. Create a separate CSV/Datastore with that policy

3. Move all virtual disks (containing the logs) to that CSV/Datastore

Why. Logs are random writes and will be cached. They are rarely read and you can “free” some cache by disabling cache for one CSV/Datastore and moving logs there.

You have to put the volume containing the database and the volume containing the logs in the same volume collection though!

The best practise guide or this KB should clarify: KB-000036 SQL Integration

Format the NTFS with 64KB.

Issues are only caused if the block size of the Nimble volume (defined with the performance policy) is larger then the blocksize the application is using. Volume blocksize for a SQL volume is typically 8KB. If it’s a CSV I wouldn’t bother and just set it to a “Hyper-V” Policy. (4KB blocksize, caching and compression enabled)

However, if SQL or another database is virtualized, there’s still some meaningful tuning you can do. I always recommend the following to my customers:

1. Create a new performance policy for Hyper-V/VMware with caching disabled

2. Create a separate CSV/Datastore with that policy

3. Move all virtual disks (containing the logs) to that CSV/Datastore

Why. Logs are random writes and will be cached. They are rarely read and you can “free” some cache by disabling cache for one CSV/Datastore and moving logs there.

You have to put the volume containing the database and the volume containing the logs in the same volume collection though!


Leave a Comment

Your email address will not be published. Required fields are marked *