The new version of OMNISPEED is available. Version 2.0 was especially developed for Data Protector 8.XX environments and supports HP-UX (Itanium) 11.31, Linux (RedHat and SUSE Linux Enterprise Server) and Microsoft Windows (2008 R2, 2012 and 2012 R2) for the Data Protector versions 8.00, 8.01 and 8.1X. The most important change is a direct connection to the internal database, therefore the tool must run on the cell server directly. Other changes include the increased runtime of 48 hours, to run the script for X times and the calculation for B2D devices (StoreOnce Gateways – Software/Hardware). The tool supports the international versions of Data Protector; this includes English, French, Japanese and tradtional Chinese, no matter which reginal settings are used. However, the output is in English. Because of the direct connection to the internal database, the runtime is faster. This allows an decreased value for the measurements; it is set to three, instead of five seconds.
For more information, please refer to the help. I look forward to further suggestions and hope you will enjoy the tool.
[wpdm_file id=22]
******************************************************************************* * * * OMNISPEED v 2.00 - Average Speed of DP Sessions * * * * CoPyRiGhT (c) 2014 Data-Protector.org - Daniel Braun * * * ******************************************************************************* Starting script on: rx2600 - 27.03.2014, 17:17:18 Usage: omnispeed.exe [options] OPTIONS: --separated output will be separated by ';' --continous, -c script runs in loop mode until CTRL-C is pressed. When no session is running, the script stops automatically. The script will wait for three seconds between each loop and stops after 57600 loops = 48 h. --sessionid, -s get speed from completed session or more details from current session. --number, -n number of cycles before exit. The script will wait for three seconds between each loop and stops after 57600 loops = 48 h. Script can be stopped using CTRL-C. --debug, -d debug mode, output is written to omnispeeddebug.log. --exitcodes, -e prints out the exit codes used in script. --version, -v displays the script version. --help, -h prints this help. Omnispeed must run on cell server, remote execution not allowed. Cause: Some commands are available on cell server only. In addition the SQL commands must be executed locally. Hint: On Windows cell server psexec can be used for remote execution. Example psexec: psexec.exe \\servername -u domain\user -h cmd.exe After the password has been entered, omnispeed can be started. Mail bug reports and suggestions to daniel-braun(at)data-protector.org.
Hello,
On one of our Cell managers omnispeed shows old sessions as running with no throughput for quite long however omnistat shows the sessions as not running. Are these sessions somehow stuck in the IDB, or might this be an issue with omnistat and if they are indeed stuck then how to purge them?
Regards,
Matyas
Hi,
Yes the session stuck, run omnidbutil -clear when no other session is running.
Best regards
Daniel