Backup and Restores Test

This indicates how often should the test be executed.

The host for which the test is to be configured.

The port at which the host server listens.

Typically, farm-level metrics - eg., metrics on farm status, site collections, usage analytics - will not vary from one SharePoint server in the farm to another. If these metrics are collected and stored in the eG database for each monitored server in the SharePoint farm, it is bound to unnecessarily consume space in the database and increase processing overheads. To avoid this, farm-level metrics collection is by default switched off for the member servers in the SharePoint farm, and enabled only if the server being monitored is provisioned as the Central Administration site. Accordingly, this parameter is set to If Central Administration by default. This default setting ensures that farm-level metrics are collected from and stored in the database for only a single SharePoint server in the farm.  

If you want to completely switch-off farm-level metrics collection for a SharePoint farm, then set this parameter to No.

Some high-security environments may not allow an eG agent to be deployed on the Central Administration site. Administrators of such environments may however require farm-level insights into status and performance. To provide these insights for such environments, you can optionally enable farm-level metrics collection from any monitored member server in the farm, even if that server is not provisioned as the Central Administration site. For this, set this parameter to Yes when configuring this test for that member server. 

If the Fetch Farm Measures flag of these tests is set to No or to If Central Administration Site, then this test should be configured with the credentials of a user with the following privileges:

• The user should be part of the SharePoint Farm Administrators group. To know how to add a user to this group, refer to Adding a User to a Farm Administrators Group.
• The user should have shell admin access to all databases in SharePoint. To know how to grant such an access to a user, refer to Granting a User Shell Admin Access to All SharePoint Databases.

• The user should have full control access to each web application that needs to be monitored on the SharePoint server. To know how to grant such an access to a user, refer to Granting a User Full Control Access to Web Applications on Microsoft SharePoint.
• The user should have read and execute access to the eG agent install directory. To know how to grant this access to a user, refer to Granting a User Read and Execute Permissions to the eG Agent Install Directory.

On the other hand, if the Fetch Farm Measures flag of these tests is set to Yes, then the user configured for the tests not only requires the four privileges discussed above, but should also be part of the following groups on the eG agent host:

• Administrators

• WSS_ADMIN_WPG

• IIS_USRS

• Performance Monitor Users

• WSS_WPG

• Users

It is recommended that you create a special user for this purpose and assign the aforesaid privileges to him/her. Once such a user is created, specify the domain to which that user belongs in the Domain text box, and then, enter the credentials of the user in the Domain User and Password text boxes. To confirm the password, retype it in the Confirm Password text box.

Provide the full path to the backup and/or restore directory to be monitored. Multiple paths can be provided as a comma-separated list. For example – C:\BackupSite,C:\RestoreSite,D:\BackupDir. Your specification can include both local and remote directories. For example - C:\BackupSite,C:\RestoreSite,\\192.168.9.70\backup\250216. However, bear the following points in mind when including remote directory paths in your specifications:

• While specifying the path of a remote directory, make sure that your specification
• begins with \\(two forward slashes) followed by the IP/hostname of the remote server in which the directory resides. This should be followed by the full path of the remote directory to be monitored. For example - \\192.168.9.70\backup\250216.
• Your Dir Path specification can include the path to multiple remote directories. Each of these directories can be in a different remote server. However, all these remote servers should operate in the same domain.
• A single user in the remote domain should have access to all the remote directories configured against Dir Path.

This parameter is applicable only if the Dir Path specification includes one/more remote directories. In this case, against Remote Server Domain, specify the domain to which the servers hosting the remote directories belong. If your Dir Path specification does not include any remote directories, set remote server domain to none.

Note:

• Only a single domain name can be specified against Remote Server Domain.
• For proper results, all the servers that host the remote directories configured against Dir Path should belong to the Remote Server Domain you specify.

These parameters are applicable only if the Dir Path specification includes one/more remote directories. In such a case, against these parameters, specify the credentials of a user who fulfills the following conditions:

• Should be a valid user in the Remote Server Domain that you have configured;
• Should be a user who has at least Read-only access to all the remote directories configured for monitoring against the Dir Path parameter.

However, if the Dir Path specification does not include any remote directories, then you can set both Remote Server User Name and Remote Server Password to none.

Confirm the Remote Server Password by retyping it here. This parameter again is applicable only if the Dir Path specification includes one/more remote directories.