Have you tried to use exclude.fs option in you inclexcl list:
exclude.fs /fsdbexp
And then "DELete FIlespace PACRS170 /fsdbexp".
This should allow you not to change domain from all-local preventing future
created filesystems missing from backup!
Zlatko Krastev
IT Consultant
PAC Brion Arnaud <arnaud.brion AT PANALPINA DOT COM> on 08.11.2001 11:33:42
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: TSM wizardry ?
Hi folks !
Here is a case that seems really strange to me.
The picture : we have a node called pacrs170, that hosts a filespace
named /fsdbexp. We used to backup this filespace daily, until we found
it was useless keeping that data. I then decided do delete this
filespace from TSM db, what worked perfectly : no trace from it at all,
using show version, q fi, q occ aso .....
The day after, I checked this node again, and found the filespace was
back, using q fi !
I am sure the filespace is excluded from my backup :
this is an extract of my inclexcl :
Exclude /fsdbexp/.../*
Exclude /fsdbexp/*
and this is an extract of backup log :
11/05/01 21:12:14 Normal File--> 847
/fsAdmin/DBA/TOOLS/SQL/upd stats ol2.sql [Sent]
11/05/01 21:12:17 Successful incremental backup of '/fsAdmin'
11/05/01 21:12:17 Successful incremental backup of '/fsdbexp'
11/05/01 21:12:17 Symbolic Link--> 18
/fr170ifxsrv2/chunk/lr170asd5101 [Sent]
This node belongs a policy domain who's default management class is
called AIX-SYSTEM, but was once backuped using another mgmt class called
backup 2 years, whose backup copy group has following caracteristics :
Versions Data Exists NOLIMIT
Versions Data Deleted NOLIMIT
Retain Extra Versions 730
Retain Only Version 730
Copy Mode MODIFIED
Copy Serialization SHRDYNAMIC
Copy Frequency 0
Copy Destination DISKPOOL ARCH
If I now do a q occ for this node, I don't see nothing concerning this
/fsdbexp filespace, but if I do a q fi I obtain :
PACRS170 /fsdbexp AIX JFS
65,536.0 85.9
Doing a show version pacrs170 /fsdbexp gives me (snippet of it) :
/fsdbexp : / pacpan save (MC: BACKUP 2 YEARS)
Active, Inserted 11/07/01 21:11:54
ObjId: 0.91678174
/fsdbexp : / tivoli (MC: BACKUP 2 YEARS)
Active, Inserted 11/07/01 21:11:54
ObjId: 0.91678175
/fsdbexp : /dbexp1/ HPL (MC: BACKUP 2 YEARS)
Active, Inserted 11/07/01 21:11:54
ObjId: 0.91678176
/fsdbexp : /dbexp1/HPL/ agent (MC: BACKUP 2 YEARS)
Active, Inserted 11/07/01 21:11:54
ObjId: 0.91678177
/fsdbexp : /dbexp1/HPL/ db admin (MC: BACKUP 2 YEARS)
Active, Inserted 11/07/01 21:11:54
ObjId: 0.91678178
Could anybody explain me why this filespace comes back when I delete it,
why I can see it using q fi, but not using q occ, and why "show version"
shows me those objects with inserted date corresponding (ok few seconds
difference) with the date of daily backup for this node, but using a
mgmt class not associated with this filespace in my incl-excl list,
furthermore this list excludes that filespace !???
Is it linked with the fact I backuped that filespace once using mgmt
class "backup 2 years" that has retain only version 730 days ? How could
I then definitely erase this data ? I'm very confused, if anybody has a
clue ...
TIA.
Arnaud
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| Arnaud Brion, Panalpina Management Ltd., IT Group |
| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01 |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|
