1. File Sharing and Archiving with StorSimple Jump Start Delivery Training
Michael Lubanski
Hybrid Cloud CoE

2. Cloud Storage Overview, Challenges and Options
Objectives
Cloud Storage Overview, Challenges and Options
Primary Storage and Platform
Cloud Integrated Tiering
Backup, Restore and Disaster Recovery
Security
Jump Start Engagement Training
9/20/2018

3. The Challenge in a Nutshell
Massive growth in Data
Regulatory Pressures
Litigation Threats
Margin Compression
Huge Shifts in Technology
Massive reduction in Data Centers
Conflicting Trends

4. Storage Challenges Are Broad
Equipment Sprawl
Data Growth & Footprint
Data Management Complexity
Backup Issues
Untested Disaster Recovery
Primary
Storage
Archival Storage
Disk-based Backup Storage
Tape Infrastructure & Management
Replicated Storage for DR
Offsite Facility for
Geo-resilience
Storage Today = Complex & Expensive

5. There are Alternatives
Traditional Data Storage
Cost per Unit of Storage
Azure Data Storage
Amount of Storage
A Simple Choice?

6. Cloud-integrated Storage (CIS) Can Help…
StorSimple + Windows Azure = 60–80% Lower TCO
Enterprise SAN Storage
Automated Cloud-as-a-Tier
Thin, Reduced Snapshots
Cloud Snapshots
Recover from Cloud to any DC
Primary
Storage
Archival Storage
Disk-based Backup Storage
Tape Infrastructure & Management
Replicated Storage for DR
Offsite Facility for
Geo-resilience
Storage Today = Complex & Expensive

7. StorSimple Cloud-integrated Storage
Connects Windows and VMware Servers to Azure Storage in Minutes with No Application Modification
Application Servers
StorSimple CIS
Most Active Data on SSD
Benefits
Consolidates primary, archive, backup, DR thru seamless integration with Azure
Cloud Snapshots = revolutionary speed, simplicity and reliability for backup and recovery
Reduces enterprise storage TCO by 60–80%
SAS Local Tier
Speed of SSD/SAN + Elasticity of Cloud
Azure Storage
Inactive Data + Backup Copies in Cloud

8. StorSimple Cloud-integrated Storage
Leveraging on-site network speeds, but with hierarchical storage to the cloud
This appliance has 20TB of On-Board Storage. Until it fills up it will never push anything to the cloud. Once it fills up it will at a block level start moving the data that is least used and move into Azure storage. Data will still be available in the cloud
No retraining of the users no re-education. They can still access it the same way
As it ages and once the appliance fills up it will start pushing out data to the cloud.
Security-all data at rest and transit encrypted Archiving/Backup: DR

9. Leading Edge Security
Multiple layers of obfuscation through the system
Original data is broken to storage blocks
Blocks are fingerprinted + deduplicated with data from other volumes
Obfuscated blocks are stored in compressed form
Encrypt everything before sending to Azure
AES-256 CBC encryption is applied before transmission using customer key
Additional SSL encryption of all data + meta-data operations with Azure
Encryption keys stay only with customer
Microsoft/StorSimple doesn’t have access to customer encryption keys
Keys can be imported from customer’s secure key mgmt system or generated from pass phrases
Encrypted / compressed / obfuscated blocks stored in Azure
Data is secure even if account gets compromised
Application Servers
Local Data
Broken into storage blocks, then:
Obfuscated
Deduplicated
Compressed
Blocks encrypted with customer key
SSL communication:
Authentication
Metadata
Data transfer
Data in cloud
Deduplicated
Compressed
Encrypted with customer key

10. Focused CIS Applications & Workloads
Target Use Cases
File Share
CIFS
NFS
File servers
NAS
SharePoint
Business intelligence
Collaboration
Content & records management
Archives
EMR/PACS
Legal
Construction
Media
Engineering
Logs, records
VMs
Regional office storage
VM sprawl
VM archives
CapEx, OpEx of traditional storage
Data grows exponentially (30–60% Annually)
Cloud Storage
Capacity
CapEx, OpEx of StorSimple
However, most I/O happens to “working set” data
Local Storage
Time

