Bugs in ABA 12.5 U1??
Hello, I use Acronis Backup Advanced 12.5 Update 1 and have a few problems or questions.
1. I create a new backup plan. The first target is a disk (storage node). The second target is another disk (storage node). Now I would like to execute a command by * .cmd after the complete backup. The problem is as follows. After the backupjob has written everything to the first destination, the * .cmd is already trying to run. But since everything is still to be written on the second goal, this is so not correct. It is only when the backup job has been completed that the post-command is executed. So only when the second target is described. Is this a bug? Or can I already realize this?
2. I secure many VMs under ESXi. The VMs are thus secured by Agent for VMware (Virtual Appliance). In a backup job, so many VMs are gathered. Now the above-described after-command (xxx.cmd) is to be executed under the AMS (Windows Server). This I enter in the backup options. However, it is always displayed as an error that the file can not be found, which is only found on the Agent for VMware (Virtual Appliance). How can I start a batch file that is on the AMS when the backup job has completed?
3. Is there now the option of ejecting removable media by Acronis Backup under the new version Update 1?
4. Is it possible to delete the removable media with a pre-command of a backup job?
5. I have a NAS that serves as a target (storage node). Here 20TB are available. If I do not provide any storage rules here, the goal will be full. I wish then that the oldest backup will be deleted automatically, if there is no more space. Is not this function?
Thank you.

- Anmelden, um Kommentare verfassen zu können

Hi A. Sanchez Paulino,
1. The post-backup scripts are executed after the backup is written to the first location, but before copying backups to 2nd location, so if your post-backup script includes manipulations with the backup files then it won't work. The proper way here is to disable the 2nd location option in the backup plan and instead create a separate backup replication plan (Plans->"Backup replication"->Create plan) which will pick up the backups from 1st location and copy then into the 2nd location on separate schedule.
2. The possible way to achieve the goal is to install Agent for VMware (Windows) onto the AMS machine and use it to back up all the VMs. The pre/post commands defined in the backup plan are always executed on the agent side by design. An alternative for the post command execution is to use Windows scheduler on AMS machine to run the commands separately (e.g. make it independent from Acronis Backup plans). In future versions we will consider an option to define which machine will be executing the pre/post commands, so it can be done not only on the agent machine, but on AMS as well.
3. There is no such option available yet. Can you please clarify which type of removable media you are using? Is it an RDX drive? If yes, then are you backing up to this drive shared over network (since backup is performed by appliance where you cannot connect RDX drive directly) and trying to eject the media after the backup is complete? Answers would give us better understanding of the whole scenario.
4. Yes, but you should take into account the fact that the pre/post commands are always executed by the agent which is responsible for the backup task execution. Also the scenario is not completely clear: e.g. if you are saving backups to removable media, then why would you eject it _before_ backup?
5. Cleanup upon insufficiency of free space is planned for future updates (internal feature ID: ABR-118624). Note however that this is not really safe to fill up the storage until it's running very low on free space, and when you need such cleanup rule - it's much more efficient to define the rules which will clean up when backups get X days old or when the number of backup exceeds some limit (these options are already available). With these options you can always predict how many (and for which period) backups are stored in the location and thus get more reliable behavior than keeping the storage almost full at all times.
Thank you.
- Anmelden, um Kommentare verfassen zu können