IBM Support

Procedure for restoring a DAOS enabled database on IBM i

Technote (FAQ)


Question

Cause

Performing a RST command directly into the Domino server's data directory with the server up can cause problems. BRMS must be used when saving/restoring data to an active Domino server.

Answer

The answer to this question varies depending on your save method and what you are trying to restore. The following scenarios will be covered:




Restoring an entire database using native SAV/RST commands:

This scenario assumes that you are recreating the entire database. It is assumed the current copy of the database will be removed / deleted from the server. This example assumes the Domino server's data directory is /notes/data and the mail file to be restored is named mailfile.nsf.

1. Check for existing replicas of the database on clients and all servers in the domain. If a replica exists you should remove the replica.

2. Restore the database in question into a directory outside of the existing data directory. For example:

    RST DEV('/qsys.lib/ tap01.devd') OBJ((' /notes/data/mail/mailfile.nsf' *INCLUDE ' /restore/mailfile.nsf'))

3. End the Domino server

4. Remove the existing mail file. For example:

    RMVLNK OBJLNK('/notes/data/mail/mailfile.nsf')

5. Move the restored database to its proper location. For example:
    MOV OBJ('/restore/mailfile.nsf') TOOBJ('/notes/data/mail/mailfile.nsf')
6. Verify/set QNOTES as the owner to the restored file. For example:
    CHGOWN OBJ('/notes/data/mail/mailfile.nsf') NEWOWN(QNOTES)

7. Restart the Domino server

8. Verify integrity of restored database and DAOS links by running fixup. For example:

    load fixup -j mail/mailfile.nsf


9. Verify that all .nlo files exist on server / generate a list of the .nlo files needed to be restored using the "listnlo" command. For example:
    tell daosmgr listnlo -o missing_nlo_files.txt MISSING mail/mailfile.nsf


10. Review output from the "listnlo" command above and restore any files listed. Note that the same file may be listed multiple times in the output, one for each reference to the missing attachment. The syntax for the restore is the same as step #2. For example:
    RST DEV('/qsys.lib/tap01.devd') OBJ(('/notes/DAOS/0001/AAC48E7FC07B6CC71ADD186896DC4F48509F165801A8702F.nlo'))

11. Create new replicas of any replicas you removed in step 1.

12. Schedule a resync of the DAOS catalog when convenient. You can see how to create a program document to resync the catalog in the Domino wiki.


Restoring a subset of documents from a database using native SAV/RST commands

This scenario assumes that you are restoring a database in order to copy and paste specific documents back into the existing database. This example assumes the Domino server's data directory is /notes/data and the mail file to be restored is named mailfile.nsf.

1. Check for existing replicas of the database on clients and all servers in the domain. If a replica exists you should disable replication or remove the replica until the restore process is complete.

2. Run compact -c or fixup -j against the existing database to change the DBIID of the database. For example:

    load fixup -j mail/mailfile.nsf

3. Restore the database in question into a directory outside of the existing data directory. For example:

    RST DEV('/qsys.lib/ tap01.devd') OBJ((' /notes/data/mail/mailfile.nsf' *INCLUDE ' /restore/mailfile.nsf'))

4. End the Domino server

5. Move the restored database to an alternate location within the server's data directory. For example:

    MOV OBJ('/restore/mailfile.nsf') TOOBJ('/notes/data/restore/mailfile.nsf')

6. Verify/set QNOTES as the owner to the restored file. For example:
    CHGOWN OBJ('/notes/data/restore/mailfile.nsf') NEWOWN(QNOTES)

7. Restart the Domino server

8. Verify integrity of restored database and DAOS links by running fixup. For example:

    load fixup -j restore/mailfile.nsf

9. Verify that all .nlo files exist on server / generate a list of the .nlo files needed to be restored using the "listnlo" command. For example:

    tell daosmgr listnlo -o missing_nlo_files.txt MISSING restore/mailfile.nsf

10. Review output from the "listnlo" command above and restore any files listed. Note that the same file may be listed multiple times in the output, one for each reference to the missing attachment. The syntax for the restore is the same as step #2. For example:

    RST DEV('/qsys.lib/tap01.devd') OBJ(('/notes/DAOS/0001/AAC48E7FC07B6CC71ADD186896DC4F48509F165801A8702F.nlo'))

