backup incremental simplesave

HP SimpleSave backup software performs automatic incremental backups?

According to the manual page 1 ' backup automatically changes every time that the computer is idle for 5 minutes. This happens if the SS drive is attached and powered. Page 5 "If you unplug your HP SimpleSave drive, just plug it back in and run HP SimpleSave by clicking on the icon of the application HP SimpleSave.» The software automatically backs up all the changed files and new files since your last backup from your computer to your HP SimpleSave drive". http://www.HP.com/CTG/manual/c01824301.PDF

Tags: HP Desktops

Similar Questions

Backup incremental level 2,3,4 RMAN.

Hello guys,.
Can someone let me know what is the meaning / usage of incremental backup of level 2,3,4.
Kind regards.

Wikipedia can have an easy to understand the reason for several additional levels:

A backup of level 1 decision Monday would only include changes made since Sunday. A backup of level 2 decision Tuesday would only include changes made since Monday. A backup of level 3 Wednesday would only include changes made since Tuesday. If a level 2 backup taken Thursday, it would include all changes made since Monday because Monday was the most recent level n - 1 backup.

https://en.Wikipedia.org/wiki/Incremental_backup

What is RMAN?

The Oracle documentation refers only to additional 0 year 1. What I understand, RMAN never supported incremental backups multilevel at 3 levels (0-4). Apparently, people often had trouble understanding the logic for levels 3 and 4. RMAN provides the clause 'cascading', which also existed in 9i and is usually an easier to understand the backup strategy. RMAN also provides or has provided an option to perform incremental backups cumulative at level 1 or higher. For simplicity, the la documentation documentation since 10 g mentions only level 0 only a 1 an other levels is deprecated.

BACKUP INCREMENTIELLE from LEVEL 1 (differential by default, changes made since the last level 0 or 1)

BACKUP INCREMENTIELLE LEVEL 1 CUMULATIVE (changes since the last last level 0)

Below some info from http://docs.oracle.com/cd/E11882_01/backup.112/e10643/obs_comm.htm#RCMRF910

RMAN version 10.0.1: levels other than 0 and 1 are deprecated.

If you make an additional workforce 1 backup, incremental or cumulative, and there is no previous level 0, RMAN automatically performs an incremental backup of level 0. BTW, a full backup is identical to a level 0 incremental backup but excluded a strategy of backup incremental level.

Why the format does not work on my backup incremental level 1 the difference?

I use following script to make a backup of difference incremental level 1.
------------------------------
Run {}
allocate channels ch1 disc type;
Set order id "Monday_INC_1_df";
backup as compressed backupset database incremental level 1
format ' / opt/oracle/rman/bk/incr1_df_%d_%U'
tag "Monday_INC_1_df".
database more entered archivelog delete;
output channel ch1.
}
-------------------------------
According to this scenario, all the rman output files are placed in "/ opt/oracle/rman/bk / '... And his label is 'Monday_INC_1_df'.
But at the bottom of the newspaper, I find the archived log rman output files located in "/ opt/oracle/flash_recovery_area/TEST/backupset/2014_12_02 / '. And his label is "TAG20141202T210529".
Also, at the bottom of the newspaper, the output data files rman files was partly on the right path "/ opt/oracle/rman/bk / '. And it seems that the data files has been supported for 2 times. The second time datafile rman output files was badly located in the path "/ opt/oracle/flash_recovery_area/TEST/backupset/2014_12_02 / '. And his label is "TAG20141202T215627".

================================================ Detail Log ===================================================================================
channel ch1: compressed boot archived log backup set
channel ch1: specifying the newspapers archived in the backup set
archived journal entry thread = 1 sequence = 36706 RECID = 2773 STAMP = 865282473
archived journal entry thread = 1 sequence = 36707 RECID = 2774 STAMP = 865282476
archived journal entry thread = 1 sequence = 36708 RECID = 2775 STAMP = 865282478
archived journal entry thread = 1 sequence = 36709 RECID = 2776 STAMP = 865282482
archived journal thread = 1 sequence = 36710 entry RECID = STAMP 2777 = 865282486
archived journal entry thread = 1 sequence = 36711 RECID = 2778 STAMP = 865285528
channel ch1: starting piece 1 at 2014-12-02 21:56:20
channel ch1: finished piece 1 at 2014-12-02 21:56:27
piece handle=/opt/oracle/flash_recovery_area/TEST/backupset/2014_12_02/o1_mf_annnn_TAG20141202T210529_b7vk8408_.bkp tag = TAG20141202T210529 comment = NONE
channel ch1: complete set of backups, time: 00:00:07
channel ch1: archived deletion or newspapers
name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36706_b7vc98xc_.arc RECID archived log file = 2773 STAMP = 865282473
name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36707_b7vc9cz7_.arc RECID archived log file = 2774 STAMP = 865282476
name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36708_b7vc9gn1_.arc RECID archived log file = 2775 STAMP = 865282478
name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36709_b7vc9l3f_.arc RECID archived log file = 2776 STAMP = 865282482
RECID = STAMP 2777 = 865282486 name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36710_b7vc9plj_.arc archived log file
name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36711_b7vg8qz5_.arc RECID archived log file = 2778 STAMP = 865285528
A backup over the 2014-12-02 21:56:27

