:
[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
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
-
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
: 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
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.
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
