All new rows inserted in the MY_TEST_TABLE are lost, as the Row Count reverts to 24,554 that was present when the Level-1 backup was taken. Title was updated. RMAN Backup Concepts - 11g Release 2 (11.2). If I create another save set (incremental level 1), the client name is database.example.org and the save set is also called RMAN:\testdb1_INCREMENTAL.
So, it would be a good idea to make frequent Incremental Level-1 backups as they could be faster (shorter duration) than the Level-0 backups (which could be scheduled during longer maintenance weekend hours). The next backup is a differential incremental backup. This blog is being aggregated by orafaq.com, Oracle Database Certified Professional 12c. Configuring Transparent Data Encryption -- 2 : My Posts on Standby Database[s] -- Data Guard, Download Oracle Virtual Box / Vagrant / Docker Images, Optimizer Environment Parameters (by Jonathan Lewis), "Bits and Pieces" -- Links by Jonathan Lewis, SQL Statement Performance Diagnosis (by Randolf Geist), Enabling and Reading Oracle Traces (by Gints Plivna), Patching most of my environments with the July 2022 Bundle Patches, New Parallel Distribution Method For Direct Path Loads, Costing Concatenated Indexes With Range Scan Predicates Part I (Nothing To Be Desired). Hope that it is clear now.
I do know rman and have always used backup as compressed backupset database plus archivelog delete input.
Rman incremental without including archive logs?? It works for me (truncating the end of long lines): Dave, I don't understand what is going on. My GitHub site -- Presentations and some code, YouTube Videos for beginners to Oracle and SQL Server. If your RMAN list backup output only shows Full and level 1 backup, then the level 0 backup must have been deleted. Cumulative incremental backups reduce the work needed for a restore operation by ensuring that you only need one incremental backup from any particular level.
I use the table "HEMANT.MY_TEST_TABLE" as the reference table at this point.
My mistake, forgive me. Please post also the output of below command: Please show the part in RMAN Backup Concepts - 11g Release 2 (11.2) that outlines that a parent backup can either be level 0 or level 1. The 10g documentation outlined the following: It seems the RMAN concepts guide for 11g was re-written and does not use the term "parent incremental backup" anymore. Great and helpful post! Is restoring the controlfile required in this case, or would using the current controlfile also work?
If you read carefully I did not say that a full backup can be a parent to a level 1 backup - I said that a level 1 can be a parent for another level 1. Then restore.
As said in previous posts you can not use a full backup to take a level 1 backup no matter what type. Since the last backup resulted in level 0, do a level 1 backup now: See what we have (controlfile autoback is off): Based on the above your assessment is wrong. I don't know, I thought it was a new topic, but it really wasn't. In NetWorker, it would complain it is duplicated object and refuse to add the later one. The restore would use the full backup and the recover would use the incremental backup. The database is unavailable (as it is not OPEN) for the duration of the BACKUP DATABASE run. Oracle does support all Incremental (as well as Full) Backups of Databases running in NOARCHIVELOG mode. Note : It does not matter that I don't use an FRA. Thanks for the merge. Similarly, the Restored database has a higher SCN because the act of Restore+Recover+Open also increments the Database SCN. 2. Try to create another incremental level 1 backup and it should automatically create a level 0 instead. For example, in a differential level 1 backup, RMAN determines which level 1 backup occurred most recently and backs up all blocks modified after that backup. You can also refer to my first post and attachment for the actual command and output. How to use [code] tags and make your code easier to read. Please note that this site uses cookies.
2. The highest Log Sequence# is 865 (the CURRENT Redo Log file) and the SCN is 864084. I am an Oracle Database Specialist in Singapore. The behavior is the same, the restore would use the full backup and the recover would use the incremental backup. So I had to create one full backup, save set is: RMAN:\testdb1_FULL.
Anonymous,Anonymous,See my follow up post https://hemantoracledba.blogspot.com/2021/02/restore-and-recover-noarchivelog.htmlRMAN won't allow an OPEN RESETLOGS if you don't restore the older Controlfile (backup).But you can fallback to the SQL commands using sqlplus as I show in the new post. RESTORE and RECOVER a NOARCHIVELOG Database, with Datapump in Oracle ADB using SQL Developer Web. You cannot restore and recover individual datafiles for a database in NOARCHIVELOG mode as you would be able to do with backups with ArchiveLogs. Such backups can be made when the database is in MOUNT (not OPEN) mode.
The UNC address hasn't given me any problems. So I think it is actually make use of the previous full backup. To specify: I recommended him to put the database in mount mode during the backup if he want to have a consistent and recoverable backup after the incremental without archived logs. The parent does not necessary needs to be a level 0 backup it can be a level 1 backup as well in case of a differential level 1 backup. In order to perform an incremental level 1 backup, a prior level 0 backup is required. There are 2 "downsides" to Backups in NOARCHIVELOG mode : 1. FYI, the full backup is performed by this command: BACKUP AS COMPRESSED BACKUPSET FULL DATABASE INCLUDE CURRENT CONTROLFILE TAG 'FULL-20170219-042008' SPFILE TAG 'SPFILE-20170219-042008' PLUS ARCHIVELOG TAG 'ARC-20170219-042008' DELETE INPUT; The incremental backup is performed by this command: BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 1 DATABASE INCLUDE CURRENT CONTROLFILE TAG 'LV1-20170219-042105' SPFILE TAG 'SPFILE-20170219-042105' PLUS ARCHIVELOG TAG 'ARC-20170219-042105' DELETE INPUT; I have performed a restore and recover of the database using the above backupset. This is usually not the case in practice and only possible if you perform a full and incremental level backup at the same time and provided there are no changes to the database files. So just want to double check a couple of things. If you lose any datafile(s) (one or more) you have to RESTORE and RECOVER the *whole* database. Why did you create a new topic for the same question? For incremental level 0 backup of testdb1, the client name is database.example.org, and the save set is called RMAN:\testdb1_INCREMENTAL. I've got a question. In the case of a cumulative level 1 backup the parent is always the level 0 backup.
I have found that the full backup size is large and the first level 1 incremental backup is very quick and the backup size is small. In this step, differential incremental backup is a level 1 backup, not level 0 backup. BTW, please note in NetWorker, there is a restriction: The client + save set name has to be unique. Day 2 - level 1 differential incremental backup - has parent level 0 from day 1 - it will backup only the blocks that were changed since the last backup which is a level 0 from day 1 --> parent is a level 0 backup, Day 3 - level 1 differential incremental backup - has parent level 1 from day 2 - it will backup only the blocks that were changed since the last backup which is the one from day 2 --> parent is a level 1 backup. If no level 1 is available, then RMAN copies all blocks changed since the base level 0 backup.
You can use RMAN to create incremental backups of datafiles, tablespaces, or the whole database. I had also tried EMC NetWorker: Full backup plus incremental level 1 backup. Also if you notice, during the recovery its restoring the files again from L1 and not actaully just applying the changes on the restored files. The company I'm working for has asked us to change the way we do our backups to comply with the way that they do backups. Hence, a full backup can not be part of an incremental level backup strategy. First of all, thanks for the replies, I do appreciate them. ------- -- -- - ----------- ------------------- ------- ------- ---------- ---. [Updated on: Thu, 25 October 2012 12:22] by Moderator. If I lose some or all of the Datafiles (and, possibly, even the Redo Log and Control Files) : I have to OPEN RESETLOGS because I must discard the Online Redo Logs as they are not consistent with what been restored (the Online Redo Logs, even if still present on disk, are in the "future" of the Recover and I do not have ArchiveLogs to bring the datafiles in sync). Q1. The earlier post do have the incremental key work, there's a couple of posts from weds that I typed rather then copy and pasted that don't have it.
Cumulative backups require more space and time than differential backups because they duplicate the work done by previous backups at the same level. Technically speaking according to the documentation: If you delete the level 0 backup, regardless of any level 1 backups that may still exist: It could also display "no level 0 found". Note the save set name is automatically generated. Let's see what the Oracle documentation has to say: In a differential level 1 backup, RMAN backs up all blocks that have changed since the most recent incremental backup at level 1 (cumulative or differential) or level 0. All other transactions (and SCN increments) since the Level-1 Backup are also lost. For the Level-1 Backup, the datafile Checkpoint SCN is higher than that had from the SQL Query because the SQL query was before the Backup was taken.
Could anyone further explain what is 'parent for a subsequent incremental backup'? Number 1, I'm not sure this can be done. This applies to RMAN backup, but not necessarily to RMAN restore and recovery. The method is the same whether an FRA is used or not. OK, Thanks, that might be it, this is my entire script, you can see that I'm NOT in mount state. Possible? I have performed a full backup and then level 1 incremental backup. Again, a incremental backup level 1 can be applied to a full or level 0 backup, depending on the SCN. The default method is the differential one since it is the fastest one to complete.
And then create one incremental backup, save set is RMAN:\testdb1_INCREMENTAL. Message was edited by: Patrick Dung
Considering the question of the OP: To my understanding and practical tests, incremental level 1 backups can be applied or restored to full or level 0 backups, but only a level 0 backup can be the base for subsequent incremental level 1 backups. The term parent refers to the level 0 backup. Q2. If the manual is correct, then the first incremental backup should be a level 0 backup? The Redo Logs get reset to Sequence#=1.
RMAN can use an incremental level 1 backup to recover the datafiles of a full backup, even without a previous level 0 restore, provided the SCN is appropriate. RMAN recovery applies incremental level 1 and archived and online redo logs as required in order to recover the database or datafiles to a consistent state. Dave, that works because line 14 of your script includes the keyword INCREMENTAL which was not in your earlier posts. You say this. Post (copy and paste) what you do and get as we did it (that is formatted), this is the only way to know. channel ORA_DISK_1: starting incremental datafile backup set restore, channel ORA_DISK_1: specifying datafile(s) to restore from backup set, destination for restore of datafile 00001: /u01/app/oracle/oradata/testdb1/system01.dbf, destination for restore of datafile 00002: /u01/app/oracle/oradata/testdb1/sysaux01.dbf, destination for restore of datafile 00003: /u01/app/oracle/oradata/testdb1/undotbs01.dbf, destination for restore of datafile 00004: /u01/app/oracle/oradata/testdb1/project0_tbs01.dbf, destination for restore of datafile 00005: /u01/app/oracle/oradata/testdb1/users01.dbf, channel ORA_DISK_1: reading from backup piece /u01/app/oracle/fast_recovery_area/TESTDB1/backupset/2017_02_19/o1_mf_nnnd1_LV1_20170219_042105_dbkc5mph_.bkp, channel ORA_DISK_1: piece handle=/u01/app/oracle/fast_recovery_area/TESTDB1/backupset/2017_02_19/o1_mf_nnnd1_LV1_20170219_042105_dbkc5mph_.bkp tag=LV1-20170219-042105, channel ORA_DISK_1: restored backup piece 1, channel ORA_DISK_1: restore complete, elapsed time: 00:00:01, media recovery complete, elapsed time: 00:00:01. In a cumulative level 1 backup, RMAN backs up all blocks used since the most recent level 0 incremental backup in either the current or parent incarnation.
This shows the Level-0 and Level-1 backps (I am listing for only 1 datafile).
I'll modify and let you know, thanks again. RMAN restore means to restore the datafiles, which can be a full backup, image copy or incremental level 0 backup. They want us to take the archivelog backups separately, and to do incremental backups (level 1 and level 0 (on Sunday)), additionally the backups are going across the network to a UNC address. Differential level 1 take less time to complete but it will take longer to restore if there are many, Cumulative level 1 take more time to complete but it will take less time to restore.
Day 2 - level 1 cumulative incremental backup - has parent level 0 from day 1 - it will backup only the blocks that were changed since the last backup which is a level 0 from day 1 --> parent is a level 0, Day 3 - level 1 cumulative incremental backup - has parent level 0 from day 1 - it will backup only the blocks that were changed since the last backup which is a level 0 from day 1 --> parent is a level 0. Can you take an incremental backup level 1 or level 0 WITHOUT archivelogs? But you cannot create an incremental level 1 backup without a previous incremental level 0 backup. Yes, you can but your database must be closed (that is in mount state). A full backup cannot be part of an incremental backup strategy; that is, it cannot be the parent for a subsequent incremental backup. Can you also give the alert log for this duration of restore ? Perhaps because using "parent" in the context was misleading. In contrast to a full backup, an incremental backup copies only those data blocks that have changed since a previous backup.
I'm being asked to create backups in this manner: I created a new thread, asking whether it's possible to do an incremental backup without including the archive logs. The fact that you do not specify the type of the level 1 incremental backup can lead to confusion. A full backup cannot be used in place of a incremental level 0 backup, and if you perform a level 1 backup without any parent level 0, RMAN will automatically perform a level 0 backup instead. Applications and Infrastructure Community, backup and restore by rman backupset.txt.zip, alert log for restoring db by backupset.txt.zip, alert log for restoring db by emc networker.txt.zip.
So, it would be a good idea to make frequent Incremental Level-1 backups as they could be faster (shorter duration) than the Level-0 backups (which could be scheduled during longer maintenance weekend hours). The next backup is a differential incremental backup. This blog is being aggregated by orafaq.com, Oracle Database Certified Professional 12c. Configuring Transparent Data Encryption -- 2 : My Posts on Standby Database[s] -- Data Guard, Download Oracle Virtual Box / Vagrant / Docker Images, Optimizer Environment Parameters (by Jonathan Lewis), "Bits and Pieces" -- Links by Jonathan Lewis, SQL Statement Performance Diagnosis (by Randolf Geist), Enabling and Reading Oracle Traces (by Gints Plivna), Patching most of my environments with the July 2022 Bundle Patches, New Parallel Distribution Method For Direct Path Loads, Costing Concatenated Indexes With Range Scan Predicates Part I (Nothing To Be Desired). Hope that it is clear now.
I do know rman and have always used backup as compressed backupset database plus archivelog delete input.
Rman incremental without including archive logs?? It works for me (truncating the end of long lines): Dave, I don't understand what is going on. My GitHub site -- Presentations and some code, YouTube Videos for beginners to Oracle and SQL Server. If your RMAN list backup output only shows Full and level 1 backup, then the level 0 backup must have been deleted. Cumulative incremental backups reduce the work needed for a restore operation by ensuring that you only need one incremental backup from any particular level.
I use the table "HEMANT.MY_TEST_TABLE" as the reference table at this point.
My mistake, forgive me. Please post also the output of below command: Please show the part in RMAN Backup Concepts - 11g Release 2 (11.2) that outlines that a parent backup can either be level 0 or level 1. The 10g documentation outlined the following: It seems the RMAN concepts guide for 11g was re-written and does not use the term "parent incremental backup" anymore. Great and helpful post! Is restoring the controlfile required in this case, or would using the current controlfile also work?
If you read carefully I did not say that a full backup can be a parent to a level 1 backup - I said that a level 1 can be a parent for another level 1. Then restore.
As said in previous posts you can not use a full backup to take a level 1 backup no matter what type. Since the last backup resulted in level 0, do a level 1 backup now: See what we have (controlfile autoback is off): Based on the above your assessment is wrong. I don't know, I thought it was a new topic, but it really wasn't. In NetWorker, it would complain it is duplicated object and refuse to add the later one. The restore would use the full backup and the recover would use the incremental backup. The database is unavailable (as it is not OPEN) for the duration of the BACKUP DATABASE run. Oracle does support all Incremental (as well as Full) Backups of Databases running in NOARCHIVELOG mode. Note : It does not matter that I don't use an FRA. Thanks for the merge. Similarly, the Restored database has a higher SCN because the act of Restore+Recover+Open also increments the Database SCN. 2. Try to create another incremental level 1 backup and it should automatically create a level 0 instead. For example, in a differential level 1 backup, RMAN determines which level 1 backup occurred most recently and backs up all blocks modified after that backup. You can also refer to my first post and attachment for the actual command and output. How to use [code] tags and make your code easier to read. Please note that this site uses cookies.
2. The highest Log Sequence# is 865 (the CURRENT Redo Log file) and the SCN is 864084. I am an Oracle Database Specialist in Singapore. The behavior is the same, the restore would use the full backup and the recover would use the incremental backup. So I had to create one full backup, save set is: RMAN:\testdb1_FULL.
Anonymous,Anonymous,See my follow up post https://hemantoracledba.blogspot.com/2021/02/restore-and-recover-noarchivelog.htmlRMAN won't allow an OPEN RESETLOGS if you don't restore the older Controlfile (backup).But you can fallback to the SQL commands using sqlplus as I show in the new post. RESTORE and RECOVER a NOARCHIVELOG Database, with Datapump in Oracle ADB using SQL Developer Web. You cannot restore and recover individual datafiles for a database in NOARCHIVELOG mode as you would be able to do with backups with ArchiveLogs. Such backups can be made when the database is in MOUNT (not OPEN) mode.
The UNC address hasn't given me any problems. So I think it is actually make use of the previous full backup. To specify: I recommended him to put the database in mount mode during the backup if he want to have a consistent and recoverable backup after the incremental without archived logs. The parent does not necessary needs to be a level 0 backup it can be a level 1 backup as well in case of a differential level 1 backup. In order to perform an incremental level 1 backup, a prior level 0 backup is required. There are 2 "downsides" to Backups in NOARCHIVELOG mode : 1. FYI, the full backup is performed by this command: BACKUP AS COMPRESSED BACKUPSET FULL DATABASE INCLUDE CURRENT CONTROLFILE TAG 'FULL-20170219-042008' SPFILE TAG 'SPFILE-20170219-042008' PLUS ARCHIVELOG TAG 'ARC-20170219-042008' DELETE INPUT; The incremental backup is performed by this command: BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 1 DATABASE INCLUDE CURRENT CONTROLFILE TAG 'LV1-20170219-042105' SPFILE TAG 'SPFILE-20170219-042105' PLUS ARCHIVELOG TAG 'ARC-20170219-042105' DELETE INPUT; I have performed a restore and recover of the database using the above backupset. This is usually not the case in practice and only possible if you perform a full and incremental level backup at the same time and provided there are no changes to the database files. So just want to double check a couple of things. If you lose any datafile(s) (one or more) you have to RESTORE and RECOVER the *whole* database. Why did you create a new topic for the same question? For incremental level 0 backup of testdb1, the client name is database.example.org, and the save set is called RMAN:\testdb1_INCREMENTAL. I've got a question. In the case of a cumulative level 1 backup the parent is always the level 0 backup. I have found that the full backup size is large and the first level 1 incremental backup is very quick and the backup size is small. In this step, differential incremental backup is a level 1 backup, not level 0 backup. BTW, please note in NetWorker, there is a restriction: The client + save set name has to be unique. Day 2 - level 1 differential incremental backup - has parent level 0 from day 1 - it will backup only the blocks that were changed since the last backup which is a level 0 from day 1 --> parent is a level 0 backup, Day 3 - level 1 differential incremental backup - has parent level 1 from day 2 - it will backup only the blocks that were changed since the last backup which is the one from day 2 --> parent is a level 1 backup. If no level 1 is available, then RMAN copies all blocks changed since the base level 0 backup.
You can use RMAN to create incremental backups of datafiles, tablespaces, or the whole database. I had also tried EMC NetWorker: Full backup plus incremental level 1 backup. Also if you notice, during the recovery its restoring the files again from L1 and not actaully just applying the changes on the restored files. The company I'm working for has asked us to change the way we do our backups to comply with the way that they do backups. Hence, a full backup can not be part of an incremental level backup strategy. First of all, thanks for the replies, I do appreciate them. ------- -- -- - ----------- ------------------- ------- ------- ---------- ---. [Updated on: Thu, 25 October 2012 12:22] by Moderator. If I lose some or all of the Datafiles (and, possibly, even the Redo Log and Control Files) : I have to OPEN RESETLOGS because I must discard the Online Redo Logs as they are not consistent with what been restored (the Online Redo Logs, even if still present on disk, are in the "future" of the Recover and I do not have ArchiveLogs to bring the datafiles in sync). Q1. The earlier post do have the incremental key work, there's a couple of posts from weds that I typed rather then copy and pasted that don't have it.
Cumulative backups require more space and time than differential backups because they duplicate the work done by previous backups at the same level. Technically speaking according to the documentation: If you delete the level 0 backup, regardless of any level 1 backups that may still exist: It could also display "no level 0 found". Note the save set name is automatically generated. Let's see what the Oracle documentation has to say: In a differential level 1 backup, RMAN backs up all blocks that have changed since the most recent incremental backup at level 1 (cumulative or differential) or level 0. All other transactions (and SCN increments) since the Level-1 Backup are also lost. For the Level-1 Backup, the datafile Checkpoint SCN is higher than that had from the SQL Query because the SQL query was before the Backup was taken.
Could anyone further explain what is 'parent for a subsequent incremental backup'? Number 1, I'm not sure this can be done. This applies to RMAN backup, but not necessarily to RMAN restore and recovery. The method is the same whether an FRA is used or not. OK, Thanks, that might be it, this is my entire script, you can see that I'm NOT in mount state. Possible? I have performed a full backup and then level 1 incremental backup. Again, a incremental backup level 1 can be applied to a full or level 0 backup, depending on the SCN. The default method is the differential one since it is the fastest one to complete.
And then create one incremental backup, save set is RMAN:\testdb1_INCREMENTAL. Message was edited by: Patrick Dung
Considering the question of the OP: To my understanding and practical tests, incremental level 1 backups can be applied or restored to full or level 0 backups, but only a level 0 backup can be the base for subsequent incremental level 1 backups. The term parent refers to the level 0 backup. Q2. If the manual is correct, then the first incremental backup should be a level 0 backup? The Redo Logs get reset to Sequence#=1.
RMAN can use an incremental level 1 backup to recover the datafiles of a full backup, even without a previous level 0 restore, provided the SCN is appropriate. RMAN recovery applies incremental level 1 and archived and online redo logs as required in order to recover the database or datafiles to a consistent state. Dave, that works because line 14 of your script includes the keyword INCREMENTAL which was not in your earlier posts. You say this. Post (copy and paste) what you do and get as we did it (that is formatted), this is the only way to know. channel ORA_DISK_1: starting incremental datafile backup set restore, channel ORA_DISK_1: specifying datafile(s) to restore from backup set, destination for restore of datafile 00001: /u01/app/oracle/oradata/testdb1/system01.dbf, destination for restore of datafile 00002: /u01/app/oracle/oradata/testdb1/sysaux01.dbf, destination for restore of datafile 00003: /u01/app/oracle/oradata/testdb1/undotbs01.dbf, destination for restore of datafile 00004: /u01/app/oracle/oradata/testdb1/project0_tbs01.dbf, destination for restore of datafile 00005: /u01/app/oracle/oradata/testdb1/users01.dbf, channel ORA_DISK_1: reading from backup piece /u01/app/oracle/fast_recovery_area/TESTDB1/backupset/2017_02_19/o1_mf_nnnd1_LV1_20170219_042105_dbkc5mph_.bkp, channel ORA_DISK_1: piece handle=/u01/app/oracle/fast_recovery_area/TESTDB1/backupset/2017_02_19/o1_mf_nnnd1_LV1_20170219_042105_dbkc5mph_.bkp tag=LV1-20170219-042105, channel ORA_DISK_1: restored backup piece 1, channel ORA_DISK_1: restore complete, elapsed time: 00:00:01, media recovery complete, elapsed time: 00:00:01. In a cumulative level 1 backup, RMAN backs up all blocks used since the most recent level 0 incremental backup in either the current or parent incarnation.
This shows the Level-0 and Level-1 backps (I am listing for only 1 datafile).
I'll modify and let you know, thanks again. RMAN restore means to restore the datafiles, which can be a full backup, image copy or incremental level 0 backup. They want us to take the archivelog backups separately, and to do incremental backups (level 1 and level 0 (on Sunday)), additionally the backups are going across the network to a UNC address. Differential level 1 take less time to complete but it will take longer to restore if there are many, Cumulative level 1 take more time to complete but it will take less time to restore.
Day 2 - level 1 cumulative incremental backup - has parent level 0 from day 1 - it will backup only the blocks that were changed since the last backup which is a level 0 from day 1 --> parent is a level 0, Day 3 - level 1 cumulative incremental backup - has parent level 0 from day 1 - it will backup only the blocks that were changed since the last backup which is a level 0 from day 1 --> parent is a level 0. Can you take an incremental backup level 1 or level 0 WITHOUT archivelogs? But you cannot create an incremental level 1 backup without a previous incremental level 0 backup. Yes, you can but your database must be closed (that is in mount state). A full backup cannot be part of an incremental backup strategy; that is, it cannot be the parent for a subsequent incremental backup. Can you also give the alert log for this duration of restore ? Perhaps because using "parent" in the context was misleading. In contrast to a full backup, an incremental backup copies only those data blocks that have changed since a previous backup.
I'm being asked to create backups in this manner: I created a new thread, asking whether it's possible to do an incremental backup without including the archive logs. The fact that you do not specify the type of the level 1 incremental backup can lead to confusion. A full backup cannot be used in place of a incremental level 0 backup, and if you perform a level 1 backup without any parent level 0, RMAN will automatically perform a level 0 backup instead. Applications and Infrastructure Community, backup and restore by rman backupset.txt.zip, alert log for restoring db by backupset.txt.zip, alert log for restoring db by emc networker.txt.zip.