TIH 2013 creating full backup instead of incremental
TIH 2013, Win 7 Pro 64 bit
My backup has a custom scheme calling for a full backup followed by 3 incrementals, then another full.
I wrote a full backup to a new external driver last week.
Today I started a backup and TIH is trying to write a full backup again, not an incremental.
If it makes any difference, I have another set of identical backups on a different external drive (with a different drive letter) that ran inbetween these two backups. That one correctly wrote incrementals.
David,
Perhaps I am not-understanding correctly but to clarify
1. A backup task ties itself to a specific settings and to the storage drive that the task pointed to when it was created.
If you are using two target locations, you need two different tasks--each pointing to the target disk which was attached at the time the task was creasted. Each task needs its own individual target and ties itself to that specific target.
2. If for any reason you edited or changed settings, the new settings may not take effect for some time and still not produce the expected results.
If editing needed, it is better to stop using the wrong task and start a new task with new settings and a new target folder/destination.
David,
Perhaps I am not-understanding correctly but to clarify
1. A backup task ties itself to a specific settings and to the storage drive that the task pointed to when it was created.
If you are using two target locations, you need two different tasks--each pointing to the target disk which was attached at the time the task was creasted. Each task needs its own individual target and ties itself to that specific target.2. If for any reason you edited or changed settings, the new settings may not take effect for some time and still not produce the expected results.
If editing needed, it is better to stop using the wrong task and start a new task with new settings and a new target folder/destination.
I have a file backup task called "Users" that writes to an external drive that mounts as E:
I cloned this operation and set the location to a different external drive that mounts as M:
The original task correctly creates incrementals. The cloned task is writing full backups each time.
In addition to the file backup task called "Users", I have another file backup task created the same way, plus a disk backup task also created the same way. All three are producing full backups each time.
Each task need a unique name and I recommend each task have its own storage folder. Do not assign the same name to multiple tasks.
Each of the cloned task must be edited after the task cloning and the new task destination changed to its new destination such as M. New Destination disk must be attached during the creating or editing of the cloned task pointing to its new location.
Each backup task uses the target disk ID as the destination and the backup will fail or run wrong if that specific drive letter and same disk is not used.
------------------------------------
One option might be edit each of cloned task not working and use the MOVE option and point the target location to the designated disk for tht specific task.
Each task will need editing with its own target disk attached.
------------------------------------------------
Depending upon the type of backup scheme you wish to create, here is an example of each type. These can be set up for Disk image, or Partiton, or Files-folders backups. These example show how to set up automatic cleanup so the program will do the deletion after it reaches your set goal of how many chains to retain.
Editing or making changes to a working/existing 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 point to a new storage sub-folder so each task has it own storage folder/sub-folder. Old task can be stopped or deleted from the task listings.
-----------------------------------------
My signature link #2 may be of assistance.
also, my signature link #1 has a bunch of links labelled GH?? with the ?? being a varied group of topics.
---------------------------------------------------
Personally, I prefer to assign high lettered (such as x or y or z) to each of my usb targets and have each task use an assigned drive letter rather than have Windows assign randomly which causes a task not to work.
Each task need a unique name and I recommend each task have its own storage folder. Do not assign the same name to multiple tasks.Each of the cloned task must be edited after the task cloning and the new task destination changed to its new destination such as M. New Destination disk must be attached during the creating or editing of the cloned task pointing to its new location.
Each backup task uses the target disk ID as the destination and the backup will fail or run wrong if that specific drive letter and same disk is not used.
After cloning the task I changed the task name and changed the destination folder (otherwise it wouldn't be pointing to the drive at the right drive letter). Each task has it's own folder.
I was able to successfully create the initial full backup for each of my three cloned and edited tasks. It's just that it won't write incrementals.
Post the backup scheme of one that is not working. Also the log file for that task which is not creating the inc.
My respons will not be tonight. This is my last response for the night.
This may help.
http://forum.acronis.com/forum/75086
Attached are the log and a screen grab of the scheme definition.
(I tried to use the rich text editor to inline the figures. When I clicked "Save", it showed a blank comment entry and said I had to enter something. I tried this 3 times. Now I'll just go with attachments).
Greetings David,
Please delete the current task/scheme and recreate from scratch. Perform a BU and validate. Once confirmed, delete the old image you created previously.
OK, I tried this. I created a new file backup from scratch. Set the scheme to incremental with 3 incrementals between fulls, 2 chains. Ran the backup. Took 5 hours. When it was done, TIH showed "not backed up". Tried again, now everything on that external drive shows "not backed up yet". I restarted TIH. Same thing. Removed and re-added the external drive, then re-started TIH. Still no backups. I can browse for the backup and find it, but then nothing happens when I click "Add to backup llist".
Does 2015 work any better than this?
Edit:
After about 10 minutes, the back ups on the external drive have finally been recognized. The one built from scratch is now willing to write an incremental. This is crazy. What good is the clone operation if it doesn't work?
Hi David,
Great news! To re-iterate what MVP Grover was eluding to, I believe the task failed to properly detect the changed back up destination, likely because of the disk ID. Assigning a permanent drive letter, one that windows wouldn't typically allocate (X, Y, Z) for a connected device usually keeps this from happening. Its easier for us to help when complete information is provided. Letting us know that you cloned the task was helpful, thank you. MVP Grover is unsurpassed at identifying and correcting tasks which are not performing as expected. Based on your initial post, I believed deleting and recreating the task was the quickest solution. MVP Grover may have additional comments to add :)
It just keeps getting weirder.
Just to recap:
Windows 7 Pro 64 bit
TI 2013 build 6514
Seagate 5GB USB3 external drive statically mapped to M:
Started with file backup called "shared_music"
cloned this backup, changed the name to shared_music_5tb
changed the destination to M:/DavidsBackups/shared_music/
Scheme is incremental, 3 increments, 2 chains, auto cleanup
Wrote a backup, then a week later, TIH wrote another full instead of incremental
Schedule is off - I only run this manually
I recreated the backup from scratch.
I let the full backup run. When it completed, TIH showed one version. I backed up again, this time it wrote an incremental, still showed one version.
I also have a disk backup that I cloned, renamed, changed destination. It also wrote only full backups despite same scheme as above. But after running the file backup described above, I reran the disk backup and it's now creating incrementals.
But -
I have third backup, also a file backup with lots of exclusions I'd hate to have to reproduce. It insists on only write full backups.
I rebooted (the windows fix-all desperation move). Plugged in the drive. Started TIH. At first could not find ANY backups. after 5 minutes or so, now it finds all the ones on disk M:
You asked about 2015. For what is included works but comparing it features to a car, the 2015 has no AC, nor heater, nor Wipers nor side mirrors. The only thing that is included is the engine. If interested in 2015, I would read other posts. The 2014 works and has all the car accessories but difficult to find. Many have removed 2015 and went back to 2014. It depends upon your needs.
David,
I would give more thought to your backup strategy. Music is already compressed so it is already about the same size when included in your backup and a TI backup does not save you space or very little.
True Image backups are proprietary and backups cannot be read by any other program. Many of the responders on this program store their music in the normal format--either stored on multiple hard drives, or multiple DVD's, etc so the copies can be read by normal windows programs. All maintain multiple copies of their music.
The problem of no inc files I believe is being caused by something you are either doing or not doing. I have seen too many instances of the program working correctly by creating inc and deleting chains correctly to believe it is the program malfunctioning. Unfortunately, I do not have the 2013 version installed so not able to provide you with test data but my signature link 2 is based on 2012 & 2013. Note particularly in signature link 2, on figure 8, that the task name and name of the tib file is two different functions and they can differ or the two names can be the same. When you perform the task clone edit, you need to be making changes to the tib name as part of the task creation edit.
This illustration was not made for you but illustrates the results.
https://forum.acronis.com/sites/default/files/mvp/user285/guides/test20…
------------------------------------------------------------------
Please do me a favor and create a new test and create the test task as per my instructions beginning next.
Attach Drive M and inside your "shared_music" folder, create a new sub-folder named "Shared_File-wexcl"
M:\DavidsBackups\Shared_music\Shared_File-wexcl\
Create a new task by cloning your backup task which has lots of exclusions which wrongly writes only full backups
Edit the cloned task and assign new task name Shared_File-wexcl
Under destination, Browse inside the target storage new sub folder and select the new folder as the destination folder.
M:\DavidsBackups\Shared_music\Shared_File-wexcl
and specifically type into the tib file name window (without the quotes) the intended tib name as below
Shared_File-wexcl (no extension needed)
Sample procedure as shown in figure 8 of this example guide for 2012 & 2013
https://forum.acronis.com/forum/28705
Browse to backup scheme creation
1. Choose Custom scheme (must read custom)
2. Backup method to read incremental
3. choose Full with 3 incrementals
4. Turn on/enable automatic cleanup
5. Store no more than 2 recent version chains (this option must be selected)
Save all the changes. Save as non-scheduled.
6. Run the task manually and the first full will be created to
M:\DavidsBackups\Shared_music\Shared_File-wexcl\Shared_File-wexcl_Full_B1_S1_V1.tib
Immediately upon completion of the full, run the backup again manually via the Back Up Now
and an incremental is expected to be created (1 of 3 Inc before the next full)
M:\DavidsBackups\Shared_music\Shared_File-wexcl\Shared_File-wexcl_Inc_Bl_S2_V1.tib
On Future backups the deletion of oldest backup chain (4 files=Full + 3 inc) will first occur after Full B3 (backup #9) created (retention quota of 2 chains exceeded) and after each full thereafter.
-------------------------------------------------------------
If you want or need to create other new backups, my suggestions for success is to
1. Attach target disk and The Task name, and the sub folder name, and the tib file name, should all be the same but unique or differ from others.
-------------------------
Edit:
FYI:
The message "not backed up" is a poorly worded program message.
The message should read " no SCHEDULED backup has run", as it should not imply no backups have been completed--which they have.
I would give more thought to your backup strategy. Music is already compressed so it is already about the same size when included in your backup and a TI backup does not save you space or very little.
True Image backups are proprietary and backups cannot be read by any other program. Many of the responders on this program store their music in the normal format--either stored on multiple hard drives, or multiple DVD's, etc so the copies can be read by normal windows programs. All maintain multiple copies of their music.
I find this remark really interesting. Presumably this is not the position of Acronis, which no doubt thinks it is delivering software to fill all of it's customer's needs. I am quite aware that mp3, etc, are already compressed, so no further compression is going to occur in the backup. What I am relying on TIH to provide is a current image of the state of my music library, so that if I can restore it if necessary. I could just copy the entire library to an external drive with regular Windows copy, but that means that each time I do this I have to copy the entire library. I suppose I could return to using SynchToy or something similar.
The problem of no inc files I believe is being caused by something you are either doing or not doing. I have seen too many instances of the program working correctly by creating inc and deleting chains correctly to believe it is the program malfunctioning. Unfortunately, I do not have the 2013 version installed so not able to provide you with test data but my signature link 2 is based on 2012 & 2013. Note particularly in signature link 2, on figure 8, that the task name and name of the tib file is two different functions and they can differ or the two names can be the same. When you perform the task clone edit, you need to be making changes to the tib name as part of the task creation edit.
It is, of course, possible that I erred in setting up my backups. However, I did change the task name, changed the file destination drive and associated name. Finally, after a couple of full backups, TIH suddenly was content to create incrementals with no further editing of the task.
Please do me a favor and create a new test and create the test task as per my instructions beginning next.
I'll try this, though probably not until tomorrow or the next day, as I have to travel. Also, the backup as described will take about 5 hours. It's a big directory tree.
You can clone another task which is shorter in time but I chose that one because it failed.
If you wish, you could do a test using just one file for inclusion into a new backup.
2013 is able to replicate your Win 7 system disk into a new disk when needed. A disk image backup restored by a disk image restore works verfy well.
My comments related to the individual backup of music libraries.
No, I don't work nor associated for Acronis but I am a long time user.