Full DB backup/Recovery

Hi,
Does anyone have the complete procedure of both Backup/Recovery?
Regards,
huamin

user12233770 wrote:
Hi,
Does anyone have the complete procedure of both Backup/Recovery?There are just steps in the 'complete' procedure,
restore database;
recover database;So if you have a valid copy of your backup, this is all what you need to do. Obviously, the underlying assumption is that you should be in the Archivelog mode with having all the archive log files intact.
HTH
Aman....

Similar Messages

Problem following full system backup recovery from TM

Hi All,
In addition to other Mac computers I also own an iMac G5. The original hard drive that came with the machine was starting to show signs of "fatigue" so I decided to get a replacement drive.
After putting in the new drive (500gb) I booted my computer using the Leopard install DVD and selected the "restore from time machine backup" under utilities. I went through the process of finding my time capsule->backup->restoring the full thing. I left it going over night so I don't actually know how long it took. Nevertheless, in the morning the process was done. Happily, I restarted my mac and got the grey screen with the apple logo in the middle. The spinning progress circle appeared and started going around. After ~10-15 seconds the screen went black and the mac rebooted itself. The same thing happened over and over and the only way to stop this was to physically turn off the computer.
Here is some additional information for those with a good idea what is going on:
1) If I install a clean Leopard system everything works. The system gets installed and the computer boots normally.
2) After restoring from time capsule (computer continues to reboot itself) I tried doing an "archive and install" from the install DVD. I reasoned that the problem likely lies somewhere within the system booting process so if that is corrupted in one way or the other putting only a new system (and archiving the old one) may allow me to boot the machine and access my user data. Long story, after going through the full recovery process I get an error that the system was installed but that there was some error so the user information could not be used. Regardless, the computer still continuously reboots itself upon startup.
3) I ran Diskwarrior on the recovered time capsule backup. Some very minor errors were found and corrected in personal files that have nothing to do with the boot process (actually, files I have not touched in ages). Directory structure etc. was fine. This did not help however to solve the problem.
4) If I boot my Mac in "safe" or "verbose" mode the screen goes black and I start getting the details of the boot process. (I do not have a copy of the text). Rather quickly it reaches a point where it say something about the HD. It seems to be checking something since the process is "hanging". Afterwards there is a whole quick list of things that the Mac goes through and then follows the dreaded reboot. This goes too fast to actually see what is the last step. (is there a way to slow/freeze the process?)
Is there anyone out there that has an idea on how to solve this issue?
thanks
iMac G5 Mac OS X (10.5.5) 1GB RAM

Thanks for your post.
I did forget to mention in my initial post that I did try to recover my time machine backup from older dates. I tried a backup from one week, one month, and two months ago. The problem persists.
I am avoiding the second option you raised (installing a clean system and migrating my data) and keeping that as a last option. The main reason is that in addition to the data I have I would like to avoid having to install all the applications.
If worse comes I'll take that route. Hopefully, a good suggestion will come up.

Recovery using Full BCV backup & archive logs

Hello DBA's ,
I have Last Sunday's Full BCV (Buisness Copy Volume) backup (i.e. ..... the tablespaces were taken into Backup mode then Sync the BCV, then split the BCV , take the backup of BCV and take the tabespaces in normal mode in short what we call as HOT BACKUP ........ ) & also I am taking only archive log & control file backup Daily.
Now I want to Run my database on Different Server using the above FULL BCV & daily backed up Archive logs & Control file.
Kindly update me- Can I go for following recovery steps for above scenario.
1) Install ORACLE software on new server.
2) Restore the last Sunday's FULL BCV (Hot backup)
3) Restore the archive log from last Sunday's Full BCV backup.
4) Restore the latest backed up control file.
5) Mount the database.
6) Recover the database using backed up control file & archive logs.
7) Open the database with RESETLOGS option.
Please Guide me whether I can Fully Recover/Start database on this new server using above steps. ---OR---- " Are there any more files except data files that need to be backed up daily after Full BCV ? " ---OR ---- More suggestions are Welcome.
I want to test this scenario bcz.
a) I can't afford daily BCV due to lack of storage with current retention given by buisness.
b) I can't afford long time taken by RMAN for backup & recovery, as it disturbs my other backup shedules, also RTO should be very low as per my buisness requirement.
c) Currently we are not thinking for any another Backup options.
OS platform -- SOLARIS 10
Database version -- ORACLE 9i/10g
Atul.

