Our File and Block architectures are similar in structure: A virtualized “engine”: just like the USP V serves as the virtualization engine for our block based infrastructure, HNAS serves as the virtualization engine for our file based infrastructure. Tiering structure: just like AMS and third party storage arrays (EMC, IBM) can be used as tiers behind the USP V, HCP and third party file appliances (dedupe devices and NetApp NAS) can be used as tiers behind HNAS. Intelligent tiering management: just like the Hitachi Tiered Storage Manager is used to manage LU tiering, Hitachi Data Discovery Suite is used to manage file tiering. Hitachi Tiered Storage Manager is integrated with HNAS, so you can have the industry’s most comprehensive end to end virtualization frame for block, file and content.
Our File and Block architectures are similar in structure: A virtualized “engine”: just like the USP V serves as the virtualization engine for our block based infrastructure, HNAS serves as the virtualization engine for our file based infrastructure. Tiering structure: just like AMS and third party storage arrays (EMC, IBM) can be used as tiers behind the USP V, HCP and third party file appliances (dedupe devices and NetApp NAS) can be used as tiers behind HNAS. Intelligent tiering management: just like the Hitachi Tiered Storage Manager is used to manage LU tiering, Hitachi Data Discovery Suite is used to manage file tiering. Hitachi Tiered Storage Manager is integrated with HNAS, so you can have the industry’s most comprehensive end to end virtualization frame for block, file and content.
Challenges:Lack of data mobility to leverage tiered storageTracking access and ensuring proper retention for legal and compliance requirementsSolution Capabilities:Policy-based file and content-aware movement within NAS or from NAS to archive tier When used with Hitachi Data Discovery Suite, content search results can be used to trigger data movement(use examples on slide)Business Benefits:By using content search results to select files for migration, customers can create automated, intelligent, content-aware data management policies to ensure that files are appropriately stored over their lifecycle. For example, a policy could be created to ensure that all .doc and .pdf files containing the word “budget” are stored in archive media instead of residing on less secure devices. You can reduce cost with the economics of tiered storage and reduce legal and compliance risks.
Content is created in the HNAS, is ingested to SharePoint when the user uploads from their home directory. Once in SharePoint, policies and user actions ingest blob data containing the selected content from the SQL Server infrastructure to the Hitachi NAS Platform. The data in SQL Server is replaced with a small stub file that is much easier for SQL Server to handle; making SharePoint achieve significantly greater scale for $€¥ invested.(from the MSFT Website: http://office.microsoft.com/en-us/sharepointportaladmin/HA011647631033.aspxStorageSharePoint Portal Server stores data in SQL Server... In general, the most important characteristics for determining the amount of storage space required are the total size of the documents stored on the portal site and the total size of the documents included in the portal site index. Database 200% of the total size of all documents stored on the portal site Index 60% of the total size of all documents stored on the portal site For example, a portal site that stores 1 million documents with an average document size of 100 kilobytes (KB) stores 100 GB of document data and, thus, requires 200 GB of storage space.RecommendationMultiply the results by a factor of 1.5 to 3 to accommodate for future growth.)Challenges SharePoint grows rapidly but scalability is tied to SQL Server SharePoint content is stored in SQL Server databases as blobs Blobs are larger than the 8K of a SQL record This affects performance, availability and backup/restore times and requires a significant investment in SQL Server as SharePoint continues to growSolution Capabilities Offload blob data from SQL Server to Hitachi NAS Platform leaving a small stub in SQL Server Hitachi Data Discovery for Microsoft SharePoint installs on the SharePoint Server as a SharePoint connector. Archive and retrieve content from the SharePoint interface It deploys as a ‘web part’, and enables users to select content to move from the SQL environment to the Hitachi NAS (or HCAP for e-discovery) environment. When needed, users select the item in the SharePoint interface and the SQL Server stub is used to retrieve the content. Since users are still working in SharePoint, very little training is required.Benefits SharePoint growth is diverted from SQL Server to Hitachi NAS Platform for dramatically improved scalability Moving data from the SQL Server environment which simply is not designed to be a content storage technology to the Hitachi NAS Platform, an environment designed for content, SharePoint environments can achieve significantly greater scale without significant costs.