Re: [Veritas-bu] Data Domain Question
If you are currently dumping SQL to disk, more than likely, you are compressing your data. Your dedup rate will not be good with this data, because of the compression. When we did our POC, I gave my DBAs specific instructions to send the backups uncompressed. That way, the DataDomain would catch the actual duplicate blocks. To my surprise, it actually caught duplicate blocks in the first backup alone. It only got better from there. The key is whether you are doing compression or not. There are DBAs out there that even though you ask them to turn compression off, they will think that you really couldn't mean it. It runs counter intuitive to how they have been taught. Just tell them its big in the beginning, but the payoff comes after a week or two. From: mitch808 nbu-fo...@backupcentral.com To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Date: 08/17/2011 05:43 PM Subject: [Veritas-bu] Data Domain Question Sent by: veritas-bu-boun...@mailman.eng.auburn.edu I've got a customer with 30TB of SQL data, and a 30% daily change rate. He at best gets a 4.5:1 reduction But I've also got another with a 4% daily change rate, that gets closer to 20:1. It just depends... Though I don't agree with the above post that dedupe appliances cant dedupe SQL well. As that is not the case in my 2nd example. +-- |This was sent by mnab...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu PLEASE NOTE: The preceding information may be confidential or privileged. It only should be used or disseminated for the purpose of conducting business with Parker. If you are not an intended recipient, please notify the sender by replying to this message and then delete the information from your system. Thank you for your cooperation. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Data Domain Question
Currently our SQL team run SQL LiteSpeed with compresson. They really dont want to turn it off. We keep 5 weeks of data for our SQL backups and are getting 2.1 to 3.5 dedupe ratio's even with compression backup on. +-- |This was sent by rich.sav...@bcbsne.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Data Domain Question
Compressing compressed data sometimes has the effect of actually INCREASING the space utilized. Luckily deduplication is preventing this for you but really, why spend processing time on the server to compress data that is going to be compressed on the appliance? -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of rsavage Sent: Thursday, August 18, 2011 2:05 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] Data Domain Question Currently our SQL team run SQL LiteSpeed with compresson. They really dont want to turn it off. We keep 5 weeks of data for our SQL backups and are getting 2.1 to 3.5 dedupe ratio's even with compression backup on. +-- |This was sent by rich.sav...@bcbsne.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu Proud partner. Susan G. Komen for the Cure. Please consider our environment before printing this e-mail or attachments. -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Data Domain Question
Simple - time to perform the backup might still be shorter. A couple years ago I did a Data Domain install at a customer that was using SQL LiteSpeed for their SQL servers. SQL LiteSpeed was compressing the data before sending it over the wire. Even though they got better dedup numbers with compression disabled, the time involved in sending the uncompressed data over the wire to the Data Domain was much longer than when they compressed it. If I remember correctly, it was on the order of 3-4x faster to do the backup with the LiteSpeed compression enabled. Data Domain doesn't provide the option of a share/export that bypasses the deduplication engine - if it did we would have used that. As it was, they had enough capacity in their Data Domain to handle a portion of data that did not deduplicate as well as theoretically possible. If you've got 10GbE everywhere, then this argument goes out the window. But I wanted to show that there are times when sending compressed data to a Data Domain makes sense. -daniel -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Lightner, Jeff Sent: Thursday, August 18, 2011 1:14 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] Data Domain Question Compressing compressed data sometimes has the effect of actually INCREASING the space utilized. Luckily deduplication is preventing this for you but really, why spend processing time on the server to compress data that is going to be compressed on the appliance? -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of rsavage Sent: Thursday, August 18, 2011 2:05 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] Data Domain Question Currently our SQL team run SQL LiteSpeed with compresson. They really dont want to turn it off. We keep 5 weeks of data for our SQL backups and are getting 2.1 to 3.5 dedupe ratio's even with compression backup on. +-- |This was sent by rich.sav...@bcbsne.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu Proud partner. Susan G. Komen for the Cure. Please consider our environment before printing this e-mail or attachments. -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Data Domain Question
I've got a customer with 30TB of SQL data, and a 30% daily change rate. He at best gets a 4.5:1 reduction But I've also got another with a 4% daily change rate, that gets closer to 20:1. It just depends... Though I don't agree with the above post that dedupe appliances cant dedupe SQL well. As that is not the case in my 2nd example. +-- |This was sent by mnab...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Data Domain Question
Hi all, Anyone using a Data Domain VTL in the following manner? - 1 normal weekly full to start (Saturday/Sunday) - 5 incrementals daily (Monday through Friday) - following Saturday/Sunday create a synthetic full backup - repeat incremental / synthetic full cycle Does this seem like a logical use of the dedupe product? Is it even feasible? What are some of the cons? I want to minimize the hit on the primary systems (reduce the backup window, etc, etc), but still be able to perform full backups every week. I'd also want to replicate all that good stuff to a remote site (which I hear DD is good at ;-) Thanks for any input. Cheers, Jon ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
