Custom Backup Schemes --All recent versions
Please take the time to read all of this link as it covers several different aspects of custom tasks. "All versons of recent years has this capability
Editing an existing backup 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 avoid confusion by pointing storage to a new sub-folder so each task has it own storage folder/sub-folder. Old task can be stopped or deleted from the task listings.
The cleanup rules are easy to understand. Take the time to give it your full attention for a few minutes/
For most users, Custom type backup schemes work the best. I would encourage every user to choose a custom scheme with automatic cleanup rules so as to avoid "disk full" error messages if cleanup not applied.
Excerpt below from Acronis 2016 User Manual on Custom Schemes
With Acronis True Image 2016 you also can create your own backup schemes. Schemes can be based on the pre-defined backup schemes. You can make changes in a selected pre-defined scheme to suit your needs and then save the changed scheme as a new one.
You cannot overwrite existing pre-defined backup schemes.
In addition, you can create custom schemes from scratch based on full, differential or incremental backup versions.
So first of all select one of the backup methods in the appropriate box.
Select this method if you want to create only full backup versions.
Select this method if you want to create backup chains containing only full and differential backup versions.
You can configure the scheme by using one of the following options:
♦ Create only differential versions after the initial full version - select this item to create only one backup version chain. Automatic cleanup is not available for this option.
♦ Create a full version after every [n] differential versions - select this item to create several backup version chains. This is a more reliable but more space-consuming backup scheme.
Select this method if you want to create backup chains containing only full and incremental backup versions.
You can configure the scheme by using one of the following options:
♦ Create only incremental versions after the initial full version - select this item to create only one backup version chain. Automatic cleanup is not available for this option.
♦ Create a full version after every [n] incremental versions - select this item to create several backup version chains. This is a more reliable but more space-consuming backup scheme.
Automatic cleanup rules (per each task)
To delete obsolete backup versions automatically, you can set one of the following cleanup rules:
(User comment: Every user should use custom tasks with automatiac cleanup to avoid disk full messages. )
♦ Delete versions older than [defined period] (available for full method only) - Select this option to limit the age of backup versions. All versions that are older than the specified period will be automatically deleted.
♦ Delete version chains older than [defined period] (available for incremental and differential methods only) - Select this option to limit the age of backup version chains. The oldest version chain will be deleted only when the most recent backup version of this chain is older than the specified period. Refer user note 1:
♦ Store no more than [n] recent versions (available for full method only) - Select this option to limit the maximum number of backup versions. When the number of versions exceeds the specified value, the oldest backup version will be automatically deleted.
♦ Store no more than [n] recent version chains (available for incremental and differential methods only) - Select this option to limit the maximum number of backup version chains. When the number of version chains exceeds the specified value, the oldest backup version chain will be automatically deleted.
User comment: This option user recommeded. ♦ Keep size of the backup no more than [defined size] - Select this option to limit maximum size of the backup. After creating a new backup version, the program checks whether the total backup size exceeds the specified value. If it's true, the oldest backup version will be deleted.
The first backup version option
Often the first version of any backup is one of the most valuable versions. This is true because it stores the initial data state (for example, your system partition with recently installed Windows) or some other stable data state (for example, data after a successful virus check).
Do not delete the first version of the backup - Select this check box to keep the initial data state. The program will create two initial full backup versions. The first version will be excluded from the automatic cleanup, and will be stored until you delete it manually.
If you select incremental or differential method, the first backup chain will start from the second full backup version. And only the third version of the backup will be incremental or differential one.
Note that when the check box is selected, the Store no more than [n] recent versions check box will change to Store no more than 1+[n] recent versions.
End of excerpt.
Grovers status = Inactive 1. Grover's New Revised Guides 4. 2014 Cleanup 2015 Cleanup 5. Attachments/How 7. TI 2015 FAQ.
2. Create BKU Tasks > 2011_2012_2013 2A. Using 2014 6. Help 2016 2015 2014 2013 8. Stop Scan for Backups 8A. ATIH Video's
3. Create new disks-Guides. 9. Register/Downloads 10. Mustang's New Guides 11. Les Seiler's Backup Video
Getting backup tasks to work successfully, these are the rules which work for me and recommended for you.
1. Before installing a new annual version of TrueImage, I remove the old and then run a TI cleanup utility such as item 4 inside my signture link below. Cleanup the residue and install into a fresh new install. Don't try to carry old tasks forward into a new installation.
2. I create all new tasks and do not later modify. If changes needed, I stop using the old task and create a new task. Each task name is different so no duplication or confusion for the program. Create a new task and point the new task to a new and empty sub-folder so there is no intermixing of backup files within the same folder. In my experience, the most frequent cause of a task not working is that the user makes changes to the task and the changes do not get implemented. Avoid those type problems. Simply create a new task with the new revised settings and a new task name and pointing to a new storage folder so there is no intermixing of backup files from any old task.
3. Each of my is tasks is uniquely named (Another task of the same name is cause for confusion. Don't reuse the same task name) , and is set up for a custom backup scheme for automatic cleanup. Backup scheme name MUST read "custom". A backup scheme with automatic cleanup usually does not require manual deletion of old backups as the cleanup is automatic. The cleanup setting I recommend is "store no more than (n) recent version cleanups with the number of chains kept your choice based on available storage space. Assorted examples below.
4. If a backup is restored, I stop using the restored tasks (which are now out of sync, and create new tasks after the restore. Each new task has its own unique name.
A. When choosing the option "Backup Entire PC", this option may also include disks other than just your system disk. The selection does not show what is included. It is supposed only to include the interenal disks but these days, many of the usb hubs and some externals are seen by the system as internal disks and so included. You may need to choose a Disk backup and select all partitions, rather than select the "Entire PC."
B. Look carefully at the default exclusions on 2015 and 2016. You may want to remove those listed exclusiions so these items CAN BE INCLUDED within the backup contents. (Thanks to User Berti for reminding me to include this recommendation.)
User Cleanup Examples of Incremental/ Differential type backup schemes:
Answers on when automatic cleanup will begin. Click example to view details.
Example 1: Full + 6 Inc. Store no more than 1 recent version chains. Chain length=7 files.
User quota of 7 files (1 chain of 7 files) will be exceeded following successful completion of Backup #8 (Full B2). Seconds later following completion of Full B2 (backup #8), oldest chain (chain 1=7 files) will be deleted. Subsequent future deletions will occur after each new FULL backup as the resulting new FULL will cause the user quota to be exceeded causing an immediate deletion of oldest chain. Storage space must always be provided for 1 chain of 7 files plus upcoming replacement Full before any deletions occur.
Example 2: Full + 6 Inc. Store no more than 3 recent version chains. Chain length=7 files.
User quota of 21 files (3 chains of 7 files) will be exceeded following successful completion of Backup #22 (Full B4). Seconds later following completion of Full B4 (backup #22), oldest chain (chain 1=7 files) will be deleted. Subsequent future deletions will occur after each new FULL backup as each new resulting new FULL will cause the user quota to be exceeded causing an immediate deletion of oldest chain. Storage space must always be provided for 3 chains= 21 files plus upcoming replacement Full before any deletions occur.
Example 3: Full + 6 Inc. Delete older than 5 days. Chain length=7 files.
Elapsed day 1 countdown begins following successful completion of Backup #8 (Full B2). Elapsed day 5 countdown ends when backup #8 (Full B2) is older than 5 days at which time oldest chain (chain 1=7 files) will be deleted. Subsequent future deletions will occur as each oldest chain of 7 files becomes older than 5 days.
Example 4: Full + 29 Inc. Delete older than 10 days. Chain length=30 files.
Elapsed day 1 countdown begins following successful completion of Backup #31 (Full B2). Elapsed day 10 countdown ends when backup #31 (Full B2) is older than 10 days at which time oldest chain (chain 1=30 files) will be deleted. Subsequent future deletions will occur as each oldest chain of 30 files becomes older than 10 days.
GH12. Create Custom Incremental Backup Scheme.
...Keep Full plus 6 Inc per chain. Store/Keep 4 chains. Use whatever number best fits your needs.
Note: If rule selected is "Delete older than 7 days", deletion will not begin until the entire oldest chain older than 7 days.
Examples of Custom Schemes:
GH-11, Custom FULL with automatic cleanup below:
GH-12,Custom Incremental with automatic cleanup below:
gh-13, Custom Differential with automatic cleanup below:
Example = keep 6 full backups deleting oldest.
You can expect cleanup deletion to apply to each task configured to keep 6 full as per this example
I am looking for a scheme to back up three computers on three portable drives. On Wednesday, I want to take Monday's drive off-site, have Tuesday's drive on-site with a good back up, and have Wednesday's drive ready to back up tonight. I was thinking of backing all three computers up each night or every other night. I get confused when I change destination drives. If computer A has a full backup on each destination drive (different days) can I make an incremental the next time that drive is plugged in and would Acronis restore properly regardless of the days where backups were made? Otherwise, should I just make a new full every time eash computer comes up for back up? I know this is confusing, which is why I am asking, I guess. Any suggestions will be apprecialted.
You would have to set a specific backup task for each drive being used and do this on each of those computers - meaning that each backup task should also be uniquely named. Ultimately, you'll just have multiple backup jobs that run on each drive and for each system. This is a good thing as it will provide you with 3 recovery options for each hard drive. The limitations are that each system will need three backup tasks (1 for each hard drive) and all tasks must have their own unique name (no overlapping or repeating).
Also. You want to ensure that each hard drive is always mounted with the same volume on each system. For instance, Hard drive 1 always needs to be mounted as H:. Hard Drive 2 always as I: hard Drive 3 as J:. Use letters that are farther out as plugging in additional drives (say flash drives), may automatically take one of those existing letters if it is the next available letter and the portable hard drives are not currently in use already. That would result in Windows automatically assigning your portable hard drive the next available letter (perhaps K) which would then cause an issue for your backups.
PC1Backup_HD1Backup; PC1Backup_HD2Backup ; PC1Backup_HD3Backup
PC2Backup_HD1Backup; PC2Backup_HD2Backup ; PC2Backup_HD3Backup
PC3Backup_HD1Backup; PC3Backup_HD2Backup ; PC3Backup_HD3Backup
Going this route, the backups will all be self-sufficient. If you plug in the wrong drive one night, or can't move them, the backup will just run on whatever disk is attached at that time (unless you schedule those tasks to only run on certain days)