ADSM-L

Re: TDP For SAP/R3 - Single File Restore Problem

2006-06-20 06:38:07
Subject: Re: TDP For SAP/R3 - Single File Restore Problem
From: "Hooft, Jeroen" <Jeroen.Hooft AT ATOSORIGIN DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 20 Jun 2006 12:37:12 +0200
Try to restore the files with backint or backfm

"backfm =p initTPP.utl" will give you a kind of filemanager where you can 
select individual files from the different backups.



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Pranav Parikh
Sent: dinsdag 20 juni 2006 12:28
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TDP For SAP/R3 - Single File Restore Problem


Hi,

I am facing problem in restoring single log file using brrrestore.  The
activity log shows that the require file archTPP.log  has been successfully 
backed by brarchive using tdp for SAP/R3 V5.2. We are unable to retrieve this 
file by brrestore command. It gives
following error while running "brrestore -n det_log -p initTPP.sap"

"option '-n' not supported for 'util_file' "

The very same -n options works fine with the direct tape backup on local
host.  The -d switch in conjunction to -n allows us to specify device i.e
tape (only) and does not support util parameter file.

Some of the log files with extension .fnf, .cds and archTPP.log file on the 
production server required for restoring the archive logs has
been lost due to corruption in oracle database.  This files are already
being backed up and are very much present in the backup set. but we are
unable to restore it either by using the switches available in brrestore
command line or brtools menu. This are vital files containing information
of the archive logs backup prior to database crashes. If we can restore
any of the above mentioned individual files from the backup set we can
restore archive logs and recover database.

If any one of you know , do let me know how to retrieve single file.  We
have restored previous online backup and required archive logs to fully
recovered from data loss.

Regards
Pranav

Attachment: Disclaimer.txt
Description: Text document

<Prev in Thread] Current Thread [Next in Thread>