Build 6597 another FLOP
YANA,
Very thanks for your interest!!!
I really appreciated that Acronis is interested in the problems of small consumers of its software.
I'll wait the answer of your Support.
Thanks!!!
YANA,
Very thanks for your interest!!!
I really appreciated that Acronis is interested in the problems of small consumers of its software.
I'll wait the answer of your Support.
Thanks!!!
.
YANA,
Very thanks for your interest!!!
I really appreciated that Acronis is interested in the problems of small consumers of its software.
I'll wait the answer of your Support.
Thanks!!!
.
@Charles Jutkins
Fwiw, all my network drives are always on all of the time so this is not my issue. My network situation may be a little more complicated? I have protected NAS shares which can only be accessed by specific users. I'm jumping out on a limb here, but I'm wondering if ATI might be trying to access these protected shares which it has no business trying to access or something?
I started playing with the program this morning and I am encountering additional problems. Its very slow to go to the main screen when selected and when I select Disk and Partition back up it does not show a location in the destination window and when I try to select it the screen goes light and it locks up. It seems to work with the existing backups jobs that were already generated in the othere versions . By the way how do you do and Incremental or Differential backup I see no way to select it.
You have to select "Disk Backup Options" (lower left) then "Backup Scheme" tab, then in the drop-down below it, pick the "Custom Scheme" option. Not real intuitive.
The main screen can take some time to completely present. I think in my case its because the backup destination for some of the backup jobs is an external NAS device, and it needs to wake the NAS up and power on the disks (It's sleeping most of the time), verify the destinations are available, then update the main screen. It's kind of strange it does it this way.
Had the printer on in the last problem even that is a network drive as its on the router attached to the ethernet.
Well its been a couple of weeks has there been any fix issued by Acronis for the network problem?
Not that I'm aware of. They will usually post a "Sticky" thread at the top of the ATIH forum if a new version update is released. With the large number of problems / issues users are having with ATIH 2011, I don't expect anything soon. The last build came out pretty quick when users were having issues upgrading / applying the update then having to reenter software keys. Unfortunately it broke other things that were working in the previous public build. So when another build gets posted as another update, it better be a significant improvement or folks will be heading off for other solutions if they haven't already.
Hi all!
Thank you for your comments.
Dear Gork, your concern is entirely understandable, and I agree with you. Still I can assure you that Acronis is not that reach to reject PPI refund in case of a technical issue in the product. It's important for us to honest with the Customers, as we work for you. Thus in case there's really a bug, we refund money without a question.
Still I completely understand your mistrust. At the very least we should have earned it with the stability of the product.
I've also forwarded your comment to the Management team. You're right that a Customer shouldn't spend money on reporting technical issue in the product. You comment has been taken under consideration, and Managers will look into the possibility of changing that system (though I cannot promise you that it will be changed soon).
Dear Charles, the incremental or differential backup can be created by going to Main Screen -> Disk and Partition (or Data) Backup -> Backup Scheme, change there the Version Chain to Custom and select in the new drop down menu between full, incremental or differential backup.
Back to the issue itself
I've got some good news:
Our Development team reported that they have fixed the issue, and the fix is included into the upcoming update. We don't have any ETA, but we believe that it will be out shortly, as it's currently passing the final stage of verification in the Tester's lab.
Please let us know if you have any questions, I'll be glad to address them.
Thank you.
@Yana
Thank you for your kind words, and your acknowledgement of the issues I have with the reporting process. Just to be clear, it isn't so much a "trust" issue as an issue with the subjective nature of what a bug is vs customer support. I say subjective because what I might consider a bug, Acronis may consider support - and the decision is one-sided because only one side makes the determination on which it is. I guess with a better rapport with the company "trust" could alleviate the "one-sided subjective nature" of the issue however.
Please let us know if you have any questions, I'll be glad to address them.
I posted this in the other thread, but I do have one question, as a user who has tried to do what he can to help with regard to these issues. Is it possible for you to give us a small description as to what the developers have found to be the issue and what the current plan for a resolution is? I don't ask because I want to police Acronis' efforts, but because I genuinely want to know.
Thanks, YANA...
Perhaps a bit premature, but can you share a list of expected "fixes" that are targeted for this upcoming release? I know you'll have a release notes file that documents what's actually in the released build, but it would be nice to know what is currently targeted to be in it since there have been so many issues discussed in this forum.
Jim
Build 6696 of TI 2011 has just been released. I have successfully backed up and restored from an external esata drive. I have also built the Rescue media , which I have successfully used. It also appears to br a little faster in some areas than build 6597,
I use a desktop with Win 7 64 and 8G of memory
Excellent. Thanks for the heads up.... Looks like I'll be digging into it this weekend. There are a number of things I'm looking to see if they've addressed in this build.