Aller au contenu principal

Hey Acronis! Are you ever going to address thread 3010? Your support is so sad :(

Thread needs solution

Nice going Acronis. You have a major, major flaw in your ABR 10 and your are totally ignoring it! It makes ABR 10 a total waste! A boat anchor! Tech support has been instructed to totally ignore the problem. Are you ever going to address thread 3010? Of course not!

For thouse of you who don't know ABR 10 will not let you overwrite a previous backup because it won't let you explicitly name a backup image. Nice going on Acronis's part huh? Then they don't respond to the issue. They totally ognor it! Nice company!

0 Users found this helpful

Still waiting ...

It is amazing! I have been in chat with them several times and as soon as I mention the flaw or ask them when they are going to fix it they immediately duck the issue. Their first response is "well ... try these work arounds..". I cut them short and tell them their work arounds don't work and ask them to focus and respond to the specfic question. They say they can't tell me where the overwrite issue stands. They duck or ignore the issue completely.

I have a bad feeling about this one. It obviously isn't a simple fix and might require a major re-write of the program. I think they know it is a major issue and I think their sales have suffered greatly because of it. They haven't figured out yet that comming clean and talking straight about it to their resellers and customers is the best approach. They are "shady characters" all the way around and their support is absolutly non-existant. This could be the downfall of Acronis ...

Still waiting on your response Acronis ...

Still waiting on your response Acronis ...

Acronis isn't commenting. To make a sad, sad story even worse a couple of weeks ago (and I think this is mentioned above) I sad down and created a batch file to delete everything on the USB hard drive. It worked fine from withing Windows. I put it as a pre-job command in ABR10 and if failed with a Invalid Parameter error.

This would have solved the problem with the overwrite but .... today I chatted with them about this error. I was told that yep .. that is a know problem with the latest release. Pre-job commands don't work. I am not worried though because .... the tech told me it would be fixed in the next release :) Whew. They had me worried for a minute ... :) Lies, lies, lies...

Quote:
1) Does Acronis consider this to be a problem or issue?
2) If Acronis does conside this to be an issue do you intend to fix it?

Forgive me Alexander but there is a common issue with the naming convention. It does not need to be handled in a individual case. The common issue is that you have no control over the image archive name. I am just amazed. The above two questions have been unanswered for months and months. Thread after thread. Two very simple questions that Acronis has yet to address. After all the replies from Acronis. They have danced, ducked, weaved and bobed but have yet to address the above two question. Absolutely amazing ...

Hello Jim,

thank you for opening the separate thread for backup naming question.

I would like to notify you that from now on we store all the information concerning the backup naming question in the following thread, so please kindly refer to this one.

Other threads regarding the same theme will be merged to the specified topic for more convenient access to the customers' suggestions, complaints and ideas.

Thank you.