From backup 2014-12-02 21:56:27
channel ch1: from compressed data file backup set incremental level 1
channel ch1: specification-datafile in the backup set (s)
Enter a number of file datafile = name=/opt/oracle/oradata/test/undotbs01.dbf 00003
Enter a number of file datafile = 00005 name=/opt/oracle/oradata/test/hp01.dbf
Enter a number of file datafile = name=/opt/oracle/oradata/test/cmtspace01.dbf 00035
Enter a number of file datafile = name=/opt/oracle/oradata/test/sysaux01.dbf 00002
Enter a number of file datafile = 00001 name=/opt/oracle/oradata/test/system01.dbf
Enter a number of file datafile = name=/opt/oracle/oradata/test/users01.dbf 00004
channel ch1: starting piece 1 at 2014-12-02 21:56:28
channel ch1: finished piece 1 at 2014-12-02 23:48:06
piece handle tag = / opt/oracle/rman/bk/incr1_df_TEST_1gpp6gcc_1_1 MONDAY_INC_1_DF = comment = NONE
channel ch1: complete set of backups, time: 01:51:38
channel ch1: from compressed data file backup set incremental level 1
channel ch1: specification-datafile in the backup set (s)
Enter a number of file datafile = name=/opt/oracle/oradata/test/undotbs01.dbf 00003
Enter a number of file datafile = 00005 name=/opt/oracle/oradata/test/hp01.dbf
Enter a number of file datafile = name=/opt/oracle/oradata/test/cmtspace01.dbf 00035
Enter a number of file datafile = name=/opt/oracle/oradata/test/sysaux01.dbf 00002
Enter a number of file datafile = 00001 name=/opt/oracle/oradata/test/system01.dbf
Enter a number of file datafile = name=/opt/oracle/oradata/test/users01.dbf 00004
channel ch1: starting piece 1 at 2014-12-02 23:48:07
channel ch1: finished piece 1 at 2014-12-03 01:17:22
piece handle=/opt/oracle/flash_recovery_area/TEST/backupset/2014_12_02/o1_mf_nnnd1_TAG20141202T215627_b7vqsq8y_.bkp tag = TAG20141202T215627 comment = NONE
channel ch1: complete set of backups, time: 01:29:15
A backup over the 2014-12-03 01:17:22
From backup 2014-12-03 01:17:23
Current archived log
channel ch1: compressed boot archived log backup set
channel ch1: specifying the newspapers archived in the backup set
archived journal entry thread = 1 sequence = 36712 RECID = 2779 STAMP = 865288890
archived journal entry thread = 1 sequence = 36713 RECID = 2780 STAMP = 865288965
archived journal entry thread = 1 sequence = 36714 RECID = 2781 STAMP = 865288971
channel ch1: starting piece 1 at 2014-12-03 01:17:24
channel ch1: finished piece 1 at 2014-12-03 01:17:49
piece handle=/opt/oracle/flash_recovery_area/TEST/backupset/2014_12_03/o1_mf_annnn_TAG20141203T011723_b7vx145d_.bkp tag = TAG20141203T011723 comment = NONE
channel ch1: complete set of backups, time: 00:00:25
channel ch1: archived deletion or newspapers
name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36712_b7vkkts7_.arc RECID archived log file = 2779 STAMP = 865288890
name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36713_b7vkn5v0_.arc RECID archived log file = 2780 STAMP = 865288965
name=/opt/oracle/flash_recovery_area/TEST/archivelog/2014_12_02/o1_mf_1_36714_b7vkncv2_.arc RECID archived log file = 2781 STAMP = 865288971
=============================================================================================================

When I here is the backup incremental level 0, everything seems good.
----------------------------------
Run {}
allocate channels ch1 disc type;
Set order id "Sunday_INC_0";
backup incremental level 0 compressed backupset
format ' / opt/oracle/rman/bk/incr0_%d_%U'
tag "Sunday_INC_0".
database more entered archivelog delete;
output channel ch1.
}
--------------------------------
But why my backup of difference in level 1 increntmental would not have good correct rman output path?

You have specified the keyword 'database' twice in the backup command. If execution is in the specified format, the second with the default format (to the FRA)

Hemant K Collette

backup incremental update feature
Hi all

can you explain this feafure when you take the copy of the image and then backup incremental and when
data file is corrupted I have to restore the copy of the data file, and then apply an incremental backup.
I do this planning, but I do not write the COPY OF THE file of DATA WITH TAG RECOVER command

I take a copy of the image and then make this table spaces and make sure is the default value for the data base and ten make change
DML, stop immediately and drop datafile can restore and recover
restore the data file 5
recover datafile 5

without any incremental update command, feature and now my database is up-to-date? can you explain to me an example please?

Thank you very much
We must use the control switch that will make the controlfile to point to the backup of the data on the disk files.
For example: you lost the data user 6 file

RMAN > switch datafile 6 to copy;
RMAN > recover datafile 6;
RMAN > alter database datafile 6 online;

The problem with incremental updates, is that, after any failure, as above, if restore us it, it will change the name and location of the data file. After restoration manual you rename them to original location.

In case of failure of the database

RMAN > switch database to copy.
RMAN > restore database;
RMAN > alter database open

Published by: renee_mathieu on August 5, 2012 07:54

RMAN backup incremental level 1 without level 0-10 gr 2

Hello

I'm a bit confused after a few tries.

The issue: It is mandatory to perform incremental level 0 backup before level 1 using Oracle 10 g 2?

On Oracle 11.2 is mandatory, but I don't know about Oracle 10.2.0.5.

11.2 test. If there is no level 0 rman take care on this subject and automatically perform level 0 before level1

RMAN> backup incremental level 1 database;

Starting backup at 29-APR-11
using channel ORA_DISK_1
no parent backup or copy of datafile 1 found
...
channel ORA_DISK_1: starting incremental level 0 datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
...

Docs said:
Incremental backups capture only blocks that change between backups in each data file.
In a typical incremental backup strategy, an incremental backup of level 0 is used as a starting point. A level 0 backup captures all the blocks in the data file.

So, on Oracle 10.2.0.5 happens not like 11.2:

Parade level 1 without level 0 backup:

RMAN> list backup;


RMAN> backup incremental level 1 database;

Starting backup at 29-APR-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting incremental level 1 datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=+DG_ORCL/db10g/datafile/system.260.749756975
...
channel ORA_DISK_1: starting piece 1 at 29-APR-11
channel ORA_DISK_1: finished piece 1 at 29-APR-11
piece handle=+DG_FRA/db10g/backupset/2011_04_29/nnndn1_tag20110429t190340_0.260.749761421 tag=TAG20110429T190340 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:25
channel ORA_DISK_1: starting incremental level 1 datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 29-APR-11
channel ORA_DISK_1: finished piece 1 at 29-APR-11
piece handle=+DG_FRA/db10g/backupset/2011_04_29/ncsnn1_tag20110429t190340_0.262.749761449 tag=TAG20110429T190340 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:05
Finished backup at 29-APR-11

RMAN> backup archivelog all delete input;

Starting backup at 29-APR-11
current log archived
using channel ORA_DISK_1
...
Finished backup at 29-APR-11

RMAN> shutdown abort;
Oracle instance shut down

Delete all (except SPFILE) ASM files.

ASMCMD> cd +DG_ORCL/DB10g
ASMCMD> ls
PARAMETERFILE/
spfiledb10g.ora

So we will perfom a database restore

oracle@butao:/home/oracle> rman target /
Recovery Manager: Release 10.2.0.5.0 - Production on Fri Apr 29 19:06:52 2011
Copyright (c) 1982, 2007, Oracle.  All rights reserved.
connected to target database (not started)
RMAN> startup nomount
Oracle instance started

Total System Global Area     293601280 bytes
Fixed Size                     2095872 bytes
Variable Size                 92275968 bytes
Database Buffers             192937984 bytes
Redo Buffers                   6291456 bytes


RMAN> restore controlfile from '+DG_FRA/db10g/backupset/2011_04_29/ncsnn1_tag20110429t190340_0.262.749761449';

Starting restore at 29-APR-11
using channel ORA_DISK_1

channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:05
output filename=+DG_ORCL/db10g/controlfile/current.263.749761699
output filename=+DG_FRA/db10g/controlfile/current.263.749761699
Finished restore at 29-APR-11

RMAN> startup mount

database is already started
database mounted
released channel: ORA_DISK_1

RMAN> restore database;

Starting restore at 29-APR-11
Starting implicit crosscheck backup at 29-APR-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 1 objects
Finished implicit crosscheck backup at 29-APR-11

Starting implicit crosscheck copy at 29-APR-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 29-APR-11

searching for all files in the recovery area
cataloging files...
cataloging done

List of Cataloged Files
=======================
File Name: +dg_fra/DB10G/BACKUPSET/2011_04_29/ncsnn1_TAG20110429T190340_0.262.749761449
File Name: +dg_fra/DB10G/BACKUPSET/2011_04_29/annnf0_TAG20110429T190442_0.264.749761485

using channel ORA_DISK_1

channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to +DG_ORCL/db10g/datafile/system.260.749756975
restoring datafile 00002 to +DG_ORCL/db10g/datafile/undotbs1.261.749757085
restoring datafile 00003 to +DG_ORCL/db10g/datafile/sysaux.262.749757095
restoring datafile 00004 to +DG_ORCL/db10g/datafile/users.264.749757107
channel ORA_DISK_1: reading from backup piece +DG_FRA/db10g/backupset/2011_04_29/nnndn1_tag20110429t190340_0.260.749761421
channel ORA_DISK_1: restored backup piece 1
piece handle=+DG_FRA/db10g/backupset/2011_04_29/nnndn1_tag20110429t190340_0.260.749761421 tag=TAG20110429T190340
channel ORA_DISK_1: restore complete, elapsed time: 00:00:26
Finished restore at 29-APR-11

RMAN> recover database;

Starting recover at 29-APR-11
using channel ORA_DISK_1

starting media recovery

archive log thread 1 sequence 27 is already on disk as file +DG_FRA/db10g/onlinelog/group_3.259.749756971
archive log thread 1 sequence 28 is already on disk as file +DG_FRA/db10g/onlinelog/group_1.257.749756963
archive log filename=+DG_FRA/db10g/onlinelog/group_3.259.749756971 thread=1 sequence=27
archive log filename=+DG_FRA/db10g/onlinelog/group_1.257.749756963 thread=1 sequence=28
media recovery complete, elapsed time: 00:00:02
Finished recover at 29-APR-11

RMAN> alter database open resetlogs;

database opened

RMAN>

See that I don't need level 0 backup to restore the level 1.

Thank you
Levi Pereira

Levi,

Please visit: http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm

If no level 0 backup is available, then the behavior depends on the setting of compatibility mode. If compatibility is > = 10.0.0, copies all blocks changed since the file was created RMAN and stores the results as a level 1 backup. In other words, the CPN at the time the incremental backup is taken is the creation of SCN file. If compatibility<10.0.0, rman="" generates="" a="" level="" 0="" backup="" of="" the="" file="" contents="" at="" the="" time="" of="" the="" backup,="" to="" be="" consistent="" with="" the="" behavior="" in="" previous="">

Same info is here:

http://www.Pythian.com/news/287/level-1-incremental-backup-in-Oracle-10G/

Concerning

Grosbois

RMAN LEVEL BACKUP INCREMENTAL 0 AND 1 OF CUMULATIVE LEVEL

Dear friends
This is Eliza, I need some clarification, your suggestion will help me more...
Currently I am working in RMAN backup and restore, recovery and I need to take the extra SIZE 0 AND LEVEL 1 CUMULATIVE
I know something about what level rman incremental 0 and level 1 cumulative can do is, first I have to take the level 0 and then level 1 respectively.
As follows
SUNDAY: LEVEL 0 CUMULATIVE
MONDAY - SATURDAY: LEVEL 1 CUMULATIVE
SUNDAY: LEVEL 0 CUMULATIVE (repetition of this cycle)
MY QUESTION IS
Can I use after an order to take INCREMENTIELLE LEVEL 1 CUMULATIVE backup of,
CUMULATIVE DATABASE INCREMENTAL LEVEL 1; # has changed since the level 0 blocks
But, if I want to take CUMULATIVE INCREMENTAL level 0 BACKUP, that is me I want to use the following,
INCREMENTAL LEVEL 0 BACKUP CUMULATIVE BASIS;
(GOLD)
DATABASE INCREMENTAL LEVEL 0 BACKUP;
(GOLD)
Suggest me your valuable idea. Thanks in advance.

Hello

I think that this CUMULATIVE or incremental level 0 backup specification makes no sense so INCREMENTAL level 0 BACKUP database; = INCREMENTAL CUMULATIVE 0 DATA LEVEL;

Customized backup (incremental) Oracle with database control

Hi all
I m running on windows server 2008R2 oracle 11 g R2.
I want to schedule a backup customized with control of the database to plan my backups. (This is the second option of the database-> scheduled backup control)
I want to have a window of 7 days recovery.
I'm a little shaky on how to plan properly.
I need to schedule backup complete everything first (by checking the option use as a base for incremental backups). (This should go once)
Then schedule incremental backup every day after that?
Could someone explain how to set up the right then that I would have a window of 7 days recovery?
Thank you.

Hemant thanks for your explanation on L0 backup.

