View Full Version : TI 9.0: How to copy scheduled tasks?
zrocker
March 29th, 2006, 11:39 PM
I've spent 10 mins selecting 50 specific files/folders that I want to backup to a separate, static (overwritable) .tib file. Now, I want to replicate that scheduled backup task 3 times and change the .tib file name to another static file name. Then, I'll have 4 (full) backup .tib files that get used over and over and not have to manage (archive or remove) .tib files.
So, how do I copy a scheduled task and then edit it to change just the .tib backup file name? Other programs have a 'job name' feature and allow you to 'Save as...' to create a copy of a configued job. I want to do basically the same thing (copy or Save as) in TI.
Howard Kaikow
March 30th, 2006, 12:14 AM
TI appears to save th scripts as XML files in, e.g., J:\Documents and Settings\All Users\Application Data\Acronis\TrueImage\Scripts.
However, the file names are programmatically generated using a GUID as the main part of the name.
TI would need to add a user friendly interface to manage the critters.
One could generate a GUID and create a unique filename for a changed script.
Don't know whether TI would accept that script when TI starts.
zrocker
March 30th, 2006, 12:21 AM
Thanks Howard.
Before I read your post, I found the scripts and copid one of them, edited it and it worked fine. I just incremented the last # in the guid filename by 1 and changed the same in the script file itself (also changed the Display name to a unique name).
Howard Kaikow
March 30th, 2006, 12:49 AM
-{ Quote: "Thanks Howard.
Before I read your post, I found the scripts and copid one of them, edited it and it worked fine. I just incremented the last # in the guid filename by 1 and changed the same in the script file itself (also changed the Display name to a unique name)." }-
Whilst what you did might work, the proper way to create a GUID is via software, not by manually changing a string that looks like a GUID.
vBulletin® Copyright ©2000-2012, Jelsoft Enterprises Ltd.
Copyright ©2002 - 2012, Wilders Security Forums