Backup and Recovery from Archive Log

Dear all,
I implemented hot backup with oracle9i and
Can anybody suggest me how to backup and recovery archive log ?
Thanks for advance.
Chara

assuming you are using RMAN for backup -
backup ( archivelog all );
backup ( archivelog all delete input ); - to delete from file system.
If you are not using RMAN but backup using a script which puts the tablespaces in hot backup mode then you just need to backup archive log directory.
The archive logs are required when you need to do a database recovery. You don't recover archive log files.
rgds

Similar Messages

DB backup and removal of archive log files?

I have an application that uses Oracle 10gR2 on Linux RedHat EL 4.5. The DB is fairly simple, so backing up daily or weekly by using expdp (Datapump) is fine for our needs. We have an install that uses Data Guard, which in archivelog mode is filling up the disks fast.
What is the best way to clean up archive log files in a Data Guard configuration? I have seen posts that indicate RMAN is tough to work with and has problems with recovery, so I would rather avoid it.
I would like script something on a daily or weekly basis.
Thanks,

RMAN not easy? Lets see how hard it is:
rman target /
RMAN> backup database;Surely that isn't too challenging.
Now if you want to do it properly you are talking about setting up a repository ... much more complex:
-- on the repository database server
CREATE USER repos
IDENTIFIED BY oracl1
DEFAULT TABLESPACE users
TEMPORARY TABLESPACE temp
QUOTA UNLIMITED on users;
GRANT create session, recovery_catalog_owner TO repos;
-- on the target server (your production db)
rman target / catalog repos/oracle1@<tnsnames_entry_for_your repository>
RMAN> create catalog;
RMAN> register database;
RMAN> backup database;If this is too much perhaps you should look into MS Access. <g>
All of this is documented at the top of the RMAN page in Morgan's Library at www.psoug.org so you can cut-and-paste your way through it if you want.
How is an export not a backup you ask?
The Oracle docs can be found at http://tahiti.oracle.com. You should consider reading them some time.
As I said before ... an export can NOT be used to recover ... ever. That says it all.
Your resistance to change. Your resistance to doing things properly. Your resistance to reading the docs. You'd better watch out. There are people who would like to have your job ... a lot of them.

Recover DB which don have backup and not in archive log mode

Hi
today one of our DB in oracle 10gR2 in AIX got crashed which is not in archive log and which does not have any backup. It was maintained by the Developers and they need it to be recovered. When trying to open it says message like getting error with system01.dbf needs to more recover. Can any body help me. Very Urgent... Is there any way to recover the db??
Thanks
Ram

Hello Mr.Sybrand Bakkar,
Thanks for your suggestion. Being a DBA i myself knows that without anything I wont be able to. I m just trying to get some suggestions whether is there any way to recover it or has some experts came across these situations and got some answers. When we are not able to think beyond our limit, we come to the forums and post question. I know that this is not the place to write where i can be rude, Hence please change ur perception. When i say urgent, it means that unfortunately they have messed up their DB and came to DB Team for assistance to get their data back which has to be given to their process partners and As a support team we are trying our best to recover it. Anyhow thanks for your reply and suggestion. Have a great day.
Thanks
Ram

Backup and recovery from an external hard-drive to another

Hi sirs/madams,
I have two external hard drives and one of them is acting really weird, lagging and it became so very very slow compared to before.
So I want to back everything up in it into the other external hard drive, I wanted to used the Disk Utility but got scared, didn't want to play with it and then lose all the work of two years.
So the question here is how to backup all the data from hard drive 1 to hard drive 2 and then recover the data back from hard drive 2 to hard drive 1?
Thanks in advance.

sara-alain wrote:
You're kidding, right?
1.2 TB of data will take nearly 10 bloody hours to be moved into another HDD.
Please give me a professional solution
A 'professional' solution? All retina MBPs have Thunderbolt capability so use that to transfer data. It will reduce transfer time by 50% or more depending upon what protocol you are using. If your MBP has Thunderbolt 2, the transfer times will be twice as fast as 'plain' Thunderbolt.
Ciao.

Need clarification for cold backup and recovery

