Salta al contenuto principale

Change default reply to error message

Thread needs solution

ATI Home 2010, Win 7 Home Premium 64 bit

During unattended scheduled backup an error is generated requiring a selection within 10 minutes or the operation will "Quit". Since this is unattended the operation then "Quits".

Rather than "Quit" I would like the default action to be "Retry" because I do not want to come back hours later and find that my backup has not been completed.

It appears to me that a "Retry" results in additional backup files similar to incremental ones and this would be acceptable.

Any comments or suggestions?

0 Users found this helpful

Are you aware of the "error handling" options within Backup options. You can change the default or at change at the backup level.

Thanks for responding so quick.

I am not aware of any "error handling options" and cannot find any reference to them in ATI Home 2010 or in your "Accumulated Wisdom Guide".

Please direct me on the location to change the default setting.

Thank you.

This is what I was referring to.

Allegato Dimensione
35455-90100.gif 42.36 KB

Normally "Do not show messages and dialogs ..." means that messages will NOT be shown BUT will be acted on so the default of "Quit in 10 minutes" will still apply.

I want to change the default to "Retry".

This is the only information I have.

user manual 9.4.1.7
Do not show messages and dialogs while processing (silent mode)
The preset is disabled.
You can enable this setting to ignore errors during backup operations. This feature was mainly designed for unattended backups when you cannot control the backup process. In this mode no notifications will be displayed if errors occur during backup. Instead you can view the detailed log of all operations after the task finishes by selecting Tasks and Log on the sidebar and then clicking the Log tab. You may use this option when configuring a backup task to be run during the night.

I forgot that I have the manual pdf also.

It is not clear if the default applies but I assume that is what will happen.

I have changed the setting for my scheduled task. Time will tell and if "Quit" is the result I will suggest to ATi that an option to change the default be offered.

The log does not give much detailed info on the error to help in eliminating it. Neither does the error window when actively watching a backup.

I will add a reply here after I find the answer.

Thanks for your time and replies.

Hello RoadBlock and GroverH!

GroverH, thank you for your valuable assistance!

RoadBlock, thank you for finding time to open the thread and share your experience with us. I completely understand your concern and will be glad to assist you.

Unfortunately due to the lack of diagnostic information it is hard to say what exactly is wrong, but according to the description you're providing us it looks more like "10 minutes timeout" feature:

Recently (in Acronis True Image Home 2010) our development team implemented 10 minutes timeout feature. It was designed for cases when you have several tasks scheduled. Our Scheduler is built in such a way that it cannot start the second task unless the first one is finished. Sometimes it may happen so that the first task is stalled. Thus we desined this timeout: in case the task is inactive during 10 minutes, it is canceled for the following tasks to have an ability to run.

Currently there is no possibility to modify this limitatiuon, and we're promised that this will be improved in the next release. Usually our customers face difficulties with this feature only when backing up to CD/DVD. In order to help you we need to find out the reason of task stalling and resolve it. Could you please provide me with the following diagnostic data:

  1. Target location for the backup
  2. Acronis Info from the machine where you have tasks stalling

It will help me to localise the issue and find an appropriate solution for you.

Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!

Thank you in advance for cooperation and patience.

ATI is backing up to a Netgear Network Attached Storage device.

Unattended, scheduled start at 1:20 AM Saturdays only.

Attached is AcronisInfo file requested plus a current directory of images with some comments added.

Allegato Dimensione
35489-90115.zip 3.83 MB
35489-90118.txt 1.16 KB

Eric,

1. Your build of this version has been updated. I suggest you get a more current build of 2010 from your registration page---7046 is the current one. Don't forget to create a new Rescue/Recovlery CD and label it with version/build/serial.
This build may provide some improvement over image numbering. I would also suggest you additionally update 7046 with the latest scheduler.
http://kb.acronis.com/content/1518

2. As I looked at your file, the error message seemed to imply that this file was at issue.

"\\NAS\AcronisImages\i7\MyBackup33(1)5.tib"

"Error occurred while writing to the file. Click Browse to specify volume location,Retry to try again, or click Cancel ?Retry//?Cancel/"

As I looked at the file names being created by TIH, your's seems to be typical (confusing) where there are multiple backup sets in the same folder. Most certainly, I would create a new task and start in a new backup storage folder--after upgrading. See #3

3. After upgrading the build, I believe you would experience a great deal of success if you were to supplement TIH with oracledba's Chain2Gen (C2G) helper program. One way you would benefit would be to have each backup set in its own folder and your C2G parameters determine how many backups in a set and when the backup is to be run.

http://forum.acronis.com/forum/11261#comment-33187

