Hi

You don't have to do full backups every hour to be able to do 
point-in-time restore of the database.

Having your recovery log in roll-forward mode, means that you don't have 
to backup your database. In case of a corrupt database, you just restore 
you're database that you have backed up earlier, and then tell TSM to do a 
point-in-time restore. This means that after TSM has restored the database 
from the tape, it will inspect the log, to see what transactions have been 
made after the database backup.

This was what I was trying to explain in my last message.

Using this scenario, you don't have to backup your database twice a day.

Best Regards

Daniel Sparrman
-----------------------------------
Daniel Sparrman
Daniel Sparrman
Exist i Stockholm AB
Propellervägen 6B
183 62 HÄGERNÄS
Växel: 08 - 754 98 00
Mobil: 070 - 399 27 51




Remco Post <r.post AT SARA DOT NL>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
2002-06-18 11:35
Please respond to "ADSM: Dist Stor Manager"

 
        To:     ADSM-L AT VM.MARIST DOT EDU
        cc: 
        Subject:        Re: DB backups


Hi,

The question is more, do you really want to be able to do a point-in-time
restore of your database. In case of a real disaster, you'll probably be
very happy if you get the server back to a state it was in 24 hours before
the disaster. In case of database corruption, You'll probably cannot 
afford
to restore 10 times just to find an approx point in time for the 
corrupting
transaction, which is still in you log... I guess that maybe a few
incremental db backups during the day would be good enough for most 
people.
We just do two fulls every day, but then again, we have two separate 
robots
for primary and copy pools... 

On Mon, 17 Jun 2002 15:04:12 +0200
"Daniel Sparrman" <daniel.sparrman AT EXIST DOT SE> wrote:

> Hi
> 
> You have to have your recovery log in "roll-forward" mode to be able to 
do
>  a point-in-time restore of the database(up to the minute).
> 
> This mean that the recovery log isn't purged at every write to the 
> database. Instead, the log is purged when a database backup occurs. This 

> means that you can restore your database "up to the second" it went 
down.
> 
> Doing backups of the database every minute seems, how am I going to put 
> it... Not the best solution. This is not a way to be able to restore the 

> database using point-in-time.
> 
> Best Regards
> 
> Daniel Sparrman
> -----------------------------------
> Daniel Sparrman
> Exist i Stockholm AB
> Propellervägen 6B
> 183 62 HÄGERNÄS
> Växel: 08 - 754 98 00
> Mobil: 070 - 399 27 51
> 
> 
> 
> 
> William Rosette <Bill_Rosette AT PAPAJOHNS DOT COM>
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 2002-06-17 14:52
> Please respond to "ADSM: Dist Stor Manager"
> 
> 
>         To:     ADSM-L AT VM.MARIST DOT EDU
>         cc: 
>         Subject:        Re: DB backups
> 
> 
> You can get "up to the minute" if you do enough database backups, and I
> still don't understand the "up to the minute" idea.  If you are doing
> backups every minute that seems logical but do not most people backup 
once
> a night? and if there is a database backup is not this database backup 
and
> "up to the day" same as "up to the minute?"
> 
> 
> 
>                     "Jolliff,
>                     Dale"                To:     ADSM-L AT VM.MARIST DOT EDU
>                     <[email protected]       cc:
>                     OM>                  Subject:     Re: DB backups
>                     Sent by:
>                     "ADSM: Dist
>                     Stor Manager"
>                     <ADSM-L AT VM DOT MAR
>                     IST.EDU>
> 
> 
>                     06/14/02 12:21
>                     PM
>                     Please respond
>                     to "ADSM: Dist
>                     Stor Manager"
> 
> 
> 
> 
> 
> 
> I have suggested this a couple of times, but have been told they need 
the
> ability to restore the TSM server "up to the minute" that rollforward
> provides.
> 
> 
> -----Original Message-----
> From: William Rosette [mailto:Bill_Rosette AT PAPAJOHNS DOT COM]
> Sent: Friday, June 14, 2002 9:49 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: DB backups
> 
> 
> We changed our roll forward to NORMAL and have seen very little (once in 
a
> year) crash due to full recovery log.  This may be an option instead of 
> the
> type FILE.
> 
> 
> 
> 
>                     "Jolliff,
>                     Dale"                To:     ADSM-L AT VM.MARIST DOT EDU
>                     <[email protected]       cc:
>                     OM>                  Subject:     DB backups
>                     Sent by:
>                     "ADSM: Dist
>                     Stor Manager"
>                     <ADSM-L AT VM DOT MAR
>                     IST.EDU>
> 
> 
>                     06/14/02 10:01
>                     AM
>                     Please respond
>                     to "ADSM: Dist
>                     Stor Manager"
> 
> 
> 
> 
> 
> 
> Is anyone doing db backups to disk using devclass type FILE?
> 
> I know, it's not necessarily a good thing, but right now we have a db 
that
> is large enough that the log can fill before a full db backup can run.
> 
> Before I set this up, I'm wondering if anyone else is doing this.


-- 
Met vriendelijke groeten,
Met vriendelijke groeten,

Remco Post

SARA - Stichting Academisch Rekencentrum Amsterdam    http://www.sara.nl
High Performance Computing  Tel. +31 20 592 8008    Fax. +31 20 668 3167

"I really didn't foresee the Internet. But then, neither did the computer
industry. Not that that tells us very much of course - the computer 
industry
didn't even foresee that the century was going to end." -- Douglas Adams