Archives and recordings in Xeoma: troubleshooting and advice
Saving recordings is an essential feature for nearly any video surveillance system. Video footage can be used as forensic evidence, or be utilized for post-incident investigations.
Xeoma video surveillance software offers a variety of ways for perpetual storage of video recordings, the main of which being with the “Preview and Archive” module.
Here are some answers to questions that some users might have while using the archive recording feature.
Possible issue: Recordings are not saved
1. Check that the module “Preview and Archive” is connected into the chain, turned on, and check the logic of the chain lest there be any preceding modules that you don’t need.
2. Check that there are no filter modules that are filtering out the video excessively. Remember that the recording module should get the signal from the preceding modules. For example, when Motion Detector is used with very strict settings, it often doesn’t let video further on to the following modules, one of which can be the “Preview and Archive” module.
3. Check that the camera stream is working and accessible (if direct saving is used, you need to check the archive stream rather than the preview stream). If the archive stream fails, Xeoma will start writing the stream to the archive for viewing. Also, an error notification will appear in the camera window. See more about direct saving to the archive here
4. Check that your storage path is valid. Open settings of the “Preview and Archive” module and check if the path entered is valid and has the writing permissions. In Linux, you can execute chmod for Xeoma to make sure there are writing rights – or try another path where you know for sure that recording is available to.
5. Check that your disk is available (especially for mounted disks). If the mounted disk was working for some time and then got disconnected, naturally Xeoma will not have the required place to store recordings to. Usually, in such case you get a warning message displayed over the preview box.
6. HDDs can stop recording due to failure. You can check the status of your drive with SMART.
7. The disk may have been overloaded. If a large number of cameras are being written to the same disk, it may not be able to handle simultaneous recording and/or deleting.
8. If there are only parts of recordings missing, check if connection to the camera is stable. If it is intermittent, recordings might be absent for the time without connection. We have a synchronization with camera memory card method in Xeoma for when the connection is known to be intermittent. Read more here.
! Also check that the computer with server part of Xeoma is not freezing due to high CPU load and/or does not get into the Sleep mode.
Possible issue: No marking / video resize / video crop seen in archive recordings
To reduce CPU and network load as well as HDD space requirements, Xeoma utilizes the so called dual streaming capabilities of the camera for direct saving to the archive. If direct saving to archive is used, no filters are applied to archive recordings (with a few exceptions like Motion Detector and some cases of Marking).
Untick the direct saving to archive options in the “Universal Camera” module settings to see if that helps – but be ready for a surge in CPU load. Contact us for free help in re-configuring your system.
Possible issue: Out-of-time mal-synchronization of archive recordings compared to the camera time or real time
1. Please see if you’re using the latest version of Xeoma. Many time issues have been fixed in the latest version of Xeoma.
2. When time is asynchronous by a matter of round hours, this can also be fixed by choosing the same timezone in Main menu – Remote Access – Users as you have in your machine where Xeoma’s server part is running.
3. Time synchronization issues where time is off by some minutes can be fixed by using a new option in “Universal Camera” settings – a checkbox called “Use the server’s system time to generate timestamps for frames (use in case of archive mistiming issues)”.
It will help if the camera stream is sending misleading timestamps that result in:
– Weird time of archive recordings
– Video distortions caused by frames getting to the wrong part of archive and thus ruining finalization of compressed files
– Missing parts of archives
Possible issue: Archive recordings are not erased, archive is overfilled, no new records are getting saved
Loop recording is working all the time, there is no special settings enabling it.
1. Please see if you’re using the latest version of Xeoma. Download it here
2. Check the preferences in disk space that Xeoma should leave free in the “Preview and Archive” settings. Sometimes there is so little space allocated to Xeoma that it has to remove recordings right after they are saved which feels like it cannot save any recordings.
Possible issue: Archive recordings are erased although they shouldn’t
Check the settings of preferences in disk space that Xeoma should leave free in the “Preview and Archive” settings. One probable reason is that one of the RAID disks is not available anymore and the total disk space is reduced, so less space is now available for Xeoma and it has to remove recordings to be able to store new ones.
Also try the latest version of Xeoma. Download it here
How do I make a backup of recordings in Xeoma
1. Failover: a backup server is always in touch with the main server (or several main servers) and is ready to substitute it if the main server is not working. Archive recordings can be saved to a network drive or RAID array of drives so that they are available in the main server’s built-in Archive viewer when it is back to function.
2. By connecting several “Preview and Archive” modules to the same chain, you can set one of them to save recordings to another place where they will be not susceptible to Xeoma’s erasure mechanisms. Also, copying Xeoma recordings to backups can be made with the computer system’s tools, outside of Xeoma, or with the FTP Upload module.
Transferring records with a database
To transfer databases correctly, please follow this procedure on the new server:
1. sudo path_to_xeoma.app -core – this will create directory /usr/local/Xeoma/
2. activate licenses
3. kill the process: sudo kill [PID]
4. put to /usr/local/Xeoma/ file settings.dat taken from original server (replacing the existing one)
5. if your server has GUI, then double click on xeoma.app; if not, repeat step 1, then connect as client
6. change the settings of “Preview and Archive” modules and record archive storage path to the ones you need (by default they are the same as in Windows)
7. repeat step 3
8. in /usr/local/Xeoma/XeomaArchive/ we put all Database folder from original server (replacing the existing one)
9. sudo path_to_xeoma.app -install -coreauto
How do I use the camera’s embedded memory space when connection to Xeoma server is lost, and then import those recordings to Xeoma when the connection is reinstated?
You can do that for ONVIF cameras with the “Synchronize with SD card” option in Xeoma Standard/Xeoma Pro. See more in this article
Failed to export an extract from the archive
If there is an error message displayed during or after the export process, please read it to know the reason for the failure. Please try to use Xeoma client and Xeoma server of the same version (for example, the latest version available from the Download page).
Usually it’s either an intermittent Internet connection for exports done remotely or too little free space in drive or memory to do export of a big piece. Try export in smaller pieces in either case.
It is also possible that you do not have access rights to create a new file with the program on your server.
How do I start recording in Xeoma?
How do I know that recording is working OK?
How do I limit space Xeoma is allowed to take with its recordings?
What limiters – space or time of storage – is prioritized is Xeoma?
10 February, 2021