Some thoughts: (a) How do you know the files are being backed up to the wrong management class?
(b) Keep in mind that *directories* are bound to the management class that has the highest RETONLY setting. In the case of two or management classes having the highest RETONLY setting, the management class whose name is highest in ASCII sorting order will be used for directories (unless overridden with the DIRMC option). Is it possible you are seeing directory entries bound to the "wrong" management class? (c) Make sure that when you do the backup, you are using the correct dsm.sys stanza that contains the desired INCLUDE statement. (d) You've got some other EXCLUDES in there that take precedent over the desired INCLUDE. Is it possible that you have files matching anything in the EXCLUDE patterms, e.g., /BACKUP/outgoing/oradata/somefile ? (e) Do a sample backup of files in the /BACKUP/outgoing directory... for example, do a SELECTIVE backup of one of these files, then do a QUERY BACKUP for the file so we can see the management class. Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 2005-09-20 02:08:23: > Hi all, > > Accidently sent the mail before without adding all the info! Apologies > for the resend. > > I am having probably a hopefully simple problem with management classes. > I backup a server and it goes to the default management class, which has > a retention of ninety days. There is one set of data on this server that > I want backed up to a different management class so it is retained for a > year instead of ninety days. Here is the dsm.sys entry on the client: > > include /BACKUP/outgoing/.../* CR_ONE_YEAR > > When I run a q inclexcl on the client I get the following: > > tsm> q inclexcl > *** FILE INCLUDE/EXCLUDE *** > Mode Function Pattern (match from top down) Source File > ---- --------- ------------------------------ ----------------- > Excl Filespace /FMS/fmsprod/gbls dsm.sys > Excl Filespace /IBS/ibsprod/gbls dsm.sys > Excl Directory /dev Server > Excl Directory /unix Server > Excl All /.../tmp/.../* Server > Excl All /.../oradata/.../* Server > Excl All /.../core Server > Incl All /BACKUP/outgoing/.../* dsm.sys > Excl All /BACKUP/online/.../* dsm.sys > No DFS include/exclude statements defined. > > And on the server here is a q mgmt: > > tsm: BKP>q mgmt standard standard cr_one_year f=d > > Policy Domain Name: STANDARD > Policy Set Name: STANDARD > Mgmt Class Name: CR_ONE_YEAR > Default Mgmt Class ?: No > Description: Management Class For Critical Systems > Space Management Technique: None > Auto-Migrate on Non-Use: 0 > Migration Requires Backup?: Yes > Migration Destination: CRDATATAPE > Last Update by (administrator): ADMIN > Last Update Date/Time: 2005.06.24 09:38:24 > Managing profile: > > And here is query of the backup copygroup for thius mgmt class: > > tsm: BKP>q copygroup > > Policy Policy Mgmt Copy Versions Versions Retain > Retain > Domain Set Name Class Group Data Data Extra > Only > Name Name Name Exists Deleted Versions > Version > --------- --------- --------- --------- -------- -------- -------- > ------- > STANDARD ACTIVE CR_ONE_Y- STANDARD 7 7 40 > 366 > EAR > STANDARD STANDARD CR_ONE_Y- STANDARD 7 7 40 > 366 > EAR > > Does anyone have any idea what I am doing wrong? When I look on the > server for the files it has it only shows the last ninety days still. > > Thanks! > > Sam > > ----------------------------------------------------------------- > ATTENTION: > The information in this electronic mail message is private and > confidential, and only intended for the addressee. Should you > receive this message by mistake, you are hereby notified that > any disclosure, reproduction, distribution or use of this > message is strictly prohibited. Please inform the sender by > reply transmission and delete the message without copying or > opening it. > > Messages and attachments are scanned for all viruses known. > If this message contains password-protected attachments, the > files have NOT been scanned for viruses by the ING mail domain. > Always scan attachments before opening them. > -----------------------------------------------------------------
