Answer» - Storage Policy: The storage policy determines where the data is saved and how long the snapshot will be kept. Copies can be found within a Storage Policy. In the IRM environment, these copies define retention for the designated storage devices. Within IRM, there are just two versions of interest. The Primary Snapshot Copy and the Primary Copy are two different copies of the same thing. The Primary Snapshot Copy merely specifies how long the SNAPSHOTS will be kept and which MediaAgent will be cataloguing them. The Primary Copy specifies the location of the catalogued indexes.
- Job Manager: Displays all information about a running job, including data protection, recovery, and Auxiliary copy, as well as settings and media usage. Snapshot jobs can be LAUNCHED, suspended, restarted, and cancelled by the Job Manager.
- Backup Set: A backup set is a sub-container present within each of these agents. The backup set is the client's overall container. The most straightforward approach to comprehending a backup set is to relate it to the context of the system being snapped in the environment. The backup set for the file system iDataAgent is the fundamental physical system storage environment, whereas the backup set for these two database agents is the Exchange Information Store or SQL instance. An overall vCenter is the backup set in a Virtual Context since it encompasses numerous ESX servers that house and manage virtual machines.
- Subclient: The SMALLEST subset of a client is called a subclient. From the perspective of a Windows host, it may be a single folder, a single database, a single Virtual machine, or a single LUN or drive letter (regardless of how many LUNs are meta-LUN'ed to produce one huge LUN pool). Sub clients are backup set definitions that are related to Storage Policies, which define the snapshot data's retention and location.
- Collect Files: During an IntelliSnap job, Collect Files are smaller text files that will gather information on what is on each of the clone/snapshots. The original information lying on the snapshots is indexed by the collect files saved under the TASK result directory under each of the IRM clients when the snapshot is mounted to be catalogued. Once the cataloguing is complete, the information will be given immediately to the MediaAgent who will store it in indexes for a longer period of time. These indexes will remain on the MediaAgent for the duration of the snapshot's retention period, either in the local MediaAgent index cache or in the disc library set up to protect the indexes and the CommCell database backup.
|
