Re: RAC, CFS and online backups

Pete, Howard, Connor, Paul, Group,

Thanks for some Good Information.

My current recommendation for backup RAC would be:

• cold backup if you can.
• hot backup by a ksh script, that should generate its own commands, and execute them at the same time (e.g. generate just before execution, to make sure it is up-2-date).

All this under assumptions:

• a clusterded file system (do not want to run RAC without it).
• an indetermined nr of nodes (e.g. expandable).
• you already have a hot-backup ksh, that generates single-node commands (like alter tablespace, cp files, and re-cp files to help during restore).
• as a conservative Dino, I do not want additional overhead of RMAN.

nb: Looking fw to a thread to discuss RAC in general: IMHO the SCALABILITY is its STRONGEST point, with failover and HA as a good, but far, second argument. HA is best assured by Good, Redundant, hardware. Whereas scalability can be done more effectively by adding nodes as-needed under a running database.
Think of a news-site reacting to increased hits by _quickly_ adding the development- test- and acceptance nodes to support production load!

Ideas anyone ?

Regards,

PdV Received on Sun Dec 08 2002 - 11:07:17 CST