Milestone M50 - Manual (Page 190)

Milestone Husky M30/M50 Administrator's Manual
www.milestonesys.com 190 Backup and restore configuration
Tip: If you get an error message telling you that the database is in use, try exiting Microsoft SQL
Server Management Studio Express completely, then repeat steps 1-8.
Tip: VIDEOOSDB is the default name of the database containing the system configuration. If you can
find the database, but it is not called VIDEOOSDB, it could be because you gave the database
another name during installation. In the following, we assume that the database uses the default
name.
Step 5: Restart the Event Server service
During the restore process, the Event Server service is stopped to prevent configuration changes
being made until you are done. Remember to start the service again:
1. On your surveillance system server, click Start > Control Panel > Administrative Tools >
Services.
2. Right-click the Event Server, click Start.
About the SQL Server Express transaction log and reasons for flushing it
Each time a change in the Milestone Husky product alarm data take place, the SQL Server logs the
change in its transaction log. The transaction log is essentially a security feature that makes it possible
to roll back and undo changes to the SQL Server Express database. The SQL Server by default stores
its transaction log indefinitely, and, therefore, the transaction log builds up more and more entries over
time.
The SQL Server's transaction log is by default located on the system drive, and if the transaction log
just keeps growing, it may in the end prevent Windows from running properly. Flushing the SQL
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. Milestone Husky
product 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 - http://support.microsoft.com) and search for
SQL Server transaction log). However, backing up the Milestone Husky product 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 Milestone Husky product alarm data in case something unexpected happens.
Export and import management application
configuration
You can export the current configuration of your Milestone Husky product 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.