Unexpected Data Loss in D2000 Archive After System Restart

Support Forum
#1

Hello

I am encountering an issue where historical data in the D2000 Archive is sometimes lost after a system restart. :upside_down_face: The real-time data collection resumes as expected but certain past records seem to disappear or become inaccessible. This happens inconsistently, making it difficult to pinpoint the exact cause.

Could this be related to incorrect database settings; improper shutdown procedures / an issue with how D2000 handles data buffering before writing to the archive? :thinking:Iā€™ve checked the configuration but I havenā€™t found any clear errors.

If thereā€™s a recommended way to ensure data persistence & prevent loss during restarts, Iā€™d appreciate any advice. :thinking:

Checked official guide on troubleshooting D2000 Archive reliability and data recovery and CISSP Course Online related to this and found it quite informative. Any suggestions from users who have dealt with similar issues would also be helpful. Thanks!

Thank you !! :slightly_smiling_face:

#2

By default, D2000 Archive commits data after ā€œCommitCountActiveā€ (default 1000) values written or after ā€œCommitTimeActiveā€ seconds elapsed (default 60 seconds), whichever comes first.

So, if a D2000 Archive is killed (or it crashes), there may be this kind of data loss if it is stopped incorrectly.
To avoid it, correctly stop the D2000 Archive. On Windows, you can stop if via D2SMC or Sysconsole (or, if it runs as a service, stop it from Windows Service Manager). To minimize data loss (on non-redundant applications), the aforementioned parameters can be changed (e.g. to commit every 5 seconds).

Are you talking about this kind of data loss? Last several seconds, up to a minute? Or are we talking about something else? Can you also provide logs of the D2000 Archive?

In high-availability systems, we use 2 (or more) D2000 Archives (e.g. instances [1] and [2] of SELF.ARC) running on different computers. And we usually configure the arcsynchro utility to automatically patch a hole in data after one of the Archives has been off for some time (e.g. due to maintenance, Windows updates, etc).