Page 1 of 1
Centralized Backup stops making backups
Posted: 12 Nov 2024, 15:00
by mouse2k3
Good afternoon, faced with such a problem, Centralized Backup stops doing backups. There is a connection with the machine, the services are up, but there are no backups in automatic mode, when manually activated, it writes that the machine is offline. This happens on all types of Windows /home/pro and even Server 2016. As I understand it, it's not about the Windows version, since on some machines (I work as a system administrator in a small company) Centralized Backup has been running like clockwork for a long time.
Tell me where to look and what to do?
As I said, the services are working, the machines are online. Restarting the users' computers and the NAS does not help. Restarting services doesn't help either. The solution is to delete Centralized Backup and reinstall it, but this is not a panacea, since visually the program does not show whether there was a failure in saving the backup. Therefore, you have to go to the backup save folder and watch the file creation time. Checking 50 backup folders takes time, and then you need to reinstall Centralized Backup on the machines that failed. And it's sad

Re: Centralized Backup stops making backups
Posted: 13 Nov 2024, 09:40
by GevinKe
mouse2k3 wrote: ↑12 Nov 2024, 15:00
Good afternoon, faced with such a problem, Centralized Backup stops doing backups. There is a connection with the machine, the services are up, but there are no backups in automatic mode, when manually activated, it writes that the machine is offline. This happens on all types of Windows /home/pro and even Server 2016. As I understand it, it's not about the Windows version, since on some machines (I work as a system administrator in a small company) Centralized Backup has been running like clockwork for a long time.
Tell me where to look and what to do?
As I said, the services are working, the machines are online. Restarting the users' computers and the NAS does not help. Restarting services doesn't help either. The solution is to delete Centralized Backup and reinstall it, but this is not a panacea, since visually the program does not show whether there was a failure in saving the backup. Therefore, you have to go to the backup save folder and watch the file creation time. Checking 50 backup folders takes time, and then you need to reinstall Centralized Backup on the machines that failed. And it's sad
Hello! In order to assist you in resolving the issue more effectively, could you please provide the specific version information for TOS and CB? Based on your description, the Agent seems to have successfully established a connection with CB, but the backup task fails to start. To analyze the problem more deeply, we greatly need you to provide some relevant videos or screenshots for reference. Please note that our email (
[email protected]) supports attachments of up to 20MB; if the file is too large, we recommend using a cloud storage service (such as Google Drive, Dropbox, etc.) or our NAS sharing function to send a link.
Additionally, regarding the issue of device and task association, we have optimized and improved it in the latest version. This update includes many important improvements and new features, so you may also consider waiting for our new version to enjoy a better user experience.
Thank you for your understanding and cooperation. We look forward to resolving your issue as soon as possible.
Re: Centralized Backup stops making backups
Posted: 16 Nov 2024, 04:04
by Amdar
Hi all,
I have the same issue.
Only I can do volumen backup of windows 11. When I selected "System only" or "Full backup" it added the task then I tried to start the backup and running in a 3 or 4 second became failed backup.
I'm using TOS 6. The last realese
I tried to find more information into the logs unsuccessfully.
Any help on it I would appreciate it.
Re: Centralized Backup stops making backups
Posted: 19 Nov 2024, 09:22
by GevinKe
Amdar wrote: ↑16 Nov 2024, 04:04
Hi all,
I have the same issue.
Only I can do volumen backup of windows 11. When I selected "System only" or "Full backup" it added the task then I tried to start the backup and running in a 3 or 4 second became failed backup.
I'm using TOS 6. The last realese
I tried to find more information into the logs unsuccessfully.
Any help on it I would appreciate it.
Hello, we sincerely apologize for any inconvenience caused to you. To assist you in resolving your issue more promptly, please follow these steps to send your backup logs to our official email (
[email protected]):
1. Use the shortcut Win+R to open the "Run" dialog box.
2. Enter "%appdata%" and press Enter, which will open the application data folder.
3. Locate the folder named "Centralized Backup" within this folder.
4. After entering the "Centralized Backup" folder, select the "Logs" folder and the file named "backup_svc_xxxx" .
5. Compress the selected files and folder into a single file.
6. Send the compressed file via email to
[email protected].
Additionally, if your backup needs are not urgent, we recommend that you wait patiently as we will be releasing a new version soon, which may address the issues you are experiencing.
Thank you once again for your understanding and cooperation. We are committed to serving you with dedication.
Re: Centralized Backup stops making backups
Posted: 19 Nov 2024, 14:45
by mouse2k3
TMgevin wrote: ↑13 Nov 2024, 09:40
mouse2k3 wrote: ↑12 Nov 2024, 15:00
Good afternoon, faced with such a problem, Centralized Backup stops doing backups. There is a connection with the machine, the services are up, but there are no backups in automatic mode, when manually activated, it writes that the machine is offline. This happens on all types of Windows /home/pro and even Server 2016. As I understand it, it's not about the Windows version, since on some machines (I work as a system administrator in a small company) Centralized Backup has been running like clockwork for a long time.
Tell me where to look and what to do?
As I said, the services are working, the machines are online. Restarting the users' computers and the NAS does not help. Restarting services doesn't help either. The solution is to delete Centralized Backup and reinstall it, but this is not a panacea, since visually the program does not show whether there was a failure in saving the backup. Therefore, you have to go to the backup save folder and watch the file creation time. Checking 50 backup folders takes time, and then you need to reinstall Centralized Backup on the machines that failed. And it's sad
Hello! In order to assist you in resolving the issue more effectively, could you please provide the specific version information for TOS and CB? Based on your description, the Agent seems to have successfully established a connection with CB, but the backup task fails to start. To analyze the problem more deeply, we greatly need you to provide some relevant videos or screenshots for reference. Please note that our email (
[email protected]) supports attachments of up to 20MB; if the file is too large, we recommend using a cloud storage service (such as Google Drive, Dropbox, etc.) or our NAS sharing function to send a link.
Additionally, regarding the issue of device and task association, we have optimized and improved it in the latest version. This update includes many important improvements and new features, so you may also consider waiting for our new version to enjoy a better user experience.
Thank you for your understanding and cooperation. We look forward to resolving your issue as soon as possible.
Hi! You will not believe it, after creating a post on the forum, the error did not appear

I did stress tests, with power off and other loads, but every time the software and the service came to work.
With the return of the error, I will also return

Re: Centralized Backup stops making backups
Posted: 21 Nov 2024, 09:19
by GevinKe
Due to the fact that PC backups are highly susceptible to various environmental factors, including but not limited to unstable network conditions, fluctuating disk performance, compatibility issues with partitioning methods, and failures in capturing snapshots, relying on log records to diagnose corresponding problems is generally more convenient and accurate.