Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ for Oracle Administrator's Guide
  3. Performing backups and restores of Oracle
  4. Single-step restore to ASM storage from an Oracle Copilot recovery point
NetBackup™ for Oracle Administrator's Guide

Single-step restore to ASM storage from an Oracle Copilot recovery point

The following procedure shows how to use RMAN to restore from a recovery point. This procedure is only viable after the command nborair -create_recovery_point is run and the recovery point is mounted on a target client.

Note:

The functionality for single-step restore to ASM storage is not in the GUI. This feature is run with RMAN only.

The procedure example assumes that a recovery point is already mounted and uses the mount point of /db_mp as the example. All RMAN commands must run from the target host.

To perform a single-step restore to ASM storage from a recovery point

  1. Catalog the backups from the recovery point.
    RMAN> catalog start with '/db_mp/';
    
    searching for all files that match the pattern /db_mp/
    
    List of Files Unknown to the Database
    =====================================
    File Name: /db_mp/data_D-ORAC112_I-3955369132_TS-SYSAUX_FNO-2_8hrgu3qd_s-1297_I-3955369132
    File Name: /db_mp/data_D-ORAC112_I-3955369132_TS-SYSTEM_FNO-1_8irgu3qk_s-1298_I-3955369132
    File Name: /db_mp/data_D-ORAC112_I-3955369132_TS-UNDOTBS1_FNO-3_8jrgu3qr_s-1299_I-3955369132
    File Name: /db_mp/data_D-ORAC112_I-3955369132_TS-USERS_FNO-4_8krgu3qt_s-1300_I-3955369132
    File Name: /db_mp/arch_D-ORAC112_I-3955369132_SCN-5248163_a8rh0s3b
    File Name: /db_mp/spfile_D-ORAC112_I-3955369132_T-20160929_a9rh0s3c
    File Name: /db_mp/cf_D-ORAC112_I-3955369132_T-20160929_aarh0s3d
    
    Do you really want to catalog the above files (enter YES or NO)? YES
    cataloging files...
    cataloging done
    
    List of Cataloged Files
    =======================
    File Name: /db_mp/data_D-ORAC112_I-3955369132_TS-SYSAUX_FNO-2_8hrgu3qd_s-1297_I-3955369132
    File Name: /db_mp/data_D-ORAC112_I-3955369132_TS-SYSTEM_FNO-1_8irgu3qk_s-1298_I-3955369132
    File Name: /db_mp/data_D-ORAC112_I-3955369132_TS-UNDOTBS1_FNO-3_8jrgu3qr_s-1299_I-3955369132
    File Name: /db_mp/data_D-ORAC112_I-3955369132_TS-USERS_FNO-4_8krgu3qt_s-1300_I-3955369132
    File Name: /db_mp/arch_D-ORAC112_I-3955369132_SCN-5248163_a8rh0s3b
    File Name: /db_mp/spfile_D-ORAC112_I-3955369132_T-20160929_a9rh0s3c
    File Name: /db_mp/cf_D-ORAC112_I-3955369132_T-20160929_aarh0s3d
    
  2. Restore the data files from the point in time of the recovery point.

    The following RMAN restore is from disk (DISK). Also, this example uses the NLS_DATE_FORMAT="DD-MM-YYYY-HH24:MI:SS" command that was set in the environment before RMAN was run. Use the date format for your environment.

    RMAN> restore until time '2016-09-29-10:00:00' database;
    
    Starting restore at 2016-10-12:15:51:22
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=193 device type=DISK
    
    channel ORA_DISK_1: restoring datafile 00001
    input datafile copy RECID=461 STAMP=925055096 
    file name=/demo_2/data_D-ORAC112_I-3955369132_TS-SYSTEM_FNO-1_8irgu3qk_s-1298_I-3955369132
    destination for restore of datafile 00001: /db/orac112/app/oradata/orac112/system01.dbf
    channel ORA_DISK_1: copied datafile copy of datafile 00001
    output file name=/db/orac112/app/oradata/orac112/system01.dbf RECID=0 STAMP=0
    Finished restore at 2016-10-12:15:51:34
    
  3. Recover the database.

    If the restore of archive logs is not available on disk, then the logs are restored from NetBackup (sbt_tape).

    RMAN> run
    {
    allocate channel ch00 type sbt_Tape;
    recover database;
    release channel ch00;
    }
    
    released channel: ORA_DISK_1
    allocated channel: ch00
    channel ch00: SID=193 device type=SBT_TAPE
    channel ch00: Veritas NetBackup for Oracle - Release 8.0 (2016091418)
    
    Starting recover at 2016-10-12:15:54:13
    
    starting media recovery
    
    archived log for thread 1 with sequence 508 is already on disk as file 
    /db/orac112/app/fast_recovery_area/ORAC112/archivelog/2016_09_29/o1_mf_1_508_cytbkv22_.arc
    archived log for thread 1 with sequence 509 is already on disk as file 
    /db/orac112/app/fast_recovery_area/ORAC112/archivelog/2016_09_29/o1_mf_1_509_cytbkv36_.arc
    ....
    archived log file name=
    /db/orac112/app/fast_recovery_area/ORAC112/archivelog/2016_09_29/o1_mf_1_508_cytbkv22_.arc 
    thread=1 sequence=508
    archived log file name=
    /db/orac112/app/fast_recovery_area/ORAC112/archivelog/2016_09_29/o1_mf_1_509_cytbkv36_.arc 
    thread=1 sequence=509
    ....
    media recovery complete, elapsed time: 00:00:55
    Finished recover at 2016-10-12:15:55:09
    
    released channel: ch00
    
    RMAN>
    

More Information

Creating an instant recovery point from an Oracle Copilot image

About using a NetBackup appliance share for Oracle backups (Oracle Copilot)

Configuring an OIP using a share on the NetBackup appliance (Oracle Copilot)

Feedback

Was this page helpful?
Previous

Cleaning up the Oracle Copilot share after point in time restore of database

Next

About restoring from a data file copy to ASM storage using RMAN

Feedback

Was this page helpful?