[Windows 7 x64 SP1] - Upgrade from ABR Standalone Workstation 10 to 11 - Horrible Experience; Reverted to ABR10
* In-place upgrade of ABR10 Build 13544 successful, but destroys all pre-existing Backup Plans and Tasks.
* Recreated backup plans and tasks reproducibly choke at 4% completion:
Failed to connect to the process.
Additional info:
--------------------
Error code: 11
Module: 300
LineInfo: 2a463402369021a1
Fields: $module : E:\Program Files (x86)\Acronis\BackupAndRecovery\mms.exe
Message: Failed to connect to the process.
--------------------
Error code: 12
Module: 300
LineInfo: 2a463402369021a2
Fields:
Message: The operation has timed out.
--------------------
* Complete uninstall of ABR11 from Control Panel. Reinstall of ABR11 successful. Reinstall does not help.
* Scrub the environment with abr_cleanup; reboot. Perform clean install of ABR11 into the default locations.
* Reconstructed backup plans and tasks likewise fail at 4% completion:
Failed to connect to the process.
Additional info:
--------------------
Error code: 11
Module: 300
LineInfo: 2a463402369021a1
Fields: $module : C:\Program Files (x86)\Acronis\BackupAndRecovery\mms.exe
Message: Failed to connect to the process.
--------------------
Error code: 12
Module: 300
LineInfo: 2a463402369021a2
Fields:
Message: The operation has timed out.
--------------------
* Completely uninstall ABR11 from Control Panel; scrub environment with abr_clean. Clean install of ABR10. Reconstructed backup plans and tasks work fine.
* Management Console GUI has always been lethargic, but in 11 seems to have regressed even further to the point of being simply dreadful. Interminable "Loading..." pauses for every instance of a repetitive task. This is for a single local console managing a single local machine with locally-attached disks. For the record, the system being managed has a quad-core CPU with 16GB RAM.
* The initialization of the Management Server Service, always flaky and slow, seems to have become even more erratic and lethargic. This makes any Windows PE-based recovery medium problematic to use, as the initialization script will always error out, and has to be manually re-launched at the command-line.
It is not my occupation to test backup software; I just use it to protect myself against occasionally breaking things in virtualized test environments. *That* is my real job. Therefore I am really not very motivated to pursue the matter further or to even submit a support case, to be quite honest.

- Log in to post comments

@ both posters,
Do you also have Acronis Disk Director installed or TIH Online Backup?
Did you install for all users or just a single logon?
If you are getting a message about the meta directory, this might indicate that not all of ABR10's components have been uninstalled as ABR11 uses a different database method.
Did a catalogue folder appear in your image directory?
- Log in to post comments

Do you also have Acronis Disk Director installed or TIH Online Backup?
No.
Did you install for all users or just a single logon?
Single logon.
Did a catalogue folder appear in your image directory?
Yes.
Even after deleting all .meta-folders i got this warnings. But for now i cannot reproduce the warnings because i setup ABR11 from scratch and deleted all existing backups. Today i had no more such warnings.
Forellenblau
- Log in to post comments

We're not going to so much as think about rolling out ABR11 until the longer of the release of the first update or six months, and maybe not even then. It's just not prudent in an environment where backup is mission-critical.
- Log in to post comments

Likewise no to Disk Director and TIH Online Backup.
The squeaky-clean install was performed by accepting all defaults; I'm sure the standard installation defaults to "Install for all users of this machine":
MSI (c) (FC:9C) [18:47:36:770]: ******* RunEngine:
******* Product: C:\Temp\668AA0E2-11B3-4EC9-AF91-F29E41ED968B\AcronisAgentCore.msi
******* Action:
******* CommandLine: REBOOT=ReallySuppress ENABLE_COMMON_ERRORS="1" ADDLOCAL=ALL BOOTSTRAP_EXE="C:\Temp\ABR11S.17217_en-US.exe" TARGETDIR="C:\Program Files (x86)\Acronis\BackupAndRecovery" ALLUSERS=2 CREATE_NEW_ACCOUNT="1" ACEP_AGREEMENT="1"
I *really* scrubbed repeatedly with abr_cleanup so I'm reasonably sure no residual ABR10 components were present.
There were no specific errors pertaining to meta-data, but to be honest I'm not sure about the .meta and Catalog folders in the image archive. I did try creating a clean Personal Vault as well. Before I sort of threw in the towel. I *really* just needed to back up ;-)
- Log in to post comments

Robert,
Which 64bit OS are you using?
Do you have VSS enabled or are you using the Acronis equivalent?
Is this being imaged over a network or to a local drive (internal or external)?
Are you connecting via local or remote machine at the console?
What components of ABR11 did you install?
- Log in to post comments

* Windows 7 x64 SP1 Ultimate
* I always use the Acronis SnapAPI provider (snapman.sys), rather than the native Microsoft VSS volume shadow-copy provider
* Backup source: local internal drive; Backup destination: local external drive (IEEE-1394 interface; non-removable medium)
* Stand-alone management console run on, and from, the local system being backed up
* AcronisAgentCore, AcronisAgentWindows, AcronisBootableComponentsMediaBuilder, AcronisCommandLineTool, AcronisStandaloneManagementConsole, AcronisTrayMonitor, and AcronisUniversalRestore; all successfully installed
Thanks for your interest. It is appeciated. Mine obviously cannot be a widespread problem. I really do intend to try again, though maybe not until the holiday weekend.
- Log in to post comments

Robert,
I'm wondering about the Firewire drive, I don't think any of the beta testers tried this interface to test for any problems and that jumps out at me as one difference to for example my setup.
Do you have a USB drive that could be tested or maybe an separate partition on an internal drive?
- Log in to post comments

You got that right.
Another Acronis botched release.
Wish they never, never had the damn License Server.
The more complicated the product the more problems.
I've tried the upgrade but fortunately made a backup of the system before installing. Had to go back to 10 to get things working.
As time goes by Acronis is more and more like Symantec.
- Log in to post comments

I'm sorry for picking up such an old thread, but I waited three months before tempting fate again, by upgrading ABR10 to ABR11 a second time (this time, build 11.0.17318). This time, I have no complaints whatsover.
* My backup jobs were actually converted
* My backup jobs actually ran
* Same hardware, same OS, same external backup device, using same IEEE-1394 interface
In other words, my expectations were never unreasonable.
These are the things ABR11 RTM had absolutely no business being released not being able to do.
- Log in to post comments