Select count(*) from backups = 28million
DB size (used) = 22GB
1 copy pool (everything copied)
-Original Message-
From: Kelly J. Lipp [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 26, 2001 3:59 PM
To: [EMAIL PROTECTED]
Subject: Database entry size for an object
Anybody have an idea
Agreed, we do have a trivial amount of archiving on this server, answer is
actually 28.2 million...
-Original Message-
From: Andy Raibeck [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 27, 2001 9:37 AM
To: [EMAIL PROTECTED]
Subject: Re: Database entry size for an object
Don't forget
-4807
Kelly J.
LippTo: [EMAIL PROTECTED]
lipp@storsolcc:
.comSubject: Database entry size for an object
Sent by:
ADSM: Dist
]
voice: 804-828-4807
Kelly J.
LippTo: [EMAIL PROTECTED]
lipp@storsolcc:
.comSubject: Database entry size
for an object
Sent by:
ADSM
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
From a posting of mine last year: (adsm v3.1)
From the occupancy table:
22,254,868 ARCHTAPE archives on tape
40,030,448 BACKUP3590_OFFSITEbackup copypool on tape
40,065,503 TAPEPOOL backups on tape
102,350,819
In article [EMAIL PROTECTED], Zoltan
Forray/AC/VCU [EMAIL PROTECTED] says:
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 ?
My fuzzy memory says that IBM reported an increase of 200 bytes for each
copy.
