on 01-05-2011 2:10 PM
As part of our procedure to test data restore for the SAP platform, recently we tried to restore a backup of the QAS SAP database from tape but had problems . During the analysis we think this problem happened because the retention of the backup on tape differs from the one in the configuration of SAP initSID.utl file; originally, the backup was made to a virtual tape using the brbackup tool /expiration parameter of 3 days, then cloned to a physical tape with a longer retention (30 days).
As a temporary solution to restore the data, we extended the u2018expirationu2019 parameter in the brbackup/brrestore configuration file (.utl) and since we still had the logs of the original backup (.anf file), we were able to complete the restore succesfully. We then changed back to the original the expiration time in the .utl file
We need to run the restore option in Production (PRO) environment but still we are not sure if this workaround is acceptable. Does anyone know if this option is correct or if thereu2019s another known solution for this case
Hi Julio
I believe you have posted your query in the wrong forum and hence you might not be getting the responses you would want.
This forum is for Operational Performance Management Business Applications like Spend Performance Management and SCPM.
Regards
Rajesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
6 | |
5 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.