Reducing incremental backup files.

Create a new backup task, set it to create x incrementals and then begin a new chain, where x is the lower number that you'd prefer.

Click on signature link #2 below and look at the illustration figure 11-Inc.
Adjusting that to your needs provides you the controls to prevent a disk full error.
This is a custom backup scheme which will do its own cleanup. Once is reaches its user set limit of full chains to keep, as new full backups are added, the older full chains will be deleted and maintain your limit of how many "recent versions chains to keep."
As MVP Tuttle indicated, a new task which should point to a new empty destination folder.
My recommendation is no inter-mixing of backup files. One different folder for each task.

Thanks guys, I'll take a look at this.

Reducing Full and Inc backup files

I have some disk physical size limitations and regularly need to delete a backup set before a new set is created. Yes, I know this is not good practice, but I do have duplicate backups in separate locations.

So here is my situation - I cannot find how to automatically delete a backup set when needed. I understand TI2013 will not cleanup (delete) old sets until until after a new backup is successfully achieved - which would be best practice. I want to arrange for cleanup unattended 'before' a new backup is created.

I first thought to write a batch file and use it as a Pre Command. but my knowledge of dos batch commands does not allow wildcards in the DELETE command. Since filename_full_b*_s*_v*.tib and filename_inc* sets need to be erased, how do I achieve it in a dos batch command. Or is there another way to implement pre cleanups?

Barry,

One very reliable solution would be to use the free CHAIN2GEN (C2G) supplement to TrueImage. This was written a couple years ago by MVP OracleDBA and one of its options would fit your needs.

With the proper configuration, it would allow the backup files to be created based on how many you want and then delete the storage folder and then recreate a new storage folder.
When TI sees the folder empty, it would start a new chain and the cycle would be repeated.

You could choose where (path) you want the storage folder to be but the name of final storage folder must be "set0".

The scheduling is done by TrueImage. The function C2G brings is that it uses your count of how many files (TRGR_ON_MAX_TIB_CNT=7 ) before removing all the old backup files so a new fresh chain can start.

More info can be found inside link #1 below under the 5A index.

!_USER_SPECIFIED_PARAMS_FOR_ACRONIS.bat
:: ---------------------------------------------------------------------------

Examples of what must completed by user in above C2G program

set TARGET_UNC_N_DEVICE=X: (your storage drive letter)
set TARGET_GENERATIONS_FOLDER=\X640-2013-1081\ (Your storage path location)(set0 folder will be added by program)
set MAX_BACKUP_GENERATIONS=0 (set to 0 for no retention of chains)
set TRGR_ON_MAX_TIB_CNT=7 (your number of backups files to be created before deletion)

If you plan on using incremental backups, you must set the backup scheme to
Incremental scheme with default settings--as illustrated in tutorial.
So only incrementals will be created after the full.
This is the user specified control which triggers the deletion of old backups.

Another option would be to write your own batch program to do the same thing but C2G already has it done.

GroverH wrote:

Barry,

With the proper configuration, it would allow the backup files to be created based on how many you want and then delete the storage folder and then recreate a new storage folder.

More info can be found inside link #1 below under the 5A index.

OK, I downloaded CHAIN2GEn and read all pdf's and link #1 below under the 5A index as you suggest. All understood.

But I cannot see where storage folder will be DELETED. I read that a MOVE function is implemented to put the tib files into History. Could you highlight how the original tib's or "storage folder" is deleted?

Barry,

set TRGR_ON_MAX_TIB_CNT=7 (your number of backups files to be created before deletion)
When C2G sees the quota has been met as to number of backups as determined by the above setting.

it will place a trigger into the set0 folder
and when C2G sees the trigger,
It then looks at the setting below and as it is set to 0,
it performs a delete rather than a move so the backup becomes a new full backup as the set0 is now empty.
There will always be only one set0 folder based on the setting below.

set MAX_BACKUP_GENERATIONS=0 (set to 0 for no retention of chains)

read the comments in these files which help to explain how the options are set.
!_USER_SPECIFIED_PARAMS_FOR_ACRONIS.bat
!_FORCE_NEW_CHAIN.bat

The program was written in 2009 by its author and it find it still works for me in 2013 with version 2010-2011-2012-2013.
I am not the author but simply offering a solution which I believe will work for you.

An example of using Chain2Gen with these parameters.