Hello everybody ....
Actually I am doing the above scenario practically and I am facing the problem that when I am applying my archive logs using backup controlfile until cancel, the recovery completes upto the available Archive logs/sequence. But it throws the following error along with it ......
ORA-00279: change 7001791222 generated at 01/13/2008 07:23:42 needed for thread
1
ORA-00289: suggestion : /oracle/EPR/oraarch/1_9623_601570270.dbf
ORA-00280: change 7001791222 for thread 1 is in sequence #9623
ORA-00278: log file '/oracle/EPR/oraarch/1_9622_601570270.dbf' no longer needed
for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 7001816252 generated at 01/13/2008 12:53:05 needed for thread
1
ORA-00289: suggestion : /oracle/EPR/oraarch/1_9624_601570270.dbf
ORA-00280: change 7001816252 for thread 1 is in sequence #9624
ORA-00278: log file '/oracle/EPR/oraarch/1_9623_601570270.dbf' no longer needed
for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log '/oracle/EPR/oraarch/1_9624_601570270.dbf'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
SQL> SQL> SQL> SQL> SQL> SQL> SQL>
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
So, I opened my database using Last (Sunday's) full hot backup only and it opens successfully without applying any archives.
Now, my question is... why my database doesn't open with OPEN RESETLOGS option when I am recovering it using command " RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE; "
I want to recover my database upto Saturday then What should I do ?
Please help me out !
Atul.

Incomplete Recovery Fails using Full hot backup & Archive logs !!

Hello DBA's !!
I am doing on Recovery scenario where I have taken One full hot backup of my Portal Database (EPR) and Restored it on New Test Server. Also I restored Archive logs from last full hot backup for next 6 days. Also I restored the latest Control file (binary) to their original locations. Now, I started the recovery scenario as follows....
1) Installed Oracle 10.2.0.2 compatible with restored version of oracle.
2) Configured tnsnames.ora, listener.ora, sqlnet.ora with hostname of Test server.
3) Restored all Hot backup files from Tape to Test Server.
4) Restored all archive logs from tape to Test server.
5) Restored Latest Binary Control file from Tape to Test Server.
6) Now, Started recovery using following command from SQL prompt.
SQL> recover database until cancel using backup controlfile;
7) Open database after Recovery Completion using RESETLOGS option.
Now in Above scenario I completed steps upto 5) successfully. But when I execute the step 6) the recovery completes with Warning : Recovery completed but OPEN RESETLOGS may throw error " system file needs more recovery to be consistent " . Please find the following snapshot ....
ORA-00279: change 7001816252 generated at 01/13/2008 12:53:05 needed for thread
1
ORA-00289: suggestion : /oracle/EPR/oraarch/1_9624_601570270.dbf
ORA-00280: change 7001816252 for thread 1 is in sequence #9624
ORA-00278: log file '/oracle/EPR/oraarch/1_9623_601570270.dbf' no longer needed
for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log '/oracle/EPR/oraarch/1_9624_601570270.dbf'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
SQL> SQL> SQL> SQL> SQL> SQL> SQL>
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
Let me know What should be the reason behind recovery failure !
Note : I tried to Open the database using Last Full Hot Backup only & not applying any archives. Then Database Opens successfully. It means my Database Installation & Configuration is OK !
Please Let me know why my Incomplete Recovery using Archive logs Goes Fail ?
Atul Patil.

oh you made up a new thread so here again:
there is nothing wrong.
You restored your backup, archives etc.
you started your recovery and oracle applyed all archives but the archive
'/oracle/EPR/oraarch/1_9624_601570270.dbf'
does not exist because it represents your current online redo log file and that is not present.
the recovery process cancels by itself.
the solution is:
restart your recovery process with:
recover database until cancel using backup controlfile
and when oracle suggests you '/oracle/EPR/oraarch/1_9624_601570270.dbf'
type cancel!
now you should be able to open your database with open resetlogs.

Missing Recovery partition after restoring full TM backup

Hello everyone,
I have a question for you Time Machine gurus. I have looked at pondini.org but could not find the answer. It is very possible I have overlooked it.
Here is the scenario:
Macbook Pro with Lion 10.7.2. I connected 1TB USB drive. Formatted it.
Rebooted while holding Option+R. Had two options: Main Drive and Recovery HD. Took Main Drive.
Ran full TM machine backup to the external.
Rebooted while holding Option+R. Had three options: Main Drive, Recovery HD and TM Backup. Took TM Backup. It worked fine, everything looked good.
The next step may not make sense to you, but I have been having some performance issues with the MBP, so I decided to format the main drive and recover it from the TM backup so that the data would be contiguous. I have read countless articles in favor or against doing this. I just thought it made sense, based on many articles I read here.
I then, while running from the TM backup, formatted my main drive.
Next I did a full recovery of the main drive from the TM backup. Everything worked just fine and I am running ok at this time. Not sure it helped performance yet, but here is the question:
Once I reboot the system holding Option+R after the recovery, I only have two options: Main Drive and TM backup. Recovery HD is gone. So it seems that was either not backed up to TM to begin with or not recovered to the Main Drive during the full recovery. Any ideas? The goal was to have it still there in the Main Drive, although with a full TM backup I would not really need it unless I am away from my external, which could happen.
Thanks for ideas or suggestions.
M

Mr. Goob-Mart wrote:
Rebooted while holding Option+R. Had two options: Main Drive and Recovery HD. Took Main Drive.
You don't need to hold the R key. Option invokes the Startup Manager, which shows all bootable volumes.
Or, you can hold Cmd+R to start from the Recovery HD on your Mac.
Once I reboot the system holding Option+R after the recovery, I only have two options: Main Drive and TM backup. Recovery HD is gone.
That's correct. A full restore erases the entire OSX volume, including the Recovery HD. (Just why it takes the Recovery HD isn't clear, but it does).
The only way to get a new one is to download a fresh copy of Lion, via the Recovery HD on the TM drive.
Once it's there, you can copy it to another drive if you want. See: OS X Lion: About Lion Recovery Disk Assistant (but you can't copy the one on your Time Machine drive).

Rescue and Recovery 4.52 - Makes Full Image Backups?

