Milestone XProtect Enterprise 2014 - Manual (Page 199)

Milestone XProtect ® Enterprise
2014
Administrator's Manual
www.milestonesys.com 199 System maintenance
Server's transaction log from time to time is therefore a good idea, however flushing it does not in itself
make the transaction log file smaller, rather it prevents it from growing out of control. Your system
does not, however, automatically flush the SQL Server's transaction log at specific intervals. This is
because users have different needs. Some want to be able to undo changes for a very long time,
others do not care.
You can do several things on the SQL Server itself to keep the size of the transaction log down,
including truncating and/or shrinking the transaction log (for numerous articles on this topic, go to
support.microsoft.com (see
http://support.microsoft.com ) - and search for SQL Server transaction log).
However, backing up the system's database is generally a better option since it flushes the SQL
Server's transaction log and gives you the security of being able to restore your system's alarm data in
case something unexpected happens.
Export and import management application configuration
You can export the current configuration of your Management Application, either as a safety measure
in order to have a backup file of your configuration, or as a clone allowing you to use a similar
Management Application configuration elsewhere. You can, at a later time, import previously exported
Management Application configurations.
Export Management Application configuration as backup
With this option, all relevant Management Application configuration files are combined into one single
.xml file, which you can specify a location for. Note that if there are unsaved changes to your
configuration, these are automatically saved when you export the configuration.
1. In the Management Application's File menu, select Export Configuration - Backup.
2. Browse to the location at which you want to store the exported configuration, specify a suitable
file name, and click Save.
If you intend to set up an identical version of your surveillance system elsewhere, do not export your
configuration as backup, since this may lead to the same device information being used twice, in
which case clients may get the following error message: Application is not able to start because
two (or more) cameras are using the same name or ID. Instead, export your configuration as a
clone. When you export as a clone, the export takes into account the fact that you are not using the
exact same physical cameras, etc. even though your new system may otherwise be identical to your
existing one.
Note that there is a difference between this Management Application configuration backup and the
system configuration backup done from the Milestone Surveillance folder because these are two
different things. The backup described here is limited to a backup of the Management Application
configuration. The type of system configuration backup done from the Milestone Surveillance folder is
a backup of your entire surveillance system setup (including, among other things, log files, event
configuration, restore points, view groups as well as the Management Application and XProtect Smart
Client configuration).
Export Management Application configuration as clone
With this option, all relevant Management Application configuration files are collected, and GUIDs
(Globally Unique IDentifiers, unique 128-bit numbers used for identifying individual system
components, such as cameras) are marked for later replacement. GUIDs are marked for later
replacement because they refer to specific components (cameras and so on). Even though you wish
to use the cloned configuration for setting up a new similar system using similar types of cameras, the