I wouldn't rule out export as a backup. It's a perfectly good method of backing up *some* data. Understand it's limitations and using it where applicable.
I use it to backup my rman catalog and a few small databases with infrequent writes and long recovery windows.
If all you want to do is copy some data for archival purposes, export may be appropriate if you understand the implications of using it. As far as a backup methodology, stay away from it. See http://marist89.blogspot.com/2005/05/backup-top-11.html for my backup tips.
Cold Backup:
- faster restore (no need to rebuild db & import is slow)
- can roll forward with archlogs if required
I think cold backup wins.
"The power of instruction is seldom of much efficacy except in those happy dispositions where it is almost superfluous" - Gibbon, quoted by R.P.Feynman
Has anyone ever told you that you have a very large brain.
I can't think of the reason we're doing an export of the rman catalog, but I think it was something like portability or how to restore the catalog if you don't have the catalog in a dr situation, or something .. it seemed like a good idea at the time.
Get this, I had an exp of a 42gig database that took hours to export and 17 DAYS to import (clobs)... long story, but it had to be export/imported.
Export automatically every day ?
Reply With Quote
Originally Posted by Mr.Hanky
Bookmarks