Direkt zum Inhalt

Acronis 11.5 - Replicating same backup file to secondary location over and over until stopped manually.

Thread needs solution

Hi

I am experiencing an issue with Acronis 11.5 on a server where the backup runs successfully and the backup file is created in the primary location (local disk) but when the replication to the secondary location happens the same file is copied over and over.

The file replicates fine but then keeps copying the same file over and over again until it is stopped manually, or the disk runs out of space.

Does anyone have any experience with this issue?

Thanks in advance.

0 Users found this helpful

Hi

I have 6 production servers running Acronis Backup and Recovery and I have been spending 30 mins + every morning investigating failed backups / backups completed with warnings / no email notifications / indefinite replication needing to be stopped manually, etc. - which defeats the purpose of using automated software for peace of mind.

What I would like to know is this:

Is there a way to use Acronis with its most basic functionality?

I would like to turn off retention rules completely (as I suspect this to be the cause of the issues) and stop using 'vaults', and just manage the backups manually.

Backup needs to be created on a schedule, encrypted, copied to a disk and I will manually clean the disk up when it gets full.

Does anybody have any thoughts on this?

Much appreciated!

Backup needs to be created on a schedule, encrypted, copied to a disk and I will manually clean the disk up when it gets full.

Copied to a disk from where? Should all backups be full or will there be incremental/diff ones? You can consider simplified naming with only full backup, then it will be overwritten in the same place with the same name after each run, and in the post-command you will be able to copy somewhere.

Thanks for your response dev-anon.

It gets replicated to an external HDD from an internal disk on the server so that we can take the external HDD off site.

The backups need to be full and cannot be overwritten. We need at least 5 days of backups.

Are you saying that the pre/post commands can replace the standard replication fincationality?

If you need several full backups, you can use [ date ] variable with simplified naming, that will allow multiple full backups that doesn't overwrite each other, and let the script take care of cleaning old backups on internal disk (or else they will accumulate forever) and copying to external disk.
Copying in post- command can replace replication in most basic case with copying files to disk or network share. If one of vaults is centralized managed vault on storage node, online storage or tape, it probably can be done using acrocmd and its 'export backup' command, but it will require some parsing of its output and is not straightforward.