EfficientArchive V3.2.3e.

Transcription

1 V3.2.3e 1

2 What s EfficientArchive? EfficientArchive is a backend software provides solution for the data center, the unstructured data (file systems) ensures, archived, and at the same time a quick "Disaster Recovery". About s are corresponding power chains (Chained Processes) displayed (e.g. from disk to disk, then to tape) By hardware integration (Hitachi HNAS API) is a particular increase in efficiency and reduction in system load possible because e.g. no longer constantly has to search the filesystem for new or changed files. Because EfficientArchive gets from HNAS API this information. By application integration via the supplied Communications Server (Orchestra by Soffico) it is possible for any external systems and protocols (, SOAP, ftp, http, CSV, EDIFACT, HL7, DICOM...) to integrate. This leads not only to an increase in efficiency (see hardware integration) in addition to a significant increase in information (metadata about the files). Thus, it is only possible as with people affected files deal after applicable data protection regulations (mandatory data erasure). This information in acquired over the unstructured data, can always be passed through the same methods to other applications and solutions (Third Party Integration - e.g. BigData, Data Warehouse, SAP HANA). 2

3 Referenzliste Sozialstiftung Bamberg - Klinikum Bamberg (> 100 TB > 50 Mio. Files > 20 s) mobil isc, Hannover (> 150 TB > 500 Mio. Files > 10 s) Klinikum Bayreuth (> 70 TB > 50 Mio. Files > 10 s) Kreiskrankenhaus Erding (new 2015) Elektronische Werke Fritz Driescher & Söhne GmbH, Moosburg (new 2015) Barmherzige Brüder München (new 2015) Uniklinik München Großhadern (EA 2015 expected, TimeStamps 2012) Krankenhaus LK Weilheim-Schongau (2015 expected) 3

4 Problems with unstructured data uncontrolled exponential growth of unstructured data - backup processes only hardly practical - operational time much too long - thus even the largest problems with Disaster Recovery - so you have long downtimes and high costs can not be soved by using features of the storage manufacturer - mirroring of the data always requires additdional backup the data (Backup to Disk and Backup to Tape) mandatory audit-proof storage of data - prorietary special hardware solutions are usually very exptensive, very slowly and lead to dependence on a single manufacturer free, unrestricted use of the data - BigData - data on slow systems can not be used for BigData 4

5 Vorteile Audit-compliant long-term archive without proprietary hardware (WORM), through the use of signatures no backup of the archived data required - thus great cost savings in backup concept fastest restore of the data from Efficient Archive by "Recovery and remapping" for productive systems met rule: 3 copies of the data, 2 of them on different storage systems, 1of them to another location or offline met Privacy Policy - Mandatory data erasure Archiving at racing speed (> 450 MByte reading of CIFS, with simultaneous 450 Mbyte writing on CIFS = 900 MB throughput for standard files medium size) "Data is the oil of the 21st century" synergies, not a data graveyard, by "Third Party Integration" - Big Data Solutions, Data Warehouse, Viewing 5

6 Overview Tamper-proof long-term archiving solution with TÜV Rheinland certificate Powerful interfaces (, SAP ArchiveLink, HL7/MDM, DICOM, HTTP, ) Automatic signature of all incoming Data - optional with fully qualified time stamps (AuthentiDate) Redundant archiving (in a multy - tier way) the data on different storage and tier classes (i.e. disk, tape, Strongbox, HCP), this gives a maximum security at top speed level Use of open standards for data storage and archiving (CIFS, NFS, LTFS) - not proprietary fastest recovery of data from EfficientArchive by recovery and remapping of the file systems EfficientArchive Content Repository (storage for meta data) for intelligent use of information (Big Data) Highly scalable over many petabytes and billions of files 6

7 for BigData BigData Ebene EfficientArchive Informationen der Dateien File Ebene HNAS Fileoperationen Metainformationen über Dateien (Name, letzter Zugriff, Typ) Infrastruktur Ebene Block Storage - HUS/VSP 7

8 What is a? Level 1 An is a logical object and comprises: Windows Server 2008/2012 (physical or VM) Associated file system - there are stored or archived files. (Network share SMB or NFS) Associated database - the metadata is stored. (usually not locally on the Windows server, but on a central server) import folder export folder(s) 8

9 s Chained Processes classical Level 1 Level 2 DMS EfficientArchive Gen Service creates Files EfficientArchive Sync Service use Files to backup and archive 9

10 s Hitachi HW-Integration API HNAS Changed File List API EfficientArchive JetCopy/JetArchive feature uses HNAS Changed File List to create Files Level 1 Level 2 EfficientArchive Sync Service use Files to backup and archive DMS 10

11 s Application SW-Integration Level 1 Level 2 DMS EfficientArchive Communication Server Modul (soffico orchestra) works with applications to get files with metadata objects and then creates Files EfficientArchive Sync Service use Files to backup and archive 11

12 Level 1 Tier 1 SAS Level 2 Tier 4 Tape DMS SAP Communication Server Integration embedded Middleware ) ( 12

13 s Chained Processes Overview Level 1 Level 2 LTFS Tier 4 Tape ViewingNode DMSPRO TIFF JPEG 2000 DICOM, PDF... Apple IOS Iphone Ipad ERP Hitachi HDS Storage API HW-Integration Microsoft Windows Compute Blade LPAR Level 1 Level 2 Level 3 DataCenter EA TimestampNode Level 3 DMS Orchestra Communication Server Application SW-Integration embedded Middleware Level 1 Tier 1 SAS Level 2 Level 3 HDS HCP SAP 13

14 Backup Process Classical with HDS HCP Backup to Disk 500 TB capacity requirements Tape 1 PB capacity requirements 100 TB structured and unstructured Data, VMware, Filesystems, Files 500 TB 200 * 4TB week retention time (4 * full, 24 * inc backup) 400 * LTO 6 Tapes (2.5 TB) Liz Backup SW HDS HCP 24 TB capacity requirements no D/R capability

15 Applikationsintegration HW-Integration Communication Server Hitachi API* CIFS / NFS Backup Archiv D/R Efficient Archive unstrukturiert Daten virtualisiert Veeam Backup VMware HyperV SQL, Exchange, SharePoint, Domain Ctlr. 15 robert.berger@hds.com

16 EfficientNodes structured and unstructured Data HDPS 20 TB structured Data, VMware Liz Backup SW Backup to Disk 100 TB 40 * 4TB HW HNAS 100 TB capacity requirements 4 week retention time (4 * full, 24 * inc backup) Tape LTO Library 100 TB (200 TB) capacity requirements 80 * LTO 6 Tapes (2.5 TB) HW EfficientArchive 80 TB unstructured Data Filesystems Files Level 1 HNAS 100 TB capacity requirements (includes versioning) 40 * 4TB Level 2 LTFS Tier 4 Tape Crossroads Strongbox 100 TB (200 TB) 80 *LTO 6 Tapes (2.5 TB) HW Liz EA HW

17 Guidelines Principle of the separation of technical archives and productive storage Data remain in production system - HSM (Stub File) only optional Archiving in a multiple redundancy way on different storage classes via asynchronous processes Implementation of privacy policies - Duty of data erasure for data privacy act Fundamental decision: Privacy duty before compliance rules for companies Preference signature methods before use of WORM technologies Check the duration of the complete recovery of data from archive Archiving processes replaces backup processes Availability to changes in legislation 17

18 Problems when deciding on a specific network storage and archiving concept Which manufacturer of storage systems I choose? Can products be combined from different manufacturers? should i opt for a NAS, ISCSI or SAN-based architecture? When purchasing products with all-embracing functionality (all-rounder) - I make myself then not dependent? - Problem of so called "egg - Legend - jack of all trades". What if I want my data audit proof archiving? Should you buy a stand-alone solution for longterm archiving? If the annual demand for memory correctly assessed (30-50% growth per year) - demand is usually calculated only linear, e.g. annually 5TB If the whole thing then sometime priceless? If this solution is then in a few years even the right one? Or man must then time the stored data and migrate costly? If a solution once begun an open and flexible to adapt upcoming new technical possibilities, or I move to a dead end?... 18

19 Contacts and Information Partner: EfficientNodes GmbH Kagerser Hauptstraße 2a D Straubing Tel.: Fax.: Albin Brandl Tel.: Mobil: