Backup to removable USB drives (over time)

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Contributions: 21
Commentaires: 29

Hi;

I've been using TI 2010 to backup 'on-demand' to USB 3.0 attached removable drives, and now I was trying to do the same thing using TI 2014. (This is all manual, so no scheduling is involved).

But, I seem to keep running afoul of TI 2014's built-in database where it gets 'confused'.

What is the recommended way to make/keep sets of backups (of the same systems drives) on different removable USB drives?

What I've been doing with TI 2010 is making a series of full+incremental backups to a given external drive, then switching to the next external drive as needed. So, each drive has a full backup and several incremental backups as I see fit. Often, I add an incremental backup to a full backup by booting the WinPE media. I rotate through all the external drives and eventually erase/overwrite the data from the oldest backups.

When I tried this with TI 2014, the listed entries seem to get 'confused', and I've made it work so far by always deleting all the entries on the backup list and re-finding the current entries each time.

Is there a way to set this up so TI 2014 knows to keep the same backup entry and just make a new Full backup when it's time to re-use the next external drive (overwrite the oldest)? (The external drives always show up as the same drive letter, and I usually first erase the oldest backup on the current external drive).

Is there an easier way? I knew how to work around TI 2010, but so far I keep fighting the 'catalog' built in to 2014.

Thanks;

dim 01/06/2014 - 15:35
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Legend
Contributions: 172
Commentaires: 11125

First, I would encourge you to review my signature link 2-A. The pictures inside answer so many questions. At the end of that guide is a listing of many links labeled "GH#" which provides examples of many of the options in use.
============================================================================
In 2013 and 2014 versions with its database history, each specific target disk must be tied to a single backup task. The program records which disk is tied to that task and will only successfully backup to that specific disk. It will up to the user to control which task is executed based on which specific disk is attached. If fewer or greater number of backups are executed on a given target disk than prescribed within the backup scheme, the type of backup (inc or full) is controlled by the number of of files specified for each chain as indicated below.

