ADSM-L

Re: Using TDP for SQL to reapply transaction logs against a BCV/Snapshot database recoverable image

2006-07-14 11:26:38
Subject: Re: Using TDP for SQL to reapply transaction logs against a BCV/Snapshot database recoverable image
From: David McClelland <David.McClelland AT REUTERS DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 14 Jul 2006 16:25:47 +0100
Hi Jeroen,

>>> Don't know if you can apply the logs this way on MSSQL. It would
work for SAP on Oracle databases, but there offline logs are used.

Thanks for your response - yeah, working with Oracle is certainly a lot
easier, and you can configure RMAN not to 'delete input' and to leave
your archived redo logs on disk (as long as you housekeep!) to ease
recovery. With SQL/TDP we don't have that option (that I know of).

>>> You will get a problem with the expiration of the logs iif you don't
make full backups to TSM.
>>> The transactionlogs will never be marked inactive. So they will stay
within TSM 'forever'.

I'd still plan do full and differential backups to offline media using
TSM in the normal manner, as well as my VDI Snapshot Backup to BCV, so
I'm not so sure that would be a problem. I'm still just not sure if I'd
be able to apply my TDPS-backed-up transaction logs to the BCV image.

Rgds,

David McClelland
Reuters Ltd



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Hooft, Jeroen
Sent: 14 July 2006 15:34
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Using TDP for SQL to reapply transaction logs
against a BCV/Snapshot database recoverable image

Don't know if you can apply the logs this way on MSSQL. It would work
for SAP on Oracle databases, but there offline logs are used.

You will get a problem with the expiration of the logs iif you don't
make full backups to TSM.
The transactionlogs will never be marked inactive. So they will stay
within TSM 'forever'.







-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
David McClelland
Sent: vrijdag 14 juli 2006 13:07
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Using TDP for SQL to reapply transaction logs against
a BCV/Snapshot database recoverable image


Guys,
 
Has anyone tried/done this before?
 
If I was to use a tool such as EMC TimeFinder (in particular, using the
EMC TimeFinder/SQL Server Integration Utility) to take a consistent
database snapshot image (via the MS SQL VDI) of a SQL Server (2000)
database (i.e. a 'recoverable database image' as opposed to a
'restartable' one), could I then use the Tivoli Data Protection for SQL
Server agent to apply subsequent backed up transaction logs to this copy
in order to roll the database forward to a point in time? Or, would TDPS
only be able to action a transaction log recovery to a database image
that has been backed up/restored using TDPS?
 
Put simply, particularly with larger SQL Server databases (hundreds of
GB's), I'm looking at ways to reduce the recovery time in the event of
failure. Restoring a database image from a daily BCV/Clone would do most
of the work very quickly indeed, but would only give me a recovery point
of a maximum of 24 hours. However, if I were able to reapply transaction
logs to this I would have the best of both worlds. As we use the TDP to
whisk away transaction logs on (usually) an hourly basis, I'd be looking
the to TDP to action the restore of the transaction logs to the BCV
copy, but appreciate that what I'm asking might not be 'native'
functionality.
 
I'm happy to expand if any of the above is unclear! Any thoughts much
appreciated.
 
Thanks and Rgds,
 
David McClelland
IBM Tivoli Certified Deployment Professional (TSM 5.2) Shared
Infrastructure Architecture and Design Reuters, London Ltd




To find out more about Reuters visit www.about.reuters.com

Any views expressed in this message are those of the individual sender, except 
where the sender specifically states them to be the views of Reuters Ltd.

<Prev in Thread] Current Thread [Next in Thread>