The Administrators Guide is a bit vague on the process of determining a
file's eligibility due to changes...
I assume ADSM uses, file timestamp, filesize as the main items. I'm doubt if
it delves as deep as changed inode numbers or fat table entries, as this
would
produce very large overhead for the server to go and check, and the database
would be huge.
NT is a different story to Unix, you're either running FAT or NTFS, I'm not
sure how TSM under NT will handle a file's physical movement on the disk.
I'm
surprised if a defragment would trigger incrementals. It's undesirable
behaviour really.
Admin guide segment follows:
"The backup of files according to policy defined in the backup copy group of
the management class for the files. An incremental backup typically backs up
all files that are new or that have changed since the last incremental
backup. "
When a user requests a full incremental backup, TSM performs the following
steps to determine eligibility:
Checks each file against the user's include-exclude list:
* Files that are excluded are not eligible for backup.
* If files are not excluded and a management class is specified with
the INCLUDE option, TSM uses that management class.
* If files are not excluded but a management class is not specified
with the INCLUDE option, TSM uses the default management class.
* If no include-exclude list exists, all files in the client domain
are eligible for backup, and TSM uses the default management class.
Checks the management class of each included file:
* If there is a bckup copy group, the process continues with step 3.
* If there is no backup copy group, the file is not eligible for
backup.
Checks the mode, frequency, and serialization defined in the backup
copy group.
Mode
Specifies whether the file is backed up only if it
has changed since the last backup (modified) or whenever a backup is
requested (absolute).
Frequency
Specifies the minimum number of days that must
elapse between backups.
Serialization
Specifies how files are handled if they are modified
while being backed up and what happens if modification occurs.
* If the mode is modified and the minimum number of days have elapsed
since the file was last backed up, TSM determines if the file has been
changed since it was last backed up:
* If the file has been changed and the serialization requirement is
met, the file is backed up.
* If the file has not been changed, it is not backed up.
* If the mode is modified and the minimum number of days have not
elapsed since the file was last backed up, the file is not eligible for
backup.
* If the mode is absolute, the minimum number of days have elapsed
since the file was last backed up, and the serialization requirement is met,
the file is backed up.
* If the mode is absolute and the minimum number of days have not
elapsed since the file was last backed up, the file is not eligible for
backup.
> -----Original Message-----
> From: Ochs, Duane [SMTP:Duane.Ochs AT QG DOT COM]
> Sent: Friday, March 22, 2002 6:28 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Why are all my NT files getting backed up again?
>
> In our environment, I have seen this when a checkdisk has been performed,
> a
> drive has been swapped, defragmenting a drive can cause the defragmented
> data to be sent, moving disks in a SAN. I would have to guess that
> breaking
> a mirror set and bringing up the mirror instead of a primary drive could
> produce the same result. To test you can move all the data from one
> directory into another and then back to the same directory, I am sure it
> will all be backed up at the next backup.
>
> I do not know every technical nuance to TSM but when the file is scanned
> and
> checked against the TSM DB it sees that the file location has changed and
> there needs to be backed up. I have not looked into a way to work around
> this but I would guess there is not a way.
>
>
> Duane Ochs
> Systems Administration
> Quad/Graphics Inc.
> 414.566.2375
>
>
> -----Original Message-----
> From: Louie, James [mailto:LouieJ AT NABISCO DOT COM]
> Sent: Thursday, March 21, 2002 3:39 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Why are all my NT files getting backed up again?
>
>
> I have a few NT4 servers with TSM 4.2.1.20 client that occasionally do a
> full backup instead of an incremental. There are many files that have no
> change in size or date or permissions (at least that I can see). I just
> turned file auditing on to see if I can catch anything. Any ideas on what
> may trigger a full backup? Thanks in advance.
>
> James Louie
> Philip Morris Management Corp.
> ITSC - Windows Integration Services
> 7 Campus Drive, Parsippany, NJ 07054
> 973.682.7150 louiej AT nabisco DOT com
>
>
>
>
> "The information in this email, and in any attachments,
> may contain confidential information and is intended
> solely for the attention and use of the named addressee(s).
> It must not be disclosed to any person without authorization.
> If you are not the intended recipient, or a person responsible for
> delivering it to the intended recipient, you are not authorized
> to, and must not, disclose, copy, distribute, or retain this
> message or any part of it."
**************************************************************************
Bunnings Legal Disclaimer:
1) This document is confidential and may contain legally privileged
information. If you are not the intended recipient you must not
read, copy, distribute or act in reliance on it.
If you have received this document in error, please telephone
us immediately on (08) 9365-1555.
2) All e-mails sent to and sent from Bunnings Building Supplies are
scanned for content. Any material deemed to contain inappropriate
subject matter will be reported to the e-mail administrator of
all parties concerned.
**************************************************************************
|
