- 2MarkdownD for Linux4
- 3DataStorm for Linux4
- 4InvoicePad 3 for Linux 32 bit11
- 8Recovery Explorer RAID - Linux18
- 9Recovery Explorer Professional - Linux36
- 10Recovery Explorer Standard - Linux19
- 11ONLYOOFFICE Desktop Editor Linux647
- 12CameraSentry for Linux18
- 13DWG to PDF Converter MX387
- 14RationalPlan Project Viewer for Linux177
- 15UFS Explorer RAID Recovery (Linux)89
Automated Crash Prevention, Recovery, Reporting & Diagnostics. Now you can relax knowing that all of your NetWare servers are protected by the Alexander Server Protection Kit (SPK). When misbehaved software threatens to bring a server down, SPK will automatically step in and prevent it! In cases were a crash cannot be prevented, it will protect your data by dismounting the volumes. In most cases your users will not know that anything occurred at all. They will continue to work while in the background the SPK buffers them from costly interruptions.In either case, the SPK will pinpoint the cause, provide comprehensive diagnostics, and report to both alert and management products. In short, the Alexander SPK will manage all aspects of a crash without human intervention, thus protecting your office productivity.
When NetWare declares an abend call, it does so because it has encountered a condition which, if not interrupted, could cause serious damage. When the SPK is on the server, the Edna module intercepts this call and works immediately to protect the server from having to actually go down. This can be done in two ways:
Edna knows of certain conditions where NetWare will think that it must abend but that conclusion is erroneous so the call to abend is countermanded.
There are many conditions whereby a misbehaving module can be suspended thus preventing the abend from being necessary.
When NetWare attempts to prevent an abend from bringing the system down it suspends a thread. The module that owns that thread is still in memory but cannot be depended upon because one of its hands is tied via suspension. It cannot be unloaded. The only way to recover its use is to down and restart the server which interrupts office productivity.
With Edna running the entire module is suspended instead of just the thread. Then she provides a special prompt that allows you to actually unload the module and reload it in seconds without interrupting anyone or anything and with out downing and restarting the server (often the problematic module has been corrupted in memory so the ability to unload and reload it fully refreshes the code in memory). This unload process is so thorough that Edna ascertains what system resources can be released and which cannot. For instance the module might share some resources with another module, these will not be freed so that the other module does not become hobbled. This is a powerful feature not found any other environment.
When a hard crash cannot be prevented, Edna protects the server by working to turn the crash into as orderly a shutdown as possible, thus reducing the likelihood of damage. This in turn increases the likelihood that the server will be able to fully recover without human intervention.
Whenever the system is restarted and Edna then loads, she cleans out all crash related files in the DOS partition regardless of who created them and places them safely in individual sub-directories under sys:edna. This is important because it means that the DOS partition will always be clear to allow for the occasional need to save a core dump image.
When the system is then up again Edna generates SNMP traps for each event telling what happened, when, on what system, and where to locate the crash report.
With NetWare alone, a core dump can only be created by a person being there at the box. In contrast, Edna allows you to set a switch which instantly dynamically configures her to make a core dump for you anytime the system abends.
NetWare creates an abend.log file by default for each crash event. These logs may contain many events but each one represents about 25k data. In contrast, the Edna Crash File (ECF) for a typical NW6 server averages about 20 MB per event. That is a tremendous difference in providing needed data. Reading an abend.log file is awkward and often lacks sufficient information to resolve the cause of the crash. In contrast, an ECF file typically takes under 60 seconds.
Customers as well as other software vendors supporting Novell have long reported that they can resolve the cause of most crashes in under 10 minutes with no outside help. A simple, free Windows viewer organizes information, enables sorting, and even for data to be copied and printed so that it can be added into internal or external reports.
Edna displays all screens from all modules running showing their state the microsecond the crash occurred. This would only be available by looking at a core dump with a debugger. Edna enables you to sort instantly through all loaded modules and locate, for instance, oldest, etc.
SendMerc is a small utility who allows you to send emails via the mercury mail system on netware servers.
DateOct 25, 2010
ActivIdentity SecureConsole™ is a powerful Novell® Netware® console security application that adds the highest level of control and accountability to NetWare servers.
DateOct 31, 2010
AdRem sfConsole is the Web-enabled, easy to install solution that allows users to effectively protect access to key NetWare servers, foiling inside and outside intrusions from a Windows workstation.
DateOct 31, 2010
NetServerMon is an extremely versatile and easy to use utility designed specifically for your Netware Servers. It allows you to view NDS partitions on one or more servers.
DateNov 2, 2010
Novell NetWare Revisor is a multifunctional tool for maintaining, copying and recovering NetWare servers running Novell NetWare 3.x, 4.x, 5.x, 6.x. The program runs on the administrator's workstation and can create images of NetWare servers.
DateNov 3, 2010