|
Configuration of ExGdRetnSpTest
ExaGrid is Tiered Backup Storage with a front-end disk-cache Landing Zone and separate Retention Tier containing all retention data. Backups are written directly to the “network-facing” ExaGrid disk-cache Landing Zone for fast backup performance. The most recent backups are kept in their full undeduplicated form for fast restores.
Once the data is committed to the Landing Zone, it is tiered into a “non-network-facing” long-term retention repository where the data is adaptively deduplicated and stored as deduplicated data objects to reduce the storage costs of long-term retention data. As data is tiered to the Retention Tier, it is deduplicated and stored in a series of objects and metadata. As with other object storage systems, the ExaGrid system objects and metadata are never changed or modified which makes them immutable, allowing only for the creation of new objects or deletion of old objects when retention is reached. The backups in the retention tier can be any number of days, weeks, months, or years that is required.
If the space in the retention repository is insufficient to hold the deduplicated data, then, critical data may be lost and the whole concept of backups and restores may fail in the target enviorrnment. In order to maintain a repository for the backups that are deduplicated in the retention repository, it is essential for the administrators to periodically monitor the space usage of the retention repository. The ExGdRetnSpTest test helps administrators in this regard!
This test reports the space utilization of the retention repository in the target ExaGrid Backup server. Using this test, administrators can figure out abnormal space usage patterns and proactively add additional space to the retention repository before data loss occurs.
The default parameters associated with this test are as follows:
By default, the eG agent supports SNMPVERSION 1. Accordingly, the default selection in the SNMPVERSION list box is v1. However, if a different SNMP framework is in use in your environment, say SNMP v2 or v3, then select the corresponding option from the SNMPVERSION list box.
The SNMP community name is that the test uses to communicate with the firewall. This parameter SNMPCOMMUNITY is specific to SNMP v1 and v2 only. Therefore, if the SNMPVERSION chosen is v3, then this parameter SNMPCOMMUNITY will not appear.
This parameter USERNAME will appear only when v3 is selected as the SNMPVERSION. SNMP version 3 (SNMPv3) is an extensible SNMP Framework which supplements the SNMPv2 Framework, by additionally supporting message security, access control, and remote SNMP configuration capabilities. To extract performance statistics from the MIB using the highly secure SNMP v3 protocol, the eG agent has to be configured with the required access privileges-in other words, the eG agent should connect to the MIB using the credentials of a user with access permissions to be MIB. Therefore, specify the name of such a user against this parameter.
This parameter CONTEXT will appear only when v3 is selected as the SNMPVERSION. An SNMP context is a collection of management information accessible by an SNMP entity. An item of management information may exist in more than one context and an SNMP entity potentially has access to many contexts. A context is identified by the SNMPEngineID value of the entity hosting the management information (also called a contextEngineID) and a context name that identifies the specific context (also called a contextName). If the Username provided is associated with a context name, then the eG agent will be able to poll the MIB and collect metrics only if it is configured with the context name as well. In such cases therefore, specify the context name of the Username in the Context text box. By default, this parameter is set to none.
This parameter AUTHTYPE too appears only if v3 is selected as the SNMPVERSION. From the AUTHTYPE list box, choose the authentication algorithm using which SNMP v3 converts the specified USERNAME and PASSWORD into a 32-bit format to ensure security of SNMP transactions. You can choose between the following options:
The ENCRYPTFLAG appears only when v3 is selected as the SNMPVERSION. By default, the eG agent does not encrypt SNMP requests. Accordingly, this flag is set to No by default. To ensure that SNMP requests sent by the eG agent are encrypted, select the Yes option.
By default, in an IT environment, all data transmission occurs over UDP. Some environments however, may be specifically configured to offload a fraction of the data traffic-for instance, certain types of data traffic or traffic pertaining to specific components-to other protocols like TCP, so as to prevent UDP overloads. In such environments, you can instruct the eG agent to conduct the SNMP data traffic related to the monitored target over TCP (and not UDP). For this, set the DATA OVER TCP flag to Yes. By default, this flag is set to No.
This parameter ENGINEID appears only when v3 is selected as the SNMPVersion. Sometimes, the test may not report metrics when AES192 or AES256 is chosen as the Encryption type. To ensure that the test report metrics consistently, administrators need to set this flag to Yes. By default, this parameter is set to No.
When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.
|