Recovering a database by restoring to a different directory under the data directory of an active server
If you have a problem restoring a database using the following
steps, you may want to try restoring the database to a different server
as outlined above. As in the scenario above, you must have archival
transactional logging enabled and have previously saved the database
you want to restore. You are restoring this database to a point in
time to be able to recover a document or documents (that point in
time may be very recent, but you need to specify a point in time for
this restore to work).
- Create a subdirectory under the data directory of the active server where the current database file is located.
- Make sure QNOTES is the owner of that subdirectory. You can use this command to change the owner: CHGOWN '/data directory of the current server/subdirectory' QNOTES
- Do an incremental save of the current active server.
- Use WRKMEDIBRM to select the database to be restored and specify
that the database is to be placed in the subdirectory of the active
server.
The name of the database to be restored to the subdirectory of the active server must be the same name and case as is found on the active server. Depending upon what release of BRMS you are using, you may be able to use the BRMS System i® Navigator client interface to do this point-in-time restore request. Otherwise follow the instructions for specifying a date and time for the point-in-time restore.
During the actual recovery process of the selected databases, no new saves of this particular server should occur. It could affect the recovery process adversely.
- Verify that the restore worked. Open the new database to recover the documents. This new database will have a new DBIID associated with it. If you want to be able to recover this version of the database, you will need to do a full save. If this is only a temporary file, and no longer needed after recovering the documents, then there is no need to do a full save.