Skip to main content

Cloud Backup file retention policy

Thread needs solution

In Cloud Backup function, are file deletions synced regardless of cleanup Options?

If it helps, here's a role play...I created a scheduled Cloud backup that is set to run at 20:00 every day, with "Delete file versions..." disabled and 1 set for "Store no more than...". At 09:00 on Day 1 I create File A, File B, File C. At 20:00 Day 1, Acronis backs up all 3 files to the Cloud. On Day 2 at 09:00, I delete File A from my computer. The question...at 20:00 during the scheduled backup on Day 2, is File A then deleted from the online backup?

The concern here...is it possible that I may be backing up numerous files that have been deleted off my system?

 

0 Users found this helpful

Scott,

Acronis Cloud backups use a different backup method that always starts with a full backup then uses a delta comparison to determine what changes are backed up thereafter.

Any backup to the Cloud is left alone once created until such time as you reach the criteria set for Acronis Cloud cleanup on the Advanced options page where you specify to delete file versions older than... or to Store no more than ... recent file versions.  There is no synchronisation for any file deletions you may perform - each backup remains exactly as it was created until such time as it is removed when the retention criteria is satisfied to allow this.

Online Cloud backup options.png

Thank you for the explanation. With regards to restoring...

Regardless of the deletion time frame, it seems very possible that in a full restore, I would be restoring files that had been previously deleted from my system?

 

Scott, if you restore a full backup from the cloud or any other storage location, then you restore the contents of that backup which can easily contain files that you have previously deleted.  For some users, this is the saving grace of having backups, especially when files are deleted by accident.

If you need to keep your files on your computer and in the Cloud synchronised, then you should perhaps be using the Synchronisation function rather than doing a backup.

From the ATIH 2017 User Guide: 

About the Sync feature

The main highlights of the Sync feature:

  • You can have the same data - documents, photos, videos, etc. - on all of your computers. Your data is within easy reach anywhere and anytime. No more emailing files to yourself or carrying an USB drive all the time.
  • You can create as many syncs as you need.
  • The Acronis Cloud keeps your synced files and versions of those files. This lets you roll back to a previous file version whenever you need it.

    Note: An Acronis Cloud Storage subscription is required to use this feature. Refer to Subscription information for details.

  • You can also access the Cloud using a web browser, without having to install our application.

Thank you. The problem with the Sync approach is I would need to sync all data folders individually, as I cannot sync an entire Drive/Disk. That said, sounds like file deletions would be synced.

May I get some recommendations here. What would be a 'best practice' approach to backing up an OS drive/disk? I'm still puzzled there is not some type of file deletions sync option for Backups. I even have that option with various Android-based apps.

 

Scott, file deletions would be synced when using the Sync method, though depending on the retention settings there would be copies of those deleted files kept for a period of time (if using the cloud).

In terms of best practice, there is a separate 'Best Practices for data protection' Forum which may have answers to some of your questions. 

There is no file deletions sync option for backups - in reality this is not needed if your backup scheme is configured to meet your requirements.

For example:  A full backup followed by incremental or differential backups at regular periods will contain all the changes that have occurred over that period of time, which in turn would allow you to recover to a specific point in time (taken from the point where any of these backups were created).  Those changes captured will include any file creations and deletions, so restoring the system back to any point will put things back as they were at that point.

 

 

In reply to by truwrikodrorow…

Hi Steve,

I know this is an old thread but my question is on the same subject and this thread answered it about 50% so I wanted to ask for clarification.

On the subject of file retention, I have my Acronis Cloud Backup set to store "No more than 20 recent file versions" as was the default selection. I understand that if I were to modify a working document 21 times and each version were backed up, then eventually the changes from the 1st to 2nd version out of 21 would be deleted from the backup.

My question is, how does this versioning apply to file deletion on the computer? If I had a large file that I deleted from my computer (after it was backed up) would that just count as one change to the file (2 versions)? Meaning that the number of "recent file versions" would never increase to 20 and thus the file would be retained on Acronis Cloud forever?

Or would each incremental backup count as a version of the file and thus after 20 incremental backups, the orginal file would be deleted because it was noted as deleted in the next 20 versions of the incremental backup?

 

In this case, would it be more appropriate for me to tick the "Delete file versions that are older than 'period of time'" box? Would this delete the file after that period of time elapses if it is no longer backed up as part of my incremental/full versions?

 

Thanks for helping me. I'm just trying to understand precisely what happens to a deleted file and how long they'll hang around in the cloud based on the policies. I am aware that you can "undelete" a file from the cloud or "delete it forever" but I want to learn what would happen with no intervention from me.

 

Thank you kindly

First, sorry for not responding to your questions sooner - I only received an email notice of your post a short time ago for some strange reason?

The first point that needs to be understood is what a version is in the context of a Cloud backup?

My own understanding here is that each new backup to the Cloud = a version of the backup.

Thus if you modify a working document 21 times you would have to run the Cloud backup after each modification to invoke the default cleanup rule that allows no more than 20 recent versions to cause the oldest version of your file to be cleaned.

If you only perform a daily backup to the Cloud, then all changes to your working document would be missed except for the last one prior to the daily backup, unless those changes are captured by some other means.

This is probably a case where you should change the default Cloud cleanup criteria to better suit your requirements, i.e. increase the number of versions allowed if your Cloud storage is sufficient to allow this, and / or your version sizes are small; or use the age criteria to manage how old versions can be before they are cleaned.

Hi Steve, thanks so much for your reply.

I assume your notification was delayed because the administrators had to approve my post.

 

This "each new backup to the Cloud = a version of the backup." seems to answer my question. I will wait and see if the file disappears after 20 backup versions. If not, I will try the time-based clean up setting and see what happens.

 

Coming back around to this topic, specifically the Sync option. Acronis Cloud Sync really frustrates me. It continues to leave older, deleted file versions in the cloud and at times, will actually transfer old files back on to my PC that I deleted previously. I understand this is how Sync is developed, however, we have the backup option that does this.

I simply want to sync files and deletions. I don't want any other versions saved...regardless, i.e. option to never save deleted files in the cloud. Heck, I have an Android app that has this capability (FolderSync Tasker plugin). to me, Acronis Sync is not much dissimilar from the backup option.

One may say...hey, that's not a good backup strategy. That person would be correct...it's not a backup, it's a sync job. I can also run a periodic backup of those same files.