get
ting
st
ar
ted
wel
c
ome
r
t
er
in
orma
tion
42
t
e
mana
ger
t
e
c
onnect
or
Appendix 3 - Backing up and restoring
ADDER.NET performs an automatic daily database backup procedure and also
allows you to create additional backups on demand. You can restore any automatic
backup from the last seven days using a straightforward selection process.
To access the backup and restore controls
1 On the ADDER.NET Manager menu bar, place your mouse pointer over
Tools
and then choose
Backup & Restore
from the drop down list:
Backups
ADDER.NET copies its database every day, immediately after midnight. The
resulting backup files are named DB-Mon.ldif to DB-Sun.ldif respectively.
Additional backups can be made at any time by providing a destination file
name at ‘Save current database to’ and clicking the ‘Save’ button. The database
file name can be any valid file name. As such it is possible to save files on
different disks and on remote systems.
For example:
name.ldif
saves a file in the backup directory of the
ADDER.NET server.
\documents\name.ldif
saves file in the specified directory on server.
\\computer\directory\name.ldif
saves file on a remote computer in specified
directory.
ADDER.NET does not maintain a list of manual backup files, it just provides
access to the default backups directory. As such, the last two examples above
are not directly accessible for the restore function and would need to be
manually copied into the backups directory before they could be used.
To enable a complete recovery of the server, it is also necessary to take a backup
of the server’s cryptographic keys. This is the complete contents of the directory
keys directory (typically \\Program files\adder.net\keys\). The cryptographic keys
do not change after installation so they do not require regular backing up.
Note that with these keys, it would be possible to control all of the devices
that have been acquired by the ADDER.NET server. You may wish to take
considerably greater care to ensure that these files do not fall into the wrong
hands, than you would take with the database backups.
continued