11. Compelling Economics: Traditional Storage vs. StorSimple
Traditional Storage + Data Protection Architecture
StorSimple Cloud-integrated Storage
Servers
Servers
Primary Volume
Disk Array ($100K; Double if Replicated)
Primary Volume
Snapshot
Local Snapshot
Disk Backup/ VTL
($100K; double if replicated)
50 TB
Media Server ($25K)
Encryption Appliance
Cloud Snapshots To Nearby Cloud Storage Service Region
Cloud Clones To Remote Cloud Storage Region for DR
Physical Tape Infrastructure ($50K)
Offsite Vault
Traditional
CapEx: $375K | Support: $75K per Year
Azure + StorSimple
CapEx: $0K | Support & Cloud: $55K per Year

12. Compelling Economics: Traditional Storage vs. StorSimple
Function
Traditional Storage Products
Traditional Storage Cost
Cost with StorSimple*
Primary and Archival Storage
Storage Array with Associated Software
$100,000 $0
Backup and Disaster Recovery
Backup Media Server and Software
$25,000
Disk Backup with Deduplication
Tape Backup Infrastructure
$50,000
Storage System for Disaster Recovery Time Objective (RTO) of 1 Week or Less
Capital Cost for the Customer
$375,000
Platinum Support Cost (20%/yr.)
$225,000
$15,000
Cloud Storage Cost
$150,000
3 Year Customer Cost
$600,000
$165,000
Other Customer Benefit
None
Tape eliminated
Ability to use cloud as secondary data center
Power/space/cooling savings
Administrator time savings
50 TB
* Based on ASAP $50K offer over 3 years

13. Compelling Economics: Traditional Storage vs. StorSimple
Virtualized
Applications
Auto-Cloud Tiering
Optimized, Deduplicated Snapshots
Cloud Snapshots
Geo-Enabled Cloud Clones
StorSimple Hybrid Cloud Storage Appliance
Cloud as Secondary Data Center
Azure Cloud Storage + StorSimple
Virtualized
Applications
Storage Today
Primary Storage
$1,300/TB
Archival Storage
$900/TB
Disk Based Backup Storage
$1,000/TB
Tape Infrastructure & Management
$600/TB
Replicated Storage for Disaster Recovery
$1,300/TB
Offsite Locations Geo-Resilience
$300/TB
$5,400/TB
$1,000/TB

14. Cloud-integrated Storage (CIS) Provides Major Benefits
Benefits Summary
Cloud-integrated Storage (CIS) Provides Major Benefits
Consolidated primary + archive + backup + DR
Significantly better backup and recovery performance
60–80% lower TCO versus traditional enterprise storage
Faster adoption of hybrid cloud computing

15. Primary Storage & Platform

16. StorSimple Cloud-integrated Architecture
SAN Storage
With Cloud Data Management
iSCSI SAN with auto-tiering (SSD/SAS)
Automated snapshots
Primary dedupe/compress
Seamless Cloud Integration for:
Tiered primary + archives
Cloud snapshots: mountable for DR
On an Enterprise-Class Platform
Certified: VMware-ready and Microsoft Windows Server-certified
HA: full redundancy + hot swaps + non-disruptive upgrades
Seamless iSCSI integration
Highly efficient storage
Thin provisioning
Primary storage de-duplication
High performance + cloud elasticity
Integrated tiering: SSD, SAS & cloud
Full security for the cloud
Local keys + encryption of all cloud data
Protecting both data-in-motion and data at rest
Fast, automated data protection + recovery
Automated snapshots to cloud
Fast online restores and elimination of tape
Integrated disaster recovery – lowest cost & complexity

17. De-dupe and compression
Total data capacity required = 10TB
Maximizes storage of ‘hot or warm data’ on- premise for higher IOPS and/or lower response times for application access.
Minimizes size of data transfer and storage in Azure
Works at the block-level and replaces duplicate data blocks with a meta data map (pointers to the original block)
Data is de-duped in the SSD tier and compressed in the SAS tier before being tiered to Azure
On-premise data capacity can be increased by 2x – 5x based on the type of data stored
Backup de-dupe: Cloud snapshots are differential and thereby eliminate copies of redundant blocks across backups E F E F
Data
blocks A A B B D A C A D C C B D C D C 5x
de-dupe ratio
Data blocks
Metadata map
Capacity used = 2TB A + B C D E F
De-duped
Compressed