......C2G is a free helper program for TrueImageHome(TIH) TIH does the scheduling and the backups. C2G does the managing of when a full is created and allows you to maintain several sets of backups. More info can be found via item 3-B and 3-A inside my signature index below. Both references can be helpful. If you want more info about C2G don't hesitate to ask. I use it myself and it works great and very dependable.

After my overnight problems early last Saturday I did download and install 7046 and used it for the following runs which produced the images in the directory I posted. The AcronisInfo.zip was also made AFTER the upgrade and runs.

I have downloaded, unzipped, and placed the Chain2Gen folder in a location which does get backed up. I have set the following parameters:
set TARGET_UNC_N_DEVICE=\\NAS\AcronisImages
set TARGET_GENERATIONS_FOLDER=\i7\
set MAX_BACKUP_GENERATIONS=4 <----- to cover months with 5 Saturdays
set TRGR_ON_OCRDAY1=1st_Sat

Attached is the resulting "Dir". Note that all "set" directories are empty.

I have set up a new ATI task to run on Saturday. I will manually run the task before if I get a chance.

If there are errors I assume that even with "silent mode" set the default "quit" will result but I have enabled emails to be sent on error so the next run may answer that question.

If you have any comments or suggestions about my settings please tell me.

Allegato Dimensione
35710-90145.txt 2.36 KB

Some general observations.
1. As mentioned in post #9, I do sugguest that you update your new 7046 with the latest scheduler which was not a part of your recent 7046 install.
http://kb.acronis.com/content/1518

2. You may be interested in this recent post by Oracledba about how C2G functions.
http://forum.acronis.com/forum/5940?page=2#comment-34925

3 Be sure you perform the security unblock as referenced in Appendix C or the at the beginning opf my pdf (index item 3B). This is an absolute necessity.

4. The frequence of backups is controlled by your frequency setting inside the TI scheduled task. I assume a weekly setting but I am not sure when you have it set to begin within the TI task schedule.

5. The setting ..... set MAX_BACKUP_GENERATIONS=4
TRGR_ON_MAX_TIB_CNT=5
will produce one full backup (first Saturday-or however you have the TI task set to run) plus one incremental backup each subsequent run until the max of 5 files (or the next first Saturday) is reached. This number could be increased if you think you might want to create some manual interim incremental backups. The "set TRGR_ON_OCRDAY1=1st_Sat" will insure that a new full backup is created each 1st Saturday.

If you wish to have only full backups performed each Saturday, then you will need to change the 4 to 0 as listed in the
!_USER_SPECIFIED_PARAMS_FOR_ACRONIS.bat parameter file.

6. While editing a TI task is strongly discouraged (too many unknown changes), you can simulate an edit and look to see if the backup target location is as listed below.
\\NAS\AcronisImages\i7\Set0\MyBackup.tib
...I am assuming that the name of your backup is MyBackup.tib and it contains no digits as the ending character. ( A user backup name such as MyBackup1.tib is known to create problems.)
------------------------------
If any of my descriptions or assumptions differ from what you intend, don't hesitate to discuss.
------------------------------

Edited.

Ref post #11 paragraphs:

1. It was not clear that you wanted me to update the SCHEDULER. I have now done that.

3. All are unblocked.

4. Weekly on Saturdays at 1:20 AM.

5. You are confusing me. With these settings is the following correct?
MAX_BACKUP_GENERATIONS=4
TRGR_ON_OCRDAY1=1st_Sat
TRGR_ON_MAX_TIB_CNT=0 (the default)

- Five generations of backups will be kept (set0, set1, to set4) or one per month.
- Each generation has one full backup plus an incremental for every following Saturday
UNTIL the first Saturday of the NEXT month.
- There is no limit on the number of "tib" files in a generation.

6. I am using \\NAS\AcronisImages\i7\Set0\MyBackup-.tib as suggested in your PDF.

I have started the log support using Acronis Schedule Manager.

I can see why you were confused. I gave you wrong information which has been blocked out on the prior post.

As to your questions based on the task being run Weekly:
---------------------------------------------
MAX_BACKUP_GENERATIONS=4
This setting will retain whatever the content is in folders set0, set1, set2 and set3. If the content contains one months of backups, then you have 4 months retention.
----------------------------------
TRGR_ON_OCRDAY1=1st_Sat
This setting will ensure that a full backup will be initiated on the first Saturday of each month.
--------------------------------
TRGR_ON_MAX_TIB_CNT=0 (the default)
A setting of 0 meaans that only one backup file will be allowed into the Set0 folder before it is rotated into becoming set1. This means that every backup will be a full backup and there will never be any incrementals and the set folders would only contain one file (full).
------------------------------------
TRGR_ON_MAX_TIB_CNT=5
will produce one full plus 4 incrementals.
One full backup (first run) plus one incremental backup each subsequent run until the max of 5 files (or the next first Saturday) is reached.

In the event that you would want or need to run additional backups for whatever reason, the additional backups would need be run by another task to be created when that need arises and the additional storage would be into another folder with the first additional run being a full backup.

Should you run this current task additionally manually during the week, the manual runs will count against the 5 total and the rotation would be more frequent than weekly.
----------------------------

However, if would you want any additional backups to be a part of the current weekly task and the additional's would always be incrementals, then additional settings are needed.

Sorry, but confusion continues because your comment in post #13 about "TIB_CNT" does not agree with the following from your !_USER_SPECIFIED_PARAMS_FOR_ACRONIS.bat

:: ---Examples begin here----------------------------------------------------
:: option 1  set a trigger based on total number of .tib files in folder
::           0 means unlimited incr
::           1 means a new full every time (1 Full + 0 incr = 1)
::           2 means a new full after 1 incr is done (1 Full + 1 incr = 2)
::           3 means a new full after 2 incr is done (1 Full + 2 incr = 3)
::           The thought behind this control is the exposure risk of an incr chain is a
::           function of the chain length. Hence start a new chain when the length
::           of the chain exceeds some threshold. (or set 0 for manual control)
::           TRGR_ON_MAX_TIB_CNT=[0-N]   0=unlimited N=max_number of ".tib" files in chain
:: --User must set this next variable if the preceding option 1 is applicable--------------
   set         TRGR_ON_MAX_TIB_CNT=0
:: ---------------------------------------------------------------------------

Eric,
Perhaps it is I that am confused. I'll ask oracledba to look at this thread. It would certainly appear that a setting of 0 would enable you to have as many (but limited for safety's sake) as you wish until the next first Saturday occurs. As I am understanding your intentions, the only full backups you want is on the first Saturday and all others are to be incremental.

Regarding param TRGR_ON_MAX_TIB_CNT=0
The above setting is typical for most users because most users either want to manually trigger a new generation or want one triggered based on some weekly/monthly calander (such as 1st saturday of the month).

For example it is NOT reconmended that one use a value of "7" to mean weekly.
There are severals reasons why this is NOT reconmended the first being the assumption that your computer will be up 24x7x365 and never ever have crash or backup issues. The first time there is a PC crashes or otherwise doesn't do its backup then your "full" backup will no longer be on its usual day but will forever be a day late.
Another reason is you no longer have the ability to do adhoc-manual backups mid-day/mid-week because if you do a special backup then you are artificially increasing the .tib count and now your "full" backup will forever be a "day" early.

In the example above if you want a weekly backup then use something such as TRGR_ON_DAY1=Sat
Some people grow concerned that if the day their PC crashes IS Saturyday then a new chain would NOT be created until the following saturday.
A work-around solution is to use TRGR_ON_MAX_TIB_CNT=9 this would mean you can do upto two "special" ad-hoc backups without causing a new chain to occur. it would also mean that a new chain will occur every saturday but if for some reason the PC was off on saturday and the backup did not occur then on at least a few days later we WOULD get a new chain when the .tib count hit 9.

with regard to param MAX_BACKUP_GENERATIONS
:: MAX_BACKUP_GENERATIONS....... 0 means no history other than the current set (set0)
:: 1 means 1 generation beyond the current "set0" backup
:: 3 is a typical value but any positive integer will work.

if you start a new chain only on the 1st_sat of the month and you have MAX_BACKUP_GENERATIONS set to 4
that means eventually will will have FOUR months of HISTORICAL backups being retain as well as the current (set0) month chain.

in your example the MAX_BACKUP_GENERATIONS has nothing to do with how many saturdays are in a month.

I think the setting you want are:
set TARGET_UNC_N_DEVICE=\\NAS\AcronisImages
set TARGET_GENERATIONS_FOLDER=\i7\
set MAX_BACKUP_GENERATIONS=3 <----- THIS IS HOW MANY MONTHS OF BACKUPS YOU WISH TO RETAIN (ex recover a file as it looked 90 days ago)
set TRGR_ON_OCRDAY1=1st_Sat <----- FORCE a new full backup (new chain) on the first saturday of every month.
set TRGR_ON_MAX_TIB_CNT=33 <----- If for some reason the PC was down on the 1st saturday at least we start a new chain eventually (33 days).

hope this helps
let us know if you still have questions.

My PC is on 24 x 7 with a UPS to maintain it in case of a power failure.

Currently I do a data backup every night and then a different virus, malware, spyware, or other security scan to act on in the morning. On Saturdays no data backup and ATI makes an image.

The only time my PC is off is when I travel away from home for more than one night and then that may include the 1st Saturday of a month so your point is well taken.

However, this does not really bother me because I would not mind one set/generation covering more than one month. It would still be a valid set.

If TRGR_ON_MAX_TIB_CNT=0 and if that does mean "unlimited" then I can run as many manual images as I want AND if my PC is off on a 1st Saturday then the remainder of the month after the PC is turned back on will be in the current set0.

I believe this will produce the same result as your suggestion in post 16 to use TIB_CNT=33 with the benefit of allowing unlimited extra manual images

I always have the option to force a new set at any time by using the !_FORCE_NEW_CHAIN.bat.

I assume from your post that TRGR_ON_MAX_TIB_CNT=0 does mean unlimited. Agreed?

I do not understand your final suggestion to set TRGR_ON_MAX_TIB_CNT=33 as meaning 33 days since my schedule is weekly on Saturdays. I think you meant to suggest 15 to cover two months plus manuals.

Eric,
Random thoughts.

1. First off. Congratulations on your adapting to Chain2Gen. This discussion certainly points to its many excellent options to fit different needs. You know..."different strokes for different folks". The options can be a combinations of many different preferences.

2. In my extended use and testing of C2G, I had not used the TRGR_ON_MAX_TIB_CNT=0 feature. This is my fault for not being aware of this important feature. My apologies for the confusion. I do use C2G within several tasks which are directed to both internal and multiple external disks--which include the use of MudCrab's DriveNotify.

3. TRGR_ON_MAX_TIB_CNT=0 While a setting of zero offers unlimited number, there are many other possibilities. In your case, a zero setting would work with other digits possible. If you know that you rarely need to run manually. You could also use some other nominal setting so that if the system is not available on the first Saturday, the nominal setting would cause a new full to be triggered based on the number of files inside the set0 folder. So one set would be slightly smaller or larger than the others.

I too have a UPS and on 24/7 but for me, that is in theory only. Recently our power was off for 18 hours due a fallen tree across the roadway. Also, when there are advertised "severe thunderstorms" in our area, I make it a practice of turning off my computer and removing the power cable of the UPS from the wall. If I get hit by a power surge, I don't want to add the expense of my computer equipment to added to the loss. Thus, I say 24/7 for me is desirable but is not always the norm.

4. While the number of incremental is unlimited, the practicality of this stretches the safety limit of the backup chain. If you have many incremental, it is impossible to predict which might become corrupt but if one does, then any subsequent incrementals are useless. So I make it a practice of limiting my incementals--but who is to say how many is too many.

5. Hopefully, when you create you weekly image, it is an disk & partition image which includes all partitions (both hidden and diagnostic). This type image offers the best chance for recovery to a replacement or larger disk. This is not to say every backup has to be of that type (all partitions) it is prudent to always have such a backup available--just in case.

6. When restoring the system partition or to a new disk, this is best done when booted from the bootable TI Rescue/Recovery media. Thus this certainly implies that the backup images (*.tif) should be validated when booted from the TI Rescue/Recovery media. While it may not be practical to validate all from the bootable media (validation is done within Windows automatically as part of the backup), it does mean that this is done occasionally so you have faith that when a restore is needed, the restore file will be readable.

7. I have my risk spread by having backups stored on multiple internal and external disks. So if one of the backup storage devices does not work, I have other options.

I was not at home last weekend but left my PC running.

ATI completed its image in set0 on Saturday morning.

On Monday I attempted to run a manual image using the same task by "double clicking" it. It "hung" at the point of trying to run the "before" batch command. The task window showed that the task attempted to run the batch but nothing happened.

I then "cloned" the task, unscheduled the clone, and renamed it. Using "right click - start" it ran and produced an incremental image in set0.

My disk is 1TB with only two partitions (C & D) which I include in the backup task. This is a Dell PC and I have now removed the Dell recover partition since ATI provides that service which does NOT then revert back to the "as received" condition. I did experience an "impending failure" warning several months after getting the PC last year. It was a PITA to have their service rep bring the free replacement exchange disk, have the rep go thru the install process, and then after he left to impress the ATI image I had made the day before from the still functioning disk. Dell gives the choice so I should have had them deliver the replacement disk for me to install. Since the original disk still worked I could have installed the new disk as secondary and used ATI to impress an image, remove the old disk for return and been back up in several less hours time.

No errors were generated during the two images so the original question of this post about "changing the default reply to error messages" is still open.

Thanks for all of your help and suggestions. This case is closed unless an error occurs.