Restore Data - Lotus Notes/Domino Server - How To
Topics |
How To |
Full System
Restore | Related Topics
Perform Cross-Machine Restore of
Databases
Perform Cross-Machine Restore of
Databases and Transaction Logs
Perform Cross-Machine Restore of Databases
The Lotus Notes Database iDataAgent
restores database backups as follows:
- If the source and destination computer have a partition with
the same data path then the data is restored to the common data path.
- If all partitions on the destination computer are different than the
source computer, then the data will be restored to the first partition.
No transaction logs are restored, and no
transactions are replayed. Follow the procedure for this mode if:
- You don't want to shut down the destination server during the restore
operation.
- The last database backup is more recent than the last transaction log
backup. In this case, there is no need to restore the transaction log.
Required Capability: See
Capabilities and Permitted Actions
To
perform a database-only cross-machine restore:
Follow the procedure described in
Browse and Restore. Make
sure to:
- Select the appropriate Destination Computer
from the Restore Options (General)
dialog box.
- Determine the restore path to the destination computer using Restore to
Same Paths.
When Restore to Same Paths is selected:
- If the source computer and the destination computer have a
partition with the same data path, the data is restored to the common
data path.
- If all partitions on the destination computer are different than the
source computer, the data will be restored to the first partition.
When Restore to Same Paths is
de-selected:
- You can select any Destination Folder on the selected destination computer.
NOTES
- For out-of-place restores, any database can be restored to a new location while the server
is running.
- Because this job does not restore log
files, some restore options are not made available (e.g., Change database instance id (DBIID),
Change database replica id).
Perform Cross-Machine Restore of Databases and Transaction Logs
The Lotus Notes Database iDataAgent
restores database backups as follows:
- If the source computer and the destination computer have a partition with
the same data path then the data is restored to the common data path.
- If all partitions on the destination computer are different than the
source computer, then the data will be restored to the first partition.
Then, log files
are restored as needed and transactions are replayed. Follow one of the
procedures for this mode if:
- You want to restore and replay transactions that took place after the
last database backup.
- You can do a database plus transaction log restore to either an active
(production) server that is an existing Notes Database client or to a new
server in the CommCell.
- If you restore directly to an active production server, you do not have to install Domino Server or the Notes
Database iDataAgent. However, you must shut down the server during the restore
job and make special preparations, as described in the procedure
instructions.
- If you don't want to shut down a production server, you can restore to a
new server. The new server will require installs of the Domino Server and the
Notes Database iDataAgent. After the cross-machine
restore finishes, you can copy the
recovered database(s) from the new server to the production server.
Choose the appropriate procedure:
Required Capability: See
Capabilities and Permitted Actions
To
perform a cross-machine restore of Notes databases and transaction logs to an
existing Domino Server:
|
The version of Domino Server on the computer to which you are restoring must be
the same as when the backup took place, since there may be differences in the
log file structures of different versions.
|
- Shut down Domino Server on the destination computer.
- On the destination computer, create a directory for restored databases and a directory for restored log files.
(If you prefer, you can use one directory for both.) We recommend that you
create these directories outside the Domino Server data path.
- Copy the source computer's server ID file (usually named server.id)
to the directory created for restored databases on the destination
computer. (If you can't access the file on the source computer, restore it
to the destination computer from backup.)
- Rename the notes.ini file on the destination computer (to notes.sav,
for example).
|
The Notes client software has its own notes.ini
file, as does each Domino Server partition. There may be multiple notes.ini
files on the computer to which you are restoring. Make sure that
you are modifying the notes.ini file for the appropriate
partition of the destination computer. |
- On the destination computer, create a notes.ini file in the same directory
as the original notes.ini file. The content of the .ini file
should be similar to the example below, with your own system information
replacing sample file and directory names.
If the directory for restored databases is D:\RestoredDBs, the
directory for restored log files is D:\RestoredLogs, the server ID file
name is server.id, and the Domino server program files directory is C:\Lotus\Domino),
the new notes.ini file will look like this:
[Notes]
Directory=D:\RestoredDBs
NotesProgram=C:\Lotus\Domino
KeyFilename=D:\RestoredDBs\server.id
TRANSLOG_Style=1
TRANSLOG_Path=D:\RestoredLogs
TRANSLOG_Status=1
Translog_MEDIAONLY=1
Be sure to
add a new line (i.e., press Enter) at the end of the file.
-
Browse the backup data and select those databases that you
want to restore. Select the Disaster Recovery / Media Recovery (to
another machine) option and a Destination Computer in the
Advanced Restore Options
(General)
dialog box in addition to any other restore options that you want.
-
Run the restore job and verify that it has completed successfully.
|
If you want to copy a restored database
back to the source computer (as opposed to any other server), DO NOT start Domino Server. DO NOT open the
restored database. Doing so may cause the database to be assigned a new
DBIID when it is opened by the Domino server on the source computer, which
will necessitate a database backup. In addition, if the database is large,
assigning a new DBIID will take some time. |
-
Optionally, copy the restored databases to another server. (If you want to
leave the databases on the computer to which they were restored, you must copy
them to the data path of a Domino partition.) We recommend
that you change the file extensions before copying (for example, to
user01mail.xxx), then rename the files with the .nsf extension after the file
copy is complete. This ensures that the server will not detect databases until
they are complete and consistent.
- Delete the notes.ini file that you created on the destination
computer, and rename the original .ini file
(e.g., notes.sav) to notes.ini. If you have copied the
restored databases to another server, you can delete the directories that
you created for restored databases and transaction logs.
You can now restart Domino Server on the destination computer.
| |
The version of Domino Server on the computer to which you are restoring must be
the same as when the backup took place, since there may be differences in the
log file structures of different versions.
|
|
To do this procedure, you must start with a
computer that does not have Domino Server installed. |
Required Capability: See
Capabilities and Permitted Actions
To
perform a cross-machine restore of Notes databases and transaction logs to a new
Domino Server:
- Install Lotus Domino Server and the Notes Database iDataAgent
on the destination computer.
|
The version of Domino Server on the computer to which you are restoring must be
the same as when the backup took place, since there may be differences in the
log file structures of different versions.
|
- Shut down the Domino server.
- Copy the source partition's
server ID file (usually named server.id) to the directory on the destination
computer that contains the server ID file. (If you can't
access the file on the source partition, restore it to the destination
computer from backup.) You may want to rename the
server ID file
in the destination computer first, so that
you don't overwrite it. If the name of the source partition's server ID file
differs from the name of the destination computer's server ID file, you must change
the KeyFileName parameter of the notes.ini file on the
destination computer to match the source computer's server ID file name.
- Add the following line to the notes.ini file of the destination
computer:
TRANSLOG_MEDIAONLY=1
If you add this line at the end of the notes.ini file, be sure to
add a new line (i.e., press Enter) after this line.
- Make sure that the transaction log directory is clean. (You can find the
path to the log directory by checking the TRANSLOG_Path parameter in
the partition's notes.ini file. If this is a relative path, it must be appended
to the path listed in the Directory parameter.) Delete any remaining
log files and the log control file. Alternately, you can delete the log
directory altogether. In this case, the restore process creates a
new log directory.
- Browse the backup data and select those databases that you
want to restore. Select the Disaster Recovery / Media Recovery (to
another machine) option and a Destination Computer in the
Advanced Restore Options
(General)
dialog box in addition to any other restore options that you
want.
- Run the restore job and verify that it has completed successfully.
|
If you want to copy a restored database
back to the source computer (as opposed to any other server), DO NOT start Domino Server. DO NOT open the
restored database. Doing so may cause the database to be assigned a new
DBIID when it is opened by the Domino server on the source computer, which
will necessitate a database backup. In addition, if the database is large,
assigning a new DBIID will take some time. |
- Optionally, copy the restored databases to another server. We recommend
that you change the file extensions before copying (for example, to
user01mail.xxx), then rename the files with the .nsf extension after the file
copy is complete. This ensures that the server will not detect databases until
they are complete and consistent.
Back to Top