Skip to main content

Azure StorSimple (Day 27 of 31)

List of all posts from this series: http://vunvulearadu.blogspot.ro/2014/11/azure-blog-post-marathon-is-ready-to.html

Short Description 
Azure Stor Simple it is a hybrid cloud storage solution based on Microsoft Azure and StorSimple. It is based on a property device that offer an overview view over all storages (on-premises and cloud).


Main Features 
Lower storage cost
This solution is powerful enough to allocate storage only when is needed, based on company and system requirements.
Compression
To reduce the necessary space, content can be compresses. In this way the space used to store data is reduces drastically.
Deduplication
In enterprise, all the data is versioned. Because of this the size of the storage can increase drastically. StorSimple is smart enough to detect data duplication between different versions of the same data. In this way the size of the storage is decrease drastically.
Integration with MMC (Microsoft Management Console) and iSCSI
It is fully integrated with different management applications and APIs like MMC.
Same interface for different storage environment
All storage environments, from on-premises, to remote servers and clouds one can be managed using only one interface and management console. In this way the storage administration becomes a simple think.
Automatically backups
Azure Stor Simple it is smart enough to create backups based on predefined rules.
Disaster Recovery
One of the most important feature is disaster recovery, that is trigger automatically by the system. Different rules and policies can be configured.
SharePoint Adapter
StorSimple contains a special adapter that can be used to manage the storage used by a SharePoint farm. All the configuration can be made directly from SharePoint administration portal.
Security
Access to all the content can be managed and controlled. In this way we can control who access the data and what kind of operations can be done over it.

Limitations 
Like any other system, Azure Stor Simple has some limitations, like:

  • Maxim size of a volume is 64TB
  • Maxim number of iSCSI connections is 512
  • Maximum number of snapshots per devices 10K
  • Restore time processing time per TB is ~5 minutes
  • Maximum number of volumes is 256


Applicable Use Cases 
Below you can find some uses cases when I would use Azure Stor Simple
Pharma and Life Care 
Because of the laws, all the pharma and life care companies needs to store their audit data for 5+ year more (each country has different laws). Because of this, they need a mechanism to store large amount of data not only in a secure and reliable way, but also in way to reduce costs. For use cases like this Azure Stor Simple can be a great options, especially because of compressing and deduplication functionality.
Disaster recovery 
There are different businesses where you data needs to be available all the time. For uses cases like this you need a system that is able to trigger a disaster recovery plan automatically. For example in car industry, where you need different documentation and manuals to be accessible all the time.

Code Sample 
-

Pros and Cons 
Pros

  • Scalable
  • Hybrid
  • Secure
  • It is a Stor Simple solution, not only Azure
  • Has support for standards protocols

Cons
Some people could see the Stor Simple hardware device like a dependency. But in this industry it is normal to have hardware devices that can manage large amount of data and storages types.

Pricing 
When you want to calculate the cost of Azure StorSimple you should take into account:

  • Storage size on cloud
  • Storage size on-premises
  • Ingest level
  • Annual subscriptions 


Conclusion
This hybrid storage solution can be very tempting for enterprise customers that need to manage and administrate a lot of data. In theory you can reduce the cost of storage with even with 60%.

Comments

  1. Well written post. I appreciate your guidance for sharing about backup and disaster recovery plan here. I really need to know about it. Great work!

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP