Our own internal Sepaton shows 22:1 ratio. Should be abit higher, since Sepaton 
shows 25-50 in dedup, but for us, it's enough. We currently have one of the 
small 10TB ones and we're currently using 15% of it. We dont have that big of 
an internal environment though, Lotus Domino, some fileservers, a few WAS 
servers and a bunch of Linux servers running Apache. Ontop of that, we 
currently have some DB2 Content Manager servers, a Commonstore box and some 
other minor servers. We're using OpenOffice internally but I dont think the 
amount of documents created by the users is our big storage part, the WAS 
servers and the apache boxes take alot more storage aswell as the economy 
system.

I'll see if I can check some of our external clients and see what they get out 
of their Sepaton boxes.

Best Regards

Daniel Sparrman

-----"ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> skrev: -----


Till: ADSM-L@VM.MARIST.EDU
Från: Ben Bullock <bbull...@bcidaho.com>
Sänt av: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU>
Datum: 11/12/2010 19:54
Ärende: Re: De-dup ratio's

I know this was aimed at Amos, but I thought I would pipe in.

Our DataDomain has NOT got the VTL option and it is configured as FILE with 
50GB files:

Device        Device         Storage     Device        Format      Est/Max      
Mount
Class         Access            Pool     Type                     Capacity      
Limit
Name          Strategy         Count                                  (MB)     
---------     ----------     -------     ---------     ------     --------     
------
A_DD          Sequential           1     FILE          DRIVE      51,200.0      
   16
DB_DD         Sequential           1     FILE          DRIVE      51,200.0      
   16
DISK          Random               5                                            
     
I_DD          Sequential           1     FILE          DRIVE      51,200.0      
   16
LTO4          Sequential           5     LTO           DRIVE                   
DRIVES

 Works great, re-claims volumes, etc.

Ben


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of 
Schneider, Jim
Sent: Friday, November 12, 2010 11:38 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] De-dup ratio's

Amos,

We are looking into purchasing one of these options.  Do have your
DataDomain device configured at disk or VTL?

Thank you,
Jim Schneider

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Amos ADSM
Sent: Friday, November 12, 2010 12:25 PM
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] De-dup ratio's

Hi All,

Im Using in the last 3 years Protectier, and most of my backup are SQL
Servers ans some ESX Servers, i get 3.9-4 Dedupe ratio, in good times i
manage to get to 6,
In the last 3 Weeks, im running DataDomain , and i get ratio 9 and its
just the begining :-) ( I hope)

In My Site we got 11 TSM Servers, 3 in the Center with more that 1000
Clients (Aix,Linux SQL) and My Diff Backup for my SQL Servers its almost
2 TB a day, and my DD Writes only 100 Gb.

Amos





On 12/11/2010 18:23, Druckenmiller, David wrote:
> I'm curious what others are seeing for de-dup ratios for various
methods.
>
> We're using IBM's ProtecTier for our TSM (5.5) primary pools and only
see about a 4 to 1 ratio.  This is less than half of what IBM was
projecting for us.  We have roughly 400 clients (mostly Windows servers)
totalling about 135TB of data.  Biggest individual uses are Exchange and
SQL Dumps.
>
> Just wondering what others might be getting for other appliances or
with TSM v6?
>
> Thanks
> Dave
>
>
>
> -----------------------------------------
> CONFIDENTIALITY NOTICE: This email and any attachments may contain
> confidential information that is protected by law and is for the
> sole use of the individuals or entities to which it is addressed.
> If you are not the intended recipient, please notify the sender by
> replying to this email and destroying all copies of the
> communication and attachments. Further use, disclosure, copying,
> distribution of, or reliance upon the contents of this email and
> attachments is strictly prohibited. To contact Albany Medical
> Center, or for a copy of our privacy practices, please visit us on
> the Internet at www.amc.edu.



[bilagan "mg_info.txt" borttagen av Daniel Sparrman/Existgruppen/SE]

Reply via email to