PROOF: How Public Cloud Transformed Two Companies. Andy Wolfe, Technical Architect, Maritz Jayme Williams, Senior System Engineer, Tencate

Size: px

Start display at page:

Download "PROOF: How Public Cloud Transformed Two Companies. Andy Wolfe, Technical Architect, Maritz Jayme Williams, Senior System Engineer, Tencate"

Jocelyn Bates
6 years ago
Views:

1 1

2 PROOF: How Public Cloud Transformed Two Companies Andy Wolfe, Technical Architect, Maritz Jayme Williams, Senior System Engineer, Tencate 2

3 JAYME WILLIAMS Senior System Engineer Tencate ANDY WOLFE Technical Architect Martiz 3

4 Azure Story with TenCate About TenCate Environment Overview Our Journey with Zerto Why Azure? Benefits and Savings Key Takeaways AWS Story with Maritz About Maritz Environment Overview Our Journey with Zerto Why AWS? Benefits and Savings Key Takeaways 4

5 About TenCate Textiles technology group Royal TenCate (TenCate) is a multinational global company Develops and produces solutions for the protection of people and their working and living environment 4,454 employees Revenues: 1,159 million

6 Environment Overview ENVIRONMENT Virtualized for increased utilization & cost saving HA/DRS FACTOR Replication between locations worldwide DATA 32 VMs 8.3 TBs APPLICATIONS SUPPORTED ERP Applications Industrial Automation VMs at sites File servers / DFS (2016) Citrix farm / RDS farm Crystal Reports Microsoft SharePoint Business Objects Microsoft SQL Server CHALLENGE 3 MBPS Limited Bandwidth 6

7 7 Our Journey with Zerto

8 Why Azure? Migration to O365 drove more investigation of Azure services Hybrid Exchange Hybrid SharePoint Hybrid Lync / Skype CRM Familiar applications supported ERP Applications Easier licensing and control of end user software Allows for up to 10 installs / home use Transition to SQL as a service Zerto supports replication to it! 8

9 Zerto Benefits & Savings RTO near our datacenter statistics No more hardware refreshes No more firmware upgrades Expansion at the click of a button Constant innovation Price competition between public cloud providers Access to expansive support network of public cloud providers Monitoring and alerting services provided 9

10 Key Takeaways Pick the service that meets your business needs Look for solutions from all providers rather than just picking a single provider Engage with peers to learn use cases Take advantage of free trials Ask your Microsoft rep for free credits! 10

11 About Maritz Helping employees attain their best so business performs its best Saint Louis Best Place to Work ~4000 employees globally Revenues: $1B

STRATEGY Self-managed datacenters in different regions Public cloud footprint in AWS (mostly

12 Environment Overview CHALLENGE Multiple RTO/RPO Requirements INFRASTRUCTURE Co-op model Share where it makes sense DR STRATEGY 74 servers in AWS 111 across legacy recovery sites HOSTING STRATEGY Self-managed datacenters in different regions Public cloud footprint in AWS (mostly IaaS) and Azure (mostly PaaS) 112 VMware hosts, ~1600 guests Several Solaris boxes for financial applications 12

13 13 Our Journey with Zerto

locked into an approach; businesses tentatively strategizing cloud first roadmap Timing: 72-hour RTO with 15-minute RPO

14 Why AWS? Business goals Recovery scope: More systems at full capacity with less cost Hosting flexibility: No 3-year capital expense locked into an approach; businesses tentatively strategizing cloud first roadmap Timing: 72-hour RTO with 15-minute RPO Technical reasoning Public cloud would greatly reduce DR-standby costs and be a proof-of-concept for cloud hosting roadmap Zerto can replicate to public cloud, at that time only to AWS Replica of servers would reduce configuration nightmare 14

previous cost estimates compared to passive standby Zerto replication addressed technical challenges Timing:

15 Zerto Benefits & Savings Public cloud recovery greatly reduced capital expense Initial implementation saved 20% over 3 years Successful recovery prompted another BU to implement DR for the first time ever, saving 90% of previous cost estimates compared to passive standby Zerto replication addressed technical challenges Timing: Local files on servers must match database recovery point Configuration management: DR mirrors production without drift 15

16 Key Takeaways Determine where it fits best AWS Increase ec2-import-instance/volume limit from 5 to 20 Import takes hours for 600GB server Assign secondary IPs and change EC2 instance sizes through script Reserve EC2 instance(s) for lower cost to run Zerto Cloud Appliances What s next for Zerto at Maritz? Expand approach to remaining BUs Recover in Azure for potentially lower RTO Protect SQL Servers and Oracle through Zerto 16

17 17 Thank You!

Super Simple and Disaster Recovery

Super Simple and Disaster Recovery Really Can Go Together Here s the Proof SUPER SIMPLE AND DISASTER RECOVERY REALLY CAN GO TOGETHER 1 Zerto is a mission-critical application for our business, and we could