Using storage caching on a standalone windows server
Sometimes you are still facing standalone systems that need to provide storage based services - like backup targets. Running this on Windows Server offers your the option to use StorageBusCache to provide awesome speed.
Sometimes you might require high performance storage on a standalone server system - for example on a system running quite speedy backup storage.
One of the many ways to do this is to take a standalone windows server and enable storagebuscache - this allows you to use flash devices (mostly NVMe) as cache tier for rotational storage.
Technically storagebuscache creates bindings between disks so that a fast device is the cache for a certain amount of slower devices. This implies that it works best if you have a multiple of slow devices than fast ones.
Steps to enable storage bus cache
The steps required to enable SBC are:
- Install Failover-Clusterin components (required to provide SBL)
- Enable StorageBusCache
- Create volume(s)
Enable clustering features
First, enable the failover-clustering features:
This is required because storagebuscache is building on top of storage bus layer which is a feature of failover-clustering. Having said that, you don't need to create a cluster.
Enable storagebuscache
Having enabled clustering, now it's time to enable storagebus cache
This will enable the storagebuscache and create a mapping of cache devices already.
Create a volume
Having set up the cache, it's time to create some volume to actually store data.
I'm using parity here as we're having a very fast write cache that receives the write-bursts. Besides bursts that don't exceed the cache size, the workload is not too heavy, parity can write down data fast enough.
Checking the cache status
To check the status, you can use
This might look like this
To check out the bindings, you can use this: