Title: SAP barestore fails after a media rescan.
Date: 28/02/2007
NV Version: 7.4
OS Version: Any
Application version:SAP R/3
Plugin version:APM 3.2 and APM 4.0
Description: Explanation of restore failure after a media rescan.
Symptoms: After a media with a SAP backint backup expires and is rescanned, brrestore can no longer find the backup to restore.
Messages in Netvault Log:
Warning 2007/02/28 12:15:31 25044 Data Plugin sap_test File 'c:\data\oracle\DEV\saparch\DEVarch1_179921_123456789.dbf' not found in given saveset
Error 2007/02/28 12:15:31 31 Jobs nvbackup Fatal error: Restore failed
Error 2007/02/28 11:15:31 31 Jobs nvbackup Job Status: Restore Failed
1) Identify the current saveset number by running a backint query:
backint -f inquire -i in_file
where in_file contains a list of required files to locate in the format:
#NULL /path/filename1
#NULL /path/filename2
Running this query will return a list of savesets containing the specified files, having identified these they can then be restored using a "backint -f restore" command:
2) backint -f restore -i in_file
where rest_file contains a list of the files to be restored identified by the saveset name found in by the inquire command:
27 /path/filename1
27 /path/filename2
Explanation:
This problem occurs when using the SAP interfaces brrestore and brrbackup rather than backint directly. SAP maintains an internal catalog of the backups and the media on which the backups are saved. However, the media identifiers for the backint interfaces use the saveset number. After a media expires and is rescanned, it is reallocated a new saveset number (ie the next number in the sequence) so the current saveset number and that stored within SAP no longer matched.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy