Milestone XProtect Express 2014 - Manual (Page 124)

Milestone XProtect ® Express 2014 Administrator's Manual
www.milestonesys.com 124 Advanced configuration
Same drive: Automatic moving or deletion of archives if drive runs out of disk space
If your system server is running out of disk space, and the archiving drive is identical to the camera
database drive, your system automatically does a number of attempts to free up space. Most of these
attempts will result in the loss of your data from archives or databases.

First, the system attempts to move archives. You can only move archives if you use dynamic
archiving, with which you can archive to several different drives. This happens if:
o there is less than 15% disk space left, and the available disk space goes below 40 GB plus
2 GB per camera
- or -
o the available disk space goes below 225 MB plus 30 MB per camera. Example: with ten
cameras, the server would be running out of disk space if the remaining available disk
space went below 525 MB (225 MB plus 30 MB for each of the ten cameras).
The difference ensures that very large disks are not necessarily considered to be running out
of disk space just because they have less than 15% disk space left.

If the system cannot move archives, your system attempts to delete the oldest archives. This
happens if:
o there is less than 10% disk space left, and the available disk space goes below 30 GB plus
1.5 GB per camera
- or -
o the available disk space goes below 150 MB plus 20 MB per camera (example: with ten
cameras, the server would be running out of disk space if the remaining available disk
space went below 350 MB (150 MB plus 20 MB for each of the ten cameras))
The difference ensures that very large disks not necessarily are considered to be running out
of disk space just because they have less than 10% disk space left.

If there are no archives to delete, your system attempts to resize camera databases by
deleting their oldest recordings. This happens if:
o there is less than 5% disk space left, and the available disk space goes below 20 GB plus
1 GB per camera
- or -
o the available disk space goes below 75 MB plus 10 MB per camera (example: with ten
cameras, the server would be running out of disk space if the remaining available disk
space went below 175 MB (75 MB plus 10 MB for each of the ten cameras))
The difference ensures that very large disks will not necessarily be considered to be running
out of disk space just because they have less than 5% disk space left.
When the system restarts your recording server after resizing the database, the original databases
sizes are used, so you should make sure that the drive size problem is solved or, alternatively, adjust
camera database sizes to reflect the altered drive size.
If the system performs the database resizing procedure, you are informed on-screen in XProtect Smart
Client, in log files, and or in notifications (if set up).