Note: Steps 9 and 10 may not be required depending on the documents you need to copy. If you prefer, you can skip these steps and attempt to copy and paste the documents. If any .nlo files are missing, an error will be generated in the console with the full path to the missing .nlo.

11. Open the restored database and the original database with a Notes Client. Copy and paste the needed documents back into the original database.

12. Remove the restored database from the server.

13. Create new replicas or enable replication on any replicas you disabled in step 1.

14. Schedule a resync of the DAOS catalog when convenient. You can see how to create a program document to resync the catalog in the Domino wiki.



Restoring an entire database using BRMS

This scenario assumes that you are recreating the entire database. It is assumed the current copy of the database will be removed / deleted from the server. This example assumes the Domino server's data directory is /notes/data and the mail file to be restored is named mailfile.nsf.

1. Check for existing replicas of the database on clients and all servers in the domain. If a replica exists you should remove the replica.

2. Use RSTBRM, WRKLNKBRM, WRKMEDIBRM, or System i Navigator to restore the database back to its existing location. Here is an example of RSTBRM:

    RSTBRM DEV(*MEDCLS) OBJ(('/notes/data/mail/mailfile.nsf'))

3. Verify integrity of restored database and DAOS links by running fixup. For example:

    load fixup -j mail/mailfile.nsf

4. Verify that all .nlo files exist on server / generate a list of the .nlo files needed to be restored using the "listnlo" command. For example:

    tell daosmgr listnlo -o missing_nlo_files.txt MISSING mail/mailfile.nsf

5. Review output from the "listnlo" command above and restore any files listed. Note that the same file may be listed multiple times in the output, one for each reference to the missing attachment. Again, the restore can be done via System i Navigator, WRKLNKBRM or RSTBRM as shown here:

    RSTBRM DEV(*MEDCLS) OBJ(('/notes/DAOS/0001/AAC48E7FC07B6CC71ADD186896DC4F48509F165801A8702F.nlo'))

6. Create any new replicas you removed in step 1.

7. Schedule a resync of the DAOS catalog when convenient. You can see how to create a program document to resync the catalog in the Domino wiki.



Restoring a subset of documents using BMRS

This scenario assumes that you are restoring a database in order to copy and paste specific documents back into the existing database. This example assumes the Domino server's data directory is /notes/data and the mail file to be restored is named mailfile.nsf.

1. Check for existing replicas of the database on clients and all servers in the domain. If a replica exists you should disable replication or remove the replica until the restore process is complete.

2. Use RSTBRM, WRKLNKBRM, WRKMEDIBRM, or System i Navigator to restore the database to an alternate location within the server's data directory. Here is an example of RSTBRM:

    RSTBRM DEV(*MEDCLS) OBJ(('/notes/data/mail/mailfile.nsf' *INCLUDE '/notes/data/restore/mailfile.nsf'))

3. Verify integrity of restored database and DAOS links by running fixup. For example:

    load fixup -j restore/mailfile.nsf

4. Verify that all .nlo files exist on server / generate a list of the .nlo files needed to be restored using the "listnlo" command. For example:

    tell daosmgr listnlo -o missing_nlo_files.txt MISSING restore/mailfile.nsf

5. Review output from the "listnlo" command above and restore any files listed. Note that the same file may be listed multiple times in the output, one for each reference to the missing attachment. Again, the restore can be done via System i Navigator, WRKLNKBRM or RSTBRM as shown here:

    RSTBRM DEV(*MEDCLS) OBJ(('/notes/DAOS/0001/AAC48E7FC07B6CC71ADD186896DC4F48509F165801A8702F.nlo'))

Note: Steps 4 and 5 may not be required depending on the documents you need to copy. If you prefer, you can skip these steps and attempt to copy and paste the documents. If any .nlo files are missing, an error will be generated in the console with the full path to the missing .nlo.

6. Open the restored database and the original database with a Notes Client. Copy and paste the needed documents back into the original database.

7. Remove the restored database from the server.

8. Create new replicas or enable replication on any replicas you disabled in step 1.

9. Schedule a resync of the DAOS catalog when convenient. You can see how to create a program document to resync the catalog in the Domino wiki.


    Product Alias/Synonym

    iSeries
    i5/OS

Document information

More support for: IBM Domino
DAOS

Software version: 8.5, 8.5.1

Operating system(s): IBM i, i5/OS

Software edition: Edition Independent

Reference #: 1420019

Modified date: 04 June 2010