quota to keep 2 files (full plus 1 inc)

Keep only the 1 chain. Never 2

Delete the chain.

Create a new replacement chain.

So GroverH,

I followed the guide in your signature for setting up incremental backups with automatic cleanup, however Acronis is not cleaning up any files.

Do you have any idea why this could be?

Nevermind, I think this may have been me being an idiot :D

Alex,
If you are having issues, show us a screen capture of your backup scheme is a good starting point.

Barry Green wrote:

Reducing Full and Inc backup files

So here is my situation - I cannot find how to automatically delete a backup set when needed. I understand TI2013 will not cleanup (delete) old sets until until after a new backup is successfully achieved - which would be best practice. I want to arrange for cleanup unattended 'before' a new backup is created.

Just wanted to let you know I finally decided to solve the pre-backup deletion with a simple .BAT file as follows:-

[ FILENAME Erase_Before.bat or Erase_after_s7.bat ]

ECHO OFF
REM
REM s7 is number of slices e.g one full plus 6 incrementals
REM Use with Acronis DEFAULT INC choice and only change number of INC copies to one less e.g. 7-1 = 6
REM If TI is set FULL scheme with no copies, then REM IF EXIST *s7*.tib and leave un-REM ERASE /Q *.*
REM ERASE "/Q" parameter erases entire folder contents without attendance. Ensure Pre Commmand is set properly.
IF EXIST *s7*.tib ERASE /Q *.*
REM either the former or next line is REM's - not both
REM ERASE /Q *.*

Two .bat's are placed in the root of the backup location and backups are placed in subfolders. One subfolder for each backup set.
It is important to set Disk Backup Options>Pre Command properly per example in my case:-

COMMAND "F:/erase_after_s7.bat" or COMMAND "F:/erase_before.bat" depending on what you wish to achieve.
WORKING DIRECTORY: F:/Disc_Partitions/C_and_D_Partitions

Everything in "Working Directory" sub folder is deleted when specified, leaving the .bat file untouched. Tested on scrap file. folder and disk backups. Works like a dream on MS XP platform

Barry,
Thank you for sharing this with us. After you have used it for a while, give us an update on its success or any changes. Thanks.

GroverH wrote:

Barry,
Thank you for sharing this with us. After you have used it for a while, give us an update on its success or any changes. Thanks.

I wrote the bat after your message on 17th as I like to keep things simple and test'able. Bat files can be tested with a double click independently before adding as a TI pre-command. If you do test the bat's independently you need to put them IN an archive directory and, of course, they will be deleted. So keep a copy for when they are properly located later in a Parent folder. I recommend testing independently of TT especially if using a Readynas so as to see permissions are all ok. After setting pre commands to use the bat files I arranged for 'un-successful ' notifications to be sent.

It is best to delete all existing backups beforehand and start with a clean regime**. This way TI does not report missing tibs when first run.
Both TI2013 FULL and INC regimes have been run with no faults reported for 7 days now. The resulting FULL and INC tib files for files/folders and disks have been test opened with no errors.

** Note: I have duplicate backup drives so clearing an archive was not a big deal for me.

Sorry GroverH, I just wanted to check as well. I made sure I followed your guide thread for setting up my backups. I didn't check the 'Make this Media Bootable' box.

In the event of my HDD failing, can I use those backups created to setup the new HDD exactly as the old one was, by booting from the TI Recovery CD?

Whether your backup can create a replacement disk is controlled by the content of the backup. If the backup is a full and complete backup of all partitions (both visible or non-lettered), then yes the backup can be recovered onto a new disk. The key is for the backup to be a backup of everything. This is illustrated via this link.

http://forum.acronis.com/forum/38691

The above is my recommendation but it is also possible to have individual backups of each partition (all partitions) so that your backup include it all within the backup groupings.

Click on item#3 below for some examples of how the backup could be restored onto a new disk. Within that link, the easiest restore is using item #2.

Edit & Addendum:

For my test, I changed the bat file so the deletion changed from *.* to *.tib
IF EXIST *s7*.tib ERASE /Q *.tib
REM either the former or next line is REM's - not both
REM ERASE /Q *.tib

Also, the bat file is stored inside the same folder where the *.tib backup files are stored.
The delete occurs only on the *.tib files and not the bat file.
The Pre command points to the bat file inside the storage folder.