The maintenance bill is due for your on-premises SAN/NAS--or it just increased. It’s hundreds of thousands or millions of dollars just to keep your existing storage gear under maintenance. And you know you will need to purchase more storage capacity for this aged hardware. Do you renew and commit another 3-5 years by paying the storage bill and further commit to a data center architecture? Do you make a forklift upgrade and buy new SAN/NAS gear or move to hyperconverged infrastructure? Do you move to the AWS cloud for greater flexibility and agility? Will you give up security and data protection?
In this webinar and demo, we covered:
1. Pros/Cons: on-premises SAN/NAS vs. hyperconverged infrastructure vs. AWS cloud storage
2. Demo: “Lift and shift” on-premises storage to AWS without re-architecting applications
3. How to fund a move to public cloud storage with existing budget
4. TCO analysis
5. Other public cloud use cases
4. The Storage Dilemma
4
Renew maintenance
contract or forklift
upgrade to new
NAS/SAN?
On-Premises
NAS/SAN
Hyperconverged
Hardware
AWS Cloud
Forklift upgrade to
hyperconverged
infrastructure?
“Lift and Shift” to the
AWS public cloud?
5. DoesThis Sound Familiar?
5
• Increasing maintenance costs?
• Exorbitant pricing for SSD?
• Never-ending pressure from business to add more storage capacity?
• Lack of low cost, high-performance object storage option?
• Pressure by CxO and senior management to move to the cloud?
• Pressure by business unit owners for agile infrastructure?
• Shadow IT competing with DevOps andCloud?
• No IT budget relief – unrealistic expectations to “do more with less or
same” resources and budget each year?
6. Comparing On-Premises, Hyperconverged and AWS
6
On-Premises Hyperconverged
Security
Customer controls their
data
Customer controls their
data
Customer controls their
data
Infrastructure
Management
Customer handles
infrastructure
Customer handles
infrastructure
AWS handles infrastructure
Scalability Limited Limited
Scale up or down to meet
your business needs
Disaster Recovery &
HA Setup
Days Days Minutes
Time to Procure More
Storage
Weeks to Months Weeks to Months Minutes
Pricing Most expensive option
Cheaper than NAS/SAN,
but more expensive than
AWS
Pay as you go; cheapest
option
7. On-Premises Management vs. AWS Management
7
Applications
Data
Runtime
Middleware
O/S
Virtualization
Servers
Storage
Networking
On-Premises /
Hyperconverged
AWS Cloud
Self-Managed
Applications
Data
Runtime
Middleware
O/S
Virtualization
Servers
Storage
Networking
ManagedbyAWS
Self-Managed • UsingAWS reduces infrastructure-
related administration
• You still manage user accounts, but jobs
like maintenance, disk swapping and
monitoring the health of your data are
now managed by Amazon
• Wave goodbye to hardware
maintenance fees and forklift upgrades!
8. 8 Reasons to Choose AWS forYour Storage Infrastructure
8
Pay as you go; pay
only for what you use
End maintenance renewals;
no longer pay the
“maintenance ransom”
ReplaceCapEx with
OpEx
Best in class security
protects your data
Easy to setup, use
and manage
Disaster recovery
and HA
Easily scalable to
meet your
business needs
Reliable
infrastructure
9. Using the AWSTCO Calculator
9
• Use theTCO calculator to
compare the cost of running
your applications on-premises
vs AWS
• Describe your on-premises
configuration to produce a
detailed cost comparison with
AWS
• URL:
https://awstcocalculator.com/
10. 3YearTotal Cost of Ownership (TCO) for AWS (40TB)
10
$-
$100,000
$200,000
$300,000
$400,000
$500,000
$600,000
$700,000
$800,000
On-Premises Hyperconverged AWS
Server Storage
On-Premises Hyperconverged AWS
Server 306,023$ 205,035$ 113,229$
Storage 156,200$ 104,654$ 57,794$
Network 160,480$ 107,522$ 59,378$
IT Labor 57,600$ 38,592$ 36,000$
Total 680,303$ 455,803$ 266,400$
$680,303
$455,803
$266,400
61% Cost
Savings
• On-premises to AWS migrations result
in cost savings of 61%
• Hyperconverged to AWS migrations
result in cost savings of 42%
Source: AWS TCO
11. How to Pay forYour Storage Migration to the Cloud?
11
Allocate existing maintenance renewal budget
$450,000 (50TB) on-premises >>> $265,000 (70TB) on AWS Cloud1
Pick a tier 2 application to migrate and test the waters2
Once the app is migrated successfully, create a workplan to migrate
the remaining apps, workloads and data
3
When all the migration is done, unplug your on-premises hardware!4
13. End-user
desktops, devices
Applications
and servers
Volumes
AFP iSCSI
Storage pools
CIFS NFS
Site A
Site B Public
Cloud
NFS
CIFS/SMB
iSCSI
AFP
Use existing
unchanged
applications…
Connect to AWS
using standard
NAS protocols…
Through AWS
hosted instances…
Leveraging AWS storage
services for flexible capacity
6
Easily Migrate Existing Applications to AWS
On-prem customers have 3 options when their maintenance renewals come up:
Either stay on prem and pay the maintenance bill (which has also become more expensive)
Consider a forklift upgrade; you can buy a new NAS/SAN or move to hyperconverged software; however you’re still on-prem and using hardware. The maintenance renewal stays
Finally, customers can lift and shift their data to AWS. Hardware will no longer be required and data centers can be “unplugged”
SoftNAS enables existing applications using standard storage protocols to operate unchanged. The SoftNAS virtual instances run on AWS compute and connect to the AWS back-end storage services. SoftNAS provides all of the Enterprise NAS capabilities in the cloud so customers don’t need to re-write their applications to make the move to AWS. We help customers make the move to AWS and preserve their budgets for the adaptations that translate to improved business outcomes instead of re-architecting their data systems.
SoftNAS can also run on-prem via virtual machine hosted servers to create a virtual NAS form a storage system, and connect to AWS for cloud hosted storage. Yes, we can run as a virtual storage appliance on-prem to create a NAS that can connect to the cloud.
Ideal use cases include:
Capturing back-ups or replicating and migrating on-prem data to AWS
Hosting applications with file protocol requirements – ideal for moving existing applications to AWS for hosting with less “re-architecture” work. Quickly SaaS enable applications that use file system.
Using off-prem snapshotting of virtual machines or application data to protect against disasters or rolling back to prior application versions
Safe keeping for development to store source code off-site
Media and content sharing or distribution