ADSM-L

Re: Disk-to-Disk Backup

2006-05-16 10:49:23
Subject: Re: Disk-to-Disk Backup
From: Jon Evans <Jon.Evans AT HALLIBURTON DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 16 May 2006 15:49:00 +0100
I have recently tested a DD460 for exactly the same reason. The results
showed that compression was good (upto 20x) but throughput was not so
good. The more clients you add, the slower each backup stream becomes. 
Off course, much depends on your infrastructure, and these results were
based on a windows filesystem, running across a gb network. 
Unfortunately, with millions of small files it is very difficult to
improve performance significantly.
Personally, I could not improve backup or restore performance over an
LTO2 or LTO3 tape drive, and the tape drives still work out cheaper.. so
I decided against it at this time..

Regards

Jon Evans
  



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Christoph Pilgram
Sent: 16 May 2006 14:43
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Disk-to-Disk Backup

Hi all,

Because we have problems to hold our service level agreements with the
customers for restoring big file-servers (10 Mio files, 1TB disk-space
in one filesystem), we are thinking about storing the backups not
anymore on tape but on disk. Does anybody has experience with that kind
of storage-pool for about 40 TB of backup data ? Does anybody use for
example a "Data Domain DD460" or other systems using COS to reduce the
amount of data.

Thanks for help

Chris 
----------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and 
privileged information for the sole use of the intended recipient.  Any review, 
use, distribution, or disclosure by others is strictly prohibited.  If you are 
not the intended recipient (or authorized to receive information for the 
intended recipient), please contact the sender by reply e-mail and delete all 
copies of this message.

<Prev in Thread] Current Thread [Next in Thread>