For ADSM V3 Windows clients after 3.1.0.5, the filespace name is based on
the Windows UNC name for each drive, rather than on the drive label. So if
somebody changed the Windows NT networking ID, that would change the UNC
name, and force a full backup again, same as Betsy describes below for V2
clients.
You can check this by looking at the filespaces for the client from the
ADMIN gui - does the client now have more filespaces represented on the
server than it has real drives?
Other things that can happen on WinNT clients are ownership changes.
ADSM checks the date of each file, the size, and also the NTFS ACL's.
If a user renamed a large directory structure, OR, if somebody fiddled with
the file permissions or ownership, that can make ADSM think it needs to back
up files even though the files themselves have not changed.
> -----Original Message-----
> From: Moir,Betsy [SMTP:betsy.moir AT ABBOTT DOT COM]
> Sent: Wednesday, May 12, 1999 3:27 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Full or Incremental?
>
> We have version 2 clients and a version 2 server and I know from reading
> this
> list that the version 3 world is much different, but whenever we've gotten
> an
> incremental backup that "looked like" and was about the size of a full
> backup, it was because the drive labels had been changed and ADSM thought
> all
> the files were new so backed them all up. I don't know if that would have
> the same kind of effect on version 3 or not.
>
>
>
>
> ADSM-L AT VM.MARIST DOT EDU on 05/12/99 02:02:17 PM
> Please respond to ADSM-L AT VM.MARIST DOT EDU @ INTERNET
> To: ADSM-L AT VM.MARIST DOT EDU @ INTERNET
> cc:
> 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
>
>
|
