Thank you to all of those offering assistance with ideas on how to handle this. I have some various options of what has been suggested that I can work on and try to get resolution to this issue.
Have a great day! Brenda -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Paul Zarnowski Sent: Friday, August 24, 2007 10:40 AM To: [email protected] Subject: Re: [ADSM-L] Remote Bkups At 10:11 AM 8/24/2007, Collins, Brenda wrote: >If we let them run too long in the attempt to get a backup, they >eventualy pin the log on the TSM server and we risk the server crashing. If you can't make your TSM recovery log larger, then perhaps you need a new TSM server instance. Sounds like your problem is that you've got other activity that is causing the head of the log to advance, in combination with this long-lasting transaction that is pinning the tail of the log. You can either speed up the tail, or slow down the head, or make the log larger. -- Paul Zarnowski Ph: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801 Em: [EMAIL PROTECTED] ___________________________________________________________________________________________________ CONFIDENTIALITY AND PRIVACY NOTICE Information transmitted by this email is proprietary to Medtronic and is intended for use only by the individual or entity to which it is addressed, and may contain information that is private, privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please delete this mail from your records. To view this notice in other languages you can either select the following link or manually copy and paste the link into the address bar of a web browser: http://emaildisclaimer.medtronic.com
