You actually do need to set up a rule - and you have to specify the <device> you want to pull data from once the server can see it again.
Marty - thanks for the reply on this. So, if I want it to only retrieve recordings during the time when communication was down, should I set the "Retrieve and store remote recordings from <devices>" rule to "Always"? Sorry, but I'm just a little unclear as to how the rule interacts with the checkbox in the Record tab - particularly if I want this to occur when communication is restored and only to fill in gaps where needed.
Thanks again - much appreciated.
Marty: sorry for the delayed reply and thank you for the clarification and the screen shots - I had it up and working in a few hours using your suggestions. Much appreciated...
Great to see a resolution here, but I wanted to note that all that *should* be needed to retrieve edge storage automatically after a lost network connection or server restart is to check that box on the recording tab of the camera(s). No rules necessary!
Edge retrieval can be finicky sometimes though. For example...
- time between camera and server must be synced
- strategy for *how* to retrieve the recordings varies based on whether the camera is recording continuously or on event (ex. motion). There is a setting for each channel in general settings for the camera to specify which strategy should be used
- lastly I'd verify the firmware is supported and the latest device pack is installed
If further troubleshooting is needed, it can help to know what to expect - the Recording Server keeps the timestamp of the last received images for edge enabled cameras in c:\programdata\milestone\xprotect recording server\edgestorage.xml and after a period of lost connection, the first newly received image timestamp is used to create an edge retrieval job between the two timestamps. The Logs folder has an edge storage log for more info, but honestly the log isn't really helpful without debug logging enabled and at that stage it's usually time to speak with technical support anyway.
Also a side note, the "video loss" event is actually primarily an event sent from analog video encoders to notify on a lost analog signal. It does not work as an event for when the network connection is lost. For that you want the built-in event "communication error".
Sorry to dig up an old thread, I did a search for XProtect and noticed Martys really helpful responses but also noted it *should* have been easier.