ADSM-L

HOWTO: TSM Policy Information Demystified

2002-02-07 18:57:06
Subject: HOWTO: TSM Policy Information Demystified
From: Josh Davis <hedgie AT OMNITECH DOT NET>
Date: Thu, 7 Feb 2002 14:46:08 -0600
-------------------
TSM Policy Settings
TSM Policy Settings
-------------------
POLICY DOMAIN - This is a container for policy and scheduling info
POLICY DOMAIN - This is a container for policy and scheduling info
                *BACKRETention* is a fallback value for any files which
                  have been backed up under the specified policy domain,
                  but for which there is now a lack of an active policy
                  set.
                *ARCHRETention* is a fallback value for any files which
                  have been archived under the specified policy domain,
                  but for which there is now a lack of an active policy
                  set.

   POLICY SET - This is a set of management classes within a POLICY
                DOMAIN.
                Only the active version has any effect.  The active
                version is created by issuing ACTIVATE POLICYSET
                <set-name-you-made>.
                After activating, you may edit the original set without
                affecting the active copy.

      MANAGEMENT CLASS - This is a classification for particular sets
                 of objects.  Minimal set to be bound is an entire
                 archive for archiving (ARCHMC option) or a single file,
                 directory,  filespace or everything for a backup
                 (INCLUDE option).
                 There can be many management classes per policy set,
                 but only ones in the active policy set may be
                 referenced
                 **The additional parameters for this structure are used
                    only for HSM migration.

         BACKUP COPYGROUP - This is the structure which defines
                 retention of backup data.  These settings are the most
                 confusing because their operation overlaps and may
                 require some to be set to "NOLIMIT" to attain the
                 desired effect.

            *VERSIONS DATA EXISTS* - This value specifies the maximum
                 number of versions of a file which may be retained.
                 If this is exceeded by additional backups or imports,
                 then the next expiration run on the server will remove
                 the oldest versions until there are only this many
                 left.
                 **This may be "NOLIMIT" or a whole number.

            *RETAIN EXTRA VERSIONS* - This value specifies the maximum
                 number of days to retain an inactive copy when there is
                 an active copy in the database.
                 **This may be "NOLIMIT" or a whole number.

            *RETAIN ONLY VERSION* - This value specifies the maximum
                 number of days to retain the only inactive version of
                 a file once there are no active versions.
                 **This may be "NOLIMIT" or a while number.
                 **This does not affect active copies which are always
                    retained.

            *VERSIONS DATA DELETED* - This is the maximum number of
                 inactive versions of a file to retain once the file no
                 longer has an active version.

            *DESTINATION* - This specifies the storage pool to which
                 newly backed up data will go if it is bound to this
                 management class during backup.
                 **Rebound data will not move to a new pool
                   automatically.
                 **Data may be moved from this pool through migration or
                    MOVE DATA commands.

         Archive Copygroup - This is the structure which defines
                 retention of archive data.

            *RETAIN VERSION* - This is the only retention parameter
                 for archives, and is the number of days that the entire
                 archive will be kept.

            *DESTINATION* - This specifies the storage pool to which
                 newly archived data will go if it is bound to this
                 management class during archive operation.
                 **Rebound data will not move to a new pool
                   automatically.
                 **Data may be moved from this pool through migration or
                    MOVE DATA commands.

   Schedule - This is a time/date/frequency setting for when commands
              may be automatically run by the tsm server either on the
              tsm server (administrative) or on the tsm client (client).

Client Association - a separate entity that binds clients to schedules.

Node - A separate entity which defines a client and allows access.




-------
CAVEATS
CAVEATS
<Prev in Thread] Current Thread [Next in Thread>
  • HOWTO: TSM Policy Information Demystified, Josh Davis <=