Somewhere it's documented that a COPY in a copy pool increases the SIZE of
the DB entry, does not create a second entry.
-----Original Message-----
From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 26, 2001 3:51 PM
To: [EMAIL PROTECTED]
Subject: Re: Database entry size for an object
I would also like to know if creating a COPY produces *2* entries in the DB
or is the 400-800 bytes a measure of WITH and WITHOUT a COPY ?
===========================
Zoltan Forray
Virginia Commonwealth University
University Computing Center
WWW.VCU.EDU
e-mail: [EMAIL PROTECTED]
voice: 804-828-4807
"Kelly J.
Lipp" To: [EMAIL PROTECTED]
<lipp@storsol cc:
.com> Subject: Database entry size
for an object
Sent by:
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>
06/26/2001
03:59 PM
Please
respond to
lipp
Anybody have an idea what the true average db entry for an object is? How
much space is really consumed per database entry for a backup object?
We're
taught 400-800 bytes per entry but this seems high.
Perhaps we can arrive at this empirically by getting an idea from some of
you about how many objects you have in your db and the size of that db.
We'll do math.
I have a customer with about 2 billion files. We're trying to size a db or
two to back this up. We're thinking at least four servers to handle this.
So some numbers please: number of items in the database and the db size.
Thanks,
Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80949-1313
(719) 531-5926
Fax: (240) 539-7175
Email: [EMAIL PROTECTED] or [EMAIL PROTECTED]
www.storsol.com
www.storserver.com
