Does Acronis 2015 look at files before backup, REALLY important to understand
This is directed specifically to ACRONIS Engineers.
Running Windows 7 Pro and Acronis 15 Build 6525
Really frustrated with how unpredictable Acronis 2015 is.
I need a full explanation of how it works while doing an INCREMENTAL backup over 7 days.
Acronis 2012 was very tricky to get it to work correctly but Acronis 2015 is simply unworkable.
Can you please provide a full explanation of what it is doing and looking for to do an INC backup.
I depend on this software to be fully automated using PRE and POST batch files to manage/move/delete all the backups. Acronis 2015 goes crazy if I do that.
Thanks
Jim Calvert
Ok, I will go that route.
Then again maybe not.
As soon as I do, they expect my VISA card number.
I am getting very tired of this.
Cheers
Jim,
Variations of your question has been asked many times before but never answerd by Acronis.
Acornis has posted they track used disk sectors.
So the incremental has the disk sectors which have changed since the last backup. Archive bit not involved. The inc backup is a snapshot of the changes and these changes are not included in any other later backup. If an inc is lost or becomes non-usable, that data is long as it is not included elsewhere until the next full backup when another snapshot occurs.
2015 does not want you having any control over the process--it want everything done within control of the program.
User cannot change name or delete outside the program. User cannot delete backup even from within the program.
In the past, when the program found the storage folder empty, the next backup would be a full backup,
now, if the folder is found empty, it cries fould and does produces an error but not new backup.
About the only control now is the use different "custom" tasks to do different things and use a the task custom backup scheme to perform automatic cleanup to control how many backups are retained and use the automatic cleanup to perform the deletion automatically, as illustrated via these examples.
Depending upon the type of backup scheme you wish to create, here is an example of each type. These can be set up for Disk image, or Partiton, or Files-folders backups. These example show how to set up automatic cleanup so the program will do the deletion after it reaches your set goal of how many chains to retain.
Editing an existing task is not recommended. Rarely does an edited task perform to user expectations. It is usually better to start with a new task using a new non-identical task name and point to a new storage sub-folder so each task has it own storage folder/sub-folder. Old task can be stopped or deleted from the task listings.
GH25. Understanding differences between Inc and Dif for Safety
GroveH,
Thanks for the 4 suggested examples.
GH12 comes the closest to what I want. It also seems to say that maybe I have interrupted the chain management somehow.
I will have to devise a short folder based test (rather than my entire C drive ) which I can manually run in a few minutes to simulate a full week of 7 executions.
Stay tuned.
Jim
Yes, it would be very easy to set up a custom test backup task with the exact same settings as the real task except the item to be backed up would be just a single small file. If you run multiple manual interations of the backup, you could see how the real task would work. Deletion of old backups occcur on the next full after retention quota has been reached.
Do be sure and stop and start the program several times during the test so the temp file gets updated with the addition of the new test backups.
Also be sure the task backup scheme type is "custom" as illustrated in the GH12.
When ready to implement, create a new task with the exact settings you want so later editiing of the task is not needed. You want a pristine task to get the best results. Don't use deisk size limits as an option! The option set "store no more than.... works much better.
No need to remind that when tragedy strikes, it helps to have multiple restore opitons.