Backup 12.5: Settings for keeping only one Backup .TIB, and purge the existing one before new backup
Hi,
i want acronis to write backups on RDX, only full backups, each day on windows drive letter G:\.
I set to keep one backup, and purge "before the backup".
Acroins leaves the existing .tib file on that RDX device untoched and adds another .tib, by counting like ED95XT.....-0001.tibx.
Since the backup is 450 GB on a 500GB RDX, it fails all the time. Is this because acronis does not have the opportunity to keep track of all the backups' on the other RDX harddiscs?
So, how can i force to empty G:\ before starting the new backup? I hope there is a build in way and i do not have to use the "before backup options" and write a script to purge G:\ ?
thanks guys

- Log in to post comments

But until 11.7 there WAS an option for e. g. backup on USB drives to DELETE old backups if not enough space is available.
When this feature will be re-integrated in 12.5???? And: why did you removed it?
- Log in to post comments

i have to agree with dk-one, this is simply unbelievable.
I now had to edit a batch file like back in 1993, and acronis does not even valid interpret this: the error below "Fehler" is, since i added "sleep 10" or "timeout /t 10" to the batchfile, which prevents acronis from starting the job.
but ok, this now is for the server, that is running management server AND has the local G:\, which is a RDX drive.
What about the 10 clients i want to add now? where do i have to put the batch file, that gets run by the acronis job? to all the local PC, which have their own RDX driveletter in windows? i dont get it. management server calls the client's local batch file and then starts the backup? come on.
I do this, like all others, in order to prevent ransomware. is this acronis answer, to have their customers try n error batch files?
thanks
- Log in to post comments

Hi,
The functionality to cleanup archive upon free space insufficiency was not migrated to Acronis Backup 12.5 yet - it is planned for future updates (internal ID: ABR-118624). The reason behind it is that not all features can be migrated at the same time and we have to re-implement some of them from scratch to match the new 12.5 platform. This particular feature didn't make it by the release but we are still planning to make it in future.
The batch files are executed by corresponding agents (not by AMS) at the time the backup starts, so they have to be put onto the protected machines local folders. Note that if you have different drive letters for the RDX drive on different agents, then you would need different backup plans for these agents in either case (the batch file can be put onto the RDX drive itself).
Thank you.
- Log in to post comments

