Hello,
We are facing a strange issue, we have a backup appliance 5220 @ NB7.6. We are configured a DB backup using oracle intelligent policy and we are used dedupe pool as destination. Backups are success, but when we try to restore DB datafiles it fails. But we are able to restore SP file and control file. And if we use advanced disk or tape for backup the restore is success with datafiles. Wea re facing issues only when we use dedupe pool (pure disk).
IF we use dedupe pool in inelligent backup policy, I Could see it swicthes to RMAN non snapshot proxy backup. See the logs below.
1179) INF - TYPE 'SBT_TAPE'
08/12/2015 21:54:58 - Info bphdb (pid=11179) INF - PARMS 'SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so64';
08/12/2015 21:54:58 - Info bphdb (pid=11179) INF - SEND 'NB_ORA_CLIENT=svuphtquesttst,NB_ORA_SID=tqlive,NB_ORA_SERV=192.168.50.102,NB_ORA_POLICY=oracle_tqlive_test,NB_ORA_PARENT_JOBID=617139,NB_ORA_SCHED=Full,NB_ORA_PC_SCHED=Full,NB_ORA_PC_STREAMS=4';
08/12/2015 21:54:58 - Info bphdb (pid=11179) INF - # DEDUPE storage unit was detected - switching to a non-snapshot proxy backup
08/12/2015 21:54:58 - Info bphdb (pid=11179) INF - BACKUP
08/12/2015 21:54:58 - Info bphdb (pid=11179) INF - INCREMENTAL LEVEL=0 PROXY
And during restore I could see below error in dbclient log:
6:36:38 (621835.xxx) Found (11) files in (4) images for Restore Job ID 621835.xxx>
16:37:05.620 [8103] <4> logCommFile: <16:36:38 (621835.004) Restoring from copy 1 of image created Fri Aug 14 12:55:07 2015 from policy oracle_tqlive_test>
16:37:05.620 [8103] <4> logCommFile: <16:36:38 (621835.004) TAR STARTED 8212>
16:37:05.620 [8103] <4> logCommFile: <16:36:54 (621835.004) INF - Beginning restore from server svuphnetbcp to client svuphtquesttst.>
16:37:05.620 [8103] <4> logCommFile: <16:36:54 (621835.004) Read access to .AtTrIbUtEs.7 was denied>
16:37:05.620 [8103] <4> logCommFile: <16:36:54 (621835.004) Read access to .LoNg_VaLuEs.4 was denied>
16:37:05.620 [8103] <4> logCommFile: <16:36:54 (621835.004) Skipping to next file header...>
16:37:05.620 [8103] <4> logCommFile: <16:36:54 (621835.004) INF - TAR EXITING WITH STATUS = 3>
16:37:05.620 [8103] <4> logCommFile: <16:36:54 (621835.004) INF - TAR RESTORED 0 OF 2 FILES SUCCESSFULLY>
And client tar log reports invalid tar header found.
Please help on this issue.
Regards,
Anish