NetVault Plug-in for Domino 4.4 - User Guide

NetVault Backup 10.x service (netvault-pgsql) does not start on Windows.

Check the Windows Event Viewer for the following message: PDT FATAL: lock file “postmaster.pid” already exists.

NetVault Backup 10.x uses a PostgreSQL database. If the PostgreSQL database does not start, NetVault Backup cannot start. To correct this issue, delete the “postmaster.pid” file from the location referenced in the log and restart the NetVault Backup Server. For more information, see https://support.questcom/netvault-backup/kb/122475.

Backup failed.

Server is not currently logged in. Resulting backup might not be recoverable.

Set up Transactional Logging on the Domino Server. For details, see Setting up Transactional logging on the Domino Server

Cold backup fails on Linux or UNIX when DAOS is configured.

A message from the client states: “Plug-in terminated unexpectedly” or “Plug-in is down.”

To change the DAOS_LOAD and DAOS_Enable settings from 1 to 0, edit the Domino Server’s “notes.ini” file, and try the backup again. After the backup has completed successfully, edit the “notes.ini” file again to change the DAOS_LOAD and DAOS_Enable settings back to 1 before you restart the Domino Server.

Hard Recovery Restore (Offline Restore) of Domino Databases, including Users Mailbox Databases, fails.

The databases being restored exist, while the Transaction Logs are missing and must be re-created. The job waits while the logs are being re-created. If the OS response is slow during this process, the thread times out and the restore job fails.

Resubmit the restore job.

Cold restore fails on Linux or UNIX when DAOS is configured.

A message from the client states: “Plug-in terminated unexpectedly” or “Plug-in is down.”

Try the following:

Cold restore of server-database files fails.

A message similar to one of the following occurs:

The version and Fix Pack (FP) level of your Domino Server affects the recovery process. You can work around this issue by restoring the files to a different directory. For more information, see Renaming and relocating data during restore.

NetVault Backup 10.x service (netvault-pgsql) does not start on Windows.

Check the Windows Event Viewer for the following message: PDT FATAL: lock file “postmaster.pid” already exists.

NetVault Backup 10.x uses a PostgreSQL database. If the PostgreSQL database does not start, NetVault Backup cannot start. To correct this issue, delete the “postmaster.pid” file from the location referenced in the log and restart the NetVault Backup Server. For more information, see https://support.questcom/netvault-backup/kb/122475.

Backup failed.

Server is not currently logged in. Resulting backup might not be recoverable.

Set up Transactional Logging on the Domino Server. For details, see Setting up Transactional logging on the Domino Server

Cold backup fails on Linux or UNIX when DAOS is configured.

A message from the client states: “Plug-in terminated unexpectedly” or “Plug-in is down.”

To change the DAOS_LOAD and DAOS_Enable settings from 1 to 0, edit the Domino Server’s “notes.ini” file, and try the backup again. After the backup has completed successfully, edit the “notes.ini” file again to change the DAOS_LOAD and DAOS_Enable settings back to 1 before you restart the Domino Server.

Hard Recovery Restore (Offline Restore) of Domino Databases, including Users Mailbox Databases, fails.

The databases being restored exist, while the Transaction Logs are missing and must be re-created. The job waits while the logs are being re-created. If the OS response is slow during this process, the thread times out and the restore job fails.

Resubmit the restore job.

Cold restore fails on Linux or UNIX when DAOS is configured.

A message from the client states: “Plug-in terminated unexpectedly” or “Plug-in is down.”

Try the following:

Cold restore of server-database files fails.

A message similar to one of the following occurs:

The version and Fix Pack (FP) level of your Domino Server affects the recovery process. You can work around this issue by restoring the files to a different directory. For more information, see Renaming and relocating data during restore.