Multiple Storage Definitions in Storage Maximizer for #SharePoint: A Mini Guide #qSharePoint

With the release of Storage Maximizer 1.1 Quest has introduced multiple storage definitions. What are multiple storage definitions and what can they do for you?

 

Well, first off they give you a massive increase in flexibility in how you optimize your storage. By having multiple storage definitions within any given scope (a scope is the boundary of the data that you are externalizing) you have the means to enable tiered storage.Tiered storage is when you layer storage from most likely faster and more expensive storage back to cheaper, possibly slower storage based on particular needs within your data set.

 

Let’s review how to create multiple storage definitions in a simple document library scenario. As with all functions within Storage Maximizer these actions are undertaken in the Central Administration site of the SharePoint farm that you want to externalize content from.

 

Start up Central Administration from your start menu.

Next select Application Management. You should see a section now for Storage Maximizer, if not get Storage Maximizer (or SMAX as we call it) and install it. It will take you less than 5 minutes to download, install and configure, then come back here. Now select View Dashboard.

The dashboard is where you both see all the statistics and activities relating to your externalization as well where you start your management of the system.

Below the charts and stats you will see a section on Storage Definition. Click on Add a storage definition.

Next pops up the Manager StorageDefinition UI. In this first Storage Definition the aim is to store smaller files on a slower drive as performance isn’t such an issue but there are potentially lots of small files so the savings in compression will be substantial.

Now for the larger files we will push these out to Faster storage. These are larger files which will get a significant performance boost by being both out of the SQL Database and on a faster data store. The storage definition is more or less the same, except that the target is now a faster file store.

Naturally this works wonders with dates as well!

 

Now in the dashboard we see the two storage definitions, both within the same scope. As this is a new document library we did not process any existing files (this is done thru the document mover job) but now as our end users upload files they are processed.

 

In a few minutes the first files have arrived and the dashboard is updated. As you can see larger files are placed in the fast storage and smaller files in the slow storage. You now have an optimized document library for large and small documents. It’s as simple as that!

 

About the Author