Difference between revisions of "RHEL 8.x Spectrum Protect Theory"
From Notes_Wiki
m |
m (Saurabh moved page Spectrum Protect Theory to RHEL 8.x Spectrum Protect Theory) |
(No difference)
|
Revision as of 06:54, 2 May 2023
Home > RHEL > RHEL 8.x > Backup tools > Spectrum Protect Backup > Spectrum Protect Theory
- Device class
- The type of storage device that can use the volumes that are defined in a sequential-access or random-access storage pool. Each device class of removable media type is associated with a single library.
- DISK device class
- In a DISK device type of storage pool, data is stored in random access disk blocks. You can use caching in DISK storage pools to increase client restore performance with some limitations on server processing. Space allocation and tracking by blocks uses more database storage space and requires more processing power than allocation and tracking by volume.
- FILE device class
- In a FILE device type of storage pool, files are stored in sequential volumes for better sequential performance than for storage in disk blocks. To the server, these files have the characteristics of a tape volume so that this type of storage pool is better suited for migration to tape. FILE volumes are useful for electronic vaulting, where data is transferred electronically to a remote site rather than by physical shipment of tape. In general, this type of storage pool is preferred over DISK storage pools.
- Storage pool
- A set of storage volumes or containers that is the destination that is used to store client data. IBM Spectrum Protect uses the following types of storage pool:
- Directory-container storage pools
- Cloud-container storage pools
- Sequential-access storage pools that are associated with a device class
- Random-access storage pools that are associated with a device class
- Policy domain
- The policy domain is the primary organizational method of grouping client nodes that share common rules for data management. Although a client node can be defined to more than one server, the client node can be defined to only one policy domain on each server.
- Policy set
- A policy set is a number of policies that are grouped so that the policy for the client nodes in the domain can be activated or deactivated as required. An administrator uses a policy set to implement different management classes based on business and user needs. A policy domain can contain multiple policy sets, but only one policy set can be active in the domain. Each policy set contains a default management class and any number of extra management classes.
- Management class
- A management class is a policy object that you can bind to each category of data to specify how the server manages the data. There can be one or more management classes. One management class is assigned to be the default management class that is used by clients unless they specifically override the default to use a specific management class.
- The management class can contain a backup copy group, an archive copy group, and space management attributes. A copy group determines how the server manages backup versions or archived copies of the file. The space management attributes determine whether the file is eligible for migration by the space manager client to server storage, and under what conditions the file is migrated.
- Copy group
- A copy group is a set of attributes in a management class that controls the following factors:
- Where the server stores versions of backed up files or archive copies
- How long the server keeps versions of backed up files or archive copies
- How many versions of backup copies are retained
- What method to use to generate versions of backed up files or archive copies
Ref:
https://www.ibm.com/docs/en/SSEQVQ_8.1.5/srv.solutions/b_srv_concepts_guide.pdf
Home > RHEL > RHEL 8.x > Backup tools > Spectrum Protect Backup > Spectrum Protect Theory