Hello Everyone ..
I have much confusion on cold backup and recovery topic.
Already i posted a scanario regarding this and i want to know some clarity points to understand.
1. I had cold backup two days before
2. I am creating an object *(EMP)* and inserting some records then issue log switch continiously.
3. Manually i removed all physical files (datafiles , control files , log files , redolog files ...)
4. then i issued STARTUP FORCE MOUNT;
5. here i am getting error identifying control file.
6. cold backup two days before all files restored
6. then i issue recover database using backup controlfile until cancel;
7. i am trying to issue select * from emp; i am getting error
select * from emp
*ERROR at line 1:
ORA-00942: table or view does not existMy QUESTION IS
After cold backup finished , i created emp table ..
when restoring old back " There is no emp table"
*- then , can i recover emp table ? - If so , please explain about this ..*
Note : REF - LINK https://forums.oracle.com/forums/message.jspa?messageID=11056341#11056341
- Above link says what i did ? . In this thread i am asking concept & logic ..
please do NOT consider as "*DUPLICATE*"

When you recover the database using backup controlfile until cancel, you have to apply archived logs. Did you apply all of them?
If the create command was in the online redo, not yet archived, and you lost the online redo, then you won't have it. This is why you want to have redo multiplexed, it is a critical piece.
In some recovery scenarios, if you haven't lost the online redo, you need to specify those files as if they were archives.
It is normally easier to just be sure you have the latest controlfiles and let Oracle figure it out automatically (which is why you want to use online RMAN backups rather than cold backups). But yes, it is important to understand what is going on for different scenarios. I used to have manual standbys, and one of the disaster instruction sets explained to try to get online redo over to the standby to lose as few transactions as possible. That could still be useful for some snapshot hardware type scenarios, assuming the business is too cheap to do proper failovers.

BACKUP AND RECOVERY USING RMAN

