You can tell if a system is down when the following is true:
- ChronBackup: Check. If chronbackup is open to an error about contacting Chronicle support, then system down.
- Server Manager: Check. If no apps are open or some are open check the services to see if the socket server is running, if not, then system down.
- Regedit: check. If regedit backup is blank, then system down.
If regedit ran more than 24 hours ago, and system is not down, then just run the back up.
If a system is down run backups> swap cti file> restart socket server> restart apps. To see that the backup ran, go to regedit and check the date/time of the CompletedBackup registry key. Registry> chronicle> ChronBackup> completedBackup> check date-time
How to run a failed backup:
- Log into server.
- Close all app minus the backup app. Or close all and restart the backup app.
- Close the Chronicle Socket Server to boot anyone that is still logged into the client. Open the server manager by right clicking on my computer > manage > configuration > services > Chronicle socket server and stop it. ((if you highlight and stop all apps on the server it will crash, so close them all first and it would boot everyone from the client)).
- Close chronserver2.exe in the task manager
- Then make sure chronserver2.exe is closed in task manager [[that should stop the process, but sometimes it gets stuck and you have to go into the processes list]] [[but if socket server is on then uesrs could have been using it so that should have been shut down first before backup]]
- To run a V1 backup: open server control panel>databases tab>non-destructive button. There is either a shortcut or go to the ‘chroniclectrlpanel’ folder and run ‘chroniclesvrctrlpanel.exe’
- To run a V2 backup: these are more common backups to run. On the Chronicle DBMaintenance screen just click unlock > password: 321Chronicle > click test/update backups > click "no" on the prompt (this only runs db backup). You can see how long it might take the backup to run by looking at the duration of the last back up.
- Once the backup is started – wait until it is done. If the backup fails that is a whole other problem
- Take a screen shot of backup data to capture the backup location for later if needed.
- Close the backup app
- Find the C:\cBackup folder> *DBTemp folder> or where ever the folder is that contains the backup file you just made
- In another window find the data folder which contains the bad CTI usually Chronicle\Data
- Rename back CTI by just adding today’s date to the name
- Copy/paste the backup you just made to the data folder
- Go to the server manager> configuration> services> right click on chronicle socket server>properties, which is set to manual, change to automatic> start it and apply settings, which restarts the socket server.
- Restart all the apps because they already crashed.
- Check the log, maybe it ran,
- Run the bridge if needed.
- Use the launch chronicle apps icon on the desktop to start all apps. ”Chronicle Servers Auto Launch”
A System down means the apps crashed. Close them all and make sure chronserver2.exe is also stopped in the process list. Including cFTP and reminder.exe