ADSM-L

detail trace: erroneous output

2003-08-04 12:38:45
Subject: detail trace: erroneous output
From: Joni Moyer <joni.moyer AT HIGHMARK DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 4 Aug 2003 12:38:35 -0400
Hello everyone!

I'm still doing this tpoc, but this time it's with lto2.  The client is SUN
at 5.2, storage agent is 5.1.6.2 and the server is a sun solaris at
5.1.6.2.  I have a detail trace on the client and I am receiving the
following output.  As you can see it is giving erroneous data for the
pre-compress/post-compress/avg. file size.  I highly doubt that I archived
18PB in 10 minutes, although that would be nice!  Has anyone experienced
this problem?  If so, how did you fix it?  Thanks in advance!!!!

      Session established with server SERVER1: Solaris 7/8
  Server Version 5, Release 1, Level 6.2
  Data compression forced off by the server
  Server date/time: 07/31/03   07:21:14  Last access: 07/31/03   07:20:22

Total number of objects inspected:        2
Total number of objects archived:         2
Total number of objects updated:          0
Total number of journal objects:          0
Total number of objects rebound:          0
Total number of objects deleted:          0
Total number of objects expired:          0
Total number of objects failed:           0
Total number of bytes transferred:     7.81 GB
LanFree data bytes:                    7.81 GB
Server-Free data bytes:                   0  B
Data transfer time:                  329.02 sec
Network data transfer rate:        24,905.47 KB/sec
Aggregate data transfer rate:      13,229.80 KB/sec
Total number of bytes pre-compress:  18,446,744,073,509,294,724
Total number of bytes post-compress: 18,446,744,073,509,294,724
Objects compressed by:                  100%
Elapsed processing time:           00:10:19
Average file size:                 8,191.99 PB


Joni Moyer
Systems Programmer
joni.moyer AT highmark DOT com
(717)975-8338

<Prev in Thread] Current Thread [Next in Thread>
  • detail trace: erroneous output, Joni Moyer <=