To view additional detailed cleaner statistics, you can use the QoreStor CLI stats --cleaner command to show the following categories of statistics:
- Last Run Files Processed (number of files processed by Cleaner)
- Last Run Bytes Processed (number of bytes processed by Cleaner)
- Last Run Bytes Reclaimed (number of bytes reclaimed by the Cleaner)
- Last Run Start Time (indicates date and time last Cleaner process started)
- Last Run End Time (indicates date and time last Cleaner process ended)
- Last Run Time To Completion(s) (indicates the number of times that Cleaner process has successfully completed)
- Current Run Start Time (indicates date and time current Cleaner process started)
- Current Run Files Processed (number of files processed by current Cleaner process)
- Current Run Bytes Processed (number of bytes processed by current Cleaner process)
- Current Run Bytes Reclaimed (number of bytes reclaimed by the current Cleaner processed)
- Current Run Phase 1 Start Time (indicates date and time for start of current Cleaner process phase 1)
- Current Run Phase 1 Records Processed (lists the number of data records processed in current Cleaner process phase 1)
- Current Run Phase 1 End Time (indicates date and time for end of current Cleaner process phase 1)
- Current Run Phase 2 Start Time (indicates date and time for start of current Cleaner process phase 2)
- Current Run Phase 2 Records Processed (lists the number of data records processed in current Cleaner process phase 2)
- Current Run Phase 2 End Time (indicates date and time for end of current Cleaner process phase 2)
- Current Run Phase 3 Start Time (indicates date and time for start of current Cleaner process phase 3)
- Current Run Phase 3 Records Processed (lists the number of data records processed in current Cleaner process phase 3)
- Current Run Phase 3 End Time (indicates date and time for end of current Cleaner process phase 3)
- Current Run Phase 4 Start Time (indicates date and time for start of current Cleaner process phase 4)
- Current Run Phase 4 Records Processed (lists the number of data records processed in current Cleaner process phase 4)
- Current Run Phase 4 End Time (indicates date and time for end of current Cleaner process phase 4)
For more information about QoreStor CLI commands, see the QoreStor Command Line Reference Guide.
The sections below contain information necessary for the proper configuration of Secure Connect. The procedures for configuring Secure Connect differ depending on your plug-in version.
- For OST and RDA plug-in version 4.1.0.265 or later
- For OST and RDA plug-in versions prior to 4.1.0.265
- For Rapid NFS plug-in version 4.0.3310.0 or later
- For Rapid CIFS plug-in version 4.0.3233.1 or later
- Adding certificates for Secure Connect
Secure Connect is enabled through the use of environmental variables on the client machine. No configuration is required on the QoreStor server.
To enable Secure Connect on a Windows client
- On the client server, press Win+R to open the Run window.
- Type sysdm.cpl and click OK.
- Click the Advanced tab, then Environment Variables.
- In the System Variables section, click New.
- In the Variable name field, enter SECURE_CONNECT.
- In the Variable value field, enter one of the following:
- 0 - disables Secure Connect
- 1 - Secure Connect is enabled, but QoreStor will failback to an unsecured connection if the Secure Connect server is unavailable.
- 2 - Secure Connect is enabled. Connection will fail if Secure Connect server is unavailable.
- Click OK, then OK.
|
|
IMPORTANT: After enabling Secure Connect, you will need to change the BypassPorts configuration in the sc_client.properties file. Refer to Configuring Secure Connect properties for information. |
|
|
IMPORTANT: After enabling Secure Connect, you must restart the DMA application services. |
To enable Secure Connect on a Linux client
- At the command prompt on the client machine, enter the following command
echo 'export SECURE_CONNECT=<0|1|2>' >> ~/.bashrc
Where:
- 0 - disables Secure Connect
- 1 - Secure Connect is enabled, but QoreStor will failback to an unsecured connection if the Secure Connect server is unavailable.
- 2 - Secure Connect is enabled. Connection will fail if Secure Connect server is unavailable.
- Log out of the QoreStor system, then log in.
|
|
IMPORTANT: After enabling Secure Connect, you will need change the BypassPorts configuration in the sc_client.properties file. Refer to Configuring Secure Connect properties for information. |
|
|
IMPORTANT: After enabling Secure Connect, you must restart the DMA application services. |
Before using Secure Connect, ensure that the default port configuration is appropriate for your environment. The ports used by Secure Connect are:
- 9443 - this is the listening port. The Secure Connect server listens for connection requests on this port.
- 10011, 11000 and 9920 - These are the standard Secure Connect communication ports.
By default, the Secure Connect ports are bypassed, which will cause Secure Connect to failback to a normal, unsecured connection. Before using Secure Connect, the BypassPorts setting must be set to 0 to enable full communication.
Secure Connect properties can be configured through the sc_client.properties file located in the client installation directory.
To configure Secure Connect
- In the client installation directory, open the sc_client.properties file with a text editor.
The default installation directory differs depending on the client type and the OS of the client machine. For example,
- The RDA client on a Windows machine installs to C:\Program Files\Quest\RDA\dynlib
- The NetVault on a Linux server installs to /usr/netvault/dynlib/sc_client.properties
- Find the entry shown below
- Do one of the following:
- Comment out the line BypassPorts = 9920, 10011, 11000 by adding a # to the front, then remove the # from BypassPorts = 0
- Delete the listed ports (9920, 10011, 11000) and replace with 0.
- Save the file.
