지금 지원 담당자와 채팅
지원 담당자와 채팅

NetVault Plug-in for Domino 12.4 - User Guide

Restoring data to an alternate server

The plug-in lets you restore Full Backups to an alternate Domino Server. This procedure can be used to copy a database from one production server to a different production server.

Before proceeding, ensure that the following requirements are met:

Same version of Domino installed: The Domino version must be same as the version running on the existing Domino Server. In addition, the server platform must be the same and the operating systems on both servers must be compatible. For example, if the source server was running Windows, the target server must also run Windows.
Properly configured Domino Instance: Verify that you have a properly configured Domino instance.
NetVault Backup software and the Plug‑in for Domino installed: The same version of NetVault Backup software and the Plug‑in for Domino must be installed and configured on the new restore target.
Heterogeneous Client added to the NetVault Backup Server: The target server must be added as a Heterogeneous Client to the NetVault Backup Server. You can perform this task from the Manage Clients page of the NetVault Backup WebUI.
Recent Full Backup available: Ensure that a recent Full Backup is available. Restore to an alternate Domino Server is completed using a Full Backup of the databases being restored. Nonlogged databases can be restored from an Incremental Backup because for such databases, an Incremental Backup actually includes the full contents of the database. For logged databases, Incremental Backups are not supported when restoring to an alternate server.

To restore the data to an alternate client, perform the following steps.

2
Click the Rollforward tab, and do one of the following in the Recovery and Rollforward section:
3
If you are restoring a partition to an alternate server, click the Restore Destination tab, and enter the partition number for the new partition in the Restore to Logical Domino Server (Partition) field:
As explained previously, the Backup Taken from Logical Domino Server (Partition) field identifies the partition from which the backup was taken and the plug-in enters the same information in the Restore to Logical Domino Server (Partition) field by default. If you have changed the partition on which the “notes.ini” file is located, you can use this field to specify the new partition number.
5
In the Target Client list, select the machine on which you want to restore the data.

Performing a disaster recovery to the same Domino Server

You can use the plug-in to perform a disaster recovery to the same server where the source Domino Server resided.

Before proceeding, ensure that the following requirements are met:

Domino software installed: Install the same OS and version of Domino on the system that existed on the damaged server.
NetVault Backup software and the Plug‑in for Domino installed: The same version of NetVault Backup software and the Plug‑in for Domino must be installed and configured on the new restore target.
Heterogeneous Client added to the NetVault Backup Server: The target server must be added as a Heterogeneous Client to the NetVault Backup Server. You can perform this task from the Manage Clients page of the NetVault Backup WebUI.
Full and Incremental Backups available: Ensure that the recent Full Backup and the required Incremental Backups are available.

To restore the data to the repaired server, perform the following steps.

5
Click Restore.
When restoring the last saveset, select the Last Backup Set check box and the Hard Recovery option. If Incremental Backups are not restored, the Domino Server re-creates any necessary Transaction Logs.

Troubleshooting

This topic describes some common errors and their solutions. In cases where an error occurs and is not described in this table, obtain the Domino error number from the NetVault Backup Logs, and then see the relevant Domino documentation for the resolution.

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

Backup completed with errors on Linux or UNIX.

Series of job messages that indicate the backup job completed successfully but that errors were noted.

If you use Domino Server on Linux or UNIX and you use symbolic links instead of absolute links for the installation or data directory, or both, the Domino Server generates error messages during the backup process. Use of symbolic links for these directories changes the owner of items, which leads to the error messages. Update the symbolic links to use absolute links and run the backup job again.

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:

To change the DAOS_LOAD and DAOS_Enable settings from 1 to 0 (DAOS_LOAD=0 and DAOS_Enable=0), edit the Domino Server’s “notes.ini” file, and try the restore again. If you try this method and if the “notes.ini” file must be restored, restore it after the other items are successfully restored. This process ensures that the modified settings are retained in the active file.
If you try the latter method and the “notes.ini” file does not have to be restored, edit the “notes.ini” file again to change the DAOS_LOAD and DAOS_Enable settings back to 1 before you restart the Domino Server.

Cold restore of server-database files fails.

A message similar to one of the following occurs:

Error 2014/04/10 13:23:52 43 Data Plugin <serverName> Failed to take database /local/notesdata/<fileName>.nsf offline.
Job Message 2014/04/10 13:23:52 43 Data Plugin <serverName> Bring database '/local/notesdata/<fileName>.nsf' online.
Error 2014/04/10 13:23:52 43 Data Plugin <serverName> Failed to Restore database '/local/notesdata/<fileName>.nsf'

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.

Common errors

This topic describes some common errors and their solutions. In cases where an error occurs and is not described in this table, obtain the Domino error number from the NetVault Backup Logs, and then see the relevant Domino documentation for the resolution.

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

Backup completed with errors on Linux or UNIX.

Series of job messages that indicate the backup job completed successfully but that errors were noted.

If you use Domino Server on Linux or UNIX and you use symbolic links instead of absolute links for the installation or data directory, or both, the Domino Server generates error messages during the backup process. Use of symbolic links for these directories changes the owner of items, which leads to the error messages. Update the symbolic links to use absolute links and run the backup job again.

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:

To change the DAOS_LOAD and DAOS_Enable settings from 1 to 0 (DAOS_LOAD=0 and DAOS_Enable=0), edit the Domino Server’s “notes.ini” file, and try the restore again. If you try this method and if the “notes.ini” file must be restored, restore it after the other items are successfully restored. This process ensures that the modified settings are retained in the active file.
If you try the latter method and the “notes.ini” file does not have to be restored, edit the “notes.ini” file again to change the DAOS_LOAD and DAOS_Enable settings back to 1 before you restart the Domino Server.

Cold restore of server-database files fails.

A message similar to one of the following occurs:

Error 2014/04/10 13:23:52 43 Data Plugin <serverName> Failed to take database /local/notesdata/<fileName>.nsf offline.
Job Message 2014/04/10 13:23:52 43 Data Plugin <serverName> Bring database '/local/notesdata/<fileName>.nsf' online.
Error 2014/04/10 13:23:52 43 Data Plugin <serverName> Failed to Restore database '/local/notesdata/<fileName>.nsf'

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.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택