Structure of versiondog

There are multiple ways a versiondog system can be structured and operated. The basic structure for a server is always the same and consists of a Windows service and the associated processes that are monitored by this service.

Server: Server processes of the VDogMasterService

The VDogMasterService monitors all subordinate server modules (processes). If there are any problems, an email is sent to the administrators. At the same time, the VDogMasterService attempts to solve the problems directly. Automatic recovery will fail only in exceptional cases. In the majority of cases, administrator intervention is not necessary.

In general, this is a very stable process structure. Even if all server modules were to become inoperative, it would still be possible to access the user data.

What do I need to do to restart the versiondog system after a server failure?

 

To restart versiondog after a server failure without losses, stop the MasterService in the Task Manager via End Process Structure before restarting the server operating system, if possible. After all relevant processes have been terminated, restart the server operating system.

Restarting the operating system can put the PostgreSQL database into a corrupt state.

 

In this tutorial: