I've been trying to avoid using RMAN for a long time...
I've always been confident with my own scripts...
But once you start getting more and more servers...more and more databases
and
on different platforms...you can get tired making separate scripts
for windows and unix.
Checking it one by one and when you change something...change it on
each server.
And another thing I liked about RMAN is that it checks each block for
corruption
and it copies only used blocks. Saves a lot of space. You can't do
that with a file backup.
=)
Michael Fontana wrote:
As a longtime Oracle DBA who has used many products, including RMAN, I find myself
guilty of a paradoxical mistrust of RMAN, dating back from the time when Oracle has tried
several products, including integration with Legato and other hardware/software backup vendors,
without a consistent direction. In the little I've used RMAN, it seems quite complex and kludgy.
Even the nomenclature and commands used by Oracle within the product are a challenge to learn.While I can get RMAN to work for most simple, basic and predictable recovery scenarios, true
recovery situations are never so neat and clean. This is not an advertisement for any particular
product, but we've had great success in my shop with a product called SQL*Backtrack from BMC.
I've also heard that Veritas makes a good product, but I've not used it.From what I've seen of RMAN, at least so far, I feel far more confident with the home-cooked scripts
I've been using for years.Any comments, or other interesting experiences?
Perhaps we can do a list poll of favorite/preferred backup software?
--
Maria Aurora VT de la Vega
Oracle DBA
Philippine Stock Exchange, Inc.
"Failure is only postponed success as long as courage 'coaches' ambition.
The habit of persistence is the habit of victory."
