ADSM Policy Requirements and Recommendations
Although the Exchange Agent operates in ways similar to other ADSM clients,
it is
unlike regular ADSM clients in that it does not always store complete
replacements for
objects on the ADSM server. An  incremental backup for the regular ADSM
client for
Windows NT sends a complete replacement for each changed file to the ADSM
server,
the  incremental and  differential backup functions of the Exchange Agent
send only the
transaction logs for the changed portion of a database object. Because of
this differ-ence, 
the Exchange Agent requires special ADSM policy settings. These are listed
below:
? The Exchange Agent stores all objects as backup objects on ADSM so an
Archive
Copy Group is not required, although it can exist.
? All objects inserted into the ADSM backup storage pool by the Exchange
Agent are
given a unique name so they are never expired by the ADSM server. The
Exchange Agent provides a delete function to remove unwanted backup objects
from the ADSM server. However, for the function to work, the VERDELETED
parameter of the Backup Copy Group should be set to 0 (zero). Then, when the
Exchange Agent marks a backup object inactive, that object is deleted from
the
ADSM server the next time expiration processing occurs. A backup object is
marked inactive when you delete it through the Exchange Agent interface.
? If the DESTINATION parameter of the Backup Copy Group points to a storage
pool
consisting of sequential access media (for example, a tape pool), or if it
points to a
disk pool which migrates to a sequential media pool, then it is best to have
collocation enabled.
? Default values should be accepted for the following Backup Copy Group
parame-ters 
because they are not applicable to the Exchange Agent:
  - FREQUENCY
  - VEREXISTS
  - RETEXTRA
  - RETONLY
  - MODE
  - SERIALIZATION
? Because the policy requirements for the Exchange Agent are probably
different
from the desired settings for the regular ADSM backup clients, you must have
a
different management class defined for the Exchange Agent. It is recommended
that you define a separate policy domain where the default management class
has
the required settings and then just register all Exchange Agent nodes to
that
domain. If you choose to define a new management class within an existing
policy
domain (which is not the default management class for that domain), then you
must add an include statement to the Exchange Agent options file to bind all
objects to that management class. For example:
  include \  mcname
See your ADSM administrator or see  ADSM for Windows NT Administrator's
Guide for
more information on defining or updating ADSM policy domains and copy
groups.

Best Regards

Hubner Vit 

Ceska Sporitelna a.s.

Prag,CZ