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 |
• |
• |
If a Domino Database with the same name does not exist on the alternate Domino Server, select the Last Backup Set check box. |
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: |
5 |
In the Target Client list, select the machine on which you want to restore the data. |
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.
1 |
5 |
Click Restore. |
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. | ||||||
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.” |
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. | ||||||
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. |
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. | ||||||
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.” |
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. | ||||||
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. |
© ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad Cookie Preference Center