18. Enterprise-class Hardware Platform
Highly available - no single point of failure
1. Full MPIOs
2. Dual controllers with auto-failover
3. Dual power
4. Dual cooling
5. RAID drives
6. Hot-spare drives
7. Non-disruptive software upgrades
8. Certified by Microsoft
* 5020, 7020, 5520 and 7520 appliances are built and distributed by Xyratex

19. StorSimple Models Appliance Model 7020 5520 7520 Capacity
Usable Local Hard Drive Capacity
4TB
10TB
20TB
SSD (eMLC) Physical Capacity
600GB
1.2TB
2TB
Effective Local Capacity
8-20TB
20-50TB
40-100TB
Max Capacity
200TB
300TB
500TB

20. Cloud-Integrated Tiering

21. Weighted Storage Layout (WSL
Weighted Storage Layout (WSL*) Core of the StorSimple Hybrid Storage Appliance
* Pronounced ‘whistle’
SCSI data from application servers
StorSimple Cloud-integrated Storage
Frequently-used working set data
Infrequently used non-working set data
BlockRank™
All volume data is dynamically broken into “chunks”, analyzed and weighted based on frequency of use, age, and others
Frequently-used data chunks stored in SSD for fast access
Real-time data deduplication enables capacity scalability
Less frequently-used data chunks can be:
Optimized and stored on integrated SAS
Optimized, encrypted and stored in the cloud
High performance local storage (SSD, SAS)
Optimized cloud storage access

22. StorSimple Tiered Architecture SSD Performance, Deduplication and Auto-Tiering to Cloud
Linear Tier A B C A B D E
SSD
Deduplicated E
SAS
Deduplicated
Compressed C D E
Data is written to the volume and stored persistently in raw/linear form on SSD
Maximizes throughput, IOPS
Minimizes response time
Transparent movement of data across tiers of storage to optimize for performance and cost
85% utilization threshold causes spilling downward toward lower-performance, lower-cost tiers of storage
Similarly, reading from slower storage causes data to be stored in faster tiers of storage
Spilling is based on a number of factors related to the data, including:
Frequency of use, reference counts
Age of the data or fingerprint
Spilling will be able to be influenced per-volume via a volume priority setting
Local-preferred
Normal
Cloud-preferred
WSL is automatic (no configuration) and transparent (no change to server’s view of storage)
Cloud
Deduplicated
Compressed
Encrypted D E

23. Backup/Restore & Disaster Recovery

24. Cloud Snapshots: Simplicity in Data Protection & Recovery
Backup, Restore & DR Today: Inefficient, Complex, Laborious, and Risky
Primary
Volume
Virtual Tape/ Replication
Physical Tape
Offsite Tape Storage
Snapshot
Backup, Restore & DR with StorSimple: Automated, Optimized, Reliable
Snapshots
Backup copy of data volume created in cloud
Changes to local volume automatically transferred
Cloud snapshots mountable for restore
Primary Volume
Benefits
Backup now as easy as snapshots
Very fast restores from off-site backups
Integrated, easy to test disaster recovery
Truly eliminates tape
Cloud Snapshots

25. …Enables Seamless Scalability and Rapid Recovery
Cloud
Snapshots
Production Data
Production Data
Enterprise Data Center 1
Enterprise Data Center 2
Connect Many Servers to Cloud Storage and Scale Data Sets with StorSimple Solution
Rapidly Recover to Any Data Center, Location-Independent, via Mounting the Cloud

26. Disaster Recovery Behind the Scenes
Configuration import process populates DR appliance with all information from original appliance
Registry restore downloads available backup information from the cloud
Clone operation fetches volume metadata from the cloud and creates the volume on the DR appliance
As and when data is requested, blocks are downloaded from the cloud
Benefits
Quick restore
Download only the required data

27. Cloud Snapshots: Up to 100x Faster RTO
Application Recovery Times from Offsite Backups in a Disaster
90 Days
Regular Cloud Backup With 100 Mbps WAN Link
30 Days
Recovery Time
7 Days
Tape
1 Day
StorSimple Cloud Snapshots With 50 Mbps WAN Link
1 Hour
15 Min.
1 TB
5 TB
20 TB
50 TB
100 TB
Primary Data

28. Security

29. Industry-leading Security for Cloud Storage
Multiple layers of obfuscation through the system
Original data is broken to storage blocks
Blocks are fingerprinted + deduplicated with data from other volumes
Obfuscated blocks are stored in compressed form
Encrypt everything before sending to Azure
AES-256 CBC encryption is applied before transmission using customer key
Additional SSL encryption of all data + meta-data operations with Azure
Encryption keys stay only with customer
Microsoft/StorSimple doesn’t have access to customer encryption keys
Keys can be imported from customer’s secure key mgmt system or generated from pass phrases
Encrypted / compressed / obfuscated blocks stored in Azure
Data is secure even if account gets compromised
Application Servers
Local Data
Broken into storage blocks, then:
Obfuscated
Deduplicated
Compressed
Blocks encrypted with customer key
SSL communication:
Authentication
Metadata
Data transfer
Data in cloud
Deduplicated
Compressed
Encrypted with customer key

30. Cloud Storage Access Security
Scenario 1: Access key got compromised
Scenario 2: Storage admin employee leaves company
Risk mitigation and best practices
Compartmentalize information
Azure subscription can have multiple storage accounts
Recommended to use different storage accounts to compartmentalize info – e.g. per dept, project, role, etc.
Periodical key rotation
Each account has two 256-bit access keys  allows easy key rotation without service disruption
Only requests with valid access keys are allowed to access stored blocks
Data fragments accessed are still obfuscated and encrypted
Frequent key rotation (e.g. every 90 days) is recommended
Ad-hoc/emergency key rotation if a key is compromised
StorSimple allows use of up to 64 storage accounts per system

31. Cloud Storage Data-at-Rest Security
Scenario 3: Cloud Provider decommissions server hardware or loses physical hard drives in maintenance process.
Risk mitigation and best practices
Data at-rest is obfuscated
Data is broken to individual small blocks and fingerprinted to comprise a global de-duplication dictionary – no volume, file system or file context
~16 Million obfuscated blocks per 1TB of Azure storage, spread across multiple hard drives
Data at-rest is encrypted
StorSimple systems encrypt data stored in cloud with a customer-provided encryption key. Federal standard AES-256 encryption used.
Up to 64 different encryption keys can be used in one appliance for data-at-rest isolation to complement access compartmentalization practice.
Encryption key is derived from Customer Passphrase or Key generated by Key Management System. Only entered input is accessible in appliance UI.
Microsoft or 3rd parties cannot read data when physical drives are lost, replaced, or repaired in Azure DC

32. Engagement Training

33. Engagement Approach Envision Plan Build Stabilize Deploy Summary
Describe the Solution concept and define the project team necessary to deliver it.
Assemble detailed plans and designs necessary to deliver the Solution.
Construct a Solution that includes all aspects of the project needs.
Polish and verify that the Solution meets customer and user needs and expectations.
Deploy and integrate the Solution to its intended production environments.
Summary
Kick-off meeting
Requirements gathering
Current state assessment
Operational impact review
Vision and scope approved
Solution alignment workshop
Project plan approval
Solution technical review
Scope complete approval
Usage, integration, and performance testing
Pilot deployment
Release communications
Release readiness approval
Documentation review
Deploy Solution in production
User training
Operations transition
Deployment approval
Key Activities
Vision and scope document
Project plan
Decision leading workshop results reports
On-the-job training
Final version of all documentation
Deliverables

34. Engagement IP

35. Technical IP

36. Deliverables Phase Deliverable Description Date Envision
Vision and scope document
Word document outlining the business, functional, technical, and operational requirements for the project. The document also identifies the objectives of the project and provides a scope of the deployment. Finally, the document defines the risk management framework.
Project plan and work breakdown structure
Provides a timeline for use in scoping the length of the engagement, based upon the Solution definition workshop and decision leading workshops. The project plan also allows for proper resource allocation and helps define dependencies within the project.
Plan
Solution alignment workshop results reports
The results reports produced during the three decision leading workshops are used as input for the architecture and design guides and are used to document the decisions made for the in-scope technologies and capabilities.
Functional specification
Test specification
These may cover the following technologies:
StorSimple
Windows Azure Backup Agent
System Center Data Protection Manager
Build
Configured lab environment
Deploy
Configured production environment

37. Feedback
Cloud Integrated Storage Feedback should be sent to