RMAN backups valid for clone database.

Hi,
If we clone the database using rman that clone database will be having different database id, incurnation number and new resetlogfiles.
so here we can't use source database backup files. if we want to use that source database backup files to clone database what is the procedure to clone the database.
please let me know.
thank you very much...!

899329 wrote:
Hi,
If we clone the database using rman that clone database will be having different database id, incurnation number and new resetlogfiles.
so here we can't use source database backup files. if we want to use that source database backup files to clone database what is the procedure to clone the database.
please let me know.
thank you very much...!You can clone/refresh database as
1) RMAN duplicate
2) RMAN restore from backups(restore control + database)
using source backup files:-
3) Hot backup clone ( begin backup, copy files, end backup, create controlfile using trace)
4) cold clone (shutdown database, copy datafiles, create controlfile)
5) whole database export & import

Similar Messages

Best pratices for RMAN backup management for many databases

Dear all,
We have many 10g databases (>40) hosted on multiple Windows servers which are backup up using RMAN.
A year ago, all backup's were implemented through Windows Scheduled Tasks using some batch files.
We have been busy (re)implementing / migrating such backup in Grid Control.
I personally prefer to maintain the backup management in Grid Control, but a colleague wants now to go back to the batch files.
What i am looking for here, are advices in the management of RMAN backup for multiple databases: do you guys use Grid Control or any third-party backup management tool or even got your home-made solution?
One of the discussion topic is the work involved in case that the central backup location changes.
Well... any real-life advices on best practices / strategies for RMAN backup management for many databases will be appreciated!
Thanks,
Thierry

Hi Thierry,
Thierry H. wrote:
Thanks for your reaction.
So, i understand that Grid Control is for you not used to manage the backups, and as a consequence, you also have no 'direct' overview of the job schedules.
One of my concern is also to avoid that too many backups are started at the same time to avoid network / storage overload. Such overview is availble in Grid Control's Jobs screen.
And, based on your strategy, do you recreate a 'one-time' Oracle scheduled job for every backup, or do your scripts create an Oracle job with multiple schedule?
You're very welcome!
Well, Grid Control is not an option for us, since each customer is in a separate infrastructure, and with their own licensing. I have no real way (in difference to your situation) to have a centralized point of control, but that on the other hand mean that I don't have to consider network/storage congestion, like you have to.
The script is run from a "permanent" job within the dba-scheduler, created like this:
dbms_scheduler.create_job(
        job_name        => 'BACKUP',
        job_type        => 'EXECUTABLE',
        job_action      => '/home/oracle/scripts/rman_backup.sh',
        start_date      => trunc(sysdate)+1+7/48,
        repeat_interval => 'trunc(sysdate)+1+7/48',
        enabled         => true,
        auto_drop       => false,
        comments        => 'execute backup script at 03:30');and then the "master-script", determines which level to use, based on weekday from the OS. The actual job schedule (start date, run interval etc) is set together with the customer IT/IS dept, to avoid congestion on the backup resources.
I have no overview of the backup status, run times etc, but have made monitoring scripts that will alert me if/when a backup either fails, or runs for too long. This, in addition with scheduled disaster/recovery tests makes me sleep rather well at night.. ;-)
I realize that there (might be) better ways of doing backup scheduling in your environment, since my requirements are so completely different than yours, but I guess that we all face the same challenges in unifying the environments as much as possible, to minimize the amount of actual work we have to do. :-)
Good luck!
//Johan

RMAN Backup script for RAC Database..please suggest

Hi All,
I am currently working on backup policy for RAC Database for my client.The client requirement is to backup while database is shutdown(mount state).I have made below script and could any one please suggest what further things should I need to add with below rman script.
echo "Shutdown Database";date
srvctl stop database -d PROD
srvctl status database -d PROD
echo "Database shutdown on";date
echo "Mount Database ";date
srvctl start instance -d PROD -i "PROD1" -o mount
srvctl status database -d PROD
echo "Start Full Database Backup on";date
$ORACLE_HOME/bin/rman target / nocatalog <<EOF
configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to '/BACKUP/PRODBKP/%F';
run{
allocate channel c1 device type disk connect 'sys/******@node1-vip:1521/PROD';
allocate channel c2 device type disk connect 'sys/*****@node2-vip:1521/PROD';
backup format '/BACKUP/PRODBKP/PROD_df_%t_%s_%p.bak'(database);
backup format '/BACKUP/PRODBKP/archive_%t_%s_%p.bak' archivelog all;
copy current controlfile to '/BACKUP/PRODBKP/PROD.ctl';
delete noprompt obsolete;
release channel c1;
release channel c2;
exit
EOF
echo "RMAN Backup Finished on";date
echo "Shutdown Database";date
srvctl stop database -d PROD
echo "Start Database";date
srvctl start database -d PROD
srvctl status database -d PROD
Please share your experiences.
Regards

Hi,
Some tweaks for your script.
echo "Shutdown Database";date
srvctl stop database -d PROD
srvctl status database -d PROD
echo "Database shutdown on";date
echo "Mount Database ";date
srvctl start instance -d PROD -i "PROD1" -o mount1. If you database does not shutdown properly , does your script stops the execution of next step?
2. configure controlfile autobackup on;
configure controlfile autobackup format for device type disk to '/BACKUP/PRODBKP/%F';(Why you need to configure this every time) ?
It's persistent at db level one time setting (until some other script changes the settings by other dba - else remove that - set the configuration at db level once for all)
- Pavan Kumar N
3.

RMAN backup in ORACLE RAC database

Hi there,
We are using RMAN backup strategy for taking backups from one node(eg.node1).Database is RAC database, version 9.2.3. and OS is Solaris 5.10.
this is the configuration which we use, as follows:
Connecting to Prod.Database using catalog database.
rman catalog=rman/rman@CATDB target=sys/oracle@PRODDB(node 2).
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 30;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rmanback/_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 5;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/rmanback/CMWPROD_%s.bak';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT 'SYS/oracle@PRODDB(node2)';
CONFIGURE MAXSETSIZE TO 7 G;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/9.2.3/dbs/snapcf_CMWPROD1.f';
As the above config shows RMAN is connecting to PROD DB (node 2). But we need to take backups (datafiles and as well as archive logs) from two nodes (i.e from node 1 and as well as node 2).
Is there any possibility for taking backups from two nodes?
Thanks,
Balu.

Duplicate thread
RMAN configuration in ORACLE RAC database
Khurram

Rman backup on physical standby database without cancelling MRP

Hi all,
Could anyone share, is this possible to take RMAN backup on physical standby database without cancelling MRP process.
regarrds,

Hi,
On Standby Side:
SQL> alter database mount;
Database altered.
SQL> alter database recover managed standby database using current logfile disconnect from session;
Database altered.
SQL> select max(Sequence#) from v$archived_log;
MAX(SEQUENCE#)
        405
SQL> select max(Sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
        404
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@oel62-x64 Desktop]$ rman target /
Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:31:43 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ADMDB (DBID=4063877183, not open)
RMAN> backup database plus archivelog delete all input;
Starting backup at 21-MAY-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=32 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=390 RECID=391 STAMP=815416638
input archived log thread=1 sequence=391 RECID=392 STAMP=815421952
input archived log thread=1 sequence=392 RECID=393 STAMP=815422343
input archived log thread=1 sequence=393 RECID=394 STAMP=815422434
input archived log thread=1 sequence=394 RECID=395 STAMP=815422570
input archived log thread=1 sequence=395 RECID=396 STAMP=815476598
input archived log thread=1 sequence=396 RECID=397 STAMP=815476615
input archived log thread=1 sequence=397 RECID=398 STAMP=815476645
input archived log thread=1 sequence=398 RECID=399 STAMP=815477471
input archived log thread=1 sequence=399 RECID=400 STAMP=815477475
input archived log thread=1 sequence=400 RECID=401 STAMP=815477628
input archived log thread=1 sequence=401 RECID=403 STAMP=815584146
input archived log thread=1 sequence=402 RECID=402 STAMP=815584137
input archived log thread=1 sequence=403 RECID=405 STAMP=816017446
*input archived log thread=1 sequence=404 RECID=404 STAMP=816017444*
*input archived log thread=1 sequence=405 RECID=406 STAMP=816017455*
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T153202_8spm937d_.bkp tag=TAG20130521T153202 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07
channel ORA_DISK_1: deleting archived log(s)
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_390_8s48hfrp_.arc RECID=391 STAMP=815416638
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_391_8s4fohwb_.arc RECID=392 STAMP=815421952
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_392_8s4g1q0v_.arc RECID=393 STAMP=815422343
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_393_8s4g4l8z_.arc RECID=394 STAMP=815422434
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_394_8s4g8t9h_.arc RECID=395 STAMP=815422570
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_395_8s631622_.arc RECID=396 STAMP=815476598
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_396_8s631qjj_.arc RECID=397 STAMP=815476615
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_397_8s632od8_.arc RECID=398 STAMP=815476645
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_398_8s63whqc_.arc RECID=399 STAMP=815477471
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_399_8s63wly4_.arc RECID=400 STAMP=815477475
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_400_8s641d8j_.arc RECID=401 STAMP=815477628
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_16/o1_mf_1_401_8s9d21jk_.arc RECID=403 STAMP=815584146
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_16/o1_mf_1_402_8s9d1skv_.arc RECID=402 STAMP=815584137
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_403_8spm6p4h_.arc RECID=405 STAMP=816017446
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_404_8spm6mqj_.arc RECID=404 STAMP=816017444
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_405_8spm6yg0_.arc thread=1 sequence=405
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T153213_8spm9fnc_.bkp tag=TAG20130521T153213 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:15
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T153213_8spmfqxf_.bkp tag=TAG20130521T153213 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
Finished backup at 21-MAY-13
RMAN> exit
Recovery Manager complete.
[oracle@oel62-x64 Desktop]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Tue May 21 15:34:42 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select max(Sequence#) from v$archived_log;
MAX(SEQUENCE#)
        405
SQL> select max(Sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
        404
SQL> There have no problem, backup database when MRP is running. But if you want delete, then you are getting RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process.
And will not delete this archived log, because it is needed for standby or upstream capture process.
Updated
When MRP stoped
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@oel62-x64 Desktop]$ rman target /
Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:46:07 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ADMDB (DBID=4063877183, not open)
RMAN> backup database plus archivelog delete all input;
Starting backup at 21-MAY-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=24 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=405 RECID=406 STAMP=816017455
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T154617_8spn3s9w_.bkp tag=TAG20130521T154617 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_405_8spm6yg0_.arc RECID=406 STAMP=816017455
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T154618_8spn3v4f_.bkp tag=TAG20130521T154618 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:16
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T154618_8spn6779_.bkp tag=TAG20130521T154618 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
Finished backup at 21-MAY-13
RMAN> Apply process is stopped and new redo received from primary.
SQL> select max(Sequence#) from v$archived_log;
MAX(SEQUENCE#)
        407
SQL> select max(Sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
        405
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@oel62-x64 Desktop]$ rman target /
Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:49:28 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ADMDB (DBID=4063877183, not open)
RMAN> backup database plus archivelog delete all input;
Starting backup at 21-MAY-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=32 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=406 RECID=407 STAMP=816018527
input archived log thread=1 sequence=407 RECID=408 STAMP=816018530
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T154937_8spnb1y3_.bkp tag=TAG20130521T154937 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_406_8spn8hkn_.arc thread=1 sequence=406
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_407_8spn8l69_.arc thread=1 sequence=407
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T154939_8spnb3f5_.bkp tag=TAG20130521T154939 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:15
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T154939_8spndhly_.bkp tag=TAG20130521T154939 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
Finished backup at 21-MAY-13
RMAN> I think, codes is understandable.
Regard
Mahir M. Quluzade
Edited by: Mahir M. Quluzade on May 21, 2013 3:36 PM

Rman backup size for Dr db is very much higher than that of primary db

Hi All,
My production database on Oracle 10.2.0.4 had a physical size of 897 Gb and logical size of around 800 Gb.
Old tables were truncated from the database and its logical size got reduced to 230 Gb.
Backup size is now 55Gb which used to be of 130 Gb before truncation.
Now this database has a DR configured. Backup of this DR database is daily taken which is used to refresh test environments.
But the backup size for DR database has not decreased. The restoration time while refreshing test environments is also same as before.
We had predicted that the backup size for DR database will also decrease and hence reducing the restoration time.
We take compressed RMAN backup.
What is the concept behind this?

When you duplicate a database it will restore all the datafiles from the RMAN backup. You will find the physical space of your source database. Remove the fragmented space using object movement. Then shrink the tablespaces and take fresh RMAN backup and restore.
Regards
Asif Kabir

RAC RMAN BACKUP Recovery FOR Oracle APPS Application

Hi,
We have an Application which is similar to Oracle APPs application and We have a RAC Database at Backend.
As I am a Oracle RAC DBA and never worked as an Oracle apps DBA.
Each Week or month We have to deploy a patch on Our Database which are kind of sql changes to Database and before we applying we need to backup our Database.
I am very comfortable while applying patches on Single instance Database:-
I Usually shutdown my database and backing up My Database(Conistent\cold Backup) before applying patch.
and I have a Flash back on both option I am having for my Database.
Problem:-
But in Production I have RAC Database, on which I already configured Hot Backup.
FlashBackup Feature is there with me, but Not reliable.
I want cold backup along with my existing hot backup, and want to restore same if something goes wrong.
Since ASM is configured so we have only option RMAN backup.
IF possible kindly Share your knowledge and Experience of your to handle Such Problem.

Sir,
RMAN is already configured for backing up database online.
My only intention is to have cold or consistent backup before applying application patch, So that at the time of crisis I will resotre my Cold/Conistent backup.
Because I am using 11gr2 RAC with ASM, so only option is there for me to use rman as backup tool.
But I never tried to Have Cold backup in RAC environment in my previous jobs, and I am new to this Oracle APPS DBA technology. So Here I am looking for a Strategy that Normally oracle apps dba use while applying patch to Oracle Database and kind of backup strategy they use.
Regards
Gaurav

Estimating the backup size for full database backup?

How to estimate the backup file size for the following backup command?
Oracle 10g R2 on HPUX
BACKUP INCREMENTAL LEVEL 0 DATABASE;
Thank you,
Smith

Depends on the number of used blocks, block size etc. You could probably get a rough formula for backup size based on the contents of dba_tab_statistics (subtract empty_blocks), dba_ind_statistics etc.

Restoring a RMAN backup to a new database instance

Hi Mates,
I have an issue with restoring a RMAN backup that i have with me to a new database instance. What i have with me are:
1. Backup of SPFile. (O1_MF_NCNNF_CTLFILE_BU_92DVGYO2_.BKP)
2. Backup of Control file (O1_MF_NNSNF_SPFILE_BU_92DVGW9H_.BKP)
3. Full database backup (O1_MF_NNSNF_FULLPROD_BU_92DVGW9H_.BKP)
I have received these files from a customer environment and I need to restore these to a new database instance in a local machine. I have given a attempt as follows (in Oracle 10g):
1, Created a new database instance (Test75) using Oracle Database Configuration Assistant
2. SET ORACLE_SID = Test75
3. Connected to this instance using RMAN
4. Tried to restore the SPFILE from the received BKP file.
I am getting errors and cannot proceed. I am not sure whether I am executing the correct steps. Please help me out by telling me how should I achieve this.
Thank you.

1. Backup of SPFile. (O1_MF_NCNNF_CTLFILE_BU_92DVGYO2_.BKP)
2. Backup of Control file (O1_MF_NNSNF_SPFILE_BU_92DVGW9H_.BKP)
The first backuppiece looks like a ControlFile and the second one looks like an SPFILE'
>I am getting errors and cannot proceed
What is the error ? (I assume that you tried to restore the SPFILE from O1_MF_NNSNF_SPFILE_BU_92DVGW9H_.BKP
Note that you also have to SET DBID before you restore the controlfile
Hemant K Chitale

Why cannot find data movement for clone database option on OEM 11gr2

Hi Expert,
I have Oracle 11gr2 11.2.3 normal OEM install to monitor our RAC database. When i go click data movement option, i can't find the clone database option. Any idea why ? Thanks

Hi;
Similar question mention in below links:
Clone Database: Select Destination in OEM 10g Database Control
Also see:
http://www.stanford.edu/dept/itss/docs/oracle/10g/em.101/b12016.pdf << part 6-6
Regard
Helios

RMAN Backup specially for tablespaces

Hi@everybody,
we have a Oracle 11gR2 (11.2.0.3.0) Server, based on RedHat 6, running in our company. For the Backups i'm using RMAN with a script. In that script this code specially creates the backup:
        run {
            allocate channel oem_backup_disk1 type disk;
            backup incremental level ${level} cumulative as COMPRESSED BACKUPSET tag '${tag}' database;
            backup as COMPRESSED BACKUPSET tag '${tag}' archivelog all not backed up;
            release channel oem_backup_disk1;
${level} is for 0 or 1, full backup or incremental backup. ${tag} is the name for the backup. This script is for the hole database. But now i want to change that script to tablespace level. We have some "test" tablespaces, where a backup is not needed. I just found that one:
backup tablespace TEST tag='BACKUP_TEST';
But now i'm not shure how i can implement that into my script.
Can you guys help me?
Thanks and best regards,
David

I've just to ask again to understand it right:
In RMAN - Console i just exclude the tablespaces that should not be backed up with:
CONFIGURE EXCLUDE FOR TABLESPACE Tbs1, tbs2, tbs5;
And then RMAN knows, when he is doing a backup of the database, he will exclude that tablespaces that i've told him? Thats awesome! And easier to handle!
EDIT: I've tested this on my Oracle Test server and it works! Thanks a lot for the answers!

Backup politics for one database

Hi,
We have an Oracle database. We do cold backup at interval of one month. After we do cold backup we delete from archives. We do full backup (level 0) with rman at interval of one week. When we do full backup with rman to do backup also at archives? On which period. Maybe we will do also a daily backup with rman.
Thank you,
Mihaela

i apologize in advance...i think i missed something here.
is your database running in archivelog mode? if so, the cold backup may be completely irrelevant -- although i have seen it stored offsite for accounting systems and some internal requirement that it be the quiesced database for that exact point in time. the problem with a cold backup is that it is specific to a point in time and unless something has changed, you can't roll it forward the way that you can with an online backup. which again, makes it good for some bean counter activities but not so good for your day to day activities.
you are running the rman level 0 once a week -- so then you must be running in archivelog mode. you need to keep those archivelogs either on disk or moved to tape or some other storage media; rman cuts one during the backup and you definitely need that one. if you take say an incremental 1 daily or so, the number of archive logs you need to maintain may be fewer, but you still need some to recover your database in the event of recovery.
hth

What is the best backup plan for Archive Databases in Exchange 2013?

Hi,
We have Exchange 2013 with Hybrid setup with O365.
We have On premise exchange 2013 servers with 3 copies of primary Database & Single Copy of Archival DBs.
Now we have to frame backup policy with Symantec Backup Exec which has to backup our primary & Archival DBs
In 2007 exchange, before migration to 2013, we had policy of DBs - Weekly Full backup & Monthly Full Backup
Please suggest what would be the best possible backup strategy we can follow with 2013 DBs.
That too, especially for Archiving DBs
Our Archiving Policy are - 3 category - Any emails older than 6 month OR 1 Year OR 2 Year should go to Archive mailbox.
Keeping this in mind how to design the backup policy ?
Manju Gowda

Hi Manju,
you do not find best practice different from the common backup guidelines, as there is no archive db specific behaviour. Your users may move items to their archive at any time as well as your retention policies may move items that machted the retention policies
at any time. The result is frequently changing content to both, mailbox and archive mailbox databases, so you need to backup both the same way. You also may handle archives together with mailboxes together in the mailbox db
Please keep in mind that backup usually means data availability in case of system failure. So you may consider to do a less frequent backup with your archive db with dependency to the "keep deleted items" (/mailboxes) setting on your mailbox database.
Example:
keep deleted items: 30 days
backup of archive db: every 14 days
restore procedure:
* restore archive DB content
* add difference from recover deleted items (or Backup Exec single item recovery) for the missing 14 days.
So it depends more on your process than on a backup principle.
Regards,
Martin

How to make and schedule backup tasks for MySQL Databases

Has NSS 322 this functionality? If not, are there any packages to do dat? I can´t see the folders that contain MySQL Databases, so I can´t backup them.
Many thanks in advance for your support.

All of the MySQL databases are visable within the phpMyAdmin application. phpMyAdmin can export, import, manage the databases directly.
To use the remote replication feature from the GUI, you need the databases visible in a share. I'm sure that is possible through the CLI, but I'm not able to tell you how to do it. Maybe someone else on the forum can help provide a solution.
You can also use the rsync command in the CLI directly.
Did you find any ideas on the phpMyAdmin website? This must be a common task that someone has worked out a solution for.

Backup solution for E- Business Suite

Hi all,
We have Oracle application and database deployed to a single server, whilst running a server on Oracle Entreprise Linx on 64 bit and running oracle R12.
Therefore basically I see 03 root folders in my server in my Oracle folder namely,
[oracle@test lab01]$ ll
total 12
drwxr-xr-x 4 oracle dba 4096 Jun 24 15:07 apps
drwxr-xr-x 4 oracle dba 4096 Jun 24 15:07 db
drwxr-xr-x 3 oracle dba 4096 Jun 24 15:06 instSo far as my backup solution I am planning to have:
- RMAN backup solution for the database which is represented by the DB folder
- OS tar command" to copy the Oracle application which is represented by the apps* folder --> correct me if I am wrong, I am not sure...
- I am not sure what is the function of the INST folder and what is the best way of backing it up.
Thanks and Regards,

Hi,
- RMAN backup solution for the database which is represented by the DB folder Correct.
- OS tar command" to copy the Oracle application which is represented by the apps* folder --> correct me if I am wrong, I am not sure...Correct.
- I am not sure what is the function of the INST folder and what is the best way of backing it up.Please refer to the "Oracle Applications Concepts" manual for details about the INST folder.
You need to use the OS command to backup this top, just the same way you back up the application tier node files.
Oracle Applications Concepts
http://download.oracle.com/docs/cd/B53825_03/current/acrobat/121oacg.pdf
Thanks,
Hussein

RMAN backups valid for clone database.

Similar Messages

Maybe you are looking for