ADSM-L

Re: Management Class DEFAULT

2000-02-09 07:29:35
Subject: Re: Management Class DEFAULT
From: Clarence Beukes <clarence AT ZA.IBM DOT COM>
Date: Wed, 9 Feb 2000 14:29:35 +0200
Hi Thomas...

Each policy set must  a default management class. The reason is that one policy
set can have many management classes, because users might decide that they want
their data to be treated differently by ADSM.

ADSM uses the default management class when:

 * A user does not specify a management class in their include-exclude
   list. The server then uses the default management class to manage files
   when they are backed up or archived.

 * The management class associated with a backup copy or archived file is
   deleted. If the default management class does not contain a backup or
   archive copy group, the retention grace period for the policy domain is
   used.

* The archive copy group is deleted from a management class; archived
  files that are bound to that management class are then managed with the
  default management class (assuming that the default management class
  contains an archive copy group). If the default management class does
  not contain an archive copy group, the archive retention grace period
  for the policy domain is used.

* A client node is reassigned to a different policy domain, and the
  active policy set does not contain management classes with the same
  name as that to which the node's backed up files were bound. The files
  are bound to the default management class if the management class
  contains a backup copy group or an archive copy group. If the default
  management class does not contain these copy groups, the retention
  grace period is used during expiration.

Hope this helps.

  GOD Bless
   Clarence Beukes
   IT Specialist (ADSM/TSM)
   IBM Intergrated Technology Services
   Tel : +2711 302 5333   Fax : +2711 302 8209
   Mobile : +2782 573 5665

"A computer is almost human - except that it does not blame its mistakes on
another computer. "


"Rupp Thomas (Illwerke)" <thomas.rupp AT ILLWERKE DOT AT> on 02/09/2000 
01:29:57 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Clarence Beukes/South Africa/IBM)
Subject:  Management Class DEFAULT




Hi *SM-ers,

In the ADSM log I've encountered the following messages when doing the
EXPIRE
INVENTORY. Node SMS is assigned to Domain STANDARD. The default Management
Class is named STANDARD as well.
I've checked my definitions - but there is no management class DEFAULT.
Do you think this message is something I should worry about?

ANR4391I Expiration processing node SMS, filespace \\sms\c$, domain
STANDARD,
         and management class DEFAULT - for BACKUP type files.

ANR4391I Expiration processing node SMS, filespace \\sms\c$, domain
STANDARD,
         and management class STANDARD - for BACKUP type files.

The include/exclude definitions in DSM.OPT look like:

Exclude "*:\macintosh volume\*"
Exclude "*:\macintosh volume\*.*"
Exclude "*:\macintosh volume\...\*"
Exclude "*:\macintosh volume\...\*.*"
Exclude "*:\microsoft uam volume\*"
Exclude "*:\microsoft uam volume\*.*"
Exclude "*:\microsoft uam volume\...\*"
Exclude "*:\microsoft uam volume\...\*.*"
Exclude "*:\...\EA DATA. SF"
Exclude *:\...\pagefile.sys
Exclude *:\...\*.dmp
Exclude *:\...\*.tmp
Exclude *:\IBMBIO.COM
Exclude *:\IBMDOS.COM
Exclude *:\MSDOS.SYS
Exclude *:\IO.SYS
Exclude *:\RECYCLER\...\*.*
Exclude *:\RECYCLER\...\*
Exclude *:\...\SYSTEM32\CONFIG\*.*
Exclude *:\...\SYSTEM32\CONFIG\...\*
Exclude "*:\...\Temporary Internet Files\...\*"
Exclude "*:\...\Temporary Internet Files\...\*.*"

Kind regards
Thomas Rupp
Vorarlberger Illwerke AG
MAIL:   thomas.rupp AT illwerke DOT at
TEL:    ++43/5574/4991-251
FAX:    ++43/5574/4991-820-8251
<Prev in Thread] Current Thread [Next in Thread>