r1soft Backup Manager fails to start? We can help you.
Generally, we face this issue when the cdp-server service restarts while a disk safe is in a state of rolling back transactions.
As part of our Server Management Services, we assist our customers with several r1soft queries.
Today, let us see how we can fix the backup error.
r1soft Backup Manager fails to start
It is possible for Backup Manager to fail to fully start following an upgrade, reboot, or restart of the cdp-server service.
The latest entry in server.log shows:
2020-01-01 12:00:00,000 INFO - Storage Cache Service starting
This occurs when the cdp-server service restart while a disk safe is rolling back transactions.
To prevent this, we place the Backup Manager in Maintenance Mode.
In addition, we allow all transactions that run to complete before the reboot or restart the cdp-server service.
How to solve this issue?
To solve, we start the Backup Manager with all disk safes closed. Then we locate the disk safe that prevents the Backup Manager from fully starting, and address the disk safe(s) in question.
1. As we mentioned before, we start the Backup Manager with all disk safes closed.
2. Then we locate the problematic disk safes.
- To do so, we click Disk Safes from Settings.
- Then we open each disk safe, and click “Open Selected”. (We can select Multiple disk safes)
- We will eventually find one (or more) that fails to open. To refresh the screen we hit F5.
- Then we click > to expand the disk safe in question.
- We note the path for each disk safe that fails to open
3. After that, we correct the issue and open the disk safe.
- Since we have identified a few or one disk safe, we navigate to the disk safe path we previously noted.
- We change directories to the Metadata2 folder
- Then we type “ls -l” and look for any files ending with “.rollback”
- We need to delete the .rollback file or rename the file to XXXXX.rollback-old
- Eventually, we try again to open the Disk Safe through the UI.
- Later we repeat for each disk safe that fails to open normally.
[Still, stuck with the error? We are here for your assistance]
In short, we saw how our Support Techs fix this error for our customers.