제품 : ORACLE SERVER
작성날짜 : 2003-08-04
BACKUP AND RECOVERY USING RMAN
==============================
1. Backup Method
1.1 backing up in noarchivelog mode
SVRMGR> shutdown;
SVRMGR> startup mount
rman을 가동시킨 후 다음을 수행
run {
# backup the database to disk
allocate channel dev1 type disk;
backup (database format '/oracle/backups/bp_%s_%p'); }
1.2 Backing up databases and tablespaces in archivelog mode >
- database 단위 backup script
run {
allocate channel dev1 type 'sbt_tape';
backup skip offline (database format '/oracle/backups/%d_%u');
release channel dev1;
- tablespace 단위 backup script
run {
allocate channel dev1 type disk;
backup
(tablespace system,tbs_1,tbs_2,tbs_3,tbs_4,tbs_5
format '/oracle/backups/bp_%s_%p');
- datafile 단위 backup script
run {
allocate channel dev1 type disk;
backup
(datafile '?/dbs/t_dbs1.f'
format '/oracle/backups/%d_%u');
- control file backup script
control file은 system datafile의 첫번째 화일을 백업받을 때 백업되며 다음과
같은 방법으로도 백업받을 수 있다.
run {
allocate channel dev1 type 'sbt_tape';
backup
(tablespace tbs_5 include current controlfile
format '%d_%u');
- archived logs backup script
NLS_LANG=american
NLS_DATE_FORMAT='Mon DD YYYY HH24:MI:SS'
run {
allocate channel dev1 type 'sbt_tape';
backup
(archivelog from time 'Nov 13 1996 20:57:13'
until time 'Nov 13 1996 21:06:05'
all
format '%d_%u');
run {
allocate channel dev1 type 'sbt_tape';
backup
(archivelog low logseq 288 high logseq 301 thread 1
all delete input
format '%d_%u');
- copying datafiles
run {
allocate channel dev1 type disk;
copy datafile '?/dbs/tbs_01.f/dbs/tbs_01.f' to '?/copy/temp3.f';
- incremental backups
새로운 데이타화일이 추가되거나 테이블스페이스가 추가된다면 level 0의 backup을
반드시 수행한다.
run {
allocate channel dev1 type 'sbt_tape';
backup incremental level 0
(database
format '%d_%u');
run {
allocate channel dev1 type 'sbt_tape';
backup incremental level 1
(database
format '&d_%u');
2. Recovery Method
- tablespace recovery
run {
allocate channel dev1 type disk;
allocate channel dev2 type 'sbt_tape';
sql "alter tablespace tbs_1 offline immediate" ;
set newname for datafile 'disk7/oracle/tbs11.f'
to 'disk9/oracle/tbs11.f' ;
restore (tablespace tbs_1) ;
switch datafile all ;
recover tablespace tbs_1 ;
sql "alter tablespace tbs_1 online" ;
release channel dev1;
release channel dev2;
- point-in-time recovery
TBS_1 테이블스페이스는 두 개의 데이타 화일 소유. TEMP1은 백업이 없으나 user
data는 없는 temporary segemnt만 가지고 있음.
NLS_LANG=american
NLS_DATE_FORMAT='Mon DD YYYY HH24:MI:SS'
SVRMGR> shutdown abort;
SVRMGR> startup nomount;
run {
# recover database until 3pm after restoring tbs_1 to a new location
allocate channel dev1 type disk;
allocate channel dev2 type 'sbt_tape';
set until time 'Nov 15 1996 15:00:00'
set newname for datafile '/vobs/oracle/dbs/tbs_11.f'
to '?/dbs/temp1.f' ;
set newname for datafile '?/dbs/tbs_12.f'
to '?/dbs/temp2.f' ;
restore controlfile to '/vobs/oracle/dbs/cf1.f' ;
replicate controlfile from '/vobs/oracle/dbs/cf1.f';
sql "alter database mount" ;
restore database skip tablespace temp1;
switch datafile all;
recover database skip tablespace temp1;
sql "alter database open resetlogs";
sql "drop tablespace temp1";
sql "create tablespace temp1 datafile '/vobs/oracle/dbs/temp1.f' size 10M";
release channel dev1;
release channel dev2;
- 전체 데이타베이스를 복구하려 할때
current redologfile이 존재할때 다음과 같은 작업으로 전체 데이타베이스를 복구할
수 있다.
replace script restore_recover_db_cf {
execute script restore_cf;
sql 'alter database mount';
execute script restore_db;
execute script recover_db;
sql 'alter database open resetlogs';
replace script alloc_1_disk {
allocate channel d1 type disk;
setlimit channel d1 kbytes 2097150 maxopenfiles 32 readrate 200;
replace script rel_1_disk {
release channel d1;
replace script restore_cf {
execute script alloc_1_disk;
restore
controlfile to '/private/db_files/twih/dbf/ctrl_twih_1.ctl';
replicate
controlfile from '/private/db_files/twih/dbf/ctrl_twih_1.ctl';
execute script rel_1_disk;
replace script restore_db {
execute script alloc_1_disk;
restore
(database);
execute script rel_1_disk;
replace script recover_db {
execute script alloc_1_disk;
recover
database;
execute script rel_1_disk;
Reference Documents
<Note:104796.1>

Hi Alok,
why there is a need for standby here? you mean to say standby db?
what i exactly need is , whether i will be making use of archivelogs which are all archived during that backup period (in mount stage) after some days, if i face any problem with the PRODUCTION Database..

Backup and Recovery in different mode

We have a database in noarchivelog mode.
Currently we convert it to archivelog mode before monthly full database RMAN backup.
And after backup,we again back it to noarchivelog mode.
Now my question is that, in case of failure can we recover this database(any how) with that backup?
Please advice and if possible give the recovery steps.
Thanks & Regards
Quazi Abdur Rab

Hi,
It's not good to switch from Archive Log Mode and No Archive Log Mode as your wish.
See, As Khurram had explained you the thing. Point in time recovery before crash is quite not possible but only last the restore point applicable for your DB. Rest of the things can be recovered. Why are the implications you are facing if the DB is in Archive Mode. ?? I Suggest do peform and maintain Archive Log which is good for your DB.
- Pavan Kumar N

Backup and recovery oracle XE

Hi, oracle guru.
I have searched in google how to backup and recover to and from removable disk or hard disk (in separated folder) in oracle XE 10g, but I didn't found any.
I tried to use backup and recovery database given from oracle itself, and I analyze which file is added and modified. I do somekind of trial and error action. First, I backup my database and then I copy 2 files (I forgot the names, 1 is about 853 kb, and one is the backup file (about 500 mb)). And then I do some user deletion (I have several users) and then I backup and copy again to different folder from the previous one. Note that I am not using archive log: on.
Unfortunately, when I copy the previous backup (the one with complete users) to oracle folder, the restore database does work until, I guess starting database, it throws error saying that something error in SYSTEM.DBF, thus making my oracle doesn't work, even I canot go to database home page.
My question is that how to backup and recover database to and from removable disk or harddisk with different folder? Which files do I need to copy or should I add backup and recover script?
Thanks for the reply.

Yes, as I already mentioned, previously (assumes) that I have database with several users (say 5 users). And I use backup database and restore database from oracle folder in start menu, and it works perfectly (assuming that I delete one user and then restore database).
However, I tried to copy the backup file (which I mentioned before, but I am not sure the files I am copying is backup file since I only analyzed it). So, I test it. First I backup, and I copy to separate folder. Next, I do some user deletion, and I do backup. Say, for example I want to use that backup file in another computer. I copy the files to oracle installation folder. One in product/database/ folder, and one in flash-recovery area. When I try to use restore database (in start menu), it works, until, I guess, starting database, and it throws error saying that error in SYSTEM.DBF.
So, my point is that, how do I backup my database so that the backup file can be in separated folder (for example in removable disk), thus I can also select backup file to be restored.

Backup and recovery questions

Hi,
I am a newbie in Oracle database 11g Release 11.2.0.1.0 and Oracle Linux and I have questions regarding backup and recovery.
I used the “Schedule Oracle-Suggested Backup” and have it run nightly to back up to local disk. In the Backup Setting, on the Retention Policy, I selected “Retain backup that are necessary for a recovery to any time within the specified number of days (point-in-time recovery) day = 7”
With the setting above, I checked the “Manage Current Backups” and I have many back sets for SPfiles, controlfiles, datafiles, and archivelogs for the last several days. However, for image copies, I have only one set and it get over write nightly. With the configuration above, is that true that I can only recover to any point in last 24 hours?
My goal is to be able to recover any “point-in-time” in the past 5 days, should I change my Retention Policy to “Retain at least the specified number of full backups for each datafile” to 5 backups (each full daily backup)? Please provide some advices. Thanks

By looking the following, it looks like by default its 24 hours but it depends upon the recovery window you choose.
Enterprise Manager makes it easy to set up an Oracle-suggested backup strategy for backups to disk that protects your data and provides efficient recoverability to any point in the a recovery window of your choosing. (In the simplest case, examined in this section, this window is 24 hours.) The Oracle-suggested strategy leverages Oracle's incremental backup and incrementally-updated backup features to provide faster backups than whole database backups, and faster recoverability than is possible through applying database changes from the archived log to your datafiles.
The Oracle-suggested backup strategy is based on creating an image copy of your database. This copy is rolled forward by means of incrementally updated backups. Oracle Enterprise Manager schedules RMAN backups jobs for you to run during the overnight hours.
For each datafile, the strategy calls for backups as follows:
At the beginning of day 1 of the strategy (the time the first scheduled job actually runs), an incremental level 0 datafile copy backup. It contains the datafile's contents at the beginning of day 1. In a restore-and-recovery scenario, the redo logs from day 1 can be used to recover to any point during day 1.
At the beginning of day 2, an incremental level 1 backup is created, containing the blocks changed during day 1. In a restore-and-recovery scenario, this incremental level 1 can be applied to quickly roll forward the level 0 backup to the beginning of day 2, and redo logs can be used to recover to any point during day 2.
At the beginning of each day n for days 3 and onwards, the level 1 backup from the beginning of day n-1 is applied to the level 0 backup. This brings the datafile copy to its state at the beginning of day n-1. Then, a new level 1 is created, containing the blocks changed during day n-1. In a restore-and-recovery scenario, this incremental level 1 can be applied to the datafile rolled forward on day n-1 to the beginning of day n, and redo logs can be used to recover the database to any point during day n.
The datafile copies used in the Oracle-suggested backup strategy are tagged with the tag ORA$OEM_LEVEL_0. The level 1 incremental backups for use in this strategy are created for use with datafile copies that are so labelled. You can safely implement other backup strategies without concern for interference from the backups for the Oracle suggested strategy.
There are also Oracle-suggested strategies that use tape backups along with disk backups, but those are beyond the scope of this chapter.

Backup and Recovery Plan

I know very little backup and recovery plan in oracle using RMAN or any agent.
Is this right way to summarize the backup and recovery plan for 24 X 7 system required to have 99.99% up time.
The backup and recovery strategy recommended below is based on the premise that database is set ‘ARCHIVE LOG’ mode.
The database files must be backed up using an RMAN backup (or tape agent i.e. Oracle Agent for Veritas) to allow for recovery of corrupted files or files on failed volumes. These archive logs and RMAN backups should be written to a directory on a separate volume from any other database files. It is not recommended to store RMAN backups in the Oracle Control files. The RMAN backups and archive logs and document images are then written to tape in accordance with the GFS backup strategy.
Any suggestions and inputs would be helpful
Thanks

It was a generic note for the productions databases, i.e. have db in archivelog mode, take backups through RMAN to TAPE or on disk which will be used in case of disaster or media recovery.
You need to decide what kind backup and recovery policy you need to have and where you are going to copy/place the backup.
Just keeping in mind the following:
1. How quickly the database can be recovered in case of disaster/media recovery.
2.Make sure no transaction are lot, in another way, recovery until point of time.
3. What kind of policy you need, incremental, cummulative or full backup.
Jaffar

Backup And Recovery on 7.2.3

i need information on backup and recovery, please help me.(from begin)
i don't speak english, but don't worry, i read the english.
Thanks you.
Oscar Rojano. [email protected]

i suggest you read the oracle backup and recovery manual sections, or take the course, as this is an extremely important topic.
a cold backup is done when the database is down. to do a cold backup, first shutdown the database. then backup all datafiles. then restart the database. you can use this type of backup if your business can tolerate the database being down for the time it takes to do the backup.
a hot backup is done when the database is up and running. the database must be running in archive log mode. then, a hot backup can be performed by putting tablespaces into backup mode, and then backing up the affected datafiles. whenever you do a hot backup, you must be sure to also back up all archive log files from the start of the backup through the end of the backup. if you must restore the backup, and you don't have the archive logs, your database will not start and you will not be able to get it back.
an export is a backup of selected tables. it is not a complete backup and should not be used if a fast, complete recovery of the entire database is required. it is good if a fast restore of a single table is something you need to do often. be aware of database consistency problems if you are restoring a single table that is updated frequently.
depending on your requirements, you will use one or more of the three backup solutions above.
i would recommend that you use the oracle RMAN (recovery manager) tool, in conjunction with an enterprise backup tool from HP, Veritas, or IBM, to be sure your backups are as complete and reliable as possible.

Issue with backup and recovery of WLS

I have installed WLS 10.3.6 in my 64-bit Linux box, now I am trying to take backup my server. I have a web-application deployed to my WLS, the path to my war file was something like:
<home_dir>/install_files/myapp.war
Now to take backup I ran tar command on my current Linux box, now I copied the .tar files to my new Linux box and extracted it. When I am starting my weblogic server it is looking for the war file from the path <home_dir>/install/myapp.war which does not exist on my new machine. So I logged into Admin console of WLS on my new machine and trying to change the path for myapp.war by clikcing update button. But I am getting this error when I change the path:
weblogic.management.ManagementException: [Deployer:149007]New source location, '/u01/Oracle/install_files/myapp.war', cannot be deployed to configured application, 'myapp'. The application source is at '<home_dir>/myapp.war'. Changing the source location is not allowed for a previously attempted deployment. Try deploying without specifying the source.
Update operation failed - no deployments changed.
Please help me how to deploy my files. I'm expecting backup and recovery option should also take care of deployed files but it is not happening in my case, is that wrong?

1. There is no specific order, but last to go down should be CMS and first to come up should be CMS.
@echo off
Stop Business Objects Services
echo
net stop "BOBJCrystalReportApplicationServer"
net stop "BOBJEventServer"
net stop "BOBJProgramServer"
net stop "BOBJOutputFileServer"
net stop "BOBJProcessServer"
net stop "BOBJInputFileServer"
net stop "BOBJDestinationServer"
net stop "BOBJCrystalReportspageserver"
net stop "BOBJJobServer_Report"
net stop "BOBJCentralMS"
exit
Similarly to Start services, instead of stop use start and put CentralMS at the top and save it as a batch file.
2. Jobs running when the server goes down will fail, other recurring jobs will wait till the server comes up.
3. Yes, backup File Store & Database.
4. Not sure about the default password for My SQL, you should be able to backup the MySQL database, I have done that once.
5. Backup FileStore & Database.

Which one is the Best Backup and Recovery Method in your point of view?

Friends,
Currently we are taking hot backup with archive mode.
we have backup script to copy the datafile and we will copy the archive files in a separate folder.
alter tablespace system begin backup;
host cp /u01/app/oracle/oradata/livedb/system.dbf /u02/online_backup
alter tablespace system end backup;
like the above script we will copy all the other data files.
then in the test environment. we will copy the datafile and archive file.
we will be recovering by using the below statement.
sql>recover database until cancel using backup controlfile.
currently no problem in backup and recovery.
What i want is......
is there any other sophisticated and safe way to take a backup and restore it to another server?
if yes, can anybody point out the steps or link.
I have heard about......
DataGuard
RMAN
EXP/IMP
but i never used the above.
Thanks
sathyguy

DataGuard
RMAN
EXP/IMP ...
The only real backup/recovery method here is RMAN, Oracle's integrated backup/recovery tool, which I prefer. As an example for a fully functional RMAN command see 'backup database plus archivelog delete all input'. This statement provides a complete hot database backup including archivelogs and deletes at the successful end all archivelogs in all destinations . Compare this statement with all the steps necessary to do the same job manually. Don't worry you have many ways to finetune your backup.
For more informations there's a quick start guide:
http://download-uk.oracle.com/docs/cd/B19306_01/backup.102/b14193/toc.htm
Dataguard is a high availibility tool, which provides a kind of backup in terms of having a logical or physical standby database. When primary side fails you can switch to this standby database. Such a constellation does not mean, database backups are no longer necessary.
Export/Import is a logical backup, still often used to recover from human errors (you accidentally dropped a table for example). Don't use it as a replacement for physical backups, especially hot backups,in case of media failures you always will have loss of data, because changes made afterwards the export are not captured.
Once again I recommend you seriously should consider RMAN.
Werner

Delete old and backed up archive log,

Hi all,
Am trying to modify our RMAN backup script to delete old and backed up archive logs off the disk.
We run daily Incremental L0 or L1 backups, with 3 daily archive log backups. Currently we delete archive logs as they are backed up (backup archivelog all delete input). However, we are considering leaving x days worth of archive logs on disk, just in case, quick restore is needed (e.g. tablespace media recovery etc. etc.)
For example,
We can delete archive logs old tha n x (where x=no_days depending on database) by,
delete archivelog until time 'sysdate-15';
We can also delete archive logs that have been backed up to disk by,
delete archivelog all backed up 1 times to disk;
Questions,
1) Why does 'backed up 1 times to disk' require the 'all' in the statement ?
2) Is there any way to combine the 2 statements ? (backed up 1 times and older than x days ?). Just being a bit extra cautious to ensure that we have everything backed up. In real-world shouldn't be a problem, as we will be alerted to any backup failures, but trying to cater for the very worst situation.
Thanks for your help and insight.

Hi,
Scratch the questions. Found the answer in another thread. Seems when I tried to combine the statements initally, I had a typo.
It is now working as expected.
Thanks and regards,

Backup and recovery a tablespace

Hi all,
I recently started reading about oracle backup and recovery concepts, and I needed to understand what is happening where we put a tablespace to a backup mode (alter tablespace tablespace_name begin backup) ?
thanks for help

Three things happen when you put a tablespace in hot backup mode:
1. A checkpoint is issued, so that dirty blocks belonging to that tablespace are flushed to disk
2. The header of the datafiles associated with the tablespace are locked from further update by CKPT.
3. The first insert/update/delete that affects a data block that is part of the tablespace being backed up, after the 'begin backup' command is issued, causes the entire block to be written to the online redo logs. Second and subsequent changes generate the same amount as redo as normal, though.
That's it. As Hemant mentions, the really important bit is number 2 in that list: whilst the header of the datafile(s) is locked, the datafiles themselves are not, and are written to as much as they always are. The idea that somehow the datafiles are not written to and that the redo logs are the only place that stuff is written to during the backup is completely and utterly wrong. CKPT is not allowed to write to the header, because that way, we know the earliest "age" of the datafile copy when it went into backup mode, and thus know the point from which redo needs to be applied during a recovery. But DBWR writes to the rest of the datafile perfectly normally.
Number 3 is also important, because it's why we don't leave tablespaces in hot backup mode more than we can help: the amount of redo generated increases because we need a 'starter image' for any block that's modified during the backup.

Backup and Recovery from Archive Log

Similar Messages

Maybe you are looking for