Skip to main content

Enterprise Storage optimization


For any Enterprise, even in the age of social computing, Email still remains as the primary medium of information sharing. It is source of information on current state of Business, communications with partners, customers etc.  It is also leveraged for sharing non-business related information.

Depending on the no. of employees, their daily activities, business transactions, the no.  of emails that are generated by them, storage requirements will grow. That too, if those emails are carrying business critical, heavy weight documents, storage requirements will still grow. Other factors that will impact storage requirements include no. of persons with whom a document is shared and no. of subsequent versions of that document before its final version is getting frozen.

Even if the Enterprises have governance mechanisms, IT policies ensuring the restrictive, optimized usage of emails, some of the business critical factors still demands increase in the per employee email storage quota and hence impacts storage requirements. Imagine a scenario where an Enterprise has 10,000 employees. Assume every employee generates 1 email per day with 1 MB average size of document. Total size of the content generated will be 10 GB / day.

Adding to these, imagine every employee shares his email with on an average with 10 other no. of employees. This will result in generation of the document copies, sizing 100 GB approximately.

Now you can visualize the impact of the Email system on the storage requirements.

Significant increase in the storage requirements will also impact the back office operational routines such as back-up / restore and it will also make things complex in DR planning for business continuity.

One solution which can be considered to tackle this problem is capability to minimize the no. of document copies that are generated & stored.

Imagine only these employees generate 1 MB of the document and the same copy will be shared with other employees. Based on our above mentioned scenario, storage requirement will get reduced by 100 GB

With the availability of Office 2013 and SharePoint 2013 from Microsoft, this capability is available now!

Site Mailbox – it leverages the combined power of Email storage capability of Exchange 2013 & Document storage capability of SharePoint 2013.

Instead of sending document as attachment in every email, he can save it in the Site mailbox. So that only one copy will exist; for the end users, they can still have the same experience as if they are accessing the document from the Email attachment.

Site mailboxes can be accessed by the users from the Outlook in a seamless manner, without compromising the native “Outlook” experience

In addition to storage optimization, Site Mailbox provides more benefits to an Enterprise …really more  !!….

Comments

Popular posts from this blog

Lambda Architecture on Microsoft Azure

Gone are those days when Enterprises will wait for hours and days to look at the dashboards based on the old, stale data. In this fast world of BYOD, fitness gears and flooding of other devices, it is becoming super important  to derive out “actionable” information from huge volume of data / noise that is generated from these devices or any other data sources and act proactively on them  in real-time, to stay competitive.

At the same time, the need for having dashboards and other analytical capabilities based on the quality, cleansed, processed data still very much exists.

With the emergence of more data types and need to handle huge volume, shift is happening from the conventional data warehouse practice to cloud based data processing & management capabilities where high volume batch processing is possible at the optimized cost. Business scenarios demanding the need to process the data in real-time   More

SharePoint 2013 Architectural Trade-Offs

When planning for deploying SharePoint 2013 based Enterprise workloads, it should be done with the consideration / awareness of impact of various architectural decisions what we make. As SharePoint 2013 is a flexible platform providing lots of options in terms of configuration of the existing OOB features and development of custom development solutions to address specific business functional needs, care should be taken when making a particular decision and its impact on overall solution. Even though SharePoint is a matured product, the effectiveness of various business capabilities such as Enterprise Social, Enterprise Search, BI, Document Management, Web Content Management, and Enterprise Content Management that will be delivered based on it, in terms of addressing the business requirements depends on architecture planning. Effectiveness here means performance, security, up-time and other architectural qualities like Scalability, Reliability etc. more ...

Flexibility through product customization - How Secured it is ?

When providing solutions based on the multiple products, the success of the solution depends on what level of OOB features of those products helps in addressing the business / functional needs and what level of flexibility those products offers in terms of customization.

Also, how those products help in addressing business needs is very important in terms of time-to-market through:
Capabilities for seamless integration with federated business partners through adapters (like what Microsoft BizTalk, & StreamInsighthave rich set of adapters minimizing the development time), Partner ecosystem with solutions(like what partners have solutions basedon SharePoint in addressing various business requirements such as document storage, DRM / IRM, BI etc)
In addition to above mentioned factors, success depends on how the products allow developer community in extending its capabilities to address complex techno-business requirements.
While allowing the developer community for customization, it is a…