On Thursday, 20 March 2003 at 13:13:18 +0100, Alexander Haderer wrote:
> At 12:53 20.03.2003 +0100, Maarten de Vries wrote:
>> On Thu, 20 Mar 2003, Dirk-Willem van Gulik wrote:
>>
>>> Depends on what access patterns you have; is it mostly dormant
>>> archiving; or lots of access, concurrent, sequential ? How safe does the
>>> data need to be; and against what (hardware failure, accidental rm -rf).
>>
>> This would be for backup. Data on about 50 webservers would be backed up
>> to it on a nightly basis. So performance wouldn't be important.
>
> Sure? Consider this:
>
> a.
> Filling 3TB with 1 Mbyte/s lasts more than 800 hours or 33 days.

I do a nightly backup to disk.  It's compressed (gzip), which is the
bottleneck.  I get this sort of performance:

dump -2uf - /home | gzip > /dump/wantadilla/2/home.gz
  ...
  DUMP: DUMP: 1254971 tape blocks
  DUMP: finished in 217 seconds, throughput 5783 KBytes/sec
  DUMP: level 2 dump on Thu Mar 20 21:01:31 2003

You don't normally fill up a backup disk at once, so this would be
perfectly adequate.  I'd expect a system of the kind that Maarten's
talking about to be able to transfer at least 40 MB/s sequential at
the disk.  That would mean he could backup over 1 TB in an 8 hour
period.

> b.
> Using ssh + dump/cpio/tar needs CPU power for encryption, especially when
> multiple clients safe their data at the same time.

You can share the compression across multiple machines.  That's what
was happening in the example above.

> c.
> When using FreeBSD 4.X a fsck after a hard reboot will block the server.
> fsck'ing a full 3TB filesystem may need a long time. Its better to use
> several smaller file systems.

You don't have to fsck at boot time, not even in Release 4.

> d.
> Wrong parameters for newfs may slowdown large filesystems and waste lots of
> space. Before using large filesystems read the manpage of newfs, especially
> the topics about options -b -f -i

Correct.  Check the -m option (free space %) as well.  There's no
reason to waste 8% of the space.

Greg
--
See complete headers for address and phone numbers

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to