So I go ahead and schedule backup complete once a week! I understand that part. (let's say I plan backup complete Sunday night)

What about backups of L1?

Should I plan Monday to Saturday sound? Or can I include it on Sunday as well?

The reason I ask is, I don't know if the Manager of the company will allow me to schedule backups every day (except a certain day) m.

I will give this a shot!

Thank you!!

When the RMAN brand is backup incremental level1 obsolete?
Hi all

On a server Oracle 10.2.0.2 particular (with ODG), I implemented a strategy of incremental backup. A level 0 backup is available and all level 1 next backups are getting recovered to this first copy of data file. So far so good.

The problem is that all these incremental backups at level 1 stay in my box of flashback and are not cleaned by RMAN. The retention policy is set on a window of 1 day.

When the RMAN will start scoring these backups to level 1 as being obsolete? I guess that these backups are obsolete right after that they were applied to the copy of the data file? This has something to do with the size of the parameter area flashback, which means that it will not begin to remove level 1 backups when RMAN runs into problems of free space on the disk?

Any help is appreciated!

JM
Hi JM,

This is expected behavior, because you have changed the default retention of redundancy strategy 1.
You can find this on My Oracle Support note + incremental backup strategies: Merge [ID 745798.1] +.

The extract of this says:
>
When using Oracle-Suggested policy or a daily incremental backup merged and using a Flash recovery area and then keep the retention policy of RMAN for redundancy 1. This will ensure that the Oracle space management will automatically remove incremental backups at level 1 of the FRA after they have been applied to the image based on the pressure of space in the FRA copy. If you increase the redundancy or set a window of recovery space is is automatically retrieved by Oracle. This works only when the retention policy is set to the default value of redundancy = 1. If the configured retention policy is set to the window of recovery or > 1 redundancy, RMAN cannot satisfy the retention policy if there is only one copy of database and it's at a later point in time. Thus, in order to satisfy political retention Oracle keeps all the incremental backups and archivelogs since the creation of the database because ideally a data file can be re-created and archivelogs can be applied to meet the retention policy (although not followed in the practical case).
>

To have made them obsolete automatically, you must add the 'UNTIL TIME 'SYSDATE-2' ' clause to the COPY of RECOVER sentence, for a 1-day recovery window.

The order having to RETRIEVE it after the BACKUP, you will have the current copy image, and you should only apply the archivelogs if you need to recover instead of use the last day of Level0 backup now level1.

Kind regards.
Nelson

Block Media Recovery and RMAN backup incremental level 1
Hello

I read somewhere that block Media Recovery will not work if a database is backed up with 1 incremental rman. Is this true and if so is there a work around?
I can't find it in the documentation of oralce.

Concerning
Me
Hello

Yes you are right, for the recovery block media, you must have full rman backup. Incremental backups are not used by block
media recovery. Only full backups and archived logs are used.

See this doc on part III

http://download-UK.Oracle.com/docs/CD/B19306_01/backup.102/b14191/TOC.htm

concerning

Jafar

Published by: jerome on October 22, 2008 19:51

Roll forward standby database with the incremental backup, when a data file is deleted in primary education

Hello
I'm nologging operations + deleting some files in the primary and you want to roll forward the day before using the incremental backup Yvert.
I do in particular, as the files are dropped?
I got to meet ( Doc ID 1531031.1 ) which explains how to roll forward when a data file is added.
If I follow the same steps, to make the move to restore the data file newly added, will it work in my case?
Can someone please clarify?
Thank you
San

I was wondering if reocover noredo is performed before restored controlfile, oracle will apply the incremental backup error-free files, and in this case, what would be the status of the data file in the control file.

Why do you consider to retrieve the day before first and then in the restaurant of the controlfile will lead to problems. Please read my first post on this thread - I had clearly mentioned that you would not face problems if you go with the method of deployment.

Here is a demo for you with force logging is disabled. For the first time the day before resuming and restored then the controlfile ensures:

Primary: oraprim

Standby: orastb

Tablespace DataFile of MYTS is removed on primary:

SYS @ oraprim > select force_logging in the database of v$.

FORCE_LOGGING

---------------------------------------

NO.

Currently the tablespace is to have 2 data files.

SYS @ oraprim > select file_name in dba_data_files where nom_tablespace = 'MYTS;

FILE_NAME

-------------------------------------------------------

/U01/app/Oracle/oradata/oraprim/myts01.dbf

/U01/app/Oracle/oradata/oraprim/myts02.dbf

In standby mode, the tablespace is to have 2 data files:

SYS @ orastb > select name from v$ datafile where ts #= 6;

NAME

--------------------------------------------------------------------------------

/U01/app/Oracle/oradata/orastb/myts01.dbf

/U01/app/Oracle/oradata/orastb/myts02.dbf

Postponement of the day before on the primary log shipping

SYS @ oraprim > alter system set log_archive_dest_state_3 = delay;

Modified system.

Dropped 1 MYTS datafile on the primary.

SYS @ oraprim > alter tablespace myts drop datafile ' / u01/app/oracle/oradata/oraprim/myts02.dbf';

Tablespace altered.

Removed some archives to create a space.

[oracle@ora12c-1 2016_01_05] $ rm - rf * 31 *.

[oracle@ora12c-1 2016_01_05] $ ls - lrt

13696 total

-rw - r - 1 oracle oinstall 10534400 5 January 18:46 o1_mf_1_302_c8qjl3t7_.arc

-rw - r - 1 oracle oinstall 2714624 5 January 18:47 o1_mf_1_303_c8qjmhpq_.arc

-rw - r - 1 oracle oinstall 526336 5 January 18:49 o1_mf_1_304_c8qjp7sb_.arc

-rw - r - 1 oracle oinstall 23552 5 January 18:49 o1_mf_1_305_c8qjpsmh_.arc

-rw - r - 1 oracle oinstall 53760 5 January 18:50 o1_mf_1_306_c8qjsfqo_.arc

-rw - r - 1 oracle oinstall 14336 Jan 5 18:51 o1_mf_1_307_c8qjt9rh_.arc

-rw - r - 1 oracle oinstall 1024 5 January 18:53 o1_mf_1_309_c8qjxt4z_.arc

-rw - r - 1 oracle oinstall 110592 5 January 18:53 o1_mf_1_308_c8qjxt34_.arc

[oracle@ora12c-1 2016_01_05] $

Current main MYTS data files:

SYS @ oraprim > select file_name in dba_data_files where nom_tablespace = 'MYTS;

FILE_NAME

-------------------------------------------------------

/U01/app/Oracle/oradata/oraprim/myts01.dbf

Current data of MYTS standby files:

SYS @ orastb > select name from v$ datafile where ts #= 6;

NAME

--------------------------------------------------------------------------------

/U01/app/Oracle/oradata/orastb/myts01.dbf

/U01/app/Oracle/oradata/orastb/myts02.dbf

Gap is created:

SYS @ orastb > select the process, status, sequence # v$ managed_standby;

STATUS OF PROCESS SEQUENCE #.

--------- ------------ ----------

ARCH. CLOSING 319

ARCH. CLOSING 311

CONNECTED ARCH 0

ARCH. CLOSING 310

MRP0 WAIT_FOR_GAP 312

RFS IDLE 0

RFS IDLE 0

RFS IDLE 0

RFS IDLE 320

9 selected lines.

Backup incremental RMAN is taken elementary school.

RMAN > incremental backup of the format of database of SNA 2686263 ' / u02/bkp/%d_inc_%U.bak';

From backup 5 January 16

using the control file of the target instead of recovery catalog database

the DISC 2 channel configuration is ignored

the DISC 3 channel configuration is ignored

configuration for DISK 4 channel is ignored

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID = 41 type device = DISK

channel ORA_DISK_1: starting full datafile from backup set

channel ORA_DISK_1: specifying datafile (s) in the backup set

Enter a number of file datafile = 00001 name=/u01/app/oracle/oradata/oraprim/system01.dbf

Enter a number of file datafile = name=/u01/app/oracle/oradata/oraprim/sysaux01.dbf 00003

Enter a number of file datafile = name=/u01/app/oracle/oradata/oraprim/undotbs01.dbf 00004

Enter a number of file datafile = name=/u01/app/oracle/oradata/oraprim/users01.dbf 00006

Enter a number of file datafile = name=/u01/app/oracle/oradata/oraprim/myts01.dbf 00057

channel ORA_DISK_1: starting total, 1-January 5, 16

channel ORA_DISK_1: finished piece 1-January 5, 16

piece handle=/u02/bkp/ORAPRIM_inc_42qqkmaq_1_1.bak tag = TAG20160105T190016 comment = NONE

channel ORA_DISK_1: complete set of backups, time: 00:00:02

Backup finished on 5 January 16

Saved controlfile on primary:

RMAN > backup current controlfile to Eve format ' / u02/bkp/ctl.ctl';

Cancel recovery in standby mode:

SYS @ orastb > alter database recover managed standby database cancel;

Database altered.

Recover the day before by using the above backup items

RMAN > recover database noredo;

From pick up to 5 January 16

the DISC 2 channel configuration is ignored

the DISC 3 channel configuration is ignored

configuration for DISK 4 channel is ignored

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID = 26 type of device = DISK

channel ORA_DISK_1: from additional data file from the restore backup set

channel ORA_DISK_1: specifying datafile (s) to restore from backup set

destination for the restoration of the data file 00001: /u01/app/oracle/oradata/orastb/system01.dbf

destination for the restoration of the data file 00003: /u01/app/oracle/oradata/orastb/sysaux01.dbf

destination for the restoration of the data file 00004: /u01/app/oracle/oradata/orastb/undotbs01.dbf

destination for the restoration of the data file 00006: /u01/app/oracle/oradata/orastb/users01.dbf

destination for the restoration of the data file 00057: /u01/app/oracle/oradata/orastb/myts01.dbf

channel ORA_DISK_1: backup /u02/bkp/ORAPRIM_inc_3uqqkma0_1_1.bak piece reading

channel ORA_DISK_1: room handle=/u02/bkp/ORAPRIM_inc_3uqqkma0_1_1.bak tag = TAG20160105T190016

channel ORA_DISK_1: restored the backup part 1

channel ORA_DISK_1: restore complete, duration: 00:00:01

Finished recover to 5 January 16

Restored the controlfile and mounted the day before:

RMAN > shutdown immediate

dismounted database

Instance Oracle to close

RMAN > startup nomount

connected to the database target (not started)

Oracle instance started

Total System Global Area 939495424 bytes

Bytes of size 2295080 fixed

348130008 variable size bytes

583008256 of database buffers bytes

Redo buffers 6062080 bytes

RMAN > restore controlfile eve of ' / u02/ctl.ctl ';

From 5 January 16 restore

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID = 20 type of device = DISK

channel ORA_DISK_1: restore the control file

channel ORA_DISK_1: restore complete, duration: 00:00:01

output file name=/u01/app/oracle/oradata/orastb/control01.ctl

output file name=/u01/app/oracle/fast_recovery_area/orastb/control02.ctl

Finished restore at 5 January 16

RMAN > change the editing of the database;

Statement processed

output channel: ORA_DISK_1

Now the data file does not exist on the standby mode:

SYS @ orastb > alter database recover managed standby database disconnect;

Database altered.

SYS @ orastb > select the process, status, sequence # v$ managed_standby;

STATUS OF PROCESS SEQUENCE #.

--------- ------------ ----------

CONNECTED ARCH 0

CONNECTED ARCH 0

CONNECTED ARCH 0

ARCH. CLOSING 329

RFS IDLE 0

RFS IDLE 330

RFS IDLE 0

MRP0 APPLYING_LOG 330

8 selected lines.

SYS @ orastb > select name from v$ datafile where ts #= 6;

NAME

--------------------------------------------------------------------------------

/U01/app/Oracle/oradata/orastb/myts01.dbf

Hope that gives you a clear picture. You can use this to roll forward day before using the SNA roll forward Eve physical database using RMAN incremental backup | Shivananda Rao

-Jonathan Rolland

Incremental backup policy

Hi experts,
In my organization, we have 4 TB size of database. If we take a complete backup of it, will it take huge time. While we do intend to follow an incremental backup of this jet of RMAN database, my question is, what kind of policy of incremental backup, we follow. I am new to an incremental backup. Yet, I was followed political only full backup.
(1) we must / should follow political not backup incremental cumulative GOLD diffrential.
(2) who is stupid or why (cumulative backup incremental GOLD diffrential)
(3) how to track level in both cases...
as = > Sunday M T W T F S Sunday
0 2 2 1 2 2 2 0
Reg,
Thomas

I would prefer cumulative incremental but if the daily a cumulative incremental size is large, you could make an additional bonus. The disadvantages of additional premium are

(a) If you lose an additional intermediate differential, you cannot restore the database past the point (unless you have backups, archivelog separated through all database backups)

(b) it may take more time to restore and recover using additional bonus you would need to restore and apply backups more

See http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmcncpt.htm#BRADV109

Note: Level 2 is is more documented. Level 2 backups are actually incremental differential.

Hemant K Collette

Incremental backup

Hello
I have a problem with incremental backups RMAN level 1 "too big (50-75% of the total DB dimensions, including the archive logs).
Attempted to change the cumulative incr to differential backups to limit the data to back up.
So, I would like to confirm that I actually run differential backups and not be combined during the days of the week.
Anyone have a query which can check the type of backup that I used?
It s an OLTP database running Oracle 11.2.
Sorry for not adding the view all and everything but I m at home after working hours, try to understand this.
See you soon

Hello

User RMAN must use a name in the 'format' or 'tag' option or two to show

type of backup was made. For example:

database backup incremental level 0 format 'c:\temp\diff_incr_zero_%U.bak ';

or

database backup incremental level 0 tag diff_incr_zero;

Without the tag, or format clauses specifying the type of backup performed.

It is not possible to use the RMAN list or any point of view RMAN command to determine

the difference of these two types of backups.

Thank you

Differential incremental backup for RAC

I inherited a CAR of two nodes (11r2 on RHEL 5.8 tikanga) with a shared network directory to be used as a backup location. He is the current backup strategy.

RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name TESTdb are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;  # default
CONFIGURE BACKUP OPTIMIZATION OFF;  # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK;  # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF;  # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';  # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;  # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;  # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;  # default
CONFIGURE MAXSETSIZE TO UNLIMITED;  # default
CONFIGURE ENCRYPTION FOR DATABASE OFF;  # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128';  # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;  # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;  # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_testdb1.f';  # default

The above is for the node 1, node 2 is identical except for line 17 (he refers to the "_testdb2.f").

The backup script is below.

run
{
recovery copy of database with tag 'ORA_OEM_LVL0_TESTdb_PRIM' until time 'SYSDATE-7';
backup check logical incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA_OEM_LVL0_TESTdb_PRIM' database;
backup check logical archivelog all tag 'ORA_OEM_ARCH_TESTdb_PRIM';
}
allocate channel for maintenance device disk type;
crosscheck backupset;
crosscheck archivelog all;
delete noprompt obsolete device type disk;

I'm a relatively new DBA, but I think that the strategy above maybe even does not work like the "db_recovery_file_dest" SQLPLUS references + FRA (not the shared network directory) and the two places (both FRA directories) and shared network directory without large amounts of data in them. I think that the previous owners of this CAR may not had adequate support DBA.

In any case, I thought to change the configuration as such:

RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name TESTdb are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON; 
CONFIGURE DEFAULT DEVICE TYPE TO DISK;  # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';  # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/SharedNetworkDrive/ora_df%t_s%s_s%p';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;  # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;  # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;  # default
CONFIGURE MAXSETSIZE TO UNLIMITED;  # default
CONFIGURE ENCRYPTION FOR DATABASE OFF;  # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128';  # default
CONFIGURE COMPRESSION ALGORITHM 'HIGH' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;  # default
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO DISK;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_testdb1.f';  # default

RUN
{
RECOVER COPY OF DATABASE WITH TAG 'incr_update' UNTIL TIME 'SYSDATE - 7';
BACKUP INCREMENTAL LEVEL 1  FOR RECOVER OF COPY WITH TAG 'incr_update' DATABASE PLUS ARCHIVELOG;
DELETE ARCHIVELOG ALL;
}

I don't know that miss me a few things in my backup strategy. Any advice is greatly appreciated!

Thank you

PS - Yes, we have a license for compression

Good point about ARCHIVELOG ALL DELETE. Your suggestion would be to replace it with DELETE NOPROMPT OBSOLETE? Do I need to perform a cross-checking beforehand or Oracle already know from the backup?

CONFIGURE ARCHIVELOG DELETION POLICY TO SAVED 1 TIME TO THE DISK.
INCREMENTAL BACKUP LEVEL 1 for BACK OF COPY WITH TAG "incr_update" DATABASE MORE ARCHIVELOG;
DELETE ARCHIVELOG ALL;

As you have Setup CONFIGURE the STRATEGY of DELETING ARCHIVELOG RMAN will not delete archivelog until archivelog backup 1 time on the disc.

But HemantKChitale have a good point, if for some reason any person clearly that the configuration you'll probably ARCHIVELOG DELETE without backup, do your backup is inconsistent.

So is advised 'INCREMENTAL BACKUP of LEVEL 1 TO RETRIEVE COPY WITH TAG "incr_update" base of DATA PLUS ARCHIVELOG DELETE INPUT' or 'BACKUP ARCHIVELOG ALL DELETE INPUT';

You can avoid delete the archivelogs without backup, because RMAN will only remove saved ARCHIVELOGS.

RMAN incremental backup continue to make backups "complete"?

Hello, I am new to RMAN. I used only the full backup by RMAN, and it was OK. Now, due to lack of disk space, I decided to make incremental backups.
I put 'to recovey retention policy window of 3 days; then made a new backup (by MS) job, looks like:
$rman_script = ' backup database cumulative device type disk tag '% TAG' extra strength 1;
backup disc tag '% TAG' type device archivelog all not saved delete all entries;
But, always visible, size of the backup is the same all the time as a full backup? Where is my mistake?
This is a backup log:
RMAN > database backup incremental level 1 cumulative device type disk tag "BACKUP_DB10_00002_070413021501".
From backup 4 July 13
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid = 1043 devtype = DISK
channel ORA_DISK_1: additional start-up compressed 1 datafile backupset
channel ORA_DISK_1: specifying datafile (s) in backupset
input datafile fno = name=/database/app/oracle/oradata/db/tablespace1.dbf 00007
input datafile fno = name=/database/app/oracle/oradata/db/tablespace2.dbf 00002
...
channel ORA_DISK_1: starting total, 1 to 4 July 13
channel ORA_DISK_1: finished piece 1 to 4 July 13
piece handle=/backup/oracle/flash_recovery_area/db/backupset/2013_07_04/o1_mf_nnnd1_BACKUP_DB10_00002_0_8x9d45f5_.bkp tag = BACKUP_DB10_00002_070413021501 comment = NONE
channel ORA_DISK_1: complete set of backups, time: 00:41:15
Backup finished on 4 July 13

> database backup incremental level 1 cumulative device type disk tag "BACKUP_DB10_00002_070413021501".

There is a Note of support Oracle ' size of level 1 or level 1 cumulative backup greater than level 0 backups [ID 1534691.1].

which applies if you use the DUNGEON and change the tag.

I note that you change the tag every day, but do not use the clause to KEEP this note should not apply.

Why not explicitly run EXTRA STRENGTH 0 backup once and then monitor subsequent LEVEL 1 backups?

Hemant K Collette

RMAN incremental backup issue
Hi all

I'm read on Oracle11g release2 doc RMAN.

In Chapter 9:

"For example, you can implement a three-tier backup plan as well as a level 0 backup is performed every month, a cumulative level 1 is taken from the week, and a premium of level 1 is taken daily. In this strategy, you will never have to apply more than one day to complete recovery redo. »

First I got an error when I try to make a level 0 backup
```
RMAN> BACKUP INCREMENTAL LEVEL 0 database;
 
Starting backup at 27-APR-11
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_DISK_4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 04/27/2011 20:42:19
RMAN-20021: database not set
RMAN-06031: could not translate database keyword
```
and if the success of step, how I would go about to implement this?
I can do this via dbms_scheduler? or I need to do this via cron?

-Thank you very much for the entry
Your DB must be in use archivelogmode use hot backups. Is your db in archivelog mode?

backup incremental simplesave

Similar Questions

Maybe you are looking for