Adam Slesinger wrote:
>
> If i could ask one more question: Where do I go to find out what the lables
> for the
> fields are in the accounting records?
The following is pasted from the Administrator's Guide
There are 29 fields, which are delimited by commas (,). Each record ends
with a new-line character. Each
record contains the following information:
+------------------------------------------------------------------------+
& Field & Contents
&
+--------+---------------------------------------------------------------&
& 1 & Product level
&
+--------+---------------------------------------------------------------&
& 2 & Product sublevel
&
+--------+---------------------------------------------------------------&
& 3 & Product name, 'ADSM',
&
+--------+---------------------------------------------------------------&
& 4 & Date of accounting (mm/dd/yyyy)
&
+--------+---------------------------------------------------------------&
& 5 & Time of accounting (hh:mm:ss)
&
+--------+---------------------------------------------------------------&
& 6 & Node name of ADSM client
&
+--------+---------------------------------------------------------------&
& 7 & Client owner name (UNIX)
&
+--------+---------------------------------------------------------------&
& 8 & Client Platform
&
+--------+---------------------------------------------------------------&
& 9 & Authentication method used
&
+--------+---------------------------------------------------------------&
& 10 & Communication method used for the session
&
+--------+---------------------------------------------------------------&
& 11 & Normal server termination indicator (Normal=X'01',
&
& & Abnormal=X'00')
&
+--------+---------------------------------------------------------------&
& 12 & Number of archive database objects inserted during the
&
& & session
&
+--------+---------------------------------------------------------------&
& 13 & Amount of archived files, in kilobytes, sent by the client to
&
& & the server
&
+--------+---------------------------------------------------------------&
& 14 & Number of archived database objects retrieved during the
&
& & session
&
+--------+---------------------------------------------------------------&
& 15 & Amount of space, in kilobytes, retrieved by archived objects
&
+--------+---------------------------------------------------------------&
& 16 & Number of backup database objects inserted during the session
&
+--------+---------------------------------------------------------------&
& 17 & Amount of backup files, in kilobytes, sent by the client to
&
& & the server
&
+--------+---------------------------------------------------------------&
& 18 & Number of backup database objects retrieved during the
&
& & session
&
+--------+---------------------------------------------------------------&
& 19 & Amount of space, in kilobytes, retrieved by backed up objects
&
+--------+---------------------------------------------------------------&
& 20 & Amount of data, in kilobytes, communicated between the client
&
& & node and the server during the session
&
+--------+---------------------------------------------------------------&
& 21 & Duration of the session, in seconds
&
+--------+---------------------------------------------------------------&
& 22 & Amount of idle wait time during the session, in seconds
&
+--------+---------------------------------------------------------------&
& 23 & Amount of communications wait time during the session, in
&
& & seconds
&
+--------+---------------------------------------------------------------&
& 24 & Amount of media wait time during the session, in seconds
&
+--------+---------------------------------------------------------------&
& 25 & Client session type. A value of 1 or 4 indicates a general
&
& & client session. A value of 5 indicates a client session that
&
& & is running a schedule.
&
+--------+---------------------------------------------------------------&
& 26 & Number of space-managed database objects inserted during the
&
& & session
&
+--------+---------------------------------------------------------------&
& 27 & Amount of space-managed data, in kilobytes, sent by the
&
& & client to the server
&
+--------+---------------------------------------------------------------&
& 28 & Number of space-managed database objects retrieved during the
&
& & session
&
+--------+---------------------------------------------------------------&
& 29 & Amount of space, in kilobytes, retrieved by space-managed
&
& & objects
&
+------------------------------------------------------------------------+
>
> thanks!
> adam
>
> Dwight Cook wrote:
>
> > OK... were there 63 "begin" and "end" sessions ? ? ?
> > what exactly were you counting to get 63 ? ? ? (accounting record
> > entries? ? ?)
> >
> > You have spotted why you want to try to keep a single adsm volume on a
> > single physical device ! (no really, good deal) ADSM ends up
> > treating all its "defined volumes" kind'a like a RAID array. Inbound
> > data is spread out across the disks... Ever wondered why a MOVE DATA
> > against a 4 GB disk volume ends up moving 20 GB to tape ? ? ?
> >
> > Also note... if you look at the accounting records for an archive
> > session that pushes only a single file, you will see 2 archive
> > objects. One is the file itself and the other is the directory
> > information (for the directory where the file resides...)
> >
> > later,
> > Dwight
> >
> > ______________________________ Reply Separator
> > _________________________________
> > Subject: Files Archived Twice - why?
> > Author: aslesinger (aslesinger AT US.BNSMC DOT COM) at unix,mime
> > Date: 3/17/99 2:48 PM
> >
> > Hello everybody. First of all, I've got to say that I love this list!
> > I've been able to resolve two other problems with the responses that
> > I've gotten. Well, what do you think of this one?
> >
> > I'm setting up our ability to archive with ADSM for Month-End. I've
> > defined four volumes (dsm.arch1, dsm.arch2, dsm.arch3, and dsm.arch4)
> > to the storage pool ARCHIVEPOOL which is disk. I kicked off an archive
> > of 4 directories and several sub directories on my PC (WIN95 - v3r1
> > level 0.1) as a test.
> >
> > Normally after a backup or archive finishes, the statistics are sent
> > from the client to the activity log on the server. Well, when I checked
> > the activity log, there was 63 sets of statistics from that archive! It
> > looked as though it did 63 archives. That's my first question: Why did
> > it do that?
> >
> > The archived data was spread out on 3 of the disk volumes and so I did a
> > 'Q CONTENT' on each one. After inspecting the output, I noticed that
> > about 50 files (the majority from one directory) were stored in one one
> > volume *and* also in another volume. That's my second question: Why did
> > it archive these files more than once, in two different places?
> >
> > My environment: ADSM Server 3.1.1.5 on AIX 4.2.1 ADSM Client 3.1.0.5
> > on WIN95
> >
> > Thanks for any help with this!!!
> > adam
> > __________________
> > Adam Slesinger
> > Corporate Information Systems
> > Brown & Sharpe, RI
> > Phone: (401) 886-2236
> > Email: aslesinger AT us.bnsmc DOT com
|
