Testing the converted databases before starting the new pnfs server is very essential. If any discrepancies are detected the system should be reverted to the old version of pnfs using the old database files. The testing is performed by repeating the procedure described in the section called “Checking the GDBM Database Files” for the new databases and comparing the results with those of the old tests. For smaller installations this is done with

[root] # conversion-scan.sh <oldPnfsDatabaseDir> <newPnfsDatabaseDir>

e.g.

[root] # conversion-scan.sh <backupDir>/databases /opt/pnfsdb/pnfs/databases

The output of the scans performed by this script can be found in /tmp/pnfs-conversion-scan-<PID>/old/ and /tmp/pnfs-conversion-scan-<PID>/new/.

For larger installations it is probably better to perform the tests by hand as described in the section called “Checking the GDBM Database Files”. The old version of the md3tool command is provided in the pnfs-postgresql package for convenience (called md3tool_gdbm.)

If all the tests succeeded, the pnfs server may be started as usual:

[root] # ${pnfs}/bin/pnfs start

Make sure that the PostgreSQL server is always started before the pnfs server - especially at system start-up. You also might have to change the path to the pnfs software from /opt/pnfs.3.1.10/pnfs/ to /opt/pnfs/ in a start-up script.