A few noob questions about TI2014
I just bought the full version of TI2014 for Win8.1 and have been using it in some form since 2009. I only use TI2014 for the basic functions. I only make full backups. I never schedule them. Other than creating an emergency boot Disk, that's all I do. I have a few basic questions I ask in hopes of streamlining the operation. Any help is appreciated included partial responses or redirects to other links, etc. Thanks!
#1. On an SSD drive, I keep a partition which I used only for the OS (win 8.1). When I backup or restore this partition, is it best to also backup/restore the "recovery (300mb)" partition along with the EFI system partition along with the OS partition?
#2. Unless I'm mistaken, because I ONLY do full back up partitions and only do them manually, I might as well disable the three processes that TI runs on Windows start ups:
Acronis Schedule Helper
Acronis TIB Mounter Monitor
Acronis True Image Monitor
I would like to direct TI2014 to NOT run any of these processes at start up, but there doesn't appears any options for this. I could use windows task manager to prevent these processes from running, but I'm hoping for a cleaner solution. I really don't need TI2014 to ever run unless I'm actually restoring or creating a backup image. Is task manager my only option?
#3. This is a small issue, but is there a way to save the default options for when I run TI2014? When I want to create a new image I always have to navigate to a the proper destination because TI2014 never remembers. Likewise, I always have to select the choice "do not schedule" because it always defaults to weekly. Is there an option to set default? Is there configuration file I can edit?
Thanks for any help you can offer, even if it's just for one of my three questions.
I just bought the full version of TI2014 for Win8.1 and have been using it in some form since 2009. I only use TI2014 for the basic functions. I only make full backups. I never schedule them. Other than creating an emergency boot Disk, that's all I do. I have a few basic questions I ask in hopes of streamlining the operation. Any help is appreciated included partial responses or redirects to other links, etc. Thanks!#1. On an SSD drive, I keep a partition which I used only for the OS (win 8.1). When I backup or restore this partition, is it best to also backup/restore the "recovery (300mb)" partition along with the EFI system partition along with the OS partition?
It is preferable to include ALL partitions of the system disk. Unless you know what you are doing, just include everything.
#2. Unless I'm mistaken, because I ONLY do full back up partitions and only do them manually, I might as well disable the three processes that TI runs on Windows start ups:
Acronis Schedule Helper
Acronis TIB Mounter Monitor
Acronis True Image Monitor
You will need to keep the first one. YOu can deactivate the last 2 ones.
I would like to direct TI2014 to NOT run any of these processes at start up, but there doesn't appears any options for this. I could use windows task manager to prevent these processes from running, but I'm hoping for a cleaner solution. I really don't need TI2014 to ever run unless I'm actually restoring or creating a backup image. Is task manager my only option?
You can disable the Acronis Monitor startup item. Do not disable anything related to the scheduler, even if you don't use scheduled backups.
#3. This is a small issue, but is there a way to save the default options for when I run TI2014? When I want to create a new image I always have to navigate to a the proper destination because TI2014 never remembers. Likewise, I always have to select the choice "do not schedule" because it always defaults to weekly. Is there an option to set default? Is there configuration file I can edit?
To create a new image, simply run a full backup task again and again.
David Henderson.. thank you I did check out those links. One thing I read seemed to suggest there was something wrong with creating an image of the OS partition FROM windows which happens to be running on that same partition. Is this really an issue? Rebooting from CD/DVD just to make an image seems excessive and inconvenient.
Pat L /Grover H
Thanks, I really appreciate the help.
RE: 3 partitions. I can easily include all the system related (OS related) partitions. It's no trouble and they don't take up much space. However, to be clear, the SSD has other non-OS partitions that I don't want to need to backup.
RE: The three processes that TI runs at startup. I'm glad to hear you say I can disable 2 out of 3, but why is the Scheduler Helper necessary given the manner in which I use TI for only full back ups without ever using the scheduler? I feel as if I could literally uninstall TI and then reinstall it as needed to create or restore images. Of course that would be a lot of work, but I'm trying to make the point that I don't know why it has to be active at all.
Also, for the processes I can deactivate, is there any way of doing this other than disabling through windows task manager? Surely after all these years TI has a cleaner solution than that I hope.
RE: Running a full backup task. I have no problem doing a manual backup. I'm just trying to make it a little simpler. I went to GroverH's link, but I don't want to switch to disk mode because I don't want to image the ENTIRE SSD. I think I need to study more about how to do a task and save a task. Ideally, I'd like TR to remember:
1) Location to save new/next image.
2) password already assigned
3) Setting for no schedule
4) Opportunity to manually input a new image name.
As I said, I'm still looking into this, but I wanted to respond sooner than later. I guess I can go to the Backup and Recovery tab and select a prior image as a sort of template. Not sure.
As far as I know, there should be no problem making a backup of the OS partition from within Windows. A good idea would be to validate the backup once it's done. It's probably a good plan to use the rescue boot disk occasionally to boot your computer to see your backups and restore a file just to make sure it works.
The idea of having a full and complete backup of all partiton relates to being able to recover your system if the system either becomes non-bootable or has blue screens, etc; or if you hard drive fails and you need to use your full and complete backup to create a new replacment disk.
This does not imply that all restores are the full disk but the full restore capability is only if needed.
The restore of C only would be the most frequent but you have the others available "just in case."
GroverH,
I understand what you mean regarding backing up the whole disk but only restoring a part or parts (OS + recovery partition, etc.)
However, I'm not interested in routinely making a full back up of my entire 250GB hard drive and should it fail I probably wouldn't get the exact same SSD anyway. That said, I understand and appreciate your point. Perhaps I was just lucky, but I using older TI versions and older windows OSes, I was able to move just the active partition from one disk to a new one without issue. My comment on this was a response to your informative links, particularly the GH3 "how to create a non-scheduled" backup. By saving-as-default I was able to lock in my custom backup scheme. However, each time I wish to create a backup image, I'm still required to manually navigate to the proper disk location and to manually select "do not schedule". Can I assume I have reached the limit of parameters that can be stored and remembered by TI2014?
I'm still hoping you or Pat can give me a follow up answer regarding whether or not there is an alternative to using W8.1 task manager to disable TI processes at start up (Acronis TIB Mounter Monitor & Acronis True Image Monitor). If there is no option for this, is there an exe parameter/flag that I can attach or config file I can edit? I'd also like to better understand why the "Acronis Schedule Helper" is required and should not be disabled from starting up. Because I only rarely create and restore images, all manually, I'd prefer to leave the whole program unactivated until I need it with nothing at all activating at startup.
Thank you for your advice and your tutorial links. Very helpful.
However, each time I wish to create a backup image, I'm still required to manually navigate to the proper disk location and to manually select "do not schedule".
To initiate a manual backup, this link shows the correct method.
------------------------------------------------------------
The backup task is created once with all the settings (scheduled or
non-scheduled) you want and then saved under the "Backup later" option.
After that is completed, any and all future non-scheduled backups are
initiated by opening the program and clicking the "Backup now" option so
unless you use different backups to backup different data areas, there is not
further need for additional backup task creation nor schedule changes.
For backups which already occur on a schedule, the clicking the Backup Now option will simply add additional backups under the numeric control of the backup scheme.
------------------------------------------
GH4. Illustrate Manual Backup Now option.
Bob,
Please post a screen capture of your main screen showing the task which causing the problems.
Perhaps this link might help.
GH1. How to change a backup task from scheduled to "Do Not Schedule".
Hi GroverH,
To follow up on your very last post here and related to some of this thread topic:
I notice in performing non scheduled (in my case "disk mode/full") backups that if I will simply click on 'Back Up now' that all settings/exclusions/destination apply to the next version of this full backup with no further user input. Naming scheme basically follows my original backup name with some extra "stuff" trailing. Great! But I have one question which I hope does not detract from the OP's train of thought:
I notice with each additional backup I preform @ 'Back up Now' it refers to itself as a "version" of the backup --- I really DON'T WANT one version dependent on an earlier version in any way or fashion. NOR DO I WANT A BUNCH of older versions cluttering up my hard drive. Now for peace of mind, I tested my recent backup to see if there was some dependency between versions.
(1.) I preformed a new non scheduled disk mode/full back up. Then I went to destination folder and deleted the older backup (older version).
(2.) Then I went back to ATI2014 backup list and clicked on Validate (intending to validate the very latest backup of course). For a second ATI2014 got confused because it could not find backup. So I took its hand and walked it over to the new version of the back up. Immediately ATI2014 recognized it and started the validation. Everything was hunkydory. The backup list was updated with correct date and backup file size.
(3.) Later I mounted the newer backup just in case to see if it looked normal. Everything looked normal with designated folders EXCLUDED just like I want. Great!
...So do I have a good (independent) full backup that will restore? I ask this because I notice that backup file sizes can vary as much as 2 GB or maybe even more BETWEEN VERSIONS which I simply cannot account for??
(Gosh I hope I didn't stray too far off main topic. My apologies.)
bcool,
The term "version" is being used to simply indicate "another" or "different" version has been created. Whenthe backup type is a full only, there is no infured dependency.
When the backup if a full only backup, there is no dependencies. It is a standalone backup.
If you have several full in a folder, only the single selected file will be validated and each full is its own single chain.
The letter b1, or b2, or b3 is the identication and none of the full has any relationship with the others except for the program to keep the numbering in order and as a method of identication for the user to trace. The date and time assigned to the file could also be a form of identication if teh b2, b2 were not in use.
The program does tract each issue so it knows which files it has created and if you decide to delete any old full backups, do be sure and use the program do perform the deletion. If the backup task exists, DO NOT PERFORM MANUAL DELETION FROM WINDOWS EXPLORER. Do any deletes from within the program. The only time you can use Windows Explorer to perform a delete is when the backup task which created the backups no longer exists.
GH5. How to delete backup files (wtihin the program) using Acronis Backup 'Explorer'
Hopefully, the above will ease your concerns. Each disk mode backup is a standalone backup capable or restoring your existing system.
Grover,
Okay, I think I understand. I was confusing the "backup name" with the file name. The "backup name" is really more of a task name that can be used over and over again to make a backup image using the selected file name as found in the "local storage" input section where you designate the location. It is on this file name that you can attach tags for date and time and such, but at first I wasn't using any of the @ tags so I didn't realize it was making a new backup each time I clicked on "back up now". The file name only changed slightly going from b_1 to b_2 or something along that order. I expected to see the "backup name" section add another entry, so at first I thought it was just copying over the original backup. Now I understand.
Thanks for your help and the clarification. Sorry it took me so long to get it.
Still hoping to get a follow up on question #2...
Regarding this comment from you Grover:
************
The program does tract each issue so it knows which files it has created and if you decide to delete any old full backups, do be sure and use the program do perform the deletion. If the backup task exists, DO NOT PERFORM MANUAL DELETION FROM WINDOWS EXPLORER. Do any deletes from within the program. The only time you can use Windows Explorer to perform a delete is when the backup task which created the backups no longer exists.
GH5. How to delete backup files (wtihin the program) using Acronis Backup 'Explorer'
Hopefully, the above will ease your concerns. Each disk mode backup is a standalone backup capable or restoring your existing system.
***********
Does this apply to FULL backups created using the same "backup name" or task name as seen in the Acronis backup "explorer"? I already noticed that if I delete the "backup name" in the Acronis backup Explorer menu that it deletes ALL the images created under that task or "backup name". Let's say I only create full backup images, under a particular backup name or task and so I end up with 10 created images, all of them "full" backups. Any single one of those backup should be fine on it's own to restore the partion(s) accordingly. In that case, surly I should be able to delete any number of the 10 images USING WINDOWS EXPLORER without it effecting the integrity of any of the remaining files (images), correct?
I'm still hoping you or Pat can give me a follow up answer regarding whether or not there is an alternative to using W8.1 task manager to disable TI processes at start up (Acronis TIB Mounter Monitor & Acronis True Image Monitor). If there is no option for this, is there an exe parameter/flag that I can attach or config file I can edit? I'd also like to better understand why the "Acronis Schedule Helper" is required and should not be disabled from starting up. Because I only rarely create and restore images, all manually, I'd prefer to leave the whole program unactivated until I need it with nothing at all activating at startup.
Thank you for your advice and your tutorial links. Very helpful.
You did the right thing by using the task manager to disable these startup items. There is no other alternative that I know of.
Pat L,
Thanks for the clarification. Given that I'm only making FULL backups and never using the scheduler, and given that I am only imaging and restoring the Primary OS partition (along with it's satellite recovery partitions) rather than the whole SSD, what would be the harm of blocking the "Acronis Schedule Helper" along with the other two processes?
Okay, I think I understand. I was confusing the "backup name" with the file name. The "backup name" is really more of a task name that can be used over and over again to make a backup image using the selected file name as found in the "local storage" input section where you designate the location. It is on this file name that you can attach tags for date and time and such, but at first I wasn't using any of the @ tags so I didn't realize it was making a new backup each time I clicked on "back up now". The file name only changed slightly going from b_1 to b_2 or something along that order. I expected to see the "backup name" section add another entry, so at first I thought it was just copying over the original backup. Now I understand.
Your understand is correct but a little clarification of my practices.
1. Once the backup task is created, I will NOT perform an changes of configuration to that task. If changes needed, I stop using the old task and create a new task with all the corrections. The only exception to changes is a change of schedule or stopping a schedule and both of these can be done from the main menu without going ito the task edit function.
The task name is not edited nor is the name or path assigned to the tib backup file.
These links show how to change or stop the schedule without using the task edit functions.
GH1. How to change a backup task from scheduled to "Do Not Schedule".
GH2. How to enable a backup task schedule or change a schedule time..
While editing a task is not prevented by the program, it is something to be avoided as the results of an edit is almost always not what is expected and an edit usually just delays the in-evitable of needing to create a new task. Usually, an edit is a waste of time. It is just quicker to start over with a new task.
2. All new tasks point to a new or empty sub folder. One storage folder per task. For example, the folder name may be MyBackups but then it has multiple sub-folders or each task has its own sub-folder. No intermixing of backup files.
3. Yes, Acronis makes it confusing by calling the task name as the backup name.
Yes, the task or backup name is one name; and the backup tib files is another name. Both can be alike or can differ. I always make sure they differ.
4. The name assigned to the tib backup file is user controlled to which user can add _@date@_ or _@time@_ which I never use, but I always add
_@exec@_
to the end of my tib file name. This adds a sequential number to each backup and becomes my backup file number.
This is the sequential number you see in this backup listing at the bottom of this link.
GH14. Custom Differential Backup Scheme. Keep 6 Diff, 4 chains. & folder
Does this apply to FULL backups created using the same "backup name" or task name as seen in the Acronis backup "explorer"?I already noticed that if I delete the "backup name" in the Acronis backup Explorer menu that it deletes ALL the images created under that task or "backup name". --
Response: Here is how to remove the task from your main menu listing. This removal of task name only removes the task and DOES NOT DELETE THE TIB FILES WHICH ARE LOCATED IN THE SPECIFIED STORAGE FOLDER. Each of these "disk mode or disk image" full backups continue to be available for Recovery as single file chains. --
GH20. Remove Single Task from Task Menu Listing
Let's say I only create full backup images, under a particular backup name or task and so I end up with 10 created images, all of them "full" backups. Any single one of those backup should be fine on it's own to restore the partition(s) accordingly. Yes.
In that case, surly I should be able to delete any number of the 10 images USING WINDOWS EXPLORER without it effecting the integrity of any of the remaining files (images), correct? YES-BUT.
If the task which created the backup files is listed on the main menu listing, then the deletion must be done from within the program via the Acronis Backup explorer. Using the program keeps the history file in synced for housekeeping purposes but nothing can change the file integrity except if it becomes corrupt due to a bad disk read. --
But, If the task does not exist, then YES, the deletion can occur from the Windows Explorer as there is no visible history tracking after the task is gone.
GroverH,
I think I got it. To be safe I started over from scratch, carefully setting up my new task for non scheduled/disk mode/full with custom exclusions which backups entire system hard disk. I'll keep three versions at all times and delete older versions within Acronis as per your illustration.
Man---is there a lot of finessing to get things just so with ATI2014! They don't happen to offer an associate degree in Acronis True Image, do they? As always, thanks.
Hopefuly, you saw both my postings (15 & 16). I still forgot to mention....
It is my practice to use a different task name for each new task created. As my backup tasks usually last for a long time (no changes) and coves many backups, using a new name each new task is not an inconvenience. A new name per task helps to keep the tasks separate.
In addition, should you need to restore your C drive or computer to a prior backup, do plan, after the restore, on starting all new tasks and cease to use the old tasks. This is necessary because the restore puts the history file out of sync with the existing backup files so a new start is needed in order to keep the numbering and auto-deletion in sync with each other. Even if the restore was the most recent backup you have, the restore is still of a snapshot which existed prior to the creation of the backup used for the restore.
As you know, my suggestions are based on what I found works best for me. Some of my suggestions are at odds with what is permitted by the program, such as editing is permitted by the program but I have found editing to be a bad idea which causes problems rather than fixes problems.
GroverH, not to belabor this topic to the point of fatigue..... a new task would constitute a task that is "new" implying "different" in some way from an existing/saved task. If I have a task saved that is for backing up my system hard disk in FULL "disk mode" with custom exclusions, and I do not wish to make any changes to the settings, this is my task. It is my existing task that is saved. If I run the same task expecting to get the same results, I should in fact get a disk mode copy of system hard disk. If so then I do not have to create a "new" task every time I would rather just click on "back up now" on my reliable/existing task ---- am I correct so far? Finally, after reading your instructions, I realize there is a better way, a correct way, to delete the older images within Acronis and thereby not cluttering up my hard drive with outdated backup images [in the case of "full" backups, "versions" are not inter-dependent]. By the way, if I can ask Acronis to prune these images automatically, I'd be happy to let her do this for me.
AN OBSERVATION: I judge by the posts I read in this forum that some users have sophisticated back up needs and some of these schemes seem complicated to me. I have no such requirements. I simply want to have on hand maybe 3 good, validated, system hard disk images in case I get into trouble. I would like to have a couple of options for recovering a good image successfully, e.g. from Acronis' boot media, or from a WinPE disk, or even starting the recovery from within an otherwise unstable Windows if that option is even possible? Whatever...as long as I can run ATI2014 from somewhere to recover one of my backup images...and when the smoke clears, I want to see my Windows 7 desktop in all her pulchritude! Thanks.
Well stated. There is nothing in your comments that I would disagree with.
My practice--The only restore from within Windows is a restore of some single files--not related to the OS or programs.
It helps n(safety wise) if your stored good images are stored on different disks.
I'll check to see if there's a specific setting that gets Acronis to prune some of these "FULL" non scheduled backups after a while. If not, I'll simply follow your "delete within Acronis" instructions, GroverH
Incidentally, I do make it a point to store 1 copy of these images on an external USB hard drive at all times. Otherwise the image set is normally written to my second PHYSICAL hard drive. For me, creating a separate image with external USB drive as destination...egods! is soooo slow. So, I use CopyHandler to simply copy a completed image file over to external USB drive, I guess for that incredibly rare instance where I wouldn't be able to access my second hard drive?? Or perhaps in case of some kind of unspecified catastrophic failure? [Anyhoo, FYI...CopyHandler has a built-in checksum for absolutely reliable copy. I guess I could also figure out a way to run a second "VALIDATE" on the copied image on the USB drive just to be really, really sure that the copy is good before I disconnect the USB drive? ]
Thanks and thanks to the original poster for bringing this topic up in the first place
Hello again Grover ---- It's probably not the best idea to bury this request for clarification deep in this thread....
but with respect to your GH5. link above in your post, I simply do not comprehend your English at the very bottom,
quote: (see image attachment).
Now regarding deleting differential backups (only files backups not disk images):
ATI2014 is set to backup my user folder and so far I have "55" versions! This of course creates differential backups of "files and folders" which are dependent. Now the concept should be simple to grasp, and perhaps I'm overthinking it...
Anyway I'd just like to "trim" some of the 55 files. Is that request so unreasonable?
And I know I have dependencies to worry about and frankly it all gives me a headache. I was tempted to just delete all 55 and let ATI2014 start over in the morning. But instead I did nothing until I understand how to prune some of these dependent versions. Obviously I want to preserve the most "recent" copy of my user folder. What do most people do? Just let ATI2014 build up versions ad infinitum so to speak?
I'm glad you are a patient helper...
I'd just like to "trim" some of the 55 files. Is that request so unreasonable?
No, not unreasonable at all. In fact, it is a good idea and has been requested many time before.
Unfortunately, this is not part of the programs current features and any deletion of any diff file (except for the most recent) will cause the task to error out and cease to continue to create new dif files.
However, if you should delete selected files, what is left should be restorable--that is, the full only or the full plus any single diff file shoud be restorable. Or at least, they have been in the past.
After the deletions, you coud also try the validate option and try working your way through the resulting error message, it may validate but it never has in the past but the files left have been restorable in the past.
I have deleted isolated dif files myself and they have been restorable for me but would not validate due to the missing files.
The option and risk is yours if you wish to try.
My preferred backup scheme is using the options as listed in this link with the user changing the number of diff and the number of chains to keep to fit their needs. I prefer the option which is the "store no more then X recent chains".
GH13. Create Custom Differential Backup Scheme. 2 Diff, Keep 2 chains.
Other combinations of delete version chains older than X days might also work but my testing was not extensive using this specific option.
-------------------------------------------
If you do the deletions on some of the 50, I would use the program to perform the deletes.
GH5. How to delete backup files using Acronis Backup 'Explorer'
ah Grover...just curious. I have "55" versions of my "user" folder backed up already. How many more differential versions do you think ATI2014 will add before somehow pruning itself? 100, 200,1000, 5000, 1,000000?
Just think of it: a million versions! Whoa!
Anyway, thank you. Your help always seems to bring me back from the brink... :-)
Some time back, Acronis indicated they have not put a limit on the number of creations possible.
Frankly, I would be concerned about the base full as being too old.
If by 55 you are implying that the full is also 55 days old, it comes down to how much your system changes.
Frankly, I would never allow my diff number to reach that before creating a new full as illustrated in GH13 example.