Hi Kelly. The Copy serialization is set to "Static". The NT
client has 2 additional drives used for storing billing invoices.
After investigating further, I found the culprit. It was our
billing people who had placed hundreds of invoice files in those
drives.
Thanks for everyone's input. Sorry for the false alarm.
Angel
P.S. Kelly, looks like we need to postpone your trip to Hawaii. :)
-----Original Message-----
From: lipp [SMTP:lipp AT storsol DOT com]
Sent: Wednesday, May 12, 1999 9:25 AM
To: ADSM-L
Cc: lipp
Subject: Re: Full or Incremental?
What sort of data is it? The very large data transfered number might
be
because you have sharstatic set as your copy serialization in the
backup
copy group. If a file is open, say a notes database or somesuch,
then ADSM
will try to back it up perhaps four times and then fail. You'll see
lots
of bytes moved, but not many files.
Tell us a little more about the data and show us the copygroup
parameters.
I think I'll need to fly on over and help out on this one, don't you
think?
How many of us would trade our ADSM problems here for ADSM problems
in
Hawaii?
Kelly J. Lipp
Storage Solutions Specialists, Inc.
www.storsol.com
lipp AT storsol DOT com
(719)531-5926
-----Original Message-----
From: ANGEL BUGARIN
Sent: Wednesday, May 12, 1999 12:54 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Full or Incremental?
Hello Everyone. Our incremental backup of one NT client
took longer than normal to complete. It ran as if it was a
full backup. I looked at the dsmsched log and it showed the
process ran as incremental. The following is a comparison
of a full backup to our daily incremental:
05/09/1999 00:17:39
------------------------------------------------------------
05/09/1999 00:17:39 Schedule Name: HOWEBP01-FULL
05/09/1999 00:17:39 Action: Selective
05/09/1999 00:17:39 Objects: c:\*.* d:\*.* e:\*.*
05/09/1999 00:17:39 Options:
05/09/1999 00:17:39 Server Window Start: 00:10:19 on 05/09/1999
05/09/1999 00:17:39
------------------------------------------------------------
.
.
05/09/1999 06:57:20 Total number of objects inspected: 26,890
05/09/1999 06:57:20 Total number of objects backed up: 25,479
05/09/1999 06:57:20 Total number of objects updated: 0
05/09/1999 06:57:20 Total number of objects rebound: 0
05/09/1999 06:57:20 Total number of objects deleted: 0
05/09/1999 06:57:20 Total number of objects failed: 140
05/09/1999 06:57:20 Total number of bytes transferred: 26.7 GB
05/09/1999 06:57:20 Data transfer time: 18,225.93 sec
05/09/1999 06:57:20 Data transfer rate: 1,537.62
KB/sec
05/09/1999 06:57:20 Average file size: 1,099.0 KB
05/09/1999 06:57:20 Elapsed processing time: 6:39:40
05/12/1999 00:40:57
------------------------------------------------------------
05/12/1999 00:40:57 Schedule Name: HOWEBP01-INC
05/12/1999 00:40:57 Action: Incremental
05/12/1999 00:40:57 Objects:
05/12/1999 00:40:57 Options:
05/12/1999 00:40:57 Server Window Start: 00:32:17 on 05/12/1999
05/12/1999 00:40:57
------------------------------------------------------------
.
.
05/12/1999 07:03:57 Total number of objects inspected: 27,239
05/12/1999 07:03:57 Total number of objects backed up: 5,752
05/12/1999 07:03:57 Total number of objects updated: 0
05/12/1999 07:03:57 Total number of objects rebound: 0
05/12/1999 07:03:57 Total number of objects deleted: 1
05/12/1999 07:03:57 Total number of objects failed: 139
05/12/1999 07:03:57 Total number of bytes transferred: 25.6 GB
05/12/1999 07:03:57 Data transfer time: 18,173.45 sec
05/12/1999 07:03:57 Data transfer rate: 1,482.83
KB/sec
05/12/1999 07:03:57 Average file size: 4,683.7 KB
05/12/1999 07:03:57 Elapsed processing time: 6:22:59
The incremental backup has been running fine since last night.
Any idea? Any suggestion on how to fix this?
Aloha,
Angel Bugarin
Sprint/Hawaii
|
