Salta al contenuto principale

TI HOME 2011 - won't make correct NAMED TIB file

Thread needs solution

TI Home 2011 - latest build ... GOAL: create a Mon/Wed/Fri rotation. Each backup is a FULL image backup and replaces the file by the same name of the previous week. By the way, done this in 2010 many times so it's not me.

So, I made a Monday task ... set it to full ... scheduled it for Monday at 8:00 ... file name is Monday (.tib of course).

Cloned the Monday task ... changed the file name to Wednesday and scheduled it for Wednesday.

Cloned the Wednesday task ... changed the file name to Friday and scheduled it for Friday.

Upon looking at each of the 3 scheduled tasks, everything looks correct. Each task RUNs at the schedule time to successful completion.

PROBLEM: They all make (and replace) the file called "Monday.TIB" even though Wednesday and Friday show file names of "Wednesday" and "Friday" respectively.

Setting the whole thing up again has the SAME result. The only way I can get it set up properly is to set up each day separately; ie don't use the clone function. Once the clone is used, the TIB filename of the cloned task is always the filename of the original task. You can change it visually and save it and SEE it but it has no effect. Cloned MONDAY tasks always make a "Monday" file no matter what I do.

Acronis always seems to screw up the simple stuff.

0 Users found this helpful

Whether you clone the task or create individually, before you save any of the tasks, you must make corrections to each individual task.

The correction you need to make to change the path and actual folder name. It appears you are changing the name of the task but not also changing the path and file name. See attached. The task name is one entity and the backup.tib name is another entity.

Each task should point to a different path and backup file name.

Having multiple tasks backups inside one folder is acceptable to TrueImage but real use by many of us have shown that you will have better results if you have 3 different folder in your example. Only Monday.tib in folder "monday". Only Wednesday.tib in folder "'Wednesday". Only Friday.tib in folder "Friday".

Actually, I have definitely changed the backup file name. I'm looking right at it now. I'm in the "Wednesday" task and the backup file name is "Wednesday". When I start the task, it makes a "Monday1.tib" until completed and then replaces the "Monday.tib" file made by the Monday task. There is something wrong here. As indicated, if I make the SAME tasks individually (instead of clone), it work fine.

If you still have some of the cloned tasks, browse to the Acronis scripts folder and open a cloned script in Notepad. Look at the contents and see if you find the error. check to see if the clone script is carrying something over and it is not being cleared.

I will try to replicate your problem but it will not be until Friday night--most likely.

Hi Bill,

Now I  have had a chance to test your task cloning issue but I all my tests were successful. The backup files were correctly created. I have pictures available.

What I did was to create a Monday task. Cloned Monday to become Wednesday. After completing Wednesday, closed Wednesday to become Friday.

I created the Monday task first with all the proper settings and a custom backup scheme and these were the procedures I followed.

Editing the cloned task:
1. Edit 1 of the Wednesday task (Monday clone) was to remove or delete the Monday task name shown on the main screen. Task name left empty for fulfilling by the file name edit. I found having the name empty worked better than trying to change it.  See image 2-item 2

2. &  3.  Edit 2 was to browse to the target directory. I had trouble accessing the browse option. I then chose a different folder and path and was able  to return to the desired folder and add the Wednesday backup file name for the Wednesday task.  See pictre 2.  When editing the Friday  task, I had to repeat this round about way but was then able to open the proper folder and assign the proper custom Friday task name.  See image, item 2

4. & 5. was reconfirming the correct settings. I did find I had to correct my backup source as my test was to create a backup of my drive E partition which was small and produced a quick backup.

6. Edited the scheduled time and dates. For my testing, I just use a few minutes time separation before each task so I could conclude the testing without too much delay. That should not affect the validity of the testing.

Also for purposes of the  test, I used the task name and task number as part of the task name. This enabled me to see which task was being run and in what sequence.

As each backup was created, I utilized one of the options to take a screenshot of the target folder so you can see how each backup was created.

Image 1: Editing the cloned task

Image 2: Assigning backup file name

Image 3: Completed tasks.

Image 4: Custom backup scheme to have each full backup to overwrite the prior one.

Image 5: This shows the storage folder as each backup is being completed.

The first Monday-Wednesday_Friday tasks were completed and then the same task sequence was repeated 3 more times. the oldest backup is listed at the first item in the directory and the most recent is at the bottom. These were run a Mon-Wed-Fri and that is how the file sequence is displayed. If you have trouble viewing this file, I have also attached a pdf file which shows the contents of the storage folder more clearly.

The above picture more clearly displayed in a pdf format below which can be enlarged.

http://forum.acronis.com/sites/default/files/forum/2009/11/5940/cloned-…