When you switch target disks, you MUST also switch backup tasks so the matedtask and disk runs as a matched pair. If you are using 4 target disks, you need an individual task for each disk (4 target disk=4 backup tasks and that specific disk must be attached during the task creation process.

Whatever TASK you click the "Back UP Now" option controls how backups will be numbered and auto deleted if you put that into your task backup scheme.

RE: target drive letter.
Each target disk can use the same letter (or a different letter) but that specific disk letter will need to be pre-assigned (via Windows disk management) to each target disk so the insertion of a flash drive or camera does not cause a letter change on the target disk.

GH32. How to clone backup task for reuse or duplication. Cloned tasks can then be edited and renamed with the target disk attached applicable to that specific task.
----------------------------------------------
There are many different number of backup schemes possible and below is just one example.

If you change disks on a weekly basis and run backups daily, one option might be to configure the task backup scheme for 1 full plus 6 incrementals (chain=1 full plus 6 incremental) and keep 4 chains of 7 files per chain or 28 files on each storage disk.

GH12. Create Custom Incremental Backup Scheme. 6 Inc, Keep 4 chains. The 6-4 is user choice. The 6 controls how many inc's are created prior to the next full. The 4 is the number of X or recent version CHAINS (CHAIN=7 FILES) TO KEEP before auto-deletion starts. Auto-deletion does not begin until your keep X number of chains has been reached within each task. The user must perform the exact number of backups as listed in the backup scheme in order for the task to begin a new full at the correct time. If fewer or greater number of backups are executed on a given target disk, the type of backup (inc or full) is controlled by the number of of files specified for each chain as indicated below.
-----------------------------------------------
Week1: Attach disk 1 Use matching Task 1
Perform 1 full plus 6 inc
Task-1 Week1_Run1_FULL_b1_s1_v1.tib
______________Run2_Inc_b1_s2_v1.tib
______________Run3_Inc_b1_s3_v1.tib
______________Run4_Inc_b1_s4_v1.tib
______________Run5_Inc_b1_s5_v1.tib
______________Run6_Inc_b1_s6_v1.tib
______________Run7_Inc_b1_s7_v1.tib

----------------------------------------------
Week2: Attach disk 2 Use matching Task 2
Perform 1 full plus 6 inc
Task-2 Week2_Run1_FULL_b1_s1_v1.tib
______________Run2_Inc_b1_s2_v1.tib
______________Run3_Inc_b1_s3_v1.tib
______________Run4_Inc_b1_s4_v1.tib
______________Run5_Inc_b1_s5_v1.tib
______________Run6_Inc_b1_s6_v1.tib
______________Run7_Inc_b1_s7_v1.tib

-----------------------------------------------
Week3: Attach disk 3 Use matching Task 3
Perform 1 full plus 6 inc
Task-3 Week3_Run1_FULL_b1_s1_v1.tib
______________Run2_Inc_b1_s2_v1.tib
______________Run3_Inc_b1_s3_v1.tib
______________Run4_Inc_b1_s4_v1.tib
______________Run5_Inc_b1_s5_v1.tib
______________Run6_Inc_b1_s6_v1.tib
______________Run7_Inc_b1_s7_v1.tib

-------------------------------------------------
Week4: Attach disk 4 Use matching Task 4
Perform 1 full plus 6 inc
Task-4 Week4_Run1_FULL_b1_s1_v1.tib
______________Run2_Inc_b1_s2_v1.tib
______________Run3_Inc_b1_s3_v1.tib
______________Run4_Inc_b1_s4_v1.tib
______________Run5_Inc_b1_s5_v1.tib
______________Run6_Inc_b1_s6_v1.tib
______________Run7_Inc_b1_s7_v1.tib
----------------------------------------------------------
The switch disk cycle begins a repeat with disk 1 inserted and use matched task 1.
Depending upon how you configure your backup scheme as to how many chains (7 files) to keep "Store x number of recent versions chains) will control whether the program deletes or keeps the oldest chain.
--------------------------------------------------------

Week5: Attach disk 1 Use matching Task 1
Perform 1 full plus 6 inc
After new full completed, the oldest chain would be auto-deleted or retain based on your backup scheme setting. 6 new inc performed.
Task-1 Week5_Run8_FULL_b2_s1_v1.tib
______________Run9_Inc_b2_s2_v1.tib
______________Run10_Inc_b2_s3_v1.tib
______________Run11_Inc_b2_s4_v1.tib
______________Run12_Inc_b2_s5_v1.tib
______________Run13_Inc_b2_s6_v1.tib
______________Run14_Inc_b2_s7_v1.tib
---------------------------------------------------------
Week6: Attach disk 2 Use matching Task 2
Perform 1 full plus 6 inc
After new full completed, the oldest chain would be auto-deleted or retain based on your backup scheme setting. 6 new inc performed.
Task-2 Week6_Run8_FULL_b2_s1_v1.tib
______________Run9_Inc_b2_s2_v1.tib
______________Run10_Inc_b2_s3_v1.tib
______________Run11_Inc_b2_s4_v1.tib
______________Run12_Inc_b2_s5_v1.tib
______________Run13_Inc_b2_s6_v1.tib
______________Run14_Inc_b2_s7_v1.tib

----------------------------------------------------------
Week7: Attach disk 3 Use matching Task 3
Perform 1 full plus 6 inc
After new full completed, the oldest chain would be auto-deleted or retain based on your backup scheme setting. 6 new inc performed.
Task-3 Week7_Run8_FULL_b2_s1_v1.tib
______________Run9_Inc_b2_s2_v1.tib
______________Run10_Inc_b2_s3_v1.tib
______________Run11_Inc_b2_s4_v1.tib
______________Run12_Inc_b2_s5_v1.tib
______________Run13_Inc_b2_s6_v1.tib
______________Run14_Inc_b2_s7_v1.tib

------------------------------------------------------------
Week8: Attach disk 4 Use matching Task 4
Perform 1 full plus 6 inc
After new full completed, the oldest chain would be auto-deleted or retain based on your backup scheme setting. 6 new inc performed.
Task-4 Week8_Run8_FULL_b2_s1_v1.tib
______________Run9_Inc_b2_s2_v1.tib
______________Run10_Inc_b2_s3_v1.tib
______________Run11_Inc_b2_s4_v1.tib
______________Run12_Inc_b2_s5_v1.tib
______________Run13_Inc_b2_s6_v1.tib
______________Run14_Inc_b2_s7_v1.tib

-----------------------------------------------------------------

Switch cycle repeats with disk 1 and task 1 in use.
Week9: Attach disk 1 Use matching Task 1
Perform 1 full plus 6 inc
After new full completed, the oldest chain would be auto-deleted or retain based on your backup scheme setting. 6 new inc performed.
Task-1 Week9_Run15_FULL_b3_s1_v1.tib
______________Run16_Inc_b3_s2_v1.tib
______________Run17_Inc_b3_s3_v1.tib
______________Run18_Inc_b3_s4_v1.tib
______________Run19_Inc_b3_s5_v1.tib
______________Run20_Inc_b3_s6_v1.tib
______________Run21_Inc_b3_s7_v1.tib
--------------------------------------------

Backup scheme Auto-deletion does not begin until your keep X number of chains has been reached within each task.

The Full "b#" changes with each full created by that particular task.

--------------------------------------

dim 01/06/2014 - 19:01
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.