So, this may seem like a simple question to some, but I can not find a conclusive answer yet.
I have Lenovo's Rescue and Recovery 4.52 - Windows 7 (64 bit) for my Lenovo T540. Will Rescue and Recovery 4.52 create a full image backup such that if in the event my hard drive crashes, I can reinstall the entire operating system, programs, etc at one time, without having to reinstall individual software programs?
I just don't want to install Rescue and Recovery 4.52 because it is a large program, without it being able to do a full image backup.
Thanks

In my personal opinion, Rescue and Recovery is obselete. For Win7 and later, my advice is to use Windows built-in backup and restore. You can create both a complete system image (what you are asking about), and also backup individual files/folders in your libraries.
http://windows.microsoft.com/en-us/windows7/products/features/backup-and-restore
Rescue and Recovery was great for XP and earlier OS when there wasn't any built-in backup and restore functions. But for Win7 and later, my advice is to use the OS built-in feature. Hope this helps.

How to Restore Full Offiline Backup using BRTOOLS from a Tape

Dear all,
I want to recover PRD Full Offline Backup using BRTOOLS from a tape in a new machine.
I have Install SAP in the new machine.
Now I want to restore the PRD Full Offiline Backup taken through BRTOOLs in tape in the new machine.
1. I have shutdown the SAP.
2. I have shutdown the database Oracle 10g.
3. I have inserted the backup tape
4. Through user ORASID I have executed BRTOOLS
I got the following options: -
BRTools main menu
1 = Instance management
2 - Space management
3 - Segment management
4 - Backup and database copy
5 - Restore and recovery
6 - Check and verification
7 - Database statistics
8 - Additional functions
9 - Exit program
I selected Option 5 Restore and recovery
And got the Following Options
Restore and recovery
1 = Complete database recovery
2 - Database point-in-time recovery
3 - Tablespace point-in-time recovery
4 - Whole database reset
5 - Restore of individual backup files
6 - Restore and application of archivelog files
7 - Disaster recovery
8 - Reset program status
1. Now which option do I need to select and then what all other options do I need to select.
2. Whether the database should be a mount state or shutdown ?
Kindly help.

Dear Mark,
Thanks.
As suggested I tried both the options however face some difficulties please suggest
brrestore -u / -c -b <backup_log.ext> -p init<SID>.sap -m full
hinrnddev:oradev 1> brrestore -u / -c -b bedflluv.fft -p initDEV.sap -m full
BR0401I BRRESTORE 7.00 (32)
BR0405I Start of file restore: redhafeh.rsb 2010-05-22 11.55.55
BR0484I BRRESTORE log file: /oracle/DEV/sapbackup/redhafeh.rsb
BR0252E Function fopen() failed for '/oracle/DEV/sapbackup/bedflluv.fft' at location BrbLogRead-1
BR0253E errno 2: No such file or directory
BR0121E Processing of log file /oracle/DEV/sapbackup/bedflluv.fft failed
BR0406I End of file restore: redhafeh.rsb 2010-05-22 11.55.55
BR0280I BRRESTORE time stamp: 2010-05-22 11.55.55
BR0404I BRRESTORE terminated with errors
When I used the brrestore command I got the above error message.
Then I tried the next option Complete database recover
BRRECOVER options for restore and recovery
1 * Recovery type (type) ............. [complete]
2 - BRRECOVER profile (profile) ...... [initDEV.sap]
3 ~ BACKINT/Mount profile (parfile) .. []
4 - Database user/password (user) .... [/]
5 - Recovery interval (interval) ..... [30]
6 - Confirmation mode (confirm) ...... [yes]
7 - Scrolling line count (scroll) .... [20]
8 - Message language (language) ...... [E]
9 - BRRECOVER command line (command) . [-p initDEV.sap -t complete -i 30 -s 20 -l E]
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
BR0662I Enter your choice:
C
Complete database recovery main menu
1 = Check the status of database files
2 * Select database backup
3 * Restore data files
4 * Restore and apply incremental backup
5 * Restore and apply archivelog files
6 * Open database and post-processing
7 * Exit program
8 - Reset program status
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
BR0662I Enter your choice:
C
Complete database recovery main menu
1 + Check the status of database files
2 # Select database backup
3 # Restore data files
4 # Restore and apply incremental backup
5 # Restore and apply archivelog files
6 + Open database and post-processing
7 = Exit program
8 - Reset program status
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
BR0662I Enter your choice:
the + sign got changed to +
and the * got changed to #
then it is getting in loop please suggest what do I do now.

Error while taking Full DB Backup

