Consequences of ARCHIVELOG

Question

The guys responsible for backing up our servers get our database (large) offline for more than 6 hours for the entire backup scene.

I spoke with them, asking if we could break this down into smaller and more frequent backup tasks, i.e. reserve each scheme at times or even sets of tables at different times.

Their answer was that it was possible if we decided to include ARCHIVELOG, which would have performance implications.

I am completely unfamiliar with this as well as using backup methods.

What other options would you guys recommend for backing up my circuits in a more efficient or at least not too intense way?

thank!

e.

Answer 1

if your database is disabled by ARCHIVELOG, you will lose data in the event of a hardware failure (possibly all data entered since the last backup). If acceptable, you can disable ARCHIVELOG.

( ). , ARCHIVELOG, . , , , RMAN, ( ). RMAN ( FULL cold backup), .

, - ( ) , .