{"id":8463,"date":"2019-10-14T19:08:51","date_gmt":"2019-10-14T09:08:51","guid":{"rendered":"https:\/\/nsrd.info\/blog\/?p=8463"},"modified":"2019-10-14T19:08:56","modified_gmt":"2019-10-14T09:08:56","slug":"basics-architecture-matters","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2019\/10\/14\/basics-architecture-matters\/","title":{"rendered":"Basics \u2013 Architecture Matters"},"content":{"rendered":"\n

Here’s a typical sort of challenge: you’ve got a workload running in public cloud, but there’s a strong desire to get a copy of the workload on-premises. Maybe it’s something like an Oracle or SQL RDS export, or maybe it’s some other database you’d like to copy out.<\/p>\n\n\n\n

Particularly for RDS protection, from a day to day basis you’re going to use cloud native protection \u2014\u00a0so something like Cloud Snapshot Manager, for instance. But what about that copy that’s going to land back on-premises, or maybe even go to another cloud? Your compliance copy matters, but so too do your recurring costs.<\/em><\/p>\n\n\n\n

Well here’s where architecture matters when it comes to deduplication efficiency, yet again.<\/p>\n\n\n\n

\"Calculating
Calculating your architectural efficiency<\/figcaption><\/figure>\n\n\n\n

Let’s say you’re comparing Product X<\/strong>, who estimate their database backups will achieve 7:1 deduplication, and a Data Domain derived solution (e.g., DDVE in public Cloud \u2014\u00a0or for that matter an IaaS system in public cloud running a backup agent) that might instead give you 20:1 deduplication for database backups.<\/p>\n\n\n\n

Now in either case, there’s going to be an export of some fashion, but then we need to either backup and replicate the data, or backup the data, and at some point that data is going to exit your cloud provider (in this case, looking at AWS) and come into your datacenter (or go to another cloud).<\/p>\n\n\n\n

So let’s assume you’ve got 100TB of databases you need to get out each month. We talk about deduplication efficiency in terms of storage size, but what about data egress amounts?<\/p>\n\n\n\n

Well, for X<\/strong>, at 7:1 deduplication, you’re going to need to pull 14.29 TB out each month. Using the AWS calculator<\/strong><\/a>, egressing that data via EC2 (i.e., a virtual machine holding the appropriate agents and tools) out of the Asia Pacific (Sydney) region is going to be a monthly fee of $2,262.94 (USD).<\/p>\n\n\n\n

Via a Data Domain deduplication engine, at 20:1 deduplication efficiency? That’d just be 5TB<\/strong> per month egress, which for Sydney again would give you a monthly fee of $1,147.33 (USD).<\/p>\n\n\n\n

Over the course of a year, that’s $27,155 USD vs $13,767 USD: a pricing increase of almost double<\/em> due to inefficient deduplication approaches.<\/p>\n\n\n\n

Architecture matters<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Here’s a typical sort of challenge: you’ve got a workload running in public cloud, but there’s a strong desire to…<\/p>\n","protected":false},"author":1,"featured_media":8464,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[3,1229],"tags":[301,1477],"class_list":["post-8463","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-architecture","category-cloud","tag-deduplication","tag-deduplication-ratio"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t