Hi,
We had Multiplexed the Archive Log File to default location(Flash Recovery Area) and log_archive_dest_1=/u02/app/oracle/oradata/orcl/archive
As too much of archive log's are generated we had removed the log_archive_dest_1.
We had scheduled full DB backup every sunday and incremental DB backup everyday(midnight) through OEM.
I am backing up all the archive log's and after each backup (incremental and full DB backup) we are deleting all Archive logs backed up.
The Full DB Backup failed as it is still trying to backup archive logs from log_archive_dest_1(/u02/app/oracle/oradata/orcl/archive)
Please find below the error log file generated after backup failed.
RMAN> backup device type disk format='/u02/backup/scheduled/Full-ARC_%d_%t_%s_%p' tag 'BACKUP_ORCL_000022_091608120501' archivelog all not backed up;
Starting backup at 16-SEP-08
current log archived
using channel ORA_DISK_1
using channel ORA_DISK_2
skipping archive log file */u02/app/oracle/oradata/orcl/archive*/1_8459_639421762.dbf; already backed on 01-SEP-08
skipping archive log file /u02/app/oracle/oradata/orcl/archive/1_8460_639421762.dbf; already backed on 01-SEP-08
skipping archive log file /u02/app/oracle/oradata/orcl/archive/1_8461_639421762.dbf; already backed on 01-SEP-08
skipping archive log file /u02/app/oracle/oradata/orcl/archive/1_8462_639421762.dbf; already backed on 01-SEP-08
archived log /u02/app/oracle/oradata/orcl/archive/1_8463_639421762.dbf not found or out of sync with catalog
trying alternate file for archivelog thread 1, sequence 8463
archived log /u02/app/oracle/oradata/orcl/archive/1_8464_639421762.dbf not found or out of sync with catalog
trying alternate file for archivelog thread 1, sequence 8464
archived log /u02/app/oracle/oradata/orcl/archive/1_8465_639421762.dbf not found or out of sync with catalog
trying alternate file for archivelog thread 1, sequence 8465
archived log /u02/app/oracle/oradata/orcl/archive/1_8466_639421762.dbf not found or out of sync with catalog
trying alternate file for archivelog thread 1, sequence 8466
archived log /u02/app/oracle/oradata/orcl/archive/1_8467_639421762.dbf not found or out of sync with catalog
trying alternate file for archivelog thread 1, sequence 8467
Please suggest me the possible outcome
Thanks and Regards
Amith

Hi,
The Archive log's has occupied full Hard Disk space so i changed the status of DB to NoArchive Log mode and deleted all the archive files available at "/u02/app/oracle/oradata/orcl/archive" using OS command.
Now I changed the DB to Archive Log Mode and now using RMAN to delete All Archive files which are backed up.
backup incremental level 0 cumulative device type disk tag '%TAG' database include current controlfile;
backup device type disk tag '%TAG' archivelog all not backed up delete all input;
Thanks
Amith
Edited by: amith r on Sep 17, 2008 3:00 PM

Need help with Backup Recovery using Rman - Point in Time.

Hi all,
I am trying to recover my database to a certain point in time. Here are the details below.
Oracle database version is. 11G R1. on 2 Node RAC. OS is AIX.
Database name is Sales.
Due to a mistake by the Application team, the database is written over by bad data. Now I have to restore the database in to a point in time, where the database was good.
For this, i took a whole (full) RMAN backup, everything, all the archivelog files and Controlfiles as well.
After doing this, i dropped the entire database. So now everything is clean.
Now i have to restore and recover the database to this point in time.. 03/16/2011 12:45:00
Please guide.
The backups are located at.. /backup/sales/rman/
I am trying various things, but each time i get the msg..
ORA-01507: database not mounted
I understand.. the reason for this message is the controlfile does not exist.. as the database is in mount mode. But as i said.. i have dropped the database in order to proceed with entire restoration.
But i have taken a whole backup.. which also includes the controlfiles + archivefiles.
Please guide.. with proper steps and commands.

Hi,
Priror to start with restore and recovery - Try to restore the control file from backups "/backup/sales/rman/"
Then further you can mount the db and further carry on with recovery (catalog the backups prior to recovery)
- Pavan Kumar N

How can I amke a full cold backup

Hi, I would like to make a full cold backup in command line mode and then recover it.How caI proceed?
Backup sets or image copy?
I have tried this but it didn't work, I made it after a normal dbstart.
connected to target database: ISCREAM (DBID=3415054131)
RMAN> backup incremental level 0
2> as compressed backupset database;
Starting backup at 26.04.06
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=145 devtype=DISK
channel ORA_DISK_1: starting compressed incremental level 0 datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00002 name=/home/oracle/oradata/iscream/undotbs01.dbf
input datafile fno=00001 name=/home/oracle/oradata/iscream/system01.dbf
input datafile fno=00003 name=/home/oracle/oradata/iscream/sysaux01.dbf
input datafile fno=00005 name=/home/oracle/oradata/iscream/example01.dbf
input datafile fno=00004 name=/home/oracle/oradata/iscream/users01.dbf
input datafile fno=00006 name=/home/oracle/oradata/iscream/tools.dbf
channel ORA_DISK_1: starting piece 1 at 26.04.06
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 04/26/2006 10:22:33
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 5242880000 limit

You did fill up flash recovery area :
$ oerr ora 19809
19809, 00000, "limit exceeded for recovery files"
//*Cause: The limit for recovery files specified by the
//        DB_RECOVERY_FILE_DEST_SIZE was exceeded.
//*Action:The error is accompanied by 19804. See message 19804 for further
//        details.
$ oerr ora 19804
19804, 00000, "cannot reclaim %s bytes disk space from %s limit"
// *Cause: Oracle cannot reclaim disk space of specified bytes from the
//         DB_RECOVERY_FILE_DEST_SIZE limit.
// *Action: There are five possible solutions:
//          1) Take frequent backup of recovery area using RMAN.
//          2) Consider changing RMAN retention policy.
//          3) Consider changing RMAN archivelog deletion policy.
//          4) Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE.
//          5) Delete files from recovery area using RMAN.
$

Re: does the full cold backup of rman include onlinde redologs?

