RMAN :: How To Move Datafile Copies From Incremental Backup
May 17, 2013
As part of an incremental backup I recover copies of the tablespaces. These by default are stored in the disk backup location diskgroup. Is it possible to move these copies to another disk group / location whilst still backing up to the default disk backup location diskgroup. I know how to do it with the main datafiles but not with the copies.
e.g.
Current situation:
Original Datafiles in +DATA
Backups in +FRA
Recovered Datafile copies in +FRA
New setup to be:
Original Datafiles in +DATA
Backups in +FRA
Recovered Datafile copies in +BACKUP
I have main database Server which is located on Server A, now I have to take the RMAN Backup of Server A and then shift the complete database on new Server B.
I am confused whether to use Backup command with AS COPY option or take the backup as backup sets. Which are the best option that I can use for the RMAN Backup.
I've a little question : Is it possible to use RMMAN to backup 2 tables incrementally ? I don't want to backup all the database but only these 2 tables.
I use kill -9 <pid> and kill the job and then i check ps -ef | grep rman and get no process of RMAN but when i login into Enterprise Manager and click on performance tab so i see the graph of RMAN (yellow in colour) which is still continue and means the RMAN backup is in progress , then i checked the top consumer page so there i see backup incr datafile(SYS$USERS)(26.8%), so i want to down this RMAN backup.i also used the this query to check the RMAN job running or not
select * from V$SESSION where MODULE like 'rman%'; it came up with no rows
We are going to implement oracle 11g. Now I wanna use rman to take the incremental backup in the follwing way:
Level-0 backup weekly, in the way:
run { allocate channel c1 type disk; allocate channel c2 type disk; BACKUP incremental level 0 DATABASE TAG 'Weekly_full' FORMAT 'E:RMAN_backupweekly_full_%d_%Y%M%D_s%s_p%p.bak'; backup archivelog all not backed up 1 times delete input TAG 'Weekly_full_arc' FORMAT 'E:RMAN_backupweekly_full_arc_%d_%Y%M%D_s%s_p%p.bak';
[code].....
and RETENTION POLICY TO RECOVERY WINDOW is set to 10 days, so that there is no chance that i will delete expired backup before taking backup.
Now my question is,
1) Is the way is correct that there is no wrong configuration. My main concern is about archive log, is it correct?
2) As i am deleting archive log files with the backup and after that the expired archive log backup is also deleted, so is there any chance of failure in recovery.
3) here how archive log backup will work with 10 days retention policy.
I have 2 seperate rman backup one backup is of only datafile ,spfile and controlfile which i am able to restore and recover without any problem say bkp1 taken at 10 am
other set of backup is of only archive log files of same day but later time than datafile backup say bkp2 taken at 8pm...if i restore and recover bkp1 and try to restore bkp2 it gives error datafile exist (possibly due to fact both backup have control file)
if i just restore bkp1 and try to restore bkp2 so that i can do one recover at time it gives error datafile permission issue (possibly due to fact both backup have control file)
I want to restore database upto 8pm time how can i use both bkp1 and bkp2 to do it(restore datafiles and apply all archive logs on it)
7 of days ago Full backup has been taken to disk due to issues with tape devices.3 days ago tape devices have been fixed and we switched to CommVault managed tape backups. CommVault calls RMAN with following command:
These backups done successfully.Then archivelog backup taken similar way.But when I issue RESTORE DATABASE PREVIEW SUMMARY; RMAN starts with Full backup set, though newer Incremental Level 0 ones are available.Why it does not use these newer ones?
Suppose our database have 100 datafiles and right now rman has completed backup of 64 datafile(from file no 1 to file no 64) and in process of backup of 65 number datafile. In mean time I executed some query and it has changed the file no 55. so now my question whether rman will go and bacup this datafile(datafile no 55) again or it will leave this file as it is?
We are trying to restore a database on the different server using RAM incremental level 0 and 1 backups. We have weekly Incremental level 0 backups along with incremental backups on daily basis. During recovery of Incremental level 0 backup, RMAN is expecting/looking for Incremental Level 0 backup of prior week as well. Is this the usual process for RMAN to look for prior level 0 backup though we need to restore from the current level 0 backup and roll forward by a week with subsequent Level 1 backup.?
We intend to restore from the Level 0 of 1/16 and roll forward with daily incrementals till 1/22. RMAN is expecting level 0 backupsets from 1/9 backup as well and keep failing since those backups are not available. quick inputs since we are in middle of recovery and trying to resolve if this is even doable.
I have no backup taken in my oracle server.Today morning i created a data file and unknowingly deleted it. Now i need to restore the datafile with its contents without using RMAN.
Erroneously created datafile, re: "/path/../large_rbs_03.dbf" was created under the SYSTEM tablespace which is supposedly be in the LARGE_RBS tablespace.
How do I make the said datafile be under LARGE_RBS?
I mistakenly added a datafile to a tablespace which is asm, however the datafile was created in a default location and not the asm location:
alter tablespace pdaiidata1 add datafile '<filename>' size 2048M;
What I should have done:
alter tablepsace <tablespace_name> add datafile '+DATA1' size 2048M;
Is there any way to move this filesystem datafile into the asm tablespace? In previous Oracle versions, I've taken a tablespace offline, moved a datafile, renamed it, then brought the tablespace back online. Can I do something similar here in this situation?
n my last post I asked abt the issues that I was facing while restoring the full backup of RMAN on a new server. I mentioned the steps as well, Now my Question is what If I want to restore the incremental backup on the new server?
What all steps do I have to follow after restoring the zero level backup on a new server.
I am using the following query to determine if my rman backup succeeded for failed. I look for "COMPLETED WITH ERRORS"
col input_type format a10 col bck_hrs format 99.9 heading "Run|Time" col status format a21 col end_dt format a20 heading "End|Time" col mbytes_per_sec format 9,999 heading "Output|Rate|MB/sec"
[code]...
output ======
End Run Output Rate INPUT_TYPE STATUS Time Time Size GB MB/sec ---------- --------------------- -------------------- ----- ---------- ------ ARCHIVELOG COMPLETED 2011-12-24 06:03:54 .5 189.4 106 DB INCR COMPLETED 2011-12-24 05:33:05 9.3 3,392.6 103 ARCHIVELOG COMPLETED 2011-12-23 10:12:27 .2 73.3 105
I know that the DB INCR is an INCR 0 backup but is there some way query I can join with my example above to tell me this is INCR 0 or FULL BKUP?
I was thinking maybe setting "COMMAND_ID" some text like INCR 0 or INCR 1 or FULL BKUP. Does that sound feasible
2nd Incremental #1 Files updates between the 1st and 2nd - Monday 3rd Incremental #2 Files updates between the 2nd and 3rd - Tuesday 4th Incremental #3 Files updates between the 3rd and 4th - Wednesday 5th Incremental #4 Files updates between the 4th and 5th - Thrusday 6th Incremental #6 Files updates between the 5th and 6th - Friday 7th Incremental #7 Files updates between the 6th and 7th - Saturday 8th Full Backup #8 Files updates from 1st,2nd to 7th - Sunday 9th Incremental #9 Files updates between the 8th and 9th _ Monday 10th Incremental #10Files updates between the 9th and 10th - Tuesday 11th Incremental #11 Files updates between the 10th and 11th - Wednesday 12th Incremental #12 Files updates between the 11th and 12th - Thrusday 13th Incremental #13 Files updates between the 12th and 13th - Friday 14th Incremental #14 Files updates between the 13th and 14th - Saturday 15th Full Backup CRASHES - NOT COMPLETED - Sunday
I would need to restore now from #8 ( full backup ) and #9 to #14 ( incremental backup )
Tell me the "restore command" to achieve the output?
"If no level 0 backup is available, then the behavior depends upon the compatibility mode setting. If compatibility is >=10.0.0, RMAN copies all blocks changed since the file was created, and stores the results as a level 1 backup. In other words, the SCN at the time the incremental backup is taken is the file creation SCN. 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 releases."
So yes, that's it. Even in the Oracle 11g OCP course and exam, the information given is for Oracle 9 (pre 10g). Seems like a major functional regression. ------------------------------------------------------------------------------------------------------------------------------------------------ Original problem.
Am I not understanding something about rman???? Using oracle 10g standard edition and rman.
No existing backups.
When I run repeated level 1 cumulative incrementals, the appear to back up everything (like a level 0 would). My understanding is that if a level 1 is run w/o an existing level 0 backup, it will generate a level 0 backup. All subsequent level 1 backups should be level 1's as expected.
If I explicitly generate an level 0, followed by level 1's it all works as expected.
I am determining what got backed up by the size of the resulting save sets.
Do I have to do an explicit level 0 and then explicit level 1's? I thought not.
We just purchased NAS (Raid5) unit to manage our data storage. I am planning to create a virtual partition on this nas device and use one partition for oracle data storage and another virtual partition will be used by other data (files and may be sqlserver data files....etc..)
We will have oracle installed on seperate oracle server. Can we use RMAN to manage incremental backups in this environment? May main worry point is that our data storage device will have many different type of datas and will we be able to tell RMAN to make backups only from certain virtual drives?
Here we have a dataguard environment with db1 as primary and db2 as physical standby database. We configured dataguard in 10g environments and we are not using grid control. What are the steps for configuring rman for incremental backups in this environment?
We want to schedule the backups to be taken in standby db, (that is applicable in case of switchover too). In the case of switchover to db2 what all do we need to do in rman manually to resume backups in db1?
how i can change backup datafile name into its original file name,bcoz at time backup datafile name is different and how i can change that name into its original datafile name so i apply recovery command in user managaed recovery..
I've got a physical standby (10g) which is missing some archive logs, and thus the managed recovery is stuck. I followed the procedure for taking an incremental backup of the primary from the last SCN in the standby, and then recovering the standby from that backup using rman.
It seemed that everything went according to the instructions, except that the "recover database" of the standby from the backup went much faster than I expected. Afterwards I checked the SCN of the standby (select current_scn from v$database) and it had indeed updated to a number beyond where it was stuck originally. The standby controlfile was restored from a backup of the primary's current controlfile, and the standby restarted. The problem is that when I started up standby recovery again, the standby is still looking for the logs which were missing. I can't figure out why! I've been googling around and digging through the docs, and the only clues I can find suggest that this would happen if the standby controlfile wasn't updated. But I did that.
Can you take an incremental backup level 1 or level 0 without archivelogs?
syntax would bebackup as compressed backupset cummulative level 1 database.
The reason I ask is because when I run backup as compressed backupset cummulative level 1 database plus archivelogs # it runs fine, but when I run backup as compressed backupset cummulative level 1 database it just hangs.
I have a Primary database and Standby database both in ASM. Recently my archive logs got deleted and i am trying to recover my standby database with an incremental backup based on scn from primary database. But i face the below error when i recover the standby database with the incremental backup taken in primary database.
RMAN> recover database noredo;Starting recover at 06-NOV-13using target database control file instead of recovery catalogallocated channel: ORA_DISK_1channel ORA_DISK_1: SID=21 device type=DISKchannel ORA_DISK_1: starting incremental datafile backup set restorechannel ORA_DISK_1: specifying datafile(s) to restore from backup setdestination for restore of datafile 00001: +STDBY/11gdb/datafile/system.258.805921881destination for restore of datafile 00002: +STDBY/11gdb/datafile/sysaux.259.805921967destination for restore of datafile 00003: +STDBY/11gdb/datafile/undotbs1.260.805922023destination for restore of datafile 00004: +STDBY/11gdb/datafile
Both source and Target DBs are in Grid Infrastructure version : 11.2.0.3
Planning to Migrate RHEL 5.4 to Solaris 10
Currently we have 3 schemas with a combined size of 4 Terabyte in 11.2.0.3 RAC ASM in RHEL 5.4. All these 3 schemas share one tablespace which has around 150 datafiles.
We want to move these 3 schemas to a Solaris RAC DB with ASM.
If we use Transportable tablespace , should there be any down time for Target DB ?
