Highlighted
liam.guinane
1 Nickel

RMAN Restore from Clone volume

Folks,

Looking for some advice, oracle rman backups are run manually from the db host, and backups are then cloned by CCR to a secondary data domain. The primary volume was overwritten but the clone volume is available. mminfo output shows the backups residing in the cloned volume.

Restore with rman is failing, as the rman catalog I believe,  is looking for the primary volume for restore.

How do I restore using the cloned device ?

Tks,

Tags (3)
0 Kudos
4 Replies
mavroc
1 Copper

Re: RMAN Restore from Clone volume

Maybe take a look at setting NSR_RECOVER_POOL in the RMAN script, to the cloned pool name.    Here is a section from the NMDA Admin guide….

"Specifies the name of the NetWorker volume pool to use for a restore. You can use this option to restore data from a specified volume pool if there are multiple copies (clones) of the backup in different volume pools."

Also keep in mind that the value is case sensitive.

HTH

Chris

0 Kudos
edino1
1 Nickel

Re: RMAN Restore from Clone volume

Hi,

if you have still problem (NSR_RECOVER_POOL did not help) to restore control file then try to find related backup piece by nsrinfo command in NetWorker. If you will find it then check logs on client side as well for further information.

Regards,

Eduard

0 Kudos
liam.guinane
1 Nickel

Re: RMAN Restore from Clone volume

Thanks  for the replies. nsr_recover_pool did not work for me, getting an error

ORA-19511: non RMAN, but media manager or vendor specific failure, error text:

   We could not read the checksum. (0:3:0)

  Using file ‘l0_19sii72r_1_1’ as an example. It’s not listed in the output of nsrinfo but is listed by mminfo

ausdwburr2210.ausrr2cdd03.ccrclone.01 austldbengdb07 11/2/2017 64 MB manual RMAN:l0_19sii72r_1_1

[oracle@austldbengdb07 /home/oracle]

$ rman target /

connected to target database: PATDB (DBID=3097235999, not open)

RMAN> run {

allocate channel ch1 type 'SBT_TAPE' parms 'ENV=(NSR_SERVER=ausdwburr2210,NSR_CLIENT=austldbengdb07.us.dell.com,NSR_RECOVER_POOL=ccrclone)';

restore database from TAG='PATDB_FULLDB_20171102';

release channel ch1;

3> }4> 5> 6> 7> 8> 9> 10> 11>

using target database control file instead of recovery catalog

allocated channel: ch1

channel ch1: SID=1147 instance=patdb1 device type=SBT_TAPE

channel ch1: NMDA Oracle v8.2.4

……..

Starting restore at 11/13/2017 02:15:56

channel ch1: starting datafile backup set restore

channel ch1: specifying datafile(s) to restore from backup set

channel ch1: restoring datafile 00004 to +DATA_1/PATDB/DATAFILE/undotbs1.306.959207061

channel ch1: reading from backup piece l0_19sii72r_1_1

………

channel ch1: ORA-27192: skgfcls: sbtclose2 returned error - failed to close file

ORA-19511: non RMAN, but media manager or vendor specific failure, error text:

   We could not read the checksum. (0:3:2)

ORA-19870: error while restoring backup piece l0_19sii72r_1_1

ORA-19501: read error on file "l0_19sii72r_1_1", block number 1 (block size=512)

ORA-27190: skgfrd: sbtread2 returned error

ORA-19511: non RMAN, but media manager or vendor specific failure, error text:

   asdf_read

channel ch1: starting datafile backup set restore

channel ch1: specifying datafile(s) to restore from backup set

channel ch1: restoring datafile 00001 to +DATA_1/PATDB/DATAFILE/system.319.959207061

channel ch1: reading from backup piece l0_17sii72q_1_1

channel ch1: ORA-27192: skgfcls: sbtclose2 returned error - failed to close file

ORA-19511: non RMAN, but media manager or vendor specific failure, error text:

   We could not read the checksum. (0:3:0)

ORA-19870: error while restoring backup piece l0_17sii72q_1_1

ORA-19501: read error on file "l0_17sii72q_1_1", block number 1 (block size=512)

ORA-27190: skgfrd: sbtread2 returned error

ORA-19511: non RMAN, but media manager or vendor specific failure, error text:

   asdf_read

channel ch1: starting datafile backup set restore

channel ch1: specifying datafile(s) to restore from backup set

channel ch1: restoring datafile 00002 to +DATA_1/PATDB/DATAFILE/sysaux.267.959207061

channel ch1: reading from backup piece l0_16sii72q_1_1

channel ch1: ORA-27192: skgfcls: sbtclose2 returned error - failed to close file

ORA-19511: non RMAN, but media manager or vendor specific failure, error text:

   We could not read the checksum. (0:3:0)

ORA-19870: error while restoring backup piece l0_16sii72q_1_1

ORA-19501: read error on file "l0_16sii72q_1_1", block number 1 (block size=512)

ORA-27190: skgfrd: sbtread2 returned error

ORA-19511: non RMAN, but media manager or vendor specific failure, error text:

   asdf_read

……..

failover to previous backup

released channel: ch1

….

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of restore command at 11/13/2017 02:21:48

RMAN-06026: some targets not found - aborting restore

RMAN-06023: no backup or copy of datafile 6 found to restore

RMAN-06023: no backup or copy of datafile 5 found to restore

RMAN-06023: no backup or copy of datafile 4 found to restore

RMAN-06023: no backup or copy of datafile 3 found to restore

RMAN-06023: no backup or copy of datafile 2 found to restore

RMAN-06023: no backup or copy of datafile 1 found to restore

0 Kudos
edino1
1 Nickel

Re: RMAN Restore from Clone volume

Some next tips:

1. If you have file system backup of client austldbengdb07.us.dell.com in the same clone pool as DB backup then try to restore it to the same target server like you have for DB restore. If it will not work then you will have NetWorker error maybe related to pool and device, but if the restore will work then we could focus on DB restore itself.

2. Output of mminfo has client name austldbengdb07 without domain, so please check aliases of that client or use client name austldbengdb07 in RMAN restore script  (...be sure that both names are in DNS or hosts file on target system, storage node, NetWorker server).

3. Check NMDA logs on client

Is any storage node involved in restore operation?

0 Kudos