question about using export as a "hot" backup
411930Jan 21 2008 — edited Jan 21 2008Hello.
I have been told to do the following task (release 9.2.0.7). A kind of backup needs to be done every 12 hours of a database (24*7) to a remote machine. I have not experience with this kind of tasks and I have been talking to several workmates who have made some suggestions.
The initial idea would be making a consistent export (of the only user involved) because of some reasons:
1. It is the simplest solution. (I have no experienced with backup and recovery).
2. There is only one file involved that be compressed and sent to the remote machine.
3. When an export is currently executed of the full user, early in the morning (let's say 4 a.m. ) when no transaction is being run, it takes about only 20 minutes.
4. It is not important how long the import can take.
But I have some doubts:
1. An export at 4 p.m. is going to be executed with transaction being run. I do not know if the export can cause locking problems to these transactions.
2. I have told that there is an option "incremental export" that I have never used that can be useful in this case.
I would thank some advice any experienced dba could tell me.