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 in a 24 hour period perhaps the environment is busting
at the seems in other areas and should perhaps be split anyway.
Even if larger logs were supported, how long would a db restore take with
roll-forward enabled? I'm thinking way too long.
Perhaps someone can share their longest db restore story with us.
Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80949-1313
(719) 531-5926
Fax: (240) 539-7175
Email: [EMAIL PROTECTED] or [EMAIL PROTECTED]
www.storsol.com
www.storserver.com
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Nicholas Cassimatis
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 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
our business.
Nick Cassimatis
[EMAIL PROTECTED]
>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 straining to go beyond. As an Enterprise
level product, I would expect TSM to be a lot more open-ended. Unless
this boost was merely a stop-gap in advance of major architectural
relief, it's not going to be enough to keep up with the demand.
Richard Sims, BU
