Sample from the activity log: ANE4952I (Session: 3299, Node: KOPSAPP1) Total number of objects inspected: 55,892 ANE4954I (Session: 3299, Node: KOPSAPP1) Total number of objects backed up: 365 ANE4958I (Session: 3299, Node: KOPSAPP1) Total number of objects updated: 0 ANE4960I (Session: 3299, Node: KOPSAPP1) Total number of objects rebound: 0 ANE4957I (Session: 3299, Node: KOPSAPP1) Total number of objects deleted: 150 ANE4959I (Session: 3299, Node: KOPSAPP1) Total number of objects failed: 12 ANE4961I (Session: 3299, Node: KOPSAPP1) Total number of bytes transferred: 12.15 GB ANE4963I (Session: 3299, Node: KOPSAPP1) Data transfer time: 2,241.35 sec ANE4966I (Session: 3299, Node: KOPSAPP1) Network data transfer rate: 5,684.97 KB/sec ANE4967I (Session: 3299, Node: KOPSAPP1) Aggregate data transfer rate: 1,311.44 KB/sec ANE4968I (Session: 3299, Node: KOPSAPP1) Objects compressed by: 63% ANE4964I (Session: 3299, Node: KOPSAPP1) Elapsed processing time: 02:41:56 NT filesize = 30GB /Regards, Birger Ulbrink -----Oprindelig meddelelse----- Fra: Richard Sims [mailto:[EMAIL PROTECTED]] Sendt: 7. november 2000 13:23 Emne: Re: Number of bytes backed up >Where do I see the number of bytes backed up? > >At the end of the schedule log (and in the accounting log) the number >of bytes transferred are shown, but this does not match the filesize >in NT. Not even taking the "objects compressed by" into the calculation! Do you see more? Less? Please cite an example. Here are my notes on the number, from http://people.bu.edu/rbs/ADSM.QuickFacts: Total number of bytes transferred: In the summary statistics from an Archive or Backup operation, or the Activity Log message ANE4961I which records the client operation stats. Note that the number will probably be less than the sum reflected by including the numbers shown on "Directory-->" lines of the report, in that *SM stores only the name and attributes of directories. Note also that Retry operations may inflate this value, if they result in the file being re-sent to the server, as in the case of the beginning of a direct-to-tape backup, when the tape is not yet mounted. Richard Sims, BU
