Backups on ASM

Similar Questions

• Backup the ASM itsself

  Hello

  I have just setup an ASM instance.

  Referring to my Docs as DBA2 training I get this message:
  There is a process of ARC redolog backup information, known as an instance of database.

  However, the manual also says "there is that no BUFFER in SGA and ASM does not use online redo logs. LGWR writes the information to an ASM Diskgroup".

  Now I'm a little confused:

  Does make sense to put the instance ASM itself in archivelog one mode run backups via RMAN?

  Or should I use md_backup instead?

  Concerning

  Christian

  11 GR 2

  If there ANY configuration changes - vote data disk is automatically saved in the OCR.

  BACKUP OF THE OCR IS AUTO-

  one) oracle Clusterware (CRSD) automatically creates backups of OCR every 4 hours.

  (b) a backup is created for each full day.

  (c) a backup is created at the end of each week.

  (d) oracle database retains the last three copies of OCR.

  But you can also make manual backups

  Example:

  To display the backup, type the commands: ocrconfig - showbackup

  Perform a manual backup: ocrconfig - manualbackup

  Logical backup: #ocrconfig-/home/oracle/ocr.backup export

  Backup only manual display: ocrconfig - showbackup manual

  The RSC (Oracle registry Local) location: #ocrcheck - local

  Logical backup of OLR: ocrconfig-local - export /... /OLR. Backup