Hi,
does the full cold backup of rman include onlinde redologs?
So that at the time of recovery when i restore the database the online redologs also restored to that point?
Please kindly add your suggestions. I read in 10g database in mount state while taking RMAN Cold backup as the all the oracle processes are down we cant copy the online redologs.
Am I Correct if not please any one answer me why the online redologs are not copied.
Thanks in Advance
Sai

976630 wrote:
Hi,
does the full cold backup of rman include onlinde redologs?No.
So that at the time of recovery when i restore the database the online redologs also restored to that point?No.
>
Please kindly add your suggestions. I read in 10g database in mount state while taking RMAN Cold backup as the all the oracle processes are down we cant copy the online redologs.
Am I Correct if not please any one answer me why the online redologs are not copied.No. They are not needed because the only valid backup for a cold (or noarchivelog mode database) backup is a consistent backup. Since the backup is already consistent there are no changes to apply.
The online redo logs are (re)created/reset by the "resetlogs" clause when the database is opened.
>
Thanks in Advance
SaiEdited by: Mark Williams on Jan 7, 2013 10:32 PM - Looks like Hemant replied whilst I was typing in my response.

Regarding Full online Backup failed

Dear All,
I have faceing one issue related to SAP system backup, i have shedule sap backup by DB13(full online backup) but frequently it will failed and showing same return code 005. Bellow mentioned is log details pls. check:-
datafile copy filename=/oracle/P01/sapbackup/behgluac.spa/p01.data26 recid=40001 stamp=767722216
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of catalog command on default channel at 11/20/2011 16:10:16
ORA-19665: size 517120 in file header does not match actual file size of 514560
ORA-19664: file type: datafile copy, file name: /oracle/P01/sapbackup/behgluac.spa/p01.data27RMAN>
Recovery Manager complete.
BR0280I BRBACKUP time stamp: 2011-11-20 16.10.17
*BR0279E Return code from 'SHELL=/bin/sh /oracle/P01/102_64/bin/rman nocatalog': 1*
BR0536E RMAN call for database instance P01 failedBR0280I BRBACKUP time stamp: 2011-11-20 16.10.17
BR0532E Cataloging backups of all database files failedBR0056I End of database backup: behgluac.fnt 2011-11-20 16.10.17
BR0280I BRBACKUP time stamp: 2011-11-20 16.10.17
BR0054I BRBACKUP terminated with errors
Pls. guide me and help me to reslove this issue.
Our server OS is solaries 10 and DB is Oracle 10g.
Regards,
Sweetdiya.

Hii,
Can you tell me option to take backup again on same day if 1st bakup will failure? Bcoz we have try to take backup on same day on same tape when 1st backup had terminated due to error sytem is not take backup. e.g if today tuesday i have take(sunday S01B01,mon S01B02 likethis) tape name S01B03 our backup is failed due to error RC:- 005. we can re-execute bakup or shedule bckup in DB13 again it is agin failed.
so can any body can guide us on this issue plz..
Thanks in advance.
Regards,
Sweetdiya
Edited by: sweetdiya on Nov 22, 2011 10:11 AM

ORACLE8 OPS BACKUP & RECOVERY

제품 : ORACLE SERVER
작성날짜 : 2004-08-16
ORACLE8 OPS BACKUP & RECOVERY
=============================
SCOPE
Standard Edition 에서는 Real Application Clusters 기능이 10g(10.1.0) 이상 부터 지원이 됩니다.
Explanation
OPS에서의 database backup & recovery 방법은 single instance의 backup 방법과
비슷하다. 즉, Single instance에서의 모든 backup 방법은 ops에서도 지원된다.
1. Backup 방법
다음의 backup 방법 모두 사용이 가능하다. 여기서는 2)의 os 명령을 이용한
backup 방법에 대해 기술합니다.
1) Recovery Manager (RMAN) : <Bulletin 11451> 참고
2) OS 명령을 활용한 백업
Noarchive log mode : full offline backup only
Archive log mode : full or partial, offline or online backup
3) export : <Bulletin 10080> 참고 : ORACLE 7 BACKUP 및 RECOVERY 방법
2. backup 정책 수립 시 고려 사항
1) disk crash나 user error 등으로 말미암은 손실을 허용하지 않는다면 ARCHIVE
LOG MODE를 사용해야 한다.
2) 대부분 모든 instance는 자동 archiving을 사용한다.
3) 모든 data backup 작업이 어떤 instance 건 가능하다.
4) media recovery 시 모든 thread의 archive file이 사용된다.
5) Instance recovery 시 살아있는 instance의 smon에 의해 자동으로 recovery된다.
3. Noarchive log mode : Full offline backup
1) 다음의 view들을 query하여 backup이 필요한 file을 알아낸다.
V$DATAFILE or DBA_DATA_FILES
V$LOGFILE
V$CONTROLFILE
2) 모든 instance를 shutdown한다.
3) 확인된 file을 backup destination으로 copy한다.
4. Archive log mode : Partial or Full Online Backup
1) 백업을 수행하기 전에 ALTER SYSTEM ARCHIVE LOG CURRENT 명령 실행(이 명령을
실행하여 현재 운영되지 않는 데이터베이스를 포함한 모든 노드의 current redo
log에 대한 로그 스위치와 그에 따른 아카이브를 모든 인스턴스에서 실행시킨다.)
2) ALTER TABLESPACE tablespace BEGIN BACKUP 명령 실행
3) ALTER TABLESPACE 명령이 성공적을 실행될 때까지 대기
4) OS에서 적절한 명령어를 활용하여 테이블스페이스에 속하는 데이터파일들을 백업
(tar, cpio, cp 등)
5) OS 명령을 활용한 백업이 다 끝날 때까지 대기
6) ALTER TABLESPACE tablespace END BACKUP 명령 수행
7) ALTER DATABASE BACKUP CONTROLFILE TO filename 이나
ALTER DATABASE BACKUP CONTROLFILE TO TRACE
명령을 수행시켜 컨트롤 파일을 백업.
만약 아카이브 로그 파일을 백업받는다면 END BACKUP 명령을 실행시킨 이후
ALTER SYSTEM ARCHIVE LOG CURRENT 명령을 실행시켜 END BACKUP 시점까지의
모든 리두 로그 파일들을 확보한다.
5. Import Parameter
1) Controlfile 내의 Redo Log History (MAXLOGHISTORY )
CREATE DATABASE 명령이나 CREATE CONTROLFILE 명령에서 MAXLOGHISTORY 값을
지정하여 parallel server에서 다 채워진 리두 로그 파일에 대한 history를
컨트롤 파일이 저장하도록 할 수 있다. 이미 데이터베이스를 생성한 후라면
log history 값을 증가시키거나 감소시키기 위해서는 컨트롤 파일을 재생성
하여야만 한다.
MAXLOGHISTORY는 컨트롤 파일 내의 archive history를 얼마나 저장할 수
있는지를 지정하며, 기본값은 플랫폼 별로 다르다. 이 값이 0이 아닌 다른
값으로 지정된다면 log switch가 발생할 때마다 LGWR 프로세스에서는 컨트롤
파일에 다음 정보를 기록한다.
thread number, log sequence number, low SCN, low SCN timestamp, next SCN
(next log의 가장 낮은 SCN값)
(이 정보는 리두 로그 파일이 archive된 후가 아니라 log switch가 발생할 때
컨트롤 파일에 저장된다.)
MAXLOGHISTORY 값에서 지정한 값을 넘어서 log history가 저장되어야 할 경우
가장 오래된 history를 overwrite하는 방식으로 저장된다. Log history 정보는
OPS에서 자동 media recovery 시 SCN, thread number를 기준으로 적절한
아카이브 로그 파일을 찾아 재구성하는 데 사용된다. 데이터베이스를 exclusive
모드에서 한개의 쓰레드만 사용하는 환경에서는 log history 정보가 필요하지 않다.
Log history 관련 정보는 V$LOG_HISTORY를 이용해 조회해 볼 수 있다.
서버 관리자에서 V$RECOVERY_LOG를 조회하면 media recovery에 필요한 아카이브
로그에 대한 정보를 얻을 수 있다.
Multiplex된 리두 로그 파일에 대해서, log history 내에서 여러개의 entry가
사용되지 않는다. 각각의 entry는 개개의 파일에 대한 정보가 아니라, multiplex
된 log 파일의 그룹에 대한 정보를 가지고 있다.
2) Archive Log Mode 시 Parameter
OPS에서 archive log mode로 변경 시 exclusive mode로 db mount 후에 변경한다.
a. LOG_ARCHIVE_FORMAT
파라미터     설명     예
%T     thread number, left-zero-padded     arch0000000001
%t     thread number, not padded     arch1
%S     log sequence number, left-zero-padded     arch0000000251
%s     log sequence number, not padded     arch251
이 가운데 %T와 %t는 OPS에서만 유효한 파라미터이다.
모든 instance의 format은 같아야 하며 OPS 환경에서는 반드시 thread 번호를
포함시켜야 한다.
예) log_archive_format = %t_%s.arc
b. LOG_ARCHIVE_START
- 자동 archiving : TRUE로 지정한 후 인스턴스를 구동시키면 background process
인 ARCH에서 자동 archiving을 수행한다. Closed Thread의 경우에는 실행 중인
thread에서 closed thread를 대신해 log switch와 archiving을 수행한다.
이것은 모든 노드에서 비슷한 SCN을 유지하도록 하기 위해 강제적으로 log switch
가 발생할 때 일어난다
- 수동 Archiving : FALSE이면 archive를 시작하도록 지시하는 명령을 명시적으로
내리지 않는 이상 동작을 멈추고 대기한다. OPS에서는 각각의 인스턴스에서 서로
다른 LOG_ARCHIVE_START 값을 사용할 수 있다.
다음과 같은 방법으로 수동 archiving을 수행할 수 있다.
ALTER SYSTEM ARCHIVE LOG SQL 명령을 실행
ALTER SYSTEM ARCHIVE LOG START 명령을 실행하여 자동 archiving을 실행하도록
지정.
수동 archiving은 명령을 실행시킨 노드에서만 실행 되며, 이 때 archiving
작업을 ARCH 프로세스가 처리하지 않는다.
c. LOG_ARCHIVE_DEST
archive log file이 만들어질 directory를 지정한다.
예) log_archive_dest = /arch2/arc
6. OPS Recovery
1) Instance Failure 시
Instance failure는 S/W나 H/W 상의 문제, 정전이나 background process에서
fail이 발생하거나, shutdown abort를 시키거나 OS crash 등 여러가지 이유로
인해 instance가 더 이상 작업을 진행할 수 없을 때 발생할 수 있다.
Single instance 환경에서는 instance failure는 instance를 restart 시키고
database를 open하여 해결된다. Mount 상태에서 open 되는 중간 단계에서 SMON은
online redo log 파일을 읽어 instance recovery 작업을 수행한다.
OPS에서는 instance failure가 발생 했을 경우 다른 방식으로 instance
recovery가 수행된다. OPS에서는 한 노드에서 fail이 발생했다고 하더라도
다른 노드의 인스턴스는 계속 운영될 수 있기 때문에 instance failure는
database가 가용하지 않다는 것을 의미하지는 않는다.
Instance recovery는 dead instance를 처음으로 발견한 SMON 프로세스에서
수행한다. Recovery가 수행되는 동안 다음과 같은 작업이 일어난다.
- Fail이 발생하지 않은 다른 인스턴스에서는 fail이 발생한 인스턴스의
redo log 파일을 읽어 들여 데이터파일에 그 내용을 적용시킨다.
- 이 기간 동안 fail이 발생하지 않은 다른 노드에서도 buffer cache 영역의
내용을 write 하지는 못한다.
- DBWR disk I/O가 일어나지 못한다.
- DML 사용자에 의해 lock request를 할 수 없다.
a. Single-node Failure
한 인스턴스에서 fail이 난 다른 인스턴스에 대한 recovery를 수행하는 동안,
정상적으로 운영 중인 인스턴스는 fail이 난 인스턴스의 redo log entry를
읽어 들어 commit이 된 트랜잭션의 결과치를 데이터베이스에 반영시킨다.
따라서 commit 된 데이터에 대한 손실은 일어나지 않으며, fail이 난
인스턴스에서 commit 시키지 않은 트랜잭션에 대해서는 rollback을 수행하고,
트랜잭션에서 사용 중이던 자원을 release시킨다.
b. Multiple-node Failure
만약 OPS의 모든 인스턴스에서 fail이 발생했을 경우, 인스턴스 recovery는
어느 한 인스턴스라도 open이 될 때 자동으로 수행된다. 이 때 open되는 인스턴스는
fail이 발생한 인스턴스가 아니라도 상관 없으며, OPS에서 shared 모드
혹은 execlusive 모드에서 데이터베이스를 mount 하더라도 상관 없이 수행된다.
오라클이 shared 모드에서 수행되던, execlusive 모드에서 수행되건,
recovery 절차는 하나의 인스턴스에서, fail이 난 모든 인스턴스에 대한
recovery를 수행하는지 여부를 제외하고는 동일하다.
2) Media Failure 시
Oracle에서 사용하는 file을 저장하는 storage media에 문제가 발생했을 경우
발생한다. 이와 같은 상황에서는 일반적으로 data에 대한 read/write가 불가능하다.
Media failure가 발생했을 경우 recovery는 single instance의 경우와
마찬가지로 recovery가 수행되어야 한다. 두 경우 모드 archive log 파일을
이용해서 transaction recovery를 수행하여야 한다.
3) Node Failure 시
OPS 환경에서, 한 노드 전체에 fail이 발생했을 때, 해당 노드에서 동작하던
instance와 IDLM 컴포넌트에서도 fail이 발생한다. 이 경우 instance recovery를
하기 위해서는 IDLM은 lock에 대한 remaster를 시키기 위해 그 자신을
reconfigure시켜야 한다.
한 노드에서 fail이 발생했을 때 Cluster Manager 또는 다른 GMS product에서는
failure를 알리고, reconfiguration을 수행하여야만 한다. 이 작업이 수행되어야만
다른 노드에서 운영 중인 LMD0 프로세스와의 통신이 가능하다.
오라클에서는 fail이 발생한 노드에서 잡고 있는 lock 정보를 access할 경우나,
LMON 프로세스에서 heartbeat을 이용해서 fail이 발생한 노드가 더 이상
가용하지 않다는 것을 감지할 때 failure가 발생한 것을 알게 된다.
IDLM에서 reconfigure가 일어나면 instance recovery가 수행된다.
Instance recovery는 recovery를 수행하는 동안 자원에 대한 contention을
피하기 위해 전체 데이터베이스의 작업을 일시 중지시킬 수 있다.
FREEZE_DB_FOR_FAST_INSTANCE_RECOVERY initialization parameter 값을
TRUE로 지정하며 전체 데이터베이스가 일시적으로 작업을 멈추게 된다.
데이터 화일에서 fine-grain lock을 사용할 경우 기본값은 TRUE이다.
이 값을 FALSE로 지정할 경우 recovery가 필요한 데이터만이 일시적으로 작업이
멈춰진다. 데이터 화일이 hash lock을 사용할 경우 FALSE가 기본 값이다.
4) IDLM failure 시
한 노드에서 다른 연관된 프로세스의 fail이나 memory fault 등의 이유로 인해
IDLM 프로세스만 fail이 발생했다면 다른 노드의 LMON에서는 이 문제를 감지하여
lock reconfiguration process를 시작한다.
이 작업이 진행 중인 동안 lock 관련 작업은 처리가 정지되고 PCM lock 또는
다른 resource를 획득하기 위해 일부 사용자들은 대기 상태로 들어간다.
5) Interconnect Failure ( GMS failure ) 시
노드 간의 interconnect에서 fail이 발생하면 각각의 노드에서는 서로 다른
노드의 IDLM과 GMS에서 fail 이 발생했다고 간주하게 된다. GMS에서는 quorum
disk나 node에 pinging 등을 수행하는 다른 방법을 통해 시스템의 상태를 확인한다.
이 경우 Fail이 발생한 connection에 대해 두 노드 혹은 한쪽 노드에서
shutdown 이 일어난다.
Oracle 8 recovery mechanism에서는 노드 혹은 인스턴스에서 강제로 fail이
발생했을 경우 IDLM이나 instance가 startup 될 수 없게 된다. 경우에 따라서는
노드 간의 IDLM communication이 가용한지 여부를 확인하기 위해 cluster
validation code를 직접 작성하여 사용할 수도 있다. 이 방법을 사용하여
GMS에서 제공하지는 않지만, 문제를 진단한 후 shutdown을 수행하도록 할 수 있다.
이같은 code를 작성하기 위해서는 단일 PCM lock에서 처리되는 단일 data block에
대해 계속해서 update 를 수행해 보는 루틴이 들어가면 된다. 서로 연결된
두 노드에서 이 프로그램을 실행시키게 될 경우 interconnect에서 fail이
난 상황을 진단할 수 있게 된다.
만약 여러개의 노드가 cluster를 구성할 경우에는 매 interconnect 마다
다른 PCM lock에 의해 처리되는 data block을 update 함으로써, 어떤 노드와의
interconnect에 문제가 발생했는지를 알아낼 수 있다.
7. Parallel Recovery
Parallel Recovery의 목표는 compute와 I/O parallelism을 사용해서 crash
recovery, single-instance recovery, media recovery 시 소요되는 시간을 줄이는
데 있다.
Parallel recovery는 여러 디스크에 걸쳐 몇 개의 데이터파일에 대해 동시에
recovery를 수행할 때 가장 효율적이다
다음과 같이 2가지 방식으로 병렬화시킬 수 있다.
- RECOVERY_PARALLELISM 파라미터 지정
- RECOVER 명령의 옵션에 지정
오라클 서버는 하나의 프로세스에서 log file을 순차적으로 읽어들이고, redo
정보를 여러 개의 recovery 프로세스에 전달해, log file에 기록된 변동 사항을
데이터파일에 적용시킬 수 있다.
Recovery Process는 오라클에서 자동적으로 구동되므로, recovery를 수행할 경우
한 개 이상의 session을 사용할 필요가 없다.
RECOVERY_PARALLELISM의 최대값은 PARALLEL_MAX_SERVERS 파라미터에 지정된 값을
초과할 수 없다.
Reference Ducumment
Oracle8 ops manual

