Frustrated - Backup Deleted For No Reason - Resolved
I have set up 2 separate tasks to backup my boot drive (about 250GB)
Backup 1 is called 1_C_ON_X and runs every day at 5:00AM. It is set for incremental backup with new full backup after 5 increments and with 650GB size limit to a local drive.
Backup 2 is called 3_C_ON_NAS and runs every Saturday at 3:00AM. It is set for incremental with new full backups after 12 increments reatining no more than 2 full backups on an external NAS drive.
Backup 1 seems to be working normally and the last full backup file was named 1_C_ON_X_full_b3_s1_v1.
I created a new Backup 2 on Sunday expecting it to increment the next Saturday. The file it created was 3_C_ON_NAS_full_b3_s1_v1. I thought it was strange that it started at b3 instead of b1. When I checked today (Wednesday), this backup had been deleted when Backup 1 executed and created 1_C_ON_X_full_b4_s1_v1. Backup 1 had incremented to b4 but deleted the b3 version of Backup 2.
To me it looks like it is confounding the two backups regarding the size limitation. Before I created Backup 2, Backup 1 showed a size of about 260 GB with a few increments. After I created Backup 2 it showed no size, but Backup 1 now showed over 500GB. I think it deleted Backup 2 thinking it was a part of the Backup 1 chain.
I loved Trueimage Home 2010 with its task manager and log files. It will run in Windows 10 if it was installed before upgrading to W10, but won't install after the upgrade.
I've had nothing but trouble with Acronis 2015. Is 2017 any better?
Dan
Steve,
Thank you for your reply. Yes the two backups are on different drives. Backup 1 is on X: (local). Backup 2 is on a networked NAS drive. As you can see by the log excerpt from Wednesday morning, Backup 1 completed normally on X:. It then went to consolodate the backup but deleted Backup 2 on Cloud (NAS). Backup 2 (3_C_ON_CLOUD_full_b3_s1_v1.tib) was created earlier in the week and had no incremnents associated with it. I'm thinking the that somehow the file size of Backup 2 was included in the consolodation limit for Backup 1 (set for 650 GB). The total size for Backup 1 and 2 would have been about 760 GB. (I'm not sure what the error code is but I see it in all the log files.)
I had had a similar problem before where the backups seem to get confounded. I had named the tasks "C ON X" and "C ON CLOUD" Thinking that maybe the naming was confusing to ATI (both starting with "C ON"). I changed the task names to start with numbers and used underscores. I have another weekly backup that images a different drive to the NAS and it operates normally.
Any suggestions? Wipe and reinstall?
Thanks,
-Danny
*Log Excerpt*
message=The following backups have been successfully created: X:\Backup\Sandisk\1_CDRIVE ON X_full_b5_s1_v1.tib
id=53; level=2; module=485; code=14; date/time=10/12/2016 6:10:29 AM
message=Consolidate Backup Archive Location: X:\Backup\Sandisk\1_CDRIVE ON X_full_b5_s1_v1.tib Destination: X:\Backup\Sandisk\1_CDRIVE ON X_full_b5_s1_v1_6DE17C26-F99D-479E-B9BA-66B758DB6335.tib
Error_Code=AQ4A5QHERaELzE1bbTxib2xkPkNvbnNvbGlkYXRlIEJhY2t1cCBBcmNoaXZlPC9ib2xkPjxlbmRsLz48dGFicG9pbnQgdmFsdWU9MzA+PGluZGVudCB2YWx1ZT00PkxvY2F0aW9uOgk8aW5kZW50IHZhbHVlPTEwPjx0ZXh0Y29sb3IgdmFsdWU9Im5hdnlibHVlIj4iWDpcQmFja3VwXFNhbmRpc2tcMV9DRFJJVkUgT04gWF9mdWxsX2I1X3MxX3YxLnRpYiI8L3RleHRjb2xvcj48L2luZGVudD48aW5kZW50IHZhbHVlPTQ+PGVuZGwvPkRlc3RpbmF0aW9uOgk8aW5kZW50IHZhbHVlPTEwPjx0ZXh0Y29sb3IgdmFsdWU9Im5hdnlibHVlIj4iWDpcQmFja3VwXFNhbmRpc2tcMV9DRFJJVkUgT04gWF9mdWxsX2I1X3MxX3YxXzZERTE3QzI2LUY5OUQtNDc5RS1COUJBLTY2Qjc1OERCNjMzNS50aWIiPC90ZXh0Y29sb3I+PC9pbmRlbnQ+PGluZGVudCB2YWx1ZT00PjxlbmRsLz48L2luZGVudD48ZW5kbC8+ACRtb2R1bGUAV0M6XFByb2dyYW0gRmlsZXMgKHg4NilcQ29tbW9uIEZpbGVzXEFjcm9uaXNcVHJ1ZUltYWdlSG9tZVxUcnVlSW1hZ2VIb21lU2VydmljZS5leGUAAAcECwDERaELzE1bbTxib2xkPkNvbnNvbGlkYXRlIEJhY2t1cCBBcmNoaXZlPC9ib2xkPjxlbmRsLz48dGFicG9pbnQgdmFsdWU9MzA+PGluZGVudCB2YWx1ZT00PkxvY2F0aW9uOgk8aW5kZW50IHZhbHVlPTEwPjx0ZXh0Y29sb3IgdmFsdWU9Im5hdnlibHVlIj4iWDpcQmFja3VwXFNhbmRpc2tcMV9DRFJJVkUgT04gWF9mdWxsX2I1X3MxX3YxLnRpYiI8L3RleHRjb2xvcj48L2luZGVudD48aW5kZW50IHZhbHVlPTQ+PGVuZGwvPkRlc3RpbmF0aW9uOgk8aW5kZW50IHZhbHVlPTEwPjx0ZXh0Y29sb3IgdmFsdWU9Im5hdnlibHVlIj4iWDpcQmFja3VwXFNhbmRpc2tcMV9DRFJJVkUgT04gWF9mdWxsX2I1X3MxX3YxXzZERTE3QzI2LUY5OUQtNDc5RS1COUJBLTY2Qjc1OERCNjMzNS50aWIiPC90ZXh0Y29sb3I+PC9pbmRlbnQ+PGluZGVudCB2YWx1ZT00PjxlbmRsLz48L2luZGVudD48ZW5kbC8+AAA=
id=54; level=2; module=11; code=1031; date/time=10/12/2016 6:10:29 AM
message=Consolidate Backup Archive Location: X:\Backup\Sandisk\1_CDRIVE ON X_full_b5_s1_v1.tib Destination: X:\Backup\Sandisk\1_CDRIVE ON X_full_b5_s1_v1_6DE17C26-F99D-479E-B9BA-66B758DB6335.tib
id=55; level=2; module=11; code=0; date/time=10/12/2016 6:10:29 AM
message=Deleting backup file with path \\CYBERZONECLOUD\Backups\Danny\3_C_ON_CLOUD_full_b3_s1_v1.tib.
id=56; level=1; module=8; code=0; date/time=10/12/2016 6:11:14 AM
message=ServerLRPC::_CloseConnection id=16,368
id=57; level=1; module=8; code=0; date/time=10/12/2016 6:11:14 AM
message=ServerLRPC::_CloseConnection id=11,296
id=58; level=1; module=8; code=0; date/time=10/12/2016 6:11:14 AM
message=ServerLRPC::_CloseConnection id=16,368
id=59; level=1; module=8; code=0; date/time=10/12/2016 6:11:14 AM
message=ServerLRPC::_CloseConnection id=11,296
id=60; level=2; module=316; code=6; date/time=10/12/2016 6:11:14 AM
message=Operation has succeeded.
Start= 10/12/2016 5:00:02 AM
Finish= 10/12/2016 6:11:14 AM
Total Time= 01:11:12
Have you ever had your NAS backup mapped as the X: drive in Windows before?
To be on the safe side, I would run schedule manager and run taskzap to clear any ghost scripts. I'd probably go ahead and run the cleanup tool (use these instructions to make sure it gets everything after using taskzap). and start "fresh" too - to try and avoid this ever happening again - never seen this behavior, but since you have it, no sense in waiting for it to come back again (if it does).
My last recommednation would be to avoid setting the file size limit as that may be the ultimate culprit. Perhaps it is reading the total limit of all backups and someone consolidating the wrong one in the process. I tend to set a consolidation job in each task based on # of version chains since they tend to be fairly easy to calculate the size of a a chain if they tend to be about the same size (give or take some normal growth).
You can keep the existing old backups, but when you start with new tasks this time, make sure to give them different names again (just in case). Use _B, _C or somethign along those lines if you want to keep a similar name, but differentiate the difference with the new ones. Try to make sure that each backup lives in it's own folder too... for me, I have one main backup location folder, and a new folder for each backup script in it. That way, they're all easy to get to, organized, and not in the exact same location (paranoia of Acronis somehow reading the other files in the same folder and doing something with or to them instead of the intended backup).
Thanks for your reply. The NAS has never been drive X:, it's always been mapped as drive Y:. The local backup resides in it's own folder with no other backups. My previous scheme was no more than 2 full images with 30 incremental versions (with no size limitation) which fits nicely on X:, a 1TB drive. A lot of increments I know, but it gives me at least 30 days of images. This works fine until Windows 10 decides to download some superpatch that causes one of the increments to be 200GB or more in size. Acronis really hates it when you run out of room on the drive.
This happened after the anniversary update (and a few times before). When it happened I tried to cancel the operation because it was stuck for lack of drive space. ATI 2015 would not cancel, just the spinning circle for more than an hour. When I killed the program and rebooted, the task name disappeared in the list, it was just blank. (Really buggy behavior for such a refined program). This prompted me to set up the size limit so it could take care of large increments.
The schedule manager is showing about 25 tasks numbered up to 1-54. I only have 3 tasks set up so I don't know if it keeps a record of all the previous tasks I was experimenting with. (See below). I will certainly try your suggestions when I get some time this weekend.
Thanks,
Danny
inst=den start=yes loc task=0-0 > get list
Id ExecApp ExecCmd
--- ---------------
CurUser 1 (Danny-Windows7\Danny):
1-1 *Activator* /script:304012CD-7BE2-4B63-8137-37EFE7DA0ACF /MMS
1-3 *Activator* /script:2C0D27B9-54A3-4C8E-80FF-50400BD05A33 /MMS
1-7 *Activator* /script:B00E2773-8E6F-48FE-899F-6412266C3397 /MMS
1-10 *Activator* /script:0EF2F1FC-45FE-4F39-A392-598B070B0281 /MMS
1-11 *Activator* /script:98F50C98-105A-4455-94CB-F6CE543FB7AD /MMS
1-12 *Activator* /script:18A3181B-C70B-414A-9D99-B18D1A551589 /MMS
1-13 *Activator* /script:B6FD1F58-3785-463C-BE69-918AA3930D90 /MMS
1-14 *Activator* /script:804DED15-2EAF-4124-A95E-D6705354CA4D /MMS
1-15 *Activator* /script:8F3AEFAB-05AC-412D-AC7D-6D8B9EF7F4E9 /MMS
1-16 *Activator* /script:5F8B9007-7212-43A1-9D26-D55024599B15 /MMS
1-17 *Activator* /script:C3873C7E-1651-4E31-9591-A9BD5B76DF6B /MMS
1-18 *Activator* /script:16E9DC97-9A61-4ECA-9998-9F61EAEB7889 /MMS
1-19 *Activator* /script:F5CD59DD-4065-4C8E-AF43-2EFB305A92FB /MMS
1-20 *Activator* /script:231D5D69-1FED-4BD0-88EF-C8B8A98BD15B /MMS
1-21 *Activator* /script:478E274C-4B62-456C-B620-15F2773B254A /MMS
1-22 *Activator* /script:31F2BE3D-2652-471D-8955-734B48B18144 /MMS
1-29 *TrueImageHomeNotify* /dummy /script:"847D13E4-940C-41B3-B757-A49EBCCB03CD" /uuid:"847D13E4-940C-41B3-B757-A49EBCCB03CD" /temp
1-30 *TrueImageHomeNotify* /dummy /script:"9AAF7CFC-46F8-4BBC-BF39-F1CA20D34DD9" /uuid:"9AAF7CFC-46F8-4BBC-BF39-F1CA20D34DD9" /temp
1-31 *TrueImageHomeNotify* /dummy /script:"4F56D6C0-35AA-489B-97F4-ADD1518AA1F2" /uuid:"4F56D6C0-35AA-489B-97F4-ADD1518AA1F2" /temp
1-37 ~*TrueImageHomeNotify* /dummy /script:"5C97543C-AF44-4AAC-838F-BD8675AD4801" /uuid:"5C97543C-AF44-4AAC-838F-BD8675AD4801" /run_mode:?RunMode?
1-44 *TrueImageHomeNotify* /dummy /script:"CDC834FA-18F3-405A-B58D-25DFB7E44F56" /uuid:"CDC834FA-18F3-405A-B58D-25DFB7E44F56" /temp
1-46 *TrueImageHomeNotify* /dummy /script:"06A3A692-B066-4AC4-9449-F472DAEAE47B" /uuid:"06A3A692-B066-4AC4-9449-F472DAEAE47B" /temp
1-50 ~*TrueImageHomeNotify* /dummy /script:"447209B9-D346-43E6-A918-BFD432254EC1" /uuid:"447209B9-D346-43E6-A918-BFD432254EC1" /run_mode:?RunMode?
1-53 C:\Program Files (x86)\Acronis\TrueImageHome\TrueImageMonitor.exe /shutup
1-54 ~*TrueImageHomeNotify* /dummy /script:"14CC238E-A6AC-452F-B53B-EC298195E368" /uuid:"14CC238E-A6AC-452F-B53B-EC298195E368" /run_mode:?RunMode?
inst=den start=yes loc task=0-0 >
Danny, thanks for the further information.
I would suggest doing a task zap to clear out the long list of scheduled tasks you found via the scheduler manager.
After than, the problem suggests that the Acronis Database has been corrupted given the mix up with two separate tasks, so I would suggest renaming the C:\ProgramData\Acronis\TrueImageHome\Database folder to Database.OLD to force a rebuild of the database information. You will need to stop all Acronis services and programs in order to do the rename. The database will be rebuild when you restart ATIH and run you backup tasks.
Steve,
I followed your procedure and everything seems to be working normally now. The task zap cleared all the schedules and I renamed the database file. Then I deleted all the tasks in the ATIH UI and re added the backups from the files and rescheduled them. I left the 650 GB consolodation limit on the daily backup to local drive but haven't seen the consolodtion yet since the size limit has not been reached. I won't be totally sure everything works until it tries to consolodate sometime this week or next.
I appreciate the time and effort you and Bobbo put into helping all of us folks who have a love/hate relationship with this software! If the consolodation works properly I'll mark the issue solved. If not, I will follow Bobbo's scorched earth advice and start over from scratch.
Thanks again,
Danny Milla
Good deal - hope all is well now. Scorched Earth isn't much more than what you've had to go through already - it just helps clear out any other install anomolies that may still exist, but hopefully the steps you went through will have sorted things out :)
Thanks Steve and Bobbo,
After two weeks all my backups are working properly. The 650GB cpnsolodation is working fine now on my local drive and my two NAS weekly backups are chugging along!
Excellent! Hopefully it's smooth sailing from now on.