• Backup RMAN ASM filesystem

  Hi all
  
  I have an rman backup (datafile and controlfile) who got caught in an instance of the DSO (not a RAC) ORACLE 11.2.0.2 on a server Linux, now I want to restore the backup into a new database under windows/Linux OS with storage system (single instance RDBMS) General files instead of ASM.
  
  Is this possible?
  
  I can restrore an rman backup ASM in a mechanisim of storage of file in a new server system?
  
  Please clarify my question.
  
  Thanks in advance...
  
  Nonuday

  Nonuday wrote:
  Hi Levi,

  Thank you for your invaluable script and the blog.

  can you tell me about this query:

  I have an RMAN backup, drawn from the ASM and the backup is the database and controlf backup file that contains the data files and controlfiles.
  Now I need to restore this on my system and here I only use ASM or archive log, I use only one instance in any database log mode archive.

  I restored the backup controfile RMAN control file.
  Before you restore the control file, I checked the pfile orginal of the backup of database with parameters such as
  "db_create_file_dest."
  "db_create_online_log_dest,"
  "db_recovery_file_dest_size."
  "db_recovery_dest,"
  'log_archive_dest '.

  Since I'm not gng to create a database in any mode of newspaper archive, I do not use any of the above parameters and created a database.

  Now my question is:
  If I restore the database and the data file get restored and after rename all the log files, the database will be open.

  I want to know if this is good or bad, and the database will work as he previously worked. Or need to create the db_file_recovery and also other settings for this database.

  All parameter:
  All these settings should reflect your current environment, any reference to the old environment must be changed.

  All file system used:
  No matter what you use the file (datafile/redolog/controlfile/archivelog/backuppiece) file system are created on binary Format that depend only on platform. Thus, the file binary (for example datafile) have same format and content on the device gross, ASM, ext3, ext2 and so on. Thus, for the database, it is just a place where the files are stored, but the file are the same. ASM has a different architecture of the regular file system and must be managed differently (IE with RMAN).

  On the database:
  Given that your database files are the same even different file system using what you need is rename your files from data/redofiles on controlfile during the restoration, the redo files will be recreated.
  So, no matter if your database are noarchivelog or archivelog, in the same way you do a restore on ASM is the same way to restore the regular file system. (just rename the database during restore controlfile)

  On blog post 'How to migrate all files on ASM to no - ASM (Unix/Linux)' is suddenly of system files to another folder. But you can change the script used for restore purposes;

  ## set newname tell to RMAN where file will be restored and keep this files location on memory buffer
  RMAN> set newname for datafile 1 to ;
  
  ### swich get list of files from memory buffer (rman) and rename on controlfile the files already restored.
  RMAN>switch datafile/tempfile all ;
  

  With mounted database, use this script below:

  I just commented on three lines that are not necessary in your case.

  SET serveroutput ON;
  DECLARE
    vcount  NUMBER:=0;
    vfname VARCHAR2(1024);
    CURSOR df
    IS
      SELECT file#,
        rtrim(REPLACE(name,'+DG_DATA/drop/datafile/','/u01/app/oracle/oradata/drop/'),'.0123456789') AS name
      FROM v$datafile;
    CURSOR tp
    IS
      SELECT file#,
        rtrim(REPLACE(name,'+DG_DATA/drop/tempfile/','/u01/app/oracle/oradata/drop/'),'.0123456789') AS name
      FROM v$tempfile;
  BEGIN
  --  dbms_output.put_line('CONFIGURE CONTROLFILE AUTOBACKUP ON;'); ### commented
    FOR dfrec IN df
    LOOP
      IF dfrec.name  != vfname THEN
        vcount      :=1;
        vfname     := dfrec.name;
      ELSE
        vcount := vcount+1;
        vfname:= dfrec.name;
      END IF;
    --  dbms_output.put_line('backup as copy datafile ' || dfrec.file# ||' format  "'||dfrec.name ||vcount||'.dbf";');  ### commented
    END LOOP;
    dbms_output.put_line('run');
    dbms_output.put_line('{');
    FOR dfrec IN df
    LOOP
      IF dfrec.name  != vfname THEN
        vcount      :=1;
        vfname     := dfrec.name;
      ELSE
        vcount := vcount+1;
        vfname:= dfrec.name;
      END IF;
      dbms_output.put_line('set newname for datafile ' || dfrec.file# ||'  to  '''||dfrec.name ||vcount||'.dbf'' ;');
    END LOOP;
    FOR tprec IN tp
    LOOP
      IF tprec.name  !=  vfname THEN
        vcount      :=1;
        vfname     := tprec.name;
      ELSE
        vcount := vcount+1;
        vfname:= tprec.name;
      END IF;
      dbms_output.put_line('set newname for tempfile ' || tprec.file# ||'  to  '''||tprec.name ||vcount||'.dbf'' ;');
      END LOOP;
        dbms_output.put_line('restore database;');
      dbms_output.put_line('switch tempfile all;');
      dbms_output.put_line('switch datafile all;');
      dbms_output.put_line('recover database;');
      dbms_output.put_line('}');
   ---   dbms_output.put_line('alter database open;');  ### comented because you need rename your redologs on controlfile before open database
      dbms_output.put_line('exit');
  END;
  /
  

  After the restoration, you must rename your redologs on controlfile to old location to the new location:

  for example

  ##  use this query to get current location of redolog
  SQL>  select group#,member from v$logfile order by 1;
  
  ## and change from  to 
  
  SQL > ALTER DATABASE
    RENAME FILE '+DG_TSM_DATA/tsm/onlinelog/group_3.263.720532229'
             TO  '/u01/app/oracle/oradata/logs/log3a.rdo'  
  

  When you change all the redolog on question below controlfile command:

  SQL> alter database open resetlogs;
  

  PS: Always follow the database in real time using the alert log database file.

  HTH,
  Levi Pereira

• Restore backup no - ASM (OMF) database to database ASM.

  All,
  
  I have a database with OMF files and a request for this restore a database with ASM. The two databases are 11.2 running on Linux. I went through the backup and Recovery Guide (RMAN) and the most appropriate section ' Chp 21: recovery of the database: advanced scenarios does not address this scenario exactly and if I need to check the following steps are correct:
  
  Background:
  
  Source DB (hosta):
  =========
  =========
  
  RMAN > outline report
  2 >.
  
  Report of the schema of the database database with db_unique_name ORAPROD
  
  List of permanent data files
  ===========================
  Size (MB) Tablespace RB segs Datafile file name
  ---- -------- -------------------- ------- ------------------------
  1 800 SYSTEM * /u03/oradata/DEVODS/datafiles/system.260.727642227
  SYSAUX 2 940 * /u03/oradata/DEVODS/datafiles/sysaux.265.727642227
  3 20480 UNDOTBS1 * /u03/oradata/DEVODS/datafiles/undotbs1.264.727642227
  
  ... etc... etc. (all files are in the same location)
  
  
  On the DB (hostb) target:
  =========
  =========
  
  RMAN > outline report;
  
  Report of the schema of the database database with db_unique_name ORAPROD
  
  List of permanent data files
  ===========================
  Size (MB) Tablespace RB segs Datafile file name
  ---- -------- -------------------- ------- ------------------------
  1 800 SYSTEM * +DISKGROUP1/devods/datafile/system.260.727642227
  SYSAUX 2 800 * +DISKGROUP1/devods/datafile/sysaux.265.727642227
  3 10240 UNDOTBS1 * +DISKGROUP1/devods/datafile/undotbs1.264.727642227
  
  ... etc... etc. (all files are in the same location)
  
  MEASURES FOR RESTORATION
  ----------------------------
  1. define the DBID and start the instance of database without editing the database.
  
  For example, run SET DBID to identify the DBID, then run STARTUP NOMOUNT:
  SET DBID < dbid >;
  STARTUP NOMOUNT
  
  RMAN will fail to find the settings, which has not yet been restored file server.
  but starts the instance with a "dummy" file
  
  It is here where I'm not clear on what to do *.
  
  2 restore spfile
  
  RUN
  {
  ALLOCATE CHANNEL c1 DEVICE TYPE dDISK;
  GAME CONTROLFILE AUTOBACKUP FORMAT for DEVICE TYPE DISK TO ' / tmp/%F'(? this would be the location of the RMAN backup?)
  RESTORE SPFILE
  TO PFILE '? / oradata/test/inittrgta.ora'
  BACKUP AUTOMATIC;
  ASIDE THE JUDGMENT;
  }
  
  3. change the settings of restored initialization file.
  Change any setting precise location, for example, those ending with dest, to
  reflect the new directory structure. For example, change the following parameters:
  -IFILE
  -LOG_ARCHIVE_DEST_1
  -CONTROL_FILES
  
  4 restart the instance with initialization parameters file edited.
  For example, enter the following command:
  STARTUP NOMOUNT PFILE='?/oradata/test/inittrgta.ora FORCE';
  
  5.
  Restore the control file from an automatic backup and then mount the database.
  For example, enter the following command:
  RUN
  {
  ALLOCATE CHANNEL c1 DEVICE TYPE DISK;
  RESTORING AUTOMATIC BACKUP CONTROLFILE; ( ??? How RMAN know the location of the backup in order to restore the controlfile?)
  ALTER DATABASE MOUNT;
  }
  
  =======================================
  
  If I can be guided to make the 5 steps above correctly, I think I can do the rest myself.
  
  Thanks in advance to anyone who helps.
  
  Concerning

  Do you need to duplicate the database or move to ASM? If you need move to ASM, try using the following procedure http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmasm.htm#i1016547

• Backup no - asm ASM

  Hello I am a compress backup my database rac (asm) and I want to restore it to my no - asm database,
  
  
  When I try to restore it, it shows me paths diskgroup that I try to use db_file_name_convert and db_log_file_convert, that it did not work.
  while I was taking backup I use this script
  RMAN target / nocatalog < < EOF
  Run {}
  allocate channel c1 type disk;
  allocate channel c2 type disk;
  allocated channel c3 type disk;
  allocate channel c4 type disk;
  allocate channel c5 type disk;
  full backup as compressed backupset
  format ' / backup/%d_%Y%M%D_t%t_s%s_p%p.rman'
  (database);
  output channel c1;
  output channel c2.
  output channel c3.
  output channel c4.
  output channel c5;
  }
  COPY CURRENT CONTROLFILE to ' / backup/%d_%Y%M%D_t%t_s%s_p%p.ctl.rman';
  
  output
  EXPRESSIONS OF FOLKLORE

  Hello

  Stop and start to mount the target database, perhaps the former setting are still in memory.

  This is not the script backup that is the problem, but certainly the script and restore/recovery files.

  device type disk level backup incremental 0 as the format of database copy tag "ASM_MIGRATION" "+ DATPRPROD2";

  make the changes, the temp, the lof archive file dest
  In pfile:
  db_create_file_dest
  db_recovery_file_dest
  control_files
  Log_archive_dest
  ...

  backup incremental level 1 to retrieve the copy with the tag "ASM_MIGRATION" database.
  retrieve the copy of the database with the tag "ASM_MIGRATION".
  ALTER database backup controlfile 'path ';

  stop immediately;
  startup nomount;

  RMAN
  target connection.
  Connect catalog rman/password@catalog
  Restore controlfile from "path."
  change the editing of the database;
  switch database to copy;
  recover the database;

• Backup of ASM

  If I activate the area of flash as an ASM filesystem recovery, but these files backup cannot be accessed by the operating system, so how is it possible to copy these backup files the ASM-based band cartrdge move, ulimately, I have to use the command copy os, OS can't read what ASM base backup piece.

  Do you want to backup 'flashback file' on ASM?

  I don't know.
  But... If you use asm on the 11g version, you can back up ASM on the local drive before and then tape backup.

  Example:
  $ asmcmd

  ASMCMD > cp file01.txt /tmp/
  copy +Vol1/db/file01.txt-> /tmp//file01.txt

  ;)

• backup of the asm instance

  Hello
  
  It is necssary to backup ASM instance? If Yes, then how to backup asm instance.if not, then what will happen
  
  If my server goes down, then hw can retrieve my asm instance.
  
  Concerning

  Dear user13367819,

  Please visit the following links. I hope that they will guide you;

  Data Instance ASM, rman backup files
  http://dbaspot.com/forums/Oracle-Server/64961-how-backup-ASM.html
  http://www.appsinsight.NET/2008/05/02/how-to-backup-Oracle-ASM-instance-using-RMAN-on-IBM-platform/

  Kind regards.

  Ogan

• Need best practices PROCESS for scheduling backups RMAN.

  Hi all

  I would like a suggestion on what follows for RMAN backups:

  Details:

  Database:-11 GR 2, size 3 TB on ASM - DW database.

  As suggestions on:

  (1) what kind of backups for plan - additional as well as backups of block?

  (2) can size necessary to allocate space for backup - one ASM or disk space?

  (3) anything else - please suggest.

  Thank you.

  Thanks Hemant, this is very useful for me - the explanation is clear and understandable.

  Thank you!

• RMAN to the ASM and network file system

  Hi all
  
  I use Oracle RAC 11 g R2 + ASM.
  I am new to RMAN, but I am trying to build daily tasks to do below:
  
  1. backup of my database to the FRA located on ASM diskgroup + FRA.
  2. at the same time I want to save my database for Network File System (NFS) to be taken by system administrators to an archive location that I can't access. Since according to my knowledge can't copy files to ASM for outside... so for this I'm planing to use the command format of the NFS mount point.
  3. on daily basis in the NFS file will be taken by a work (that I am not responsible for) to the Archive, and then it will be purged from this location.
  4. I am planing to have my windows of 15 days retention strategy.
  5. on every day, I am planing to cross check my backup and then delete the expired so that taken from NFS in the journal of the archives is deleted.
  
  The RMAN I am planing to run it on a daily basis are:
  

  backup incremental level 0 cumulative device type disk tag 'FULL_DB_INCR_LV0' database; -- this will be to the default location (+FRA)
  backup incremental level 0 cumulative device type disk tag 'FULL_DB_INCR_LV0' database format 'NFS/oracle/backup%U';--another copy to be taken to the archive location
  crosscheck backupset;
  delete expired backupset; -- this will delete the backups taken to the Archive location

  Now my questions:
  
  1 what good solutions? take account of the fact that I need backup on the file system of the operating system so that the jobs of system administrators take the backup of their archives.
  2. If a backup is needed, I use CATALOGUE START WITH to recover and then recover.
  3. because my retention period is 15 days, and the backup in NFS files will be deleted on a daily basis, so this retention will apply for backups in ASM, is this a problem?

  Hello

  Easy way is to use the tag. Find the number of backupset is a difficult task.

  Create a template for your tag with a date.

  How to use the Substitution Variables of orders RMAN [427229.1 ID]

  How to use the tag name of RMAN with different attributes or variables. [580283.1 ID]

  You can check which backup doesn't have a copy on NFS using the query below:

  SELECT   BS.RECID BSKEY,
    BP.RECID KEY,
    BP.RECID RECID,
    BS.PIECES PIECECOUNT,
    BP.HANDLE FILENAME,
    BP.TAG TAG,
    BP.COPY# COPYNUMBER,
    BP.STATUS STATUS,
    BP.PIECE# PIECENUMBER
  FROM V$BACKUP_PIECE BP,
    V$BACKUP_SET BS
  WHERE (BP.SET_COUNT = BS.SET_COUNT
  AND BP.SET_STAMP    = BS.SET_STAMP)
  order by  bskey,copynumber
  

• Recovery of database production after a loss of database of Prod and SAN Server

  So, I was asked this morning... we can find our database if we lose the database server and the SAN.
  
  A bit of information:
  Database: 10 gr 2
  With the help of ASM
  Backup on ASM
  SAN is on-site
  
  My first reaction was of course we save at least twice a day, and then once a week pass these backups to an offsite location.
  
  Then I started to think about it anymore. If we lose the SAN we have backups off site of the SAN together once a week so we could recover the SAN. If we lose the server, we would lose starts where the backups are stored.
  
  So my question is... and don't laugh for me never to think before, please lol, but I have to backup ASM instance to restore ASM to be able to do my backups that are stored inside the ASM starts? If so should I make this old-school by stopping and it backup because there isn't any current archiving? If this isn't the case, anyone recommend a way to do this kind of thing?
  
  Thanks in advance
  Luke

  See Note MetaLink #333257.1.

  You can't save an ASM Instance. You must document your ASM starts separately. Metadata are on disk groups, so if lose you, you lose the metadata!

  11g ASM is supposed to have included a command to save the metadata.

  I suggest that you connect an SR asking for clarification on this note.

• Can store backups RMAN in a diskgroup in ASM?

  RDBMS version: 11.2.0.4

  OS: Oracle Linux 6.6

  RAC environment

  Can store backups RMAN in a diskgroup in ASM? If so, is it recommended?

  Yes, you can:

  CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '+diskgroupname';
  

  It depends on your requirements and backup strategy.

• ASM files using RMAN backupset backup system migration

  my script to backup daily as below

  backup in the format of compressed backupset "$BACKUP_DIR/db_%U" database

  backup current controlfile "$BACKUP_DIR/Cont_%U" format

  backup as backupset archivelog Tablet format all '$BACKUP_DIR/arch_%U ';

  It is possible to migrate the database ASM uses above backup backupset RMAN?

  because I restore the database is restored, the problem is when he try to recover it, unable to understand the archivelog and redlog files.

  Hello

  in fact, after I moved the pieces to another server and called with RMAN (including the archivelog files)

  1. When you have moved to another server, then at this stage - my hypothesis, you have restored the controlfile to fileystem and mounted

  2. as you said moved to another server, the parts are on file system or (ASM location - still the second server can see)? If your answer is no, when you catalog now, controfile must save it with the file system path but not ASM

  Note - If you're still see ASM path then. the migration of the ASM to no - asm (the steps are not correct) logically you went wrong and implementation/execution thrown.

  3. provide the plan and execution - what you did (while we can fix). To be honest, while on the move DB to non - asm, why you need first to recovery? Tell me about your backup procedure itself is gone bad.

  To be honest, you try to database host of ASM no - asm as backup in function (but no real process of moving).  Therefore, in spite of the use of rman backup in dual function duplication... you have implemented in the wrong approach.

  This is the reason why I have provided the link and examples to understand.

  Hope you understand now.

  -Pavan Kumar N

• Found backup files in ASM

  Hello

  I have a database in Oracle 11 g 2 and I installed Oracle Grid on Oracle Linux 5.9. I have discs of towing groups:

  /etc/init.d/oracleasm listdisks:

  flash_recovery_area

  DATA

  The first disc is mounted on/U01 and the second is mounted on /flash_recovery_area.

  The value of the fra parameters are in below:

  db_reovery_file_dest = / + flash_recovery_area

  db_reovery_file_dest_size = 30G

  When I want to connect to rman and get the current database backup, I can, but I can't find anything to /flash_recovery_area destination.

  can someone help me?

  Thank you

  Hello

  You are looking for in your previous comment and the output of the command ' RMAN > backup list; ', I can understand that your backup is located under the FLASH_RECOVERY_AREA disk group:

  List of backup sets

  ===================

  ....

  Time of accomplishment BS key Type LV size device Type elapsed time

  ------- ---- -- ---------- ----------- ------------ ---------------
  2 full 1.02 G DISK 00:00:09 31 March 15
  BP key: situation 2: AVAILABLE Tablet: NO Tag: TAG20150331T023932
  Name of the element:
  +FLASH_RECOVERY_AREA/ORCL/backupset/2015_03_31/nnndf0_tag20150331t023932_0.256.875759973
  List of files of data in backup set 2

  ....

  .....

  Time of accomplishment BS key Type LV size device Type elapsed time

  ------- ---- -- ---------- ----------- ------------ ---------------
  3 full 9.36 M DISK 00:00:00 31 March 15
  BP key: 3 location: AVAILABLE Tablet: NO Tag: TAG20150331T023947
  Name of the element:
  +FLASH_RECOVERY_AREA/ORCL/autobackup/2015_03_31/s_875759987.257.875759987

  ....

  ....

  Time of accomplishment BS key Type LV size device Type elapsed time

  ------- ---- -- ---------- ----------- ------------ ---------------
  4 whole 1.02 G DISK 00:00:07 31 March 15
  BP key: 4 location: AVAILABLE Tablet: NO Tag: TAG20150331T034834
  Name of the element:
  +FLASH_RECOVERY_AREA/ORCL/backupset/2015_03_31/nnndf0_tag20150331t034834_0.258.875764115
  List of files of data backup set 4

  Time of accomplishment BS key Type LV size device Type elapsed time

  ------- ---- -- ---------- ----------- ------------ ---------------
  5 whole 9.36 M DISK 00:00:00 31 March 15
  BP key: 5 location: AVAILABLE Tablet: NO Tag: TAG20150331T034841
  Name of the element:
  +FLASH_RECOVERY_AREA/ORCL/autobackup/2015_03_31/s_875764121.259.875764121
  SPFILE included: Modification Date: March 31, 15
  SPFILE db_unique_name: ORCL
  Control file included: cash SNA: 1103219 cash time: 31 March 15

  Time of accomplishment BS key Type LV size device Type elapsed time
  ------- ---- -- ---------- ----------- ------------ ---------------
  6 whole 1.02 G DISK 00:00:10 1 April 15
  BP key: 6 location: AVAILABLE Tablet: NO Tag: TAG20150401T021712
  Name of the element:
  +FLASH_RECOVERY_AREA/ORCL/backupset/2015_04_01/nnndf0_tag20150401t021712_0.260.875845033
  List of files of backup data the value 6

  Time of accomplishment BS key Type LV size device Type elapsed time

  ------- ---- -- ---------- ----------- ------------ ---------------
  7 full 9.36 M DISK 00:00:00 1st April 15
  BP key: 7 location: AVAILABLE Tablet: NO Tag: TAG20150401T021727
  Name of the element:
  +FLASH_RECOVERY_AREA/ORCL/autobackup/2015_04_01/s_875845047.261.875845047
  SPFILE included: Date of change: April 1, 15
  SPFILE db_unique_name: ORCL
  Control file included: cash SNA: 1108193 cash time: April 1, 15

  Time of accomplishment BS key Type LV size device Type elapsed time
  ------- ---- -- ---------- ----------- ------------ ---------------
  8 whole 1.03 G DISK 00:00:09 April 1, 15

  
  BP key: situation 8: AVAILABLE Tablet: NO Tag: TAG20150401T032943
  Name of the element:
  +FLASH_RECOVERY_AREA/ORCL/backupset/2015_04_01/nnndf0_tag20150401t032943_0.263.875849383
  List of files to backup set of 8 data

  ....

  .

  Time of accomplishment BS key Type LV size device Type elapsed time
  ------- ---- -- ---------- ----------- ------------ ---------------
  9 whole 9.36 M DISK 00:00:00 1st April 15
  BP key: 9 situation: AVAILABLE Tablet: NO Tag: TAG20150401T032958
  Name of the element:
  +FLASH_RECOVERY_AREA/ORCL/autobackup/2015_04_01/s_875849398.264.875849399
  SPFILE included: Date of change: April 1, 15
  SPFILE db_unique_name: ORCL
  Control file included: cash SNA: 1113472 cash time: April 1, 15

  Thus, your backup files are shown in the output above.

  And to archive them with command lines:

  $ . oraenv
  ---> +ASM
  $ asmcmd
  ASMCMD> ls -l  +FLASH_RECOVERY_AREA/orcl/backupset/2015_03_31/nnndf0_tag20150331t023932_0.256.875759973
  ASMCMD> ls -l +FLASH_RECOVERY_AREA/orcl/autobackup/2015_03_31/s_875759987.257.875759987
  ASMCMD> ls -l +FLASH_RECOVERY_AREA/orcl/backupset/2015_03_31/nnndf0_tag20150331t034834_0.258.875764115
  ....
  ....
  

  Best regards

• How to take database backup ASM/Instance?

  Hello
  
  I'm new with ASM. We take ASM/instance of database backup.
  
  can we have the idea to backup ASM?
  
  1. what components should be saved as database/Instance ASM / ASM all files?
  
  
  Please do the needful.
  
  Thank you
  Nitin

  Hello Nitin,

  First of all, you must understand that the RDBMS & ASM instance is different but yes, both are running on the same computer.

  ASM includes essentially two things: ASM instance (1) and the storage of the DSO (2).

  (1) ASM instance
  ------------------------

  That's just an instance when we do not backup but Yes if you want to keep the ASM instance configuration file then just follow these steps:

  [grid@host01 ~] $. oraenv
  ORACLE_SID = [+ ASM1]? + ASM1
  The basic Oracle for ORACLE_HOME=/u01/app/11.2.0/grid is/u01/app/grid

  SQL > create pfile='/home/grid/init+ASM1.ora' of spfile;

  Created file.

  (2) ASM STORAGE
  -------------------------

  -Storage ASM includes essentially ASM starts, namely new set of disks.

  -Whenever we do not create ASM diskgroup diskgroup contains still three things:

  (a) disc ASM
  (b) models and metadata
  (c) the ASM files (essentially datafile or all database files)

  -We take backup of two things on three things in ASM diskgroup:

  (1) ASM files - with RMAN because these are files of database.
  (2) ASM diskgroup models & metadata - with the MD_BACKUP of ASMCMD command.

  Now, MD_BACKUP will create a backup as your specified location file and this file will includes all models and metadata of the diskgroup. Benefits of taking diskgroup metadata are, if we lost the diskgroup, so we do not worry some details configuration command MD_RESTORE use to recreate the diskgroup with the same configuration. But remember that it does not restore the data file or any other file that was there on the diskgroup going to use RMAN to restore the missing files.

  See the example:

  ASMCMD > lsdg

  State Type sector Rebal to Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files name of the block
  EXTERN MOUNTED N 512 4096 1048576 11742 11643 0 11643 0 N ABC /.
  NORMAL CLIMB N 512 4096 1048576 15656 10661 1259 4701 0 N DATA.
  EXTERN MOUNTED N 512 4096 1048576 15656 13874 0 13874 0 N FRA.
  ASMCMD >
  >

  ASMCMD >/home/grid/data_backup_file - G DATA md_backup
  Group of disk to save metadata: DATA
  Path to current directory alias: cluster01
  Path to current directory alias: ORCL
  Path to current directory alias: ORCL/fichier_parametres
  Path to current directory alias: ORCL/DATA file
  Current directory alias path: cluster01/OCRFILE
  Path to current directory alias: ORCL/CONTROLFILE
  Path to current directory alias: ORCL/TEMPFILE
  Path to current directory alias: ORCL/ONLINELOG
  Current directory alias path: cluster01/ASMPARAMETERFILE
  ASMCMD >

  * vim # / home/grid/data_backup_file *.

  @diskgroup_set =)
  {
  "ATTRINFO"-ONLINE {}
  "MODEL. OCRBACKUP. REDUNDANCY '-ONLINE 18',
  "MODEL. FICHIER_PARAMETRES. MIRROR_REGION '-ONLINE '0',
  "MODEL. TEMPORARY FILE. REDUNDANCY '-ONLINE 18',
  "MODEL. TEMPORARY FILE. MIRROR_REGION '-ONLINE '0',
  "MODEL. FICHIER_PARAMETRES. REDUNDANCY '-ONLINE 18',
  "SECTOR_SIZE"-ONLINE '512',
  "MODEL. DATAGUARDCONFIG. REDUNDANCY '-ONLINE 18',
  ' ACCESS_CONTROL. UMASK '-ONLINE '066'.
  "MODEL. ASM_STALE. STRIPE '-ONLINE '0',
  "MODEL. ARCHIVELOG. STRIPE '-ONLINE '0',
  "MODEL. DATAGUARDCONFIG. PRIMARY_REGION '-ONLINE '0',
  "MODEL. OCRBACKUP. STRIPE '-ONLINE '0',
  "MODEL. DATA FILE. STRIPE '-ONLINE '0',
  "AU_SIZE"-ONLINE '1048576',
  "MODEL. ASMPARAMETERFILE. STRIPE '-ONLINE '0',
  "MODEL. TRACK CHANGES. PRIMARY_REGION '-ONLINE '0',
  "MODEL. CONTROLFILE. REDUNDANCY '-ONLINE 19',
  "MODEL. FLASHFILE. STRIPE '-ONLINE '0',
  "MODEL. BACKUPSET. PRIMARY_REGION '-ONLINE '0',
  "MODEL. ARCHIVELOG. PRIMARY_REGION '-ONLINE '0',
  "MODEL. TRACK CHANGES. STRIPE '-ONLINE '0',
  "MODEL. ONLINELOG. PRIMARY_REGION '-ONLINE '0',
  "MODEL. TRACK CHANGES. REDUNDANCY '-ONLINE 18',
  "MODEL. BACKUPSET. STRIPE '-ONLINE '0',
  "MODEL. OCRFILE. MIRROR_REGION '-ONLINE '0',
  "DISK_REPAIR_TIME' => '3.6 h."
  "MODEL. AUTOBACKUP. REDUNDANCY '-ONLINE 18',
  "MODEL. DUMPSET. REDUNDANCY '-ONLINE 18',
  "MODEL. RETURN OF FLAME. MIRROR_REGION '-ONLINE '0',
  "MODEL. DUMPSET. MIRROR_REGION '-ONLINE '0',
  "MODEL. DUMPSET. PRIMARY_REGION '-ONLINE '0',
  "MODEL. ASM_STALE. REDUNDANCY '-ONLINE 19',
  "MODEL. RETURN OF FLAME. PRIMARY_REGION '-ONLINE '0',
  "MODEL. CONTROLFILE. STRIPE '-ONLINE 1',
  "MODEL. DATA FILE. REDUNDANCY '-ONLINE 18',
  "MODEL. XTRANSPORT. REDUNDANCY '-ONLINE 18',
  "MODEL. AUTOBACKUP. PRIMARY_REGION '-ONLINE '0',
  "MODEL. CONTROLFILE. MIRROR_REGION '-ONLINE '0',
  "MODEL. DATA FILE. PRIMARY_REGION '-ONLINE '0',
  "MODEL. ASMPARAMETERFILE. REDUNDANCY '-ONLINE 18',
  "MODEL. FLASHFILE. MIRROR_REGION '-ONLINE '0',
  "MODEL. ASM_STALE. MIRROR_REGION '-ONLINE '0',
  "MODEL. RETURN OF FLAME. REDUNDANCY '-ONLINE 18',
  "MODEL. DATAGUARDCONFIG. STRIPE '-ONLINE '0',
  "CELL. SMART_SCAN_CAPABLE'-ONLINE 'FALSE. '
  "TEMPLATE_VERSION"-ONLINE '186646528',
  "MODEL. FICHIER_PARAMETRES. STRIPE '-ONLINE '0',
  "MODEL. DATA FILE. MIRROR_REGION '-ONLINE '0',
  "MODEL. FICHIER_PARAMETRES. PRIMARY_REGION '-ONLINE '0',
  "MODEL. BACKUPSET. MIRROR_REGION '-ONLINE '0',
  "MODEL. OCRBACKUP. MIRROR_REGION '-ONLINE '0',
  "MODEL. ONLINELOG. REDUNDANCY '-ONLINE 18',
  "MODEL. ASMPARAMETERBAKFILE. STRIPE '-ONLINE '0',
  ' ACCESS_CONTROL. PERMIT TO '-ONLINE 'FALSE. '
  "MODEL. DATAGUARDCONFIG. MIRROR_REGION '-ONLINE '0',
  "MODEL. TEMPORARY FILE. PRIMARY_REGION '-ONLINE '0',
  "COMPATIBLE. RDBMS '-ONLINE '10.1.0.0.0'.
  "MODEL. FLASHFILE. PRIMARY_REGION '-ONLINE '0',
  "MODEL. ONLINELOG. MIRROR_REGION '-ONLINE '0',
  "MODEL. FLASHFILE. REDUNDANCY '-ONLINE 18',
  "MODEL. OCRBACKUP. PRIMARY_REGION '-ONLINE '0',
  "MODEL. OCRFILE. STRIPE '-ONLINE '0',
  "MODEL. AUTOBACKUP. MIRROR_REGION '-ONLINE '0',
  "MODEL. ASM_STALE. PRIMARY_REGION '-ONLINE '0',
  "MODEL. ASMPARAMETERBAKFILE. PRIMARY_REGION '-ONLINE '0',
  "MODEL. XTRANSPORT. PRIMARY_REGION '-ONLINE '0',
  "MODEL. DUMPSET. STRIPE '-ONLINE '0',
  "MODEL. TEMPORARY FILE. STRIPE '-ONLINE '0',
  "MODEL. OCRFILE. PRIMARY_REGION '-ONLINE '0',
  "MODEL. ONLINELOG. STRIPE '-ONLINE '0',
  "MODEL. ARCHIVELOG. REDUNDANCY '-ONLINE 18',
  "MODEL. OCRFILE. REDUNDANCY '-ONLINE 18',
  "MODEL. ARCHIVELOG. MIRROR_REGION '-ONLINE '0',
  "MODEL. ASMPARAMETERFILE. MIRROR_REGION '-ONLINE '0',
  "MODEL. RETURN OF FLAME. STRIPE '-ONLINE '0',
  "MODEL. CONTROLFILE. PRIMARY_REGION '-ONLINE '0',
  "MODEL. XTRANSPORT. MIRROR_REGION '-ONLINE '0',
  "MODEL. BACKUPSET. REDUNDANCY '-ONLINE 18',
  "MODEL. ASMPARAMETERBAKFILE. REDUNDANCY '-ONLINE 18',
  "MODEL. XTRANSPORT. STRIPE '-ONLINE '0',
  "MODEL. TRACK CHANGES. MIRROR_REGION '-ONLINE '0',
  "COMPATIBLE. ASM '-ONLINE '11.2.0.0.0'.
  "MODEL. ASMPARAMETERBAKFILE. MIRROR_REGION '-ONLINE '0',
  "MODEL. ASMPARAMETERFILE. PRIMARY_REGION '-ONLINE '0',
  "MODEL. AUTOBACKUP. STRIPE'-'0' ONLINE
  },
  "DISKSINFO"-ONLINE {}
  "ASMDISK02"-ONLINE {}
  "ASMDISK02"-ONLINE {}
  "TOTAL_MB"-ONLINE '3914',
  "FAILGROUP" => "ASMDISK02."
  "NAME" => "ASMDISK02."
  "DGNAME"-ONLINE "DATA."
  'PATH' => 'ORCL:ASMDISK02 '.
  }
  },
  "ASMDISK01"-ONLINE {}
  "ASMDISK01"-ONLINE {}
  "TOTAL_MB"-ONLINE '3914',
  "FAILGROUP" => "ASMDISK01."
  "NAME" => "ASMDISK01."
  "DGNAME"-ONLINE "DATA."
  'PATH' => 'ORCL:ASMDISK01 '.
  }
  },
  "ASMDISK04"-ONLINE {}
  "ASMDISK04"-ONLINE {}
  "TOTAL_MB"-ONLINE '3914',
  "FAILGROUP" => "ASMDISK04."
  "NAME" => "ASMDISK04."
  "DGNAME"-ONLINE "DATA."
  'PATH' => 'ORCL:ASMDISK04 '.
  }
  },
  "ASMDISK03"-ONLINE {}
  "ASMDISK03"-ONLINE {}
  "TOTAL_MB"-ONLINE '3914',
  "FAILGROUP" => "ASMDISK03."
  "NAME" => "ASMDISK03."
  "DGNAME"-ONLINE "DATA."
  'PATH' => 'ORCL:ASMDISK03 '.
  }
  }
  },
  "DGINFO"-ONLINE {}
  "DGTORESTORE"-ONLINE 0
  "DGCOMPAT"-ONLINE ' 11.2.0.0.0. "
  "DGNAME"-ONLINE "DATA."
  "DGDBCOMPAT"-ONLINE ' 10.1.0.0.0. "
  "DGTYPE"-ONLINE "NORMAL."
  "DGAUSZ"-ONLINE '1048576'
  },
  "ALIASINFO"-ONLINE {}
  '6' => {
  "DGNAME"-ONLINE "DATA."
  'LEVEL'-ONLINE 1
  "ALIASNAME"-online "cluster01/ASMPARAMETERFILE"
  'REFERENCE_INDEX'-'16777322' ONLINE
  },
  '3' => {
  "DGNAME"-ONLINE "DATA."
  'LEVEL'-ONLINE 1
  "ALIASNAME" => "ORCL/CONTROLFILE.
  'REFERENCE_INDEX'-'16777534' ONLINE
  },
  '7' => {
  "DGNAME"-ONLINE "DATA."
  'LEVEL'-ONLINE 1
  "ALIASNAME" => "ORCL/FICHIER_PARAMETRES,"
  'REFERENCE_INDEX'-'16777693' ONLINE
  },
  '2' => {
  "DGNAME"-ONLINE "DATA."
  'LEVEL'-ONLINE 1
  "ALIASNAME" => "ORCL/ONLINELOG,"
  'REFERENCE_INDEX'-'16777587' ONLINE
  },
  '8' => {
  "DGNAME"-ONLINE "DATA."
  'LEVEL'-ONLINE 1
  "ALIASNAME"-online "cluster01/OCRFILE"
  'REFERENCE_INDEX'-'16777375' ONLINE
  },
  '1' => {
  "DGNAME"-ONLINE "DATA."
  'LEVEL'-ONLINE 0
  "ALIASNAME"-online "cluster01."
  'REFERENCE_INDEX'-'16777269' ONLINE
  },
  '4' => {
  "DGNAME"-ONLINE "DATA."
  'LEVEL'-ONLINE 1
  "ALIASNAME" => ORCL/DATA FILE"."
  'REFERENCE_INDEX'-'16777481' ONLINE
  },
  '0' => {
  "DGNAME"-ONLINE "DATA."
  'LEVEL'-ONLINE 0
  "ALIASNAME" => "ORCL".
  'REFERENCE_INDEX'-'16777428' ONLINE
  },
  '5' => {
  "DGNAME"-ONLINE "DATA."
  'LEVEL'-ONLINE 1
  "ALIASNAME" => "ORCL/TEMPFILE"
  'REFERENCE_INDEX'-'16777640' ONLINE
  }
  },
  'TEMPLATEINFO'-ONLINE {}
  '11' => {}
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  'TEMPNAME' => 'AUTOBACKUP.
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '7' => {
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'ASMPARAMETERFILE."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '2' => {
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'ARCHIVELOG."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '17' => {}
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'OCRBACKUP."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '1' => {
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'ASM_STALE."
  "REDUNDANCY"-ONLINE "HIGH."
  'SYSTEM' => 'Y '.
  },
  '18' => {}
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'ONLINELOG."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '0' => {
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  'TEMPNAME' => 'DATAFILE ',.
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '16' => {}
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'OCRFILE."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '13' => {}
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME'-ONLINE"TRACK CHANGES. "
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '6' => {
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'ASMPARAMETERBAKFILE."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '3' => {
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'FLASHFILE."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '9' => {
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME" => "TEMPFILE"
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '12' => {}
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'XTRANSPORT."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '14' => {}
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME'-ONLINE"FLASHBACK. "
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '15' => {}
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'DATAGUARDCONFIG."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '8' => {
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'FICHIER_PARAMETRES."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '4' => {
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE "FINE."
  'TEMPNAME' => 'CONTROLFILE.
  "REDUNDANCY"-ONLINE "HIGH."
  'SYSTEM' => 'Y '.
  },
  '10' => {}
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'BACKUPSET."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  },
  '5' => {
  "DGNAME"-ONLINE "DATA."
  "STRIPE"-ONLINE 'ROUGH. "
  "TEMPNAME' => 'DUMPSET."
  "REDUNDANCY"-ONLINE "MIRROR."
  'SYSTEM' => 'Y '.
  }
  }
  }
  );

  NOTE:

  To re-create the diskgroup dropped with the same restoration of the configuration of the diskgroup even with the aid of diskgroup as:

  asmcmd >/home/grid/data_backup_file - full - G DATA md_restore

  Hope its clear now.

  Thank you

  Ashish Shukla

• Order for the disk to backup ASM, OCR and vote in RAC HP - UX Itanium for upgrade

  Hi gurus,
  I plan to upgrade my Database 10.2.0.1 to 10.2.0.4 that is in a CCR on HP - UX environment. OCR, the voting record and ASM are in the RAW file system. I need to take backup of these (OCR, voting disk, ASM). Can you please share how to take backup of these before upgrading?
  
  
  Kind regards
  XIC
  
  Published by: XIC on 6 April 2013 20:25

  Here you go...

  For the voting disk backup

  http://www.reachdba.com/showthread.php?348-voting-disk-backup-and-recovery

  For the backup of the OCR

  http://www.reachdba.com/showthread.php?346-backup-of-OCR