Salta al contenuto principale

Changes to Backup Scheme Don't Seem to Work

Thread needs solution

When I change the Backup Scheme settings for an incremental backup, they become erratic. The number of incremental versions appears to change, but doesn't or may change to something other than what I changed it to. The store no more than x chains gets confused too. Please help/

Fred

0 Users found this helpful

A task works best when created and then leave it alone without further changes or edits. If you use the edit function to change a task which is already functional, rarely does it work "as expected by the user" after the changes. So, create the task and then leave it alone. If changes need, stop using the old task and create a new task with the correct settings.

The default program is designed to work on a "per task" basis. The settings saved inside that task WILL WORK but they are designed only for that single task. The backup scheme has a default view and each time you begin to create a new task, the program reverts to the default view--same as when the program was installed. The only time you will find your personalized settings is when you click the OPERATIONS/EDIT SETTINGS/ and look at the settings you saved for THAT SPECIFIC SINGLE TASK.

Show us a screen capture of your backup scheme so we can see its settings so we can analyze how it should work.

GH12. Create Custom Incremental Backup Scheme. ...Keep Full plus 6 Inc per chain. Store/Keep 4 chains. Use whatever number best fits your needs.

http://forum.acronis.com/forum/75086

http://forum.acronis.com/forum/64640

http://forum.acronis.com/forum/71342

Fred Hutchings wrote:
Then why is there an Edit Settings option?

Fred

I agree--the program should be more explicit as to what can be changed--but it isn't. These are my suggestions as to what works for me. I'm not Acronis so my comments are to help you get the existing program working as it exists today.

1. Regarding your untitled2.jpg
As often said, the bottom line is (or the short of it is)
your backup scheme has configured the program to create 20 backup files and for deletion NOT TO OCCUR until after the 21 backup (Full B3) has been created. Following the first deletion, subsequent deletion will occur after each new FULL thereafter.

2. The bottom option "Do not delete the first version of the backup" is not displayed in your capture so I will assume is not enabled and can be ignored. If option WERE checked or enabled tells the program for the first backup run to be a Full backup only and it is NOT to be deleted by the program. Deletion, if wanted is a user responsibility. If enabled, this would be named Full-B1 S1 V1 and will have no other backups numbered in B1. This option will be ignored as not enabled.

3. Option "Full plus 9 incremental's"
tells the computer that chain length will be 10 tib files

Store 2 recent version chains
tells the computer to create 2 chains (10 fies per chain) which is B1 and B2 listed next.
Full_B1_S1_V1
Inc_B1_S2_V1
Inc_B1_S3_V1
Inc_B1_S4_V1
Inc_B1_S5_V1
Inc_B1_S6_V1
Inc_B1_S7_V1
Inc_B1_S8_V1
Inc_B1_S9_V1
Inc_B1_S10_V1

Full_B2_S1_V1
Inc_B2_S2_V1
Inc_B2_S3_V1
Inc_B2_S4_V1
Inc_B2_S5_V1
Inc_B2_S6_V1
Inc_B2_S7_V1
Inc_B2_S8_V1
Inc_B2_S9_V1
Inc_B2_S10_V1

User tib storage quota = 2 chains or total of 20 tib files. No deletion has occurred (as yet) because user quota has not been exceeded.

4. When user quota is exceeded (>20) or Full B3 created, deletion of oldest chain will occur,
or when Full B3 exists, 21 files exist and oldest chain B1 (10 files) will be deleted.

Chain B2 will remain plus Full B3 or 11 tib files exist following the deletion.
The next 9 incremental's will accrue to achieve the user quota of 20 files..

5. When user quota is exceeded (>20) or Full B4 created, deletion of oldest chain will again occur,
or when Full B4 exists, 21 files exist and oldest chain B2 (10 files) will be deleted.

Chain B3 will remain plus Full B4 or 11 tib files exist following the deletion.
The next 9 incremental's will accrue to achieve the user quota of 2 chains or 20 files..

6. As new backups occur, history will repeat with each new FULL backup causing the 21 files to exist
immediately followed by the deletion of oldest chain (10 files).

-----------------------------------------
RE: your untitled.jpg screen capture
scheduler option advises the program that each bootup, the program is to check if the backup failed to run the prior session (if scheduled) or backup was missed, then the backup is to begin upon startup--possibly interfering with other startup usage or activities. This is just an FYI comment.
----
If you were to start a new task with the settings used in my example here, the preceding examples are the results you could expect. My recommendation is that A new task should have its own unique name pointing to its own individual storage folder.
--------------------------------------------
Do understand the limitation of the incremental backup. An incremental contains the changes that occurred since the last backup, so the data contained in that specific incremental is NOT contained in any other incremental and will NOT be backed up again until the next FULL or some other totally separate backup. This indicates that if the data that exists in Inc S2 (or other specific inc) is deleted by the user or a bad disk read, then all incremental backups NEWER than S2 ( or other specific inc) will have NO recoverable value.

GH25. Understanding differences between Inc and Dif for Safety
----------------------------------------------------