Vasily thanks for coming back to this. like i stated, pre-backup script causes acronis to abort.
when i pre-backup run something like "rmdir g:\backup" it gets executed and the folger deleted. but then, i assume, acronis can not "fast enough" write to the device and aborts, see log below.
when i re-run the same backup plan a minute after abort without changing anything, acronis startes to backup. really, what is the official solution to this? dont tell me i have to use windows task to empty G:\ in order to have acronis execute its backup job.
thanks
2017-06-20 22:36:48:728 1604 I0135003A: Der Benutzer 'JME2\Administrator' (clientProfileID=5EF8C0B8-84EE-27B7-3802-2482668EBC3C; clientSessionID=ECE2158B-C7F9-405F-B995-E1D3C88031E8; tenantID=00000000-0000-0000-0000-000000000000) führt gerade den Befehl 'Backup-Plan 'JME-S2-Voll-Tgl'' aus.
2017-06-20 22:36:57:392 5948 I0135003A: Der Benutzer 'JME2\Administrator' (clientProfileID=5EF8C0B8-84EE-27B7-3802-2482668EBC3C; clientSessionID=ECE2158B-C7F9-405F-B995-E1D3C88031E8; tenantID=00000000-0000-0000-0000-000000000000) führt gerade den Befehl 'Executing pre-backup command' aus.
2017-06-20 22:36:58:741 5948 I00010400: Child-Prozess endete mit dem Code '0'.
2017-06-20 22:36:58:761 5948 I0135003B: Befehl 'Executing pre-backup command' wurde erfolgreich abgeschlossen.
2017-06-20 22:37:00:940 1684 I0135003A: Der Benutzer 'JME2\Administrator' (clientProfileID=5EF8C0B8-84EE-27B7-3802-2482668EBC3C; clientSessionID=ECE2158B-C7F9-405F-B995-E1D3C88031E8; tenantID=00000000-0000-0000-0000-000000000000) führt gerade den Befehl 'Backup' aus.
2017-06-20 22:37:01:112 1684 I00000000: I00000000: Backup Inclusions list:
2017-06-20 22:37:01:127 1684 I00000000: I00000000: C:
2017-06-20 22:37:01:142 1684 I00000000: I00000000: DATAPART1 (D:)
2017-06-20 22:37:01:157 1684 I00000000: I00000000: System-reserviert
2017-06-20 22:37:01:174 1684 I00000000: I00000000: Daten2 (E:)
2017-06-20 22:37:01:193 1684 I00000000: I00000000: Archive: G:/bu/\JME-S2.JME2.local-EB97D6B3-DA58-4474-89A8-B4651B687E9F-DEB19F08-D452-4110-8D4D-AAF301322B3BA
2017-06-20 22:37:02:551 1604 E01350016: Fehler 0x1350016: TOL: Failed to execute the command. Backup
| Ablaufverfolgungsebene: Fehler
| Channel: tol-activity#575FF0F7-4510-4963-9C7B-F0636D326379
| Zeile: 0x8d165e86fb81959b
| Datei: k:\7048\enterprise\common\tol\command\command.cpp:461
| Funktion: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: service_process_vsa64_7048
|
| Fehler 0x1350016: TOL: Failed to execute the command. Backup
| Zeile: 0x8d165e86fb81959b
| Datei: k:\7048\enterprise\common\tol\command\command.cpp:461
| Funktion: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: gtob_backup_command_addon_vsa64_7048
|
| Fehler 0xf90004: Dml::AsyncServer::State::JobPool
| Zeile: 0x20f14f64de1eccac
| Datei: k:\7048\enterprise\common\dml\messaging\async_server.cpp:242
| Funktion: Dml::Messaging::AsyncServer::State::State
| $module: mms_vsa64_7048
|
| Fehler 0x14b002f: Cannot find item '\local\hd_sign(28E37FD2)' selected for backup.
| Zeile: 0xfcaee9d6a8889a95
| Datei: k:\7048\enterprise\managers\gtob\providers\disk_item_provider\impl\item_iterators.cpp:301
| Funktion: GctDiskItemProvider::ChildResolver::Next
| $module: disk_item_provider_vsa64_7048
2017-06-20 22:37:02:571 1604 E01350016: Fehler 0x1350016: TOL: Failed to execute the command. Backup workflow
| Ablaufverfolgungsebene: Fehler
| Channel: tol-activity#575FF0F7-4510-4963-9C7B-F0636D326379
| Zeile: 0x8d165e86fb81959b
| Datei: k:\7048\enterprise\common\tol\command\command.cpp:461
| Funktion: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: F30407D6-601F-11E0-9C67-FF46DFD72085
| $module: mms_vsa64_7048
|
| Fehler 0x1350016: TOL: Failed to execute the command. Backup workflow
| Zeile: 0x8d165e86fb81959b
| Datei: k:\7048\enterprise\common\tol\command\command.cpp:461
| Funktion: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: F30407D6-601F-11E0-9C67-FF46DFD72085
| $module: gtob_backup_command_addon_vsa64_7048
|
| Fehler 0x1490002: Schritt 'Backup' ist fehlgeschlagen.
| Zeile: 0x8edc81ea38faba77
| Datei: k:\7048\enterprise\managers\gtob\backupers\backup_command\impl\backup_workflow_command.cpp:619
| Funktion: `anonymous-namespace'::BackupWorkflowCommand::ProcessWorkflowSteps
| TraceLevel: 0x1
| StepType: 0x2
| $module: gtob_backup_command_addon_vsa64_7048
|
| Fehler 0x1350016: TOL: Failed to execute the command. Tol::IsolateCommand
| Zeile: 0x8d165e86fb81959b
| Datei: k:\7048\enterprise\common\tol\command\command.cpp:461
| Funktion: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 4504F8D4-2727-42AB-BB4F-A42EDBB790A0
| $module: mms_vsa64_7048
|
| Fehler 0x1350016: TOL: Failed to execute the command. Backup
| Zeile: 0x8d165e86fb81959b
| Datei: k:\7048\enterprise\common\tol\command\command.cpp:461
| Funktion: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: service_process_vsa64_7048
|
| Fehler 0x1350016: TOL: Failed to execute the command. Backup
| Zeile: 0x8d165e86fb81959b
| Datei: k:\7048\enterprise\common\tol\command\command.cpp:461
| Funktion: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: gtob_backup_command_addon_vsa64_7048
|
| Fehler 0xf90004: Dml::AsyncServer::State::JobPool
| Zeile: 0x20f14f64de1eccac
| Datei: k:\7048\enterprise\common\dml\messaging\async_server.cpp:242
| Funktion: Dml::Messaging::AsyncServer::State::State
| $module: mms_vsa64_7048
|
| Fehler 0x14b002f: Cannot find item '\local\hd_sign(28E37FD2)' selected for backup.
| Zeile: 0xfcaee9d6a8889a95
| Datei: k:\7048\enterprise\managers\gtob\providers\disk_item_provider\impl\item_iterators.cpp:301
| Funktion: GctDiskItemProvider::ChildResolver::Next
| $module: disk_item_provider_vsa64_7048
2017-06-20 22:37:02:602 1604 E0135003D: Fehler 0x135003d: Befehl 'Backup-Plan 'JME-S2-Voll-Tgl'' ist fehlgeschlagen.
| Ablaufverfolgungsebene: Fehler
| Channel: tol-activity#575FF0F7-4510-4963-9C7B-F0636D326379
| Zeile: 0x4a8728dc8a1c95a1
| Datei: k:\7048\enterprise\common\tol\gating_activity.cpp:251
| Funktion: Tol::`anonymous-namespace'::BusinessActivityTracker::OnCompleted
| $module: mms_vsa64_7048
|
| Fehler 0x1350016: TOL: Failed to execute the command. Backup-Plan 'JME-S2-Voll-Tgl'
| Zeile: 0x8d165e86fb81959b
| Datei: k:\7048\enterprise\common\tol\command\command.cpp:461
| Funktion: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: D332948D-A7A9-4E07-B76C-253DCF6E17FB
| $module: mms_vsa64_7048
|
| Fehler 0x1350016: TOL: Failed to execute the command. Backup-Plan 'JME-S2-Voll-Tgl'
| Zeile: 0x8d165e86fb81959b
| Datei: k:\7048\enterprise\common\tol\command\command.cpp:461
| Funktion: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: D332948D-A7A9-4E07-B76C-253DCF6E17FB
| $module: agent_protection_addon_vsa64_7048
|
| Fehler 0x1330029: Ausführen des Befehls fehlgeschlagen.
| Zeile: 0xe6792a5ee190de2c
| Datei: k:\7048\enterprise\managers\gtob\protection\agent_engine\protect_command.cpp:218
| Funktion: `anonymous-namespace'::ProtectCommand::SafeExecute
| $module: agent_protection_addon_vsa64_7048
|
| Fehler 0x1350035: 2 Aktivitäten konnten nicht erfolgreich abgeschlossen werden. Eine davon wird angezeigt.
| Zeile: 0x2e7e9e174f1fb719
| Datei: k:\7048\enterprise\common\tol\replica\event_processor.cpp:110
| Funktion: Tol::`anonymous-namespace'::CreateCumulativeError
| FailCount: 0x2
| $module: agent_protection_addon_vsa64_7048
|
| Fehler 0x1350016: TOL: Failed to execute the command. Backup
| Zeile: 0x8d165e86fb81959b
| Datei: k:\7048\enterprise\common\tol\command\command.cpp:461
| Funktion: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: service_process_vsa64_7048
|
| Fehler 0x1350016: TOL: Failed to execute the command. Backup
| Zeile: 0x8d165e86fb81959b
| Datei: k:\7048\enterprise\common\tol\command\command.cpp:461
| Funktion: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: gtob_backup_command_addon_vsa64_7048
|
| Fehler 0xf90004: Dml::AsyncServer::State::JobPool
| Zeile: 0x20f14f64de1eccac
| Datei: k:\7048\enterprise\common\dml\messaging\async_server.cpp:242
| Funktion: Dml::Messaging::AsyncServer::State::State
| $module: mms_vsa64_7048
|
| Fehler 0x14b002f: Cannot find item '\local\hd_sign(28E37FD2)' selected for backup.
| Zeile: 0xfcaee9d6a8889a95
| Datei: k:\7048\enterprise\managers\gtob\providers\disk_item_provider\impl\item_iterators.cpp:301
| Funktion: GctDiskItemProvider::ChildResolver::Next
| $module: disk_item_provider_vsa64_7048
2017-06-20 22:37:02:060 1684 E0135003D: Fehler 0x135003d: Befehl 'Backup' ist fehlgeschlagen.
| Ablaufverfolgungsebene: Fehler
| Channel: tol-activity#E0B9E2D6-FD44-479C-8D15-BC64C667F054
| Zeile: 0x4a8728dc8a1c95a1
| Datei: k:\7048\enterprise\common\tol\gating_activity.cpp:251
| Funktion: Tol::`anonymous-namespace'::BusinessActivityTracker::OnCompleted
| $module: service_process_vsa64_7048
|
| Fehler 0x1350016: TOL: Failed to execute the command. Backup
| Zeile: 0x8d165e86fb81959b
| Datei: k:\7048\enterprise\common\tol\command\command.cpp:461
| Funktion: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: service_process_vsa64_7048
|
| Fehler 0x1350016: TOL: Failed to execute the command. Backup
| Zeile: 0x8d165e86fb81959b
| Datei: k:\7048\enterprise\common\tol\command\command.cpp:461
| Funktion: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 8F01AC13-F59E-4851-9204-DE1FD77E36B4
| $module: gtob_backup_command_addon_vsa64_7048
|
| Fehler 0xf90004: Dml::AsyncServer::State::JobPool
| Zeile: 0x20f14f64de1eccac
| Datei: k:\7048\enterprise\common\dml\messaging\async_server.cpp:242
| Funktion: Dml::Messaging::AsyncServer::State::State
| $module: mms_vsa64_7048
|
| Fehler 0x14b002f: Cannot find item '\local\hd_sign(28E37FD2)' selected for backup.
| Zeile: 0xfcaee9d6a8889a95
| Datei: k:\7048\enterprise\managers\gtob\providers\disk_item_provider\impl\item_iterators.cpp:301
| Funktion: GctDiskItemProvider::ChildResolver::Next
| $module: disk_item_provider_vsa64_7048
- Log in to post comments

Hi,
The error shown in the quoted log doesn't seem to be related to pre/post commands execution. It indicates that the plan tries to find partition "\local\hd_sign(28E37FD2)" (bolded is the NT signature) which is no longer present in the system. I'll need to check the history of the backups execution, e.g. check the log from successful attempt (which as you mentioned can be done if you re-run the same plan) in order to compare it with the failed one.
Also it's better to clean up the files rather than entire folder as in general this approach might have issues if you delete the folder which was supposed to be used as backup destination. I've run a few tests of the scenario and in general it works properly if I create a folder for backups on a dedicated volume, and clean up *.tibx + *.tib + *.xml files from inside it via batch file. See screen shot below showing my settings. I've emulated the drive removal by deleting the entire G: drive and creating a new partition on the freed space. Hope it helps.
Thank you.
- Log in to post comments