Configuration files of the Oracle Application server can be backed up by "Backup and Recovery Tool"
Pls refer to the documentation,
http://download.oracle.com/docs/cd/B32110_01/core.1013/b32196/part5.htm#i436649
Also "backup to tapes feature" is not yet supported by this tool
thanks,
Murugesh
Message was edited by:
Murugesan Appukuttty

Full OS backup and restoration

I have a Win 2012 R2 server installed on a Dell PE730 box. The box is highly critical and there are lot of configurations in that server that I want to create a full backup and incase of failure of the box, the backup should be useful to restore the box
with all configurations.
I don't use any third party tools for backup - use Windows backup role in Win 2012, also plans to use the Windows feature itself to restore also.
What is the best method of creating a backup and restore plan. Pls suggest

Hi,
You can use a full server backup to perform all types of recoveries, including system state and bare metal recoveries. We recommend this option. Then you could recover your server operating system or full server by using Windows Recovery Environment.
For more detailed information, you could refer to the articles below:
Backing Up Your Server
https://technet.microsoft.com/en-us/library/cc753528.aspx
Recover the Operating System or Full Server
https://technet.microsoft.com/en-us/library/cc755163.aspx
Best Regards,
Mandy
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Full Server Backup for Domain Computer

Having Windows 2012 Domain Controllers. I have a requirement to provide a backup for one domain controller to be sent to a another data center, so that if all our main datacenters are destroyed for any reason, we can have a media with backup of our AD.
So i took a Full Server Backup for one of our domain controllers, put it on a tape, send it to the security team so that they can send it to the standby datacenter.
Security team asking me that on the standby datacenter, they want to simulate complete disaster ( that is all domain controllers are destroyed) and they want to give me a machine so that i can restore the full server backup of AD on it.
Is this supported ? To save the Full Server backup of a domain controller in a Tape so that it can be restored in standby datacenter in different computer when things get bad?
ammarhasayen

As Tero already mentioned, one you have your test environment up and running, you need to prepare your DRP (Disaster Recovery Plan).
See that:
http://technet.microsoft.com/en-us/library/cc757662(v=ws.10).aspx
http://technet.microsoft.com/en-us/library/bb727048.aspx
Make sure that you are taking periodic system state backups of at least one DC/GC server.
For the standby datacenter, you can simply promote a new DC/DNS/GC server there and keep it active to be used in case of disasters as I previously mentioned. By configuring properly your AD sites and subnets, you can be sure that your Windows servers and
client computers do not use this DC for daily authentication.
This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Get Active Directory User Last Logon
Create an Active Directory test domain similar to the production one
Management of test accounts in an Active Directory production domain - Part I
Management of test accounts in an Active Directory production domain - Part II
Management of test accounts in an Active Directory production domain - Part III
Reset Active Directory user password

Full DB backup/Recovery

Similar Messages

Maybe you are looking for