I believe that TSM backs up the directory, too, if any files have changed in
that directory.
And unless you specify a DIRMC, TSM uses the management class with the
longest retention for DIRECTORY entries. This was a problem people saw
before IBM implemented the DIRMC option. For Unix servers, directory entries
are just entries in the TSM database and do not have any associated data.
Unlike Novell and Windows where you have "data" like the ACL's associated
with directories. Then you have space occupied in a storage pool.
We always create a DIRECTORY management class with the highest retention and
force the DIRMC option out with client option sets. The destination storage
pool for this is a DISK storage pool that doesn't migrate. Just gets backed
up to copypool tape. That way restores are quick as the data comes right
from disk.
Bill Boyer
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
PAC
Brion Arnaud
Sent: Tuesday, March 08, 2005 9:53 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Directory path backed up again and again ...
Hi *SM'ers,
I recently found that one (surely others too) of our AIX clients was
getting part of it's directory structure backed up everyday although it
did not change, but can't find the reason why.
As Andy says it in his excellent web page : A normal Incremental Backup
will *not* back up directories whose timestamp has changed since the
last backup.
We're performing incremental backups, copymode used for this client is
set to modified, so I can't understand what's happening ! The worse is
that the mgmt-class having the longest retention period (retonly 768) in
this domain is used for storing that data, so I end up with thousands
(probably more if other servers are affected !) entries in TSM DB which
are worthless.
This in an example of what I get, using "show version" (snippet of it)
on this server:
/export/mksysb : / (MC: BACKUP_2_YEARS)
Inactive, Inserted 01/07/05 20:51:51, Deactivated 01/10/05 20:37:15
ObjId: 0.539953678, GroupMap 00000000, objType 0x01
/export/mksysb : / (MC: BACKUP_2_YEARS)
Inactive, Inserted 01/10/05 20:37:15, Deactivated 01/12/05 20:37:32
ObjId: 0.541340571, GroupMap 00000000, objType 0x01
/export/mksysb : / (MC: BACKUP_2_YEARS)
Inactive, Inserted 01/12/05 20:37:32, Deactivated 01/14/05 20:37:16
ObjId: 0.542636928, GroupMap 00000000, objType 0x01
/export/mksysb : / (MC: BACKUP_2_YEARS)
Inactive, Inserted 01/14/05 20:37:16, Deactivated 01/15/05 20:38:31
ObjId: 0.544018035, GroupMap 00000000, objType 0x01
/export/mksysb : / (MC: BACKUP_2_YEARS)
Inactive, Inserted 01/15/05 20:38:31, Deactivated 01/16/05 20:38:29
ObjId: 0.544640259, GroupMap 00000000, objType 0x01
/export/mksysb : / (MC: BACKUP_2_YEARS)
Inactive, Inserted 01/16/05 20:38:29, Deactivated 01/17/05 20:38:53
ObjId: 0.545097616, GroupMap 00000000, objType 0x01
This is a NIM server, where "MKSYSB" files from other servers are stored
everyday, so the content of the directory is changing, but not it's
structure.
TSM server is at 5.2.2.1 on AIX 5.2, client is 5.2.3.1,on AIX 5.3
Could someone tell me what is happening here, and how to avoid this ?
TIA.
Arnaud
************************************************************************
******
Panalpina Management Ltd., Basle, Switzerland, CIT Department
Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: arnaud.brion AT panalpina DOT com
************************************************************************
******
|
