Life of a GB
•Download as PPTX, PDF•
0 likes•292 views
You’ve ignored storage management for long enough. In this session we’ll cover: What happens to data as it flows through the life cycle of a case Learn how to proactively structure your client/case directories appropriately Learn how to manage archiving of cases/data
Recommended
More Related Content
Similar to Life of a GB
Similar to Life of a GB (20)
More from Ipro Tech
More from Ipro Tech (20)
Recently uploaded
Recently uploaded (20)
Life of a GB
- 1. Life of a GB
- 2. Private and Confidential – Copyright 2019 Life of a GB You’ve ignored storage management for long enough. In this session we’ll cover: • What happens to data as it flows through the life cycle of a case • Learn how to proactively structure your client/case directories appropriately • Learn how to manage archiving of cases/data Your 15TB Fileserver is almost out of space. Old matters have been deleted, but you’re still in the red.
- 3. Presentation TitlePrivate and Confidential – Copyright 2019 Private and Confidential – Copyright 2019 Private and Confidential – Copyright 2019 Typical Ipro Directory Structure Directories in BLUE are created by the user
- 5. Presentation TitlePrivate and Confidential – Copyright 2019 Private and Confidential – Copyright 2019 Private and Confidential – Copyright 2019 Cloud Options for Processing Data Self Service Media Manager
- 6. Presentation TitlePrivate and Confidential – Copyright 2019 Private and Confidential – Copyright 2019 Private and Confidential – Copyright 2019 Self Service Data not stored in Network Location Self-Service Processing Case Directory
- 7. Presentation TitlePrivate and Confidential – Copyright 2019 Private and Confidential – Copyright 2019 Private and Confidential – Copyright 2019 Media Manager: Drive on Copy Station Copy Station with Physical Media Attached Media Manager Processing Case Directory
- 8. Presentation TitlePrivate and Confidential – Copyright 2019 Private and Confidential – Copyright 2019 Private and Confidential – Copyright 2019 Media Manager: Network Share Network Share Media Manager
- 9. Presentation TitlePrivate and Confidential – Copyright 2019 Private and Confidential – Copyright 2019 Private and Confidential – Copyright 2019 Streaming Discovery Data Extract Jobs Processing Jobs Upload1 Self Service Copy CC Media Manager Copy Station Copy PR000001 Processing Case Directory Media Manager Network Share already staged Discovery Jobs DJ000001 Source Data
- 10. Presentation TitlePrivate and Confidential – Copyright 2019 Private and Confidential – Copyright 2019 Private and Confidential – Copyright 2019 Streaming Discovery Staged Data Discovery JobsExtracted Files
- 11. Presentation TitlePrivate and Confidential – Copyright 2019 Private and Confidential – Copyright 2019 Private and Confidential – Copyright 2019 Streaming Discovery – Export/Auto Import Processing Case Directory Review Case Directory Processing Case Directory Option 1 Option 2
- 12. Presentation TitlePrivate and Confidential – Copyright 2019 Private and Confidential – Copyright 2019 Private and Confidential – Copyright 2019 Post Processing Data Management Data Extract Jobs Processing Jobs Upload1 CC PR000001 Processing Case Directory Discovery Jobs DJ000001 Source Data
- 13. Review Data
- 14. Private and Confidential – Copyright 2019 Enterprise Imaging Review Case Directory Enterprise Integration
- 15. Private and Confidential – Copyright 2019 Productions Review Case Directory Enterprise Integration Production
- 16. Private and Confidential – Copyright 2019 SQL Config Databases ADD eCapture Eclipse NIST Enterprise Databases EntFlowCopy EntImg EMT Client Data Databases Processing Review StageDiscovery Production
- 17. Thank you for joining us!
Editor's Notes
- You’re in charge of archival and restores People frequently ask you “Can I delete this folder?” You administer the software ecosystem and want a better understanding of how data flows between the applications In this session, you’ll get an understanding of what happens to the data that is being staged, processed and reviewed in an Ipro Cloud environment. With this knowledge, you will be able to proactively structure your client/case directories appropriately and also manage archiving of cases/data.
- SA – Most vendors do not combine review and processing data in the same client directory. Directory structure and deigned to match their pricing models. If someone asks questions about our recommendation below, please understand the focus should be to structure your storage to match your billing. Ipro is just making a recommendation with simplicity in mind. Scott How do you organize your ESI? Do you store all case data under a Case Folder? Subfolder: Processing, Review, Source Data, Productions Do you store all source (original) data under a Source Data folder? Subfolder: per case In Ipro Cloud, every “Client” created will have an associated Code Name along with Processing and Review cases. Best Practice when creating a new client and case, create a folder named per the matter/case. Then when you create the client in Ipro Cloud, you should name “Client Name” with the actual matter/case. Then you can create a processing and review case underneath. So in this example, the Client Name is Sample v Dataset When you create the processing and review cases associated with that case in Ipro Cloud, it will automatically create them under that Data Directory You can also create a Source Data folder and Eclipse Export Set/Production folder under that Data Directory as well So in terms of Life of a GB, by organizing your data this way, you can pretty much know that the Life of that GB will be contained in that folder
- Cloud Options for Processing Data - Self-Service – Uploaded and copied to Processing Case folder - Media Manager - Drive attached to Copy Machine: Forensic copy made in Processing Case folder - Network Location – data already exists on your fileserver – No copy is made
- Self Service will upload container file to an upload folder within the eCapture Case Directory
- If you are adding Media with a Media Type of Drive, then you be plugging in the physical media to a Copy Station. When you create a Data Location, the directories selected will be copied to a CC folder within the specific Discovery Job folder it is tied to. Media Manager will then reference the data forensically copied to the CC folder
- If you are adding Media with a Media Type of Drive, then you be plugging in the physical media to a Copy Station. When you create a Data Location, the directories selected will be copied to a CC folder within the specific Discovery Job folder it is tied to. Media Manager will then reference the data forensically copied to the CC folder
- Self Service will upload container file to an upload folder within the eCapture Case Directory Media Manager If you are adding Media with a Media Type of Network Share, then Media Manager will reference the data staged in your source data folder If you are adding Media with a Media Type of Drive, then you be plugging in the physical media to a Copy Station. When you create a Data Location, the directories selected will be copied to a CC folder within the specific Discovery Job folder it is tied to. Media Manager will then reference the data forensically copied to the CC folder
- Scott Streaming Discovery File Extraction If file is a loose file, then file is referenced in place If file is a container (pst, zip) or forensic image, then files are extracted from container and stored within processing case folder So what this tells you is that the Processing Data Directory does not contain a complete copy of the staged data
- Export Options/Eclipse Import Default Template saves Streaming Discovery Export to Review Case Folder Natives Native Copy for Eclipse Point Eclipse to eCapture storage Pros & Cons of both Point to eCapture Storage One copy of data But if you processed a large amount of data but only hosting a small portion (due to deduplication or other filtering), you have to keep all processed data online Native Copy for Eclipse Another copy of data for what is hosted But you can archive or delete the Source Data and processed data (Discovery Jobs) This becomes more and more important with many companies moving to the cloud and storage becomes import
- Source Data and Processed Data that has finished processing, including publishing of errors can be archived/removed New data processed in the same case will not be affected. Deduplication is tracked within SQL and does not require the source or processed data to be present
- Enterprise Imaging Job submitted from Eclipse and sent to eCapture Job references natives stored in Eclipse Integration Directory is used as the working directory during imaging The images are then moved to the Review Case Directory A reference is left in the Integration Directory as a Document.xml file that is used for QC purposes S.A – Why are images left behind sometimes? We need to address exceptions and the implications of deleting data from this directory.
- Enterprise Imaging Export Set (Production) submitted from Eclipse and sent to eCapture All information required for production (images, natives, text, metadata) is pulled from Eclipse and sent to eCapture eCapture builds the export/production Integration Directory is used as the working directory during production The data is them moved to the specified export directory. There is nothing left in the Integration directory S.A. – We should address what the .cxt files are in the integration directory and how they are used during production.
- SQL ADD – Media Manager, Self Service, Managing/Client/Case Info, Users/Groups/Permissions, Components eCapture – Client/Case Info, Processing Environment Settings, Enterprise Job Info/Status, Task List and Worker Info Eclipse – Client/Case Info, Job Queue (Scheduler), minor environment settings EntFlowcopy DB - Stores all copy job info EntImg DB – Stores all imaging job info NIST DB – Stores all MD5Hash of known system files from NSRL (must be updated manually) Processing – DBs created per Client Streaming StageDiscovery DBs These get deleted once the Discovery Job has been completed (errors published) Export DBs These get deleted once the Export Job has been completed Email Threading DB These get deleted once the EMT Job has been completed Review – DBs created per Case Email Threading DB – Tied to main review DB – this can be deleted since all data is moved to main database Production DBs – Tied to main review DB – this can be deleted since all data is moved to main database