You have questions about EDT and we have answers. Here are some of the most frequently asked questions we receive. If you have a question that is not answered here, please refer to our other online support resources or contact us for assistance.
- What is EDT?
- Enterprise DistribuTape, or EDT, handles the interaction between a TSM data manager and a media manager (e.g., ACSLS). The data manager backs up and restores the data for all the computers on a network via a set of software applications or databases. The media manager controls the robotic tape library. It handles the mounting and dismounting of tape volumes, entering and ejecting tape volumes from the library and keeping track of the volume media type and location within the library.
- EDT is an interface program that communicates with the data manager (TSM) and the various media managers (such as ACSLS, ADIC, and 3494). EDT efficiently uses the resources available and optimizes backup and restoration of data.
- How do I know if EDT will work with our environment?
- Check our support matrix link for a list of environments that work with EDT: http://webserver.greshamstorage.com/support_matrix.htm
- Does EDT support 64-bit TSM?
- Yes. EDT versions 7.4.3 and above support 64-bit TSM. Check our support matrix link for a list of 64-bit environments that work with EDT: http://webserver.greshamstorage.com/support_matrix.htm
- If a tape has been written in an EDT environment, can I read that tape on a non-EDT system?
- Yes. EDT sits between TSM and ACSLS and increases the flexibility and efficiency of your storage operation, but the end result is data written to a tape by ACSLS, as instructed by TSM. That tape is identical to the tape that would have been produced had EDT not been included in the configuration. All the tape metadata is held by ACSLS and TSM, so there should be no problem retrieving the data on a machine without EDT installed.
- Who do I contact if I would like to try EDT?
- Please contact one of our sales representatives for a temporary key. Also, visit our website for more information about EDT: http://www.gresham-storage.com/forms/contactsales.aspx
- How do I get technical support?
- You can contact us 24 hours a day, 7 days a week:
| e-mail: |
storagesupport@gresham-computing.com |
| USA (Toll Free): |
Telephone: 1 (888) 819-7618 |
| Americas: |
Telephone: 1 (512) 407-2680 |
| Europe, Middle East, and Africa: |
Telephone: +44 (0) 1489 555400 |
- From 04:00 to 16:00 GMT, support calls are answered in the United Kingdom. (This is 11:00 PM to 11:00 AM Eastern Time in the United States.) From 16:00 to 04:00 GMT, support calls are answered in the United States. (This is 11:00 AM to 11:00 PM Eastern Time in the United States.)
- Can I run EDT-CC through a firewall?
- Yes. CC should be accessible through a firewall if the setup is performed properly. Currently the port is set to 22402 and cannot be changed. The firewall could have a rule that listens on that port and forwards it to the that port on the server machine. However, because of the way Java's RMI works, the remote machine must to be able to resolve the NodeServer's hostname.
- How do I run EDT with LANfree TSM clients through a firewall?
- Assuming that the other TSM LANfree clients that are working also have a firewall between themselves and ACSLS:
- Change the ACSLS line in the elm.conf file so that the host matches what is specified in rc.edt as MEDIA_MNGR_HOST.
- Set the SSI_HOSTNAME in the rc.edt file. This should be set to the IP address of the EDT server. This address tells ACSLS to send its responses to that IP address, regardless of where they appear to have originated.
- After changing the parameters in step 2, restart EDT.
- Check the firewall logs to see if there are packets being blocked either way. Without having ping enabled, it's very difficult to check that the network routing is correct.
- How do I generate keys and download code?
- Gresham provides an online license server to allow you to generate your own keys at any time. Go to: http://license.greshamstorage.com/license/index.jsp
- If you do not already have a login and password for this server, go to this site and click on [Customer Registration] to obtain a login for your account.
- How do I find information about installing and upgrading EDT and other technical information about EDT?
- Please refer to our technical manuals by going to: http://webserver.greshamstorage.com/document_index.htm
- How do I upgrade EDT 6 to EDT 7?
- Upgrade instructions are included on the EDT 6 End-of-Service announcement.
- Upgrading EDT.doc 32KB 3/29/2007
- How do I stop EDT?
- On Unix systems, you can use the rc.edt utility to stop EDT:
- rc.edt kill_api
- Using the "kill" command to shut down the SSI and mini_el daemons is also an acceptable way of stopping EDT.
- ps -e | grep ssi (to find the process_id)
kill -TERM 22168
If that fails, then try "-9" instead:
kill -9 22168
- On Windows systems, you can use the EDT Configuration Utility to stop the GES EDT Service.
- What would be the first thing to check if I am having communication problems between the admin client and the node server?
-
- Make sure you are using the same EDT-CC version for both the admin client and the node server.
- Make sure the same Java version is running on both the admin client and the node server.
- Why would I get an "Invalid Key" error message on install?
- Check the EDT configuration file, named elm.conf. The file contains a keyword called LICENSE. This line needs to be in all uppercase with only 1 space between keywords.
-
--elm.conf file snippet------------------------------
LIBRARY SL8500
LIBTYPE ACSLS
CLIENTID csldcbarp001_sa
License TEMP 12345678900 -> here is the problem!!!
Or
LICENCE PERM 1234567890
--elm.conf file snippet------------------------------
- Where are the EDT logs located?
- Read the EDT configuration file, named elm.conf. The elm.conf file is in the bin directory under the EDT base installation directory:
| Operating System |
elm.conf Location |
| AIX |
/usr/lpp/GESedt-acsls/bin |
| Solaris |
/opt/GESedt-acsls/bin |
| HP-UX |
/opt/GESedt-acsls/bin |
| Linux |
/opt/GESedt-acsls/bin |
| Windows |
[C-Z]:\Program Files\GES\EDT-ACSLS\bin |
- In the elm.conf file, look for lines that start with MSG and DBG. The MSG directive specifies the full name of the messages file. The DBG directive specifies the full name of the debugging file. The debugging file is primarily for the use of the developers; it may be difficult to understand. The messages file is more user-friendly; it is probably where you want to start.
- Note: The messages file includes any error messages sent from ACSLS. Our users often assume that these errors are caused by EDT when EDT is only reporting what it got from ACSLS.
- How do I send Gresham support log files that are too large for email?
- Gresham has an anonymous FTP site for files too large to email. Our FTP site is:ftp://webserver2.greshamstorage.com
- The login is "anonymous" and the password is your email address. Place any files in the 'incoming' directory, and please send us email to let us know that they're there.
- How can I find out what drive error codes (errno's) mean?
- These are errors generated by the hardware (usually a tape drive). There is a standard list of errno codes used by all tape drives. On UNIX systems, all errno's are defined in the operating system's errno.h header file. The integer corresponding to the errno may vary by operating system, but the error codes (ENXIO, EIO, ENODEV, EBUSY, etc.) are specified by industry standards.
- For example, on AIX, an errno 46 corresponds to ENOTREADY, indicating that the device is not ready for operations. This may be because the tape is loading, rewinding, being positioned, unloading, etc. The error is repeatable, and the operation will eventually succeed if there is no problem with the tape drive or configuration. It is not uncommon to see pairs of ENOTREADY and EBUSY (errno 16 on AIX) when the ACS_ID to /dev/mt mapping in the elm.conf file is not correct.
- If you cannot view an errno.h file, you can find the errno codes by consulting appendix B in the EDT Technical Reference Guide .
- What does this message mean: "bindprocessor err could not bind process to 0. errno = Not owner"? How do I correct the problem?
- This is an AIX message that does not affect EDT performance. You may safely ignore it. It means that the bindprocessor function was invoked by a process that did not have root privileges.
- The AIX "bindprocessor" command can bind a process to a specific processor in a multi-processor system. In some cases, binding a process to a CPU can improve its performance. For example, binding can be useful for CPU intensive programs that experience few interrupts. Binding eliminates the overhead of setting up the cache when AIX scheduler moves the process between processors. It is not necessary for EDT.
- How do I use SSI API tracing?
- The SSI API has a trace facility to help diagnose communication problems. To turn the trace on and off:
- UNIX
- Set these environment variables in the system environment file:
export SSI_EE=1
export SSI_EE2=1
SSI_EE3=1
- To activate, log out and log back in. Refresh the API with:
rc.edt refresh_api.
- To deactivate, remove the exports from the system environment file. Log out and log back in. Refresh the API with:
rc.edt refresh_api.
- The trace from the application is placed in /tmp/edtapp.log. The trace from SSI is placed in /tmp/edtssi.log.
- Windows
- Create variables SSI_EE2 and SSI_EE3 as system environmental variables.
- Reboot the system to activate tracing on SSI.
- To deactivate tracing, delete the system variables and reboot.
- The trace from the application on Windows is in edtapp.log in the directory where the application is started. For the elmdt process, this directory is usually windows/system32. The trace from SSI is in edtssi.log in windows/system32.
