Hi Debi, Well I'm glad you at least found the culprit.
You can expand the SYSTEM OBJECT and back up the pieces one at a time to find which one is really hanging, but I'm not sure that will help you. You can: 1) try to fix it with a new patch level (This is the first time I've heard of this problem at a client level higher than 5.1.6.2). 2) report it to Tivoli as a bug and let them work on a solution, or 3) , a good solution is to exclude the system object from TSM's backup, and set up an ntbackup of the system object to a flat file as a Windows scheduled task. TSM will then back up the flat file, and your're covered. (Also saves wear and tear on your TSM DB). We're using solution 3) on a bunch of our servers because the Windows client backup of the system object is a perpetual problem. Hope that helps Wanda Prather Johns Hopkins University Applied Physics Laboratory 443-778-8769 "Intelligence has much less practical application than you'd think" - Dilbert/Scott Adams -----Original Message----- From: Debi Randolph [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 10, 2003 2:52 PM To: [EMAIL PROTECTED] Subject: Re: Backup doesn't confirm completion. Your right Wanda, it is something with the system object. I did a 'backup systemobject' and it just sat there after the successful completion of the backup of the RSM Database. It's been 1 hour and it's still just sitting there. The active sessions are gone from the query session. The activity log is still putting out idle session timeout messages. Guess I'll try to upgrade to a new version of TSM and see if that helps. Thanks, Deb "Prather, Wanda" <[EMAIL PROTECTED] To: [EMAIL PROTECTED] UAPL.EDU> cc: Sent by: "ADSM: Subject: Re: Backup doesn't confirm completion. Dist Stor Manager" <[EMAIL PROTECTED] .EDU> 12/10/2003 01:10 PM Please respond to "ADSM: Dist Stor Manager" Did you try manual backup of just the system object? When I've seen that happen, it was always something in the backup of system objects that was hanging it. Only solution was to upgrade, but we are at 5.1.6.2 and running OK. -----Original Message----- From: Debi Randolph [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 09, 2003 2:25 PM To: [EMAIL PROTECTED] Subject: Backup doesn't confirm completion. Anybody...... Windows 2003 Server, TSM Version 5.2.1.0 I have a Windows 2000 Client running TSM version 5.1.6.7. It backs up everything just fine but never reports the backup completed. In the DSMsched.log, you see the last thing it backed up was 'Successful incremental backup of RSM Database'. Then nothing else, ever. The backup does not report it's stats to the dsmsched.log, nor to the TSM activity log. The client never picks up it's schedule again and doesn't backup again, until I bounce the TSM Scheduler service. Then you can see the schedule in the log and the next night it backs up, but just dies after 'Successful incremental backup of RSM Database'. again. There are no errors in the dsmsched.log There are no errors in the dsmerror.log Q Sess - reports no active sessions for the client. I've tried it in both polling and prompted mode, with the exact same results. I can manually backup the server without any issues. Any ideas? Deb Randolph First Banks, Inc. St. Louis, MO ******************* N O T I C E ******************* The information contained in this e-mail, and in any accompanying documents, may constitute confidential and/or legally privileged information. The information is intended only for use by the designated recipient. If you are not the intended recipient (or responsible for the delivery of the message to the intended recipient), you are hereby notified that any dissemination, distribution, copying, or other use of, or taking of any action in reliance on this e-mail is strictly prohibited. If you have received this e-mail communication in error, please notify the sender immediately and delete the message from your system. *************************************************** ******************* N O T I C E ******************* The information contained in this e-mail, and in any accompanying documents, may constitute confidential and/or legally privileged information. The information is intended only for use by the designated recipient. If you are not the intended recipient (or responsible for the delivery of the message to the intended recipient), you are hereby notified that any dissemination, distribution, copying, or other use of, or taking of any action in reliance on this e-mail is strictly prohibited. If you have received this e-mail communication in error, please notify the sender immediately and delete the message from your system. *************************************************** ******************* N O T I C E ******************* The information contained in this e-mail, and in any accompanying documents, may constitute confidential and/or legally privileged information. The information is intended only for use by the designated recipient. If you are not the intended recipient (or responsible for the delivery of the message to the intended recipient), you are hereby notified that any dissemination, distribution, copying, or other use of, or taking of any action in reliance on this e-mail is strictly prohibited. If you have received this e-mail communication in error, please notify the sender immediately and delete the message from your system. ***************************************************
