Mike - Someone else may have specific experience with your Fedora platform, but some general observations...
We are at a disadvantage of not knowing what your backup operation was or client options or other configuration information, which may play a part. Too many sites install a client and then launch into a whole file system backup and then don't know what's going on when something goes wrong. When trying a new client, I would strongly suggest starting with basic validation steps... Do 'dsmc q opt' to check that your options are valid; and, as a side effect, this will perform the first interaction with the TSM server (to look for any client options stored on the server side). Then do 'dsmc q inclexcl' to verify that Include/Exclude specifications are valid. (Not all come from your client specs: some may be defined on the server.) Now perform a trivial backup to see if the mechanics work for a real session which involves storage: 'dsmc Selective <AnyFile>'. This will exercise the flow path from the client to the server, through the initial storage pool defined via your Management Class and Copy Group - which will uncover a problem if needed definitions or resources are not in place on the server. Thereafter, do 'dsmc Incremental' on a directory. (This is exercise stuff - the resulting filespaces can be discarded if desired.) If problems or anomalies, check the client dsmerror.log and the server Activity Log. Perform Query SEssion on the server during and after the interaction, looking for issues and verifying data transfer in both directions, per statistics reported. The TSM Problem Determination Guide is there for pointers and checklists on things to look for in pursuing client sessions. You can also run the client under the Unix 'truss' command to see what's going on, and TSM client tracing is available. Richard Sims On Apr 27, 2006, at 3:55 PM, Mike Anderson wrote:
I have a very low end client (600mhz) running fedora 5, that one of our customers wants backed up. The client installed ok but when I try to run a backup the backup just hangs. I tried to use memory efficient, took compression off, and even changed large comm buffers to off. It goes through all the files ok but when it starts to backup the files just hangs. The client looks like its running, but the TSM server shows its status as idle wait. Client version 5.3.2 Server version Windows 5.2.3 Any ideas? Mike Anderson [EMAIL PROTECTED] CONFIDENTIALITY NOTICE: This message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
