7.2 Configuring Policy Domain for client data protection (Part 1)

7.2 Configuring Policy Domain for client data protection (Part 1)

08:35 No Comments

Defining Policy Domain for client backup and archives

Before you start taking backup of any clients, client should be registered to  default Policy Domain  (STANDARD) settings or you can define your own policy domain settings according to your business requirements. You first have to define a policy domain, policy set, management class and then backup/archive copy group. In this post we will see the purpose of these parameters and how to define them. You have to configure according to the policy domain hierarchy as shown in the below image.
policy domain structure
Image Source: IBM
Policy Domain
A policy domain provides a logical way of managing backup and archive policies for a group of nodes with common needs. It is a collection of one or more nodes and one or more policies. Each domain is an object that the Tivoli Storage Manager database stores, with a name that contains from 1 to 30 characters. The number of policy domains that you can define on a Tivoli Storage Manager server is limitless. 

A client node is associated with only one policy domain on a specific Tivoli Storage Manager server. However, a client or node might be registered (defined) to more than one server. Each domain can have one or more clients or nodes associated with it. The clients or nodes can run on the same or different platforms. Some installations can require only a single policy domain.

 Also Read: Installation & Configuration of IBM Spectrum Protect (TSM) Server

A policy domain also contains a grace period backup and an archive retention period. This grace period acts as a safety net to ensure that data that is backed up or archived in a storage pool is not inadvertently deleted. Use the following define domain command to
define a policy domain for clients
  define domain LINUX description=“Policy domain or LINUXclients”

Each policy domain contains a backup grace retention period and an archive grace retention period. The grace retention period protects backup versions and archive copies from immediate deletion when the default management class has no backup or archive copy group. The client node uses the grace retention period only if there is no other defined retention period. The policy domain grace retention period is specified in the define domain command.
  • Backup retention grace period defaults to 30 (BACKRETention=30).
  • Archive retention grace period defaults to 365 (ARCHRETention=365).
Use the policy domain grace retention period when default MGMTCLASS has no copy group for backup and archive. One of the following situations must also apply:
  • MGMTCLASS for backup no longer contains backup copy group.
  • MGMTCLASS for an archive no longer contains archive copy group.
  • MGMTCLASS no longer exists.
Policy Set
A policy set is a group of rules in a policy domain. These rules specify how data is automatically managed for client nodes in the policy domain. The ACTIVE policy set is the set that contains the policy rules currently in use by all client nodes assigned to the policy domain.
define policyset domainname policyname

Management classes
A management class associates backup and archive groups with files and specifies if and how client node files are migrated to storage pools. Users can bind, which means associate, their files with a management class by using the include-exclude list. 
 define mgmtclass LINUX lab LINUXMC
  • A management class (MC) represents a business requirements policy or service level agreement.
  • A management class is associated with a backup copy group and archive copy group.
  • The default management class does not require a backup copy group or an archive copy group, but such a group might be useful.
  • Clients can explicitly select a management class.
  • The server database stores management class information.
  • A management class can contain a backup copy group, an archive copy group, both copy groups, or no copy groups.
The management class that is specified in the policy domain defines the backup and archive criteria for client nodes in the policy domain. If you do not specify the Management Class, the default Management Class is used.

 Also Read: Understanding Management Class Binding and Management Class Rebinding

Client users have the option of creating an include-exclude list to identify the files that are eligible for backup services and specifying how Tivoli Storage Manager manages backed up or archived files. The INCLUDE and EXCLUDE options are specified in the client option file.

Copy Groups
A copy group contains the specific storage management attributes that describe how the server manages backed up or archived files. Copy groups contain the parameters that control the generation and expiration of backup and archive data. There are two types of copy groups Backup and Archive Each management class contains up to two copy groups. If it has two copy groups, one is for backups, and one is for archives. All copy groups are named STANDARD. The attributes in any copy group define the following information
  • The storage pool destination where the backed up or archived data is stored
  • The minimal interval, in days, between backup and archive operations
  • Whether the file is backed up regardless of whether it has been modified since the last backup
  • Whether the file can be in use when a user attempts to back up or archive the file
  • The maximum number of different backup versions that are retained for files that are no longer on the file system of the client
  • The retention period, in days, for all but the most recent backup version, and for the last remaining backup version that is no longer on the file system of the client
  • The number of days that an archive copy is retained
Also Read: Full vs Differential vs Incremental vs Progressive Incremental Backups 

 The set of backup parameters defines the following attributes:
  • Frequency
  • Mode (modified or absolute)
  • Destination
  • Copy serialization
  • Number of versions
  • Number of versions when the file is deleted
  • Retention days for all but the last version
  • Retention days for the last version when the file is deleted
The set of archive parameters defines the following attributes:
  • Frequency (always CMD)
  • Mode (always ABSOLUTE)
  • Destination
  • Copy serialization
  • Retention days for archive copies

0 Comment to "7.2 Configuring Policy Domain for client data protection (Part 1)"

Post a Comment

Subscribe to: Post Comments (Atom)