Re: Recovery log size

2005-12-15 Thread Lawrence Clark
you can look back in the recovery log and see that the log filled at the point it abandoned the task. Nothing to be done except to increase the log size. >>> [EMAIL PROTECTED] 12/15/2005 1:30:03 PM >>> Hi, I´ve 42 clients configured and in one of them I´ve a missed status when i try to back

Recovery log size

2005-12-15 Thread Marcelo Barreto
Hi, I´ve 42 clients configured and in one of them I´ve a missed status when i try to backup because of the following error: 12/09/2005 08:22:22 ANS1228E Sending of object '\\server01\c$\WINDOWS\msagent\agentctl.dll' failed 12/09/2005 08:22:22 ANS1316E The server does not have enough recover

Database "trashing" (was Re: Recovery Log size / roll forward benefits)

2001-08-21 Thread Mark Stapleton
On Thu, 2 Aug 2001 17:28:54 -0400, you wrote: >If I ask the list how rare it is, I'm sure I'll get flames from everybody >who HAS seen software corruption, and probably NO response from the many >people who are running fine. Guess again. >Maybe somebody in Tivoli support could venture a guess as

Re: Recovery Log size / roll forward benefits

2001-08-03 Thread Sheelagh Treweek
I agree with Paul, it is pretty rare - but it can happen. You can't guarantee to prevent software or hardware corruption : you just have to plan the recovery path ... The last corruption I had was on a (pretty large) test DB when trying to see the impact of a problem I had at 3.7 (live) on the 4

Re: Recovery Log size / roll forward benefits

2001-08-02 Thread Paul Zarnowski
riginal Message- > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of > > Paul Zarnowski > > Sent: Thursday, August 02, 2001 4:16 PM > > To: [EMAIL PROTECTED] > > Subject: Re: Recovery Log size / roll forward benefits > > > > > >

Re: Recovery Log size / roll forward benefits

2001-08-02 Thread Lindsay Morris
mean? > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of > Garrison, Tony > Sent: Thursday, August 02, 2001 2:21 PM > To: [EMAIL PROTECTED] > Subject: Re: Recovery Log size / roll forward benefits > > > We use Roll-forward here. T

Re: Recovery Log size / roll forward benefits

2001-08-02 Thread Lindsay Morris
:[EMAIL PROTECTED]]On Behalf Of > Paul Zarnowski > Sent: Thursday, August 02, 2001 4:16 PM > To: [EMAIL PROTECTED] > Subject: Re: Recovery Log size / roll forward benefits > > > Lindsay, et al, > > It is very possible to lose your database but not the log (we have done &

Re: Recovery Log size / roll forward benefits

2001-08-02 Thread Garrison, Tony
with what we have. -Original Message- From: Lindsay Morris [mailto:[EMAIL PROTECTED]] Sent: Friday, June 22, 2001 9:55 AM To: [EMAIL PROTECTED] Subject:Re: Recovery Log size / roll forward benefits I'm with Kelly in thinking that roll-forward is unnecessary in most

Re: Recovery Log size / roll forward benefits

2001-08-02 Thread Paul Zarnowski
rward? If so, would you mind discussing it briefly? > > > > > > > > -Original Message- > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of > > Kelly J. Lipp > > Sent: Friday, June 22, 2001 10:36 AM > > To: [EMAIL PROTECTED

Logmode (Was: Recovery Log size)

2001-06-25 Thread Reinhard Mersch
> At 08:35 AM 6/22/2001 -0600, Kelly J. Lipp wrote: > >Doesn't this bring back the issue of Roll-Forward vs. not? I guess I'm > >still in the not camp with no compelling reason to join the other. Also, > >for those in the other camp, I'm thinking if your environment is so large as > >to fill a 1

Re: Recovery Log size

2001-06-22 Thread Paul Zarnowski
At 08:35 AM 6/22/2001 -0600, Kelly J. Lipp wrote: >Doesn't this bring back the issue of Roll-Forward vs. not? I guess I'm >still in the not camp with no compelling reason to join the other. Also, >for those in the other camp, I'm thinking if your environment is so large as >to fill a 13 GB log i

Re: Recovery Log size

2001-06-22 Thread Jeff Bach
> -Original Message- > From: Nicholas Cassimatis [SMTP:[EMAIL PROTECTED]] > Sent: Friday, June 22, 2001 9:22 AM > To: [EMAIL PROTECTED] > Subject: Re: Recovery Log size > > With the current limit of 5.3GB, and the steps we've all taken to work > within that lim

Re: Recovery Log size

2001-06-22 Thread Richard Sims
>With the current limit of 5.3GB, and the steps we've all taken to work >within that limit, I don't think many people will be hitting the 13GB limit >all that quick. An incremental database backup will still flush the log, >and, with 13GB, I think we'll be OK if we don't change the way we are doi

Re: Recovery Log size / roll forward benefits

2001-06-22 Thread Lindsay Morris
feel really merits logmode=rollforward? If so, would you mind discussing it briefly? > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of > Kelly J. Lipp > Sent: Friday, June 22, 2001 10:36 AM > To: [EMAIL PROTECTED] > Subject: R

Re: Recovery Log size

2001-06-22 Thread Kelly J. Lipp
simatis Sent: Friday, June 22, 2001 8:22 AM To: [EMAIL PROTECTED] Subject: Re: Recovery Log size With the current limit of 5.3GB, and the steps we've all taken to work within that limit, I don't think many people will be hitting the 13GB limit all that quick. An incremental database b

Re: Recovery Log size

2001-06-22 Thread Nicholas Cassimatis
With the current limit of 5.3GB, and the steps we've all taken to work within that limit, I don't think many people will be hitting the 13GB limit all that quick. An incremental database backup will still flush the log, and, with 13GB, I think we'll be OK if we don't change the way we are doing o

Re: Recovery Log size

2001-06-21 Thread Richard Sims
>An FYI - TSM 4.2 will increase the limit to 13GB. I think we're all wondering when the first voice will be heard asking when the 13 GB limit will be increased. And I think we're all wondering why the increase was little more than a doubling of the current limit - which customers are already str

Re: Recovery Log size

2001-06-21 Thread Dave Canan
roadcast-- on this list, and >at any SHARE, Storage symposium, Oxford- type meeting. > >lisa > > > > >"Gill, Geoffrey L." <[EMAIL PROTECTED]> >06/21/2001 08:31 AM >Please respond to "ADSM: Dist Stor Manager" > > > To: [EMAIL PRO

Re: Recovery Log size

2001-06-21 Thread Coyle, Jack
i[SMTP:[EMAIL PROTECTED]] > Reply To: ADSM: Dist Stor Manager > Sent: Thursday, June 21, 2001 9:55 AM > To: [EMAIL PROTECTED] > Subject: Re: Recovery Log size > > Yes, it made it to the list. I've been anxiously awaiting a response from > someone conf

Re: Recovery Log size

2001-06-21 Thread Lisa Cabanas
ond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: (bcc: Lisa Cabanas/SC/MODOT) Subject:Recovery Log size I posted this 2 days ago but saw no responses. Did it make it to the list? Hello all, Last week I attended the 2 day DRM class in L.A.. In on

Re: Recovery Log size

2001-06-21 Thread Paul Zarnowski
Yes, it made it to the list. I've been anxiously awaiting a response from someone confirming this. I am unaware of this "special fix", but we could certainly benefit from it. I have heard that some relief *may* be in a new release of TSM, perhaps 4.2, which I just received in the mail yesterday

Re: Recovery Log size

2001-06-21 Thread David Longo
Yes, we saw it. I haven't heard any responses or heard anything else about it. David Longo >>> [EMAIL PROTECTED] 06/21/01 09:31AM >>> I posted this 2 days ago but saw no responses. Did it make it to the list? Hello all, Last week I attended the 2 day DRM class in L.A.. In one the discussions

Recovery Log size

2001-06-21 Thread Gill, Geoffrey L.
I posted this 2 days ago but saw no responses. Did it make it to the list? Hello all, Last week I attended the 2 day DRM class in L.A.. In one the discussions we had it was mentioned by the instructor that the size of the recovery log could be over the 5.5gb current limit. I questioned him on th

Recovery Log Size

2001-06-19 Thread Gill, Geoffrey L.
Hello all, Last week I attended the 2 day DRM class in L.A.. In one the discussions we had it was mentioned by the instructor that the size of the recovery log could be over the 5.5gb current limit. I questioned him on this since there has been much discussion on it, quite recently in fact. Accor