Full/incremental backups - how to set full backup for a particular day

According to your captured schedule, backups will occur Tuesday through Saturday with no backup scheduled on Sunday or Monday. Is this your intention?
The backup scheme shows that backup creation occurs first with a full and then 5 successive incrementals. So the next full occurs on backup day 7 so your schedule and your backup scheme are out of sync. If you are on a 5 day work weeks, you will want to change the number of incrementals from 5 to 4 so each full is on the same day of the following week .

The program does not provide any method to make a full backup occur on a particular day except user control of the backup number.
If you wish the full backup to occur on Friday 1 am. You will need to make sure that all the incrementals have been completed prior to the running of the full backup. As you are using the weekly schedule, the first full will occur on whatever day to create the weekly schedluled task. This may not be what you want if the computer is shut down on Sunday and Monday. You may need a daily schedule rather than weekly??

Each backup storage disk must have its own specific backup task so that each storage disk is mated to a specific backup task.
When you attach a different storage disk, you will need to switch to the backup task mated to that disk, and stop using the task mated to the disk which was removed. Some users of disk switching prefer not to use the scheduler and perform their backups manually so they have more control to make sure the correct task is put into use.

I have a problem which tech support is unwilling or unable to resolve. The internal hard drive (C:) on my HP laptop is 298GB (HEX) or 320GB (DEC). I am backing it up to an external (USB) hard drive of the exact same size. The used portion of my internal hard drive is now approximately 155GB (HEX). When I attempt a backup, just before to be finished, I get a message saying backup disk is full, try another location, delete files off external hard drive, etc (or something like that). When I delete the previous generation, the program looks for it and then the job is cancelled because it is not there. In order for me to have an effective backup of my internal hard drive, I have to delete and recreate the backup on a nightly basis. I have a HP laptop running Windows 7 Ultimate (SP1). I set the backup as follows: Custom Scheme, based on Full Backup Method, Automatic Cleanup is turned on and set to store no more than one generation. It appears that the previous generation is not being fully deleted before the current generation is attempting to fully write. Any assistance with this problem would be fully appreciated. Please email me at hyag81100@yahoo.com if there are any solutions. Thank you very much.

Howard,
You are caught in a "catch22" as the program is working against you.
Your problem is that it is Trueimage policy will not delete the old backup until it has first created its replacement. As there is not enough room for 2 full backups, it errors out as disk full. There is no way to make the program first delete the old backup before createing a new full backup.

The one and only way you can get this to work is for you to delete the old backup before creating its replacement.
The storage need will always need to be free of any tib backups before you wil be able to succeed in creating any new full backup.

You can use the program to perform the delete so you can keep the data base records in sync.

GH5. How to delete backup files using Acronis Backup 'Explorer'

A much larger disk would allow you to automate your backups but for now, you are stuck with the need to use the program and manually delete the all the old backups on the 320 each time you want to create a full backup.

Hi.

As you have pointed out, there doesn't seem to be a way of setting the day that the full backup occurs on. I assume that if I create a separate full backup task, then the incremental tasks won't add onto this full backup task.

I have been using ATI for a number of years, in preference to other products, because it has been possible to change removable disks without the software complaining.

These are the dates of full backups - they don't seem to make much sense to me:

02/05/2014 02:15 AM 30,307,596,288 Backup_full_b2_s1_v1.tib
08/05/2014 02:15 AM 30,837,222,912 Backup_full_b3_s1_v1.tib
17/05/2014 02:15 AM 31,058,905,600 Backup_full_b4_s1_v1.tib
30/05/2014 02:06 AM 33,342,049,280 Backup_full_b5_s1_v1.tib
03/06/2014 01:10 AM 33,221,402,112 Backup_full_b6_s1_v1.tib
14/06/2014 01:12 AM 33,962,689,536 Backup_full_b7_s1_v1.tib
27/06/2014 01:11 AM 33,376,087,552 Backup_full_b8_s1_v1.tib
28/06/2014 01:10 AM 33,392,577,024 Backup_full_b9_s1_v1.tib

Maybe the solution, as you have suggested, is to change the number of incremental backups to 4. I'll do this on Thursday afternoon after the disk is changed - if I move all of the old backups into a new directory this might force the full backup to occur on Friday - as intended.

Giver yourself a chance. On Thursday sometime after 1 a.m after the disk switch., create a brand new scheduled task for the disk just inserted. Do NOT create any manual backups.
When the TI scheduler reaches Friday 1 am., let it kick off the backup. As the storage folder will be empty, the backup will have to be a full type backup.

My suggestion for a new task will be as listed below, except change the inc number to keep 4 inc.
The 60 days option you have set will give you problems, instead, set the "store no more than X recent version chains and set the x to be 9 chains.
whcih will be 9 weeks of backups (63 days) or set a different number of weeks to keep. Using this option, the program will create 9 weeks of backups and then will begin the deletion of the first or oldest chain. For every new full created, the program will delete the oldest chain of 5 files.

Change the 6 and 4 settings to 4 inc and and keep 9 chains.
https://forum.acronis.com/system/files/10-2inc-custom_keep64.jpg

Making changes to an ongoing task causes more problems than it fixes. For your best chance of success, start over with a new task.
Point the new task to a new and empty storage folder--or, if you wish, use Windows and move the old tib files to another folder so the target folder is empty. If you simply edit the existing task, there is no assurance that the edit will function correctly when the next full is due after the next 4 inc backups.

In additon to my previous posting...
Chain2Gen (C2G), a helper program designed to work with TrueIamage of long ago can help you to achieve your goal of controlling when a full backup occurs.

TrueImage does the scheduling and running of the backups. C2G controls tib file retention and when the full occurs. C2G has many optons as to when a full backup can occur. Basically, C2G looks at the day and date and compares it to the C2G user parameter file as to whether action by C2G is needed.

C2G requires that the last folder in the storage path be named set0. It is "set0" which stores tib files.

For example, assuming that you want your backup to occur on Friday.
C2G works from the TrueImage Pre/post command. C2G determines that this is Full backup day.
The action C2G takes is to rename into a higher set# and recreate the set0 folder empty.
TrueImage sees the empty folder and a full backup is performed.

User C2G parameter file tells the program how many full to keep and each full is in its own set# folder.
When user max full attainted, C2G will delete the oldest set# folder and will retain the correct number of full on a revolving basis. Eash full and its 4 inc will be stored in its own individual set# folder.

IF interested in more details, click on my signature link #1 and review index item 5-A and 5-B.