Hemant Shah wrote:
> How about exporting/dumping one table at a time and then backing up the
> exported data using bacula.

Unfortunately, export is not really suitable for a DR solution. The main
reason is that each table is exported at a different time, and so the
complex relationships between individual records cannot be maintained
(unless you use the CONSISTENT flag on the export, but the timeframe
involved here would blow your rollback resources, and you would have to do
the entire export as a single operation).

If you are using Oracle 10g or above, I would recommend RMAN together with
BLOCK CHANGE TRACKING. These 2 combined allow you to only back up the data
that has actually changed, thus reducing the size of your backup
significantly in most situations.

If you have enough spare disk space on the server (roughly the same as the
database size plus some more - a bit vague I know but this varies
significantly from one database to another), then look into setting up a
FLASH RECOVERY AREA and use that as a staging area for your backups.
-- 
Mike Holden

http://www.by-ang.com - the place to shop for all manner of hand crafted
items, including Jewellery, Greetings Cards and Gifts



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users