We use sql-backtrack for Sybase, but not Oracle - never wanted to
spend the money.  We've also looked at RMAN, but rejected it for
various reasons.  The incremental hot seems good, but you're still
just pulling out changed blocks, which is basically whats in the logs.

The vast majority of our oracle databases run a hot once a week and
full export on the other 6 nights as an integrity check.  Logs are
backed up nightly to tsm.

On certain large and active databases, we run hots 3 times a week
with 4 full exports.  There is a lot of log activity on these
systems, so we backup the logs to tsm each hour.

All of our Hot backups are performed by a multi-threaded ksh script
that creates a compressed backup on disk.  The current project is to
modify this script to handle raw volumes.

Rick



On 13 Aug 2001, at 15:49, Thiha Than wrote:
> hi,
>
> >Our oracle DBA claims that 'hot' incremental backups of Oracle takes as =
> >long as 'hot' full backups using SQL-BACKTRACK. Instead he does weekly =
> >full 'hot' backups of the database and backups of the redo logs thru the
> =
> >week.
>
> >Is that how others using SQL-BACKTRACK and ORACLE do thier backups?
>
>
> It's the same for backing up oracle databases using RMAN, incremental
> takes almost as long as a full backup.  I have never used sql-backtrack
> before so I cannot comment on it.  With RMAN, it has to scan through every
> single Oracle data block to find the changed block.  So the incremental
> backup will take a long time, but the amount of data sent through can be
> significantly less.
>
> regards,
> Thiha
>