Cyber Protect 15 - Replication Task not starting as scheduled
We do use several replication plans to replicate our hdd backups to tape.
All of a sudden these tasks stopped starting at the scheduled day and time.
No warning, no email, no further notice. It just stopped doing anything.
The replication plans do run just fine when started manually.
It is now the 2nd time this problem occurs. Last time the "solution" was to create an new plan and the promise it will be solved in "the next update".
This time i'm not willing to accept that.
Tell me how to permanently solve that problem. we need a backup software we can rely on.
Hi,
I have built a collection of two scripts to fix this in the folder C:\Skript on the management server.
Script 1 (PowerShell, name fix-AcronisReplication.ps1) - this has to be executed as Administrator:
#Requires sqlite.exe, fixAcronis.cmd and the exported replication plans in C:\Skript
$replicationplans = gci "C:\Skript\*.json"
foreach ($plan in $replicationplans) {
#extract PlanID from json file
$rawPlanID = [string](get-content $plan | select-string -pattern "planID")
$anfang = $rawPlanID.IndexOf(":") + 2
$PlanID = $rawPlanID.Substring($anfang+1,$rawPlanID.Length-$anfang-3)
#transfer variable $PlanID to batch
cmd /c C:\Skript\fixAcronis.cmd $PlanID
}
Get-Service asm | restart-service
Script 2 (batch file, name fixAcronis.cmd):
@rem Addition to clean-AcronisReplication.ps1
@rem Parameter: Variable plan_id
C:\Skript\sqlite3.exe C:\ProgramData\Acronis\BackupManager\acronis_backup_manager.db "update policies_events set tasks='null' where plan_id='%1';"
If you get access denied messages for the batch file even with admin permissions, you may need to alter the path to access the database over network, since Acronis self protection may kick in with local access, i.e. \\server\c$\ProgramData\Acronis\BackupManager\acronis_backup_manager.db
This script combo was created as result of a session with the Acronis support to solve the very same issue. I run it only, if the replication is not executed, one could also perform a conditional check (i.e. no new data on RDX media) and/or run it as Scheduled Task in Windows.
Best greetings from Germany
Olaf
Start by examining the logs of your backup software to see if there are any error messages or warnings related to the failed tasks. This can provide clues about what went wrong.
I had the same problem with the "Backup to VM" plans. After a certain amount of time, these simply no longer started as planned. No warning, no message. I only ever noticed it during a manual check. Support was never able to offer a solution. Luckily I no longer need this feature.
cerberus wrote:I had the same problem with the "Backup to VM" plans. After a certain amount of time, these simply no longer started as planned. No warning, no message. I only ever noticed it during a manual check. Support was never able to offer a solution. Luckily I no longer need this feature.
Hello, thanks for sharing your feedback.
As far as I can see in the records, our support team offered a remote session that you declined. Feel free to reopen the ticket if you desire further investigation of the issue.
Thanks in advance!
I had already opened several tickets before this ticket, all of which contained similar errors. I spent a few hours in remote sessions and many more hours collecting log files and recreating errors. Unfortunately, all of this never led to a positive result. At some point you have to justify your own effort to your own employer. Acronis never gave us any kind of bonus or discount.
Apparently only new features are being added or the transformation to security software is being pushed forward; in my opinion, there is no longer any troubleshooting.
Replication is kind of the redheaded stepchild of the Acronis Cyber Protect product... (not yet fully sure in cloud version, bot not supporting tapes as local target for cloud based management has been another unnice experience).
I have rarely problems with the Acronis software in all scenarios without replication (once the initial hassles after some updates have been resolved).
The problem is the time difference between full backups and replications which make it sometimes hard to avoid replication.
Best greetings from Germany
Olaf