0% found this document useful (0 votes)
6 views2 pages

Findings

The Total Cost of Ownership (TCO) for Dell EMC VxRail on-premises solution is at least 30% lower than AWS over three years, offering enhanced features and performance. VxRail provides simplified management, consistent latency, and superior networking capabilities compared to AWS. Additionally, AWS's TCO calculations may overlook significant network costs and resource overprovisioning, which can lead to higher expenses for customers.

Uploaded by

gusoviedo001
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
6 views2 pages

Findings

The Total Cost of Ownership (TCO) for Dell EMC VxRail on-premises solution is at least 30% lower than AWS over three years, offering enhanced features and performance. VxRail provides simplified management, consistent latency, and superior networking capabilities compared to AWS. Additionally, AWS's TCO calculations may overlook significant network costs and resource overprovisioning, which can lead to higher expenses for customers.

Uploaded by

gusoviedo001
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Findings

(The Total Cost of Ownership of On-Premises SAP on Dell VxRail HCI Versus Amazon Web Services Public
Cloud)
10-07-2021
目次

Findings

Findings
The approximate TCO for the Dell EMC VxRail on-premises solution was a minimum of 30% (with the
potential for more) over three years with more features and performance benefits guaranteed.

Beyond TCO, the VxRail platform provides:

Single cluster and simple management


Easy updates; all updates (firmware, drivers, SW) with simple qualified clicks
Single pane of glass management
25 GB networking (compared to 10 GB from AWS)
Latency consistent with current on-premises experiences (compared with unknown latency from
Direct Connect)

Other observations

AWS TCO white papers do not estimate any form of network costs, which tend to be high and
equivocally cited in high volume workloads such as HANA databases.
In this TCO calculation, we assume the need of direct connect data transfer at a lower end of the
spectrum. However, depending on customer’s need and application characteristics, data transfer
costs could require a higher bandwidth connection which may further increase the AWS solution
costs.
The Inter-AZ traffic volume due to high availability scenarios can create a peculiar impact, where
customers are cognizant of volume or velocity of Inter-AZ data transfer.
AWS does not offer a choice of a 1.5 TB RAM instance. In this case, the customer must
overprovision resources that they are not supposed to and is an extra cost to the customer.
Depending on customer’s backup and recovery strategy, storage costs can also impact the
operational budgets.
This TCO has backups that align to a standard performance tier of Elastic File System (EFS)
service (networked file system).
The EFS costs can significantly impact the operational budget when moving to Provisioned
Throughput mode. Also, the customer must keep a tight check on backup volume or frequency to
avoid overwhelming associated costs with cloud TCO.
EFS pricing can create cost complexities that impact customers as shown in theAmazon Elastic
File System (EFS) Cloud File Storage Pricing page (scroll to the Pricing table).

1
Findings

Findings

You might also like