Aller au contenu principal

Work around for 'Sector 63' issue

Thread needs solution

As I'm sure plenty of you are aware True Image Echo and Server 2008 x64 don't work well together when you introduce an external hard drive. We've had several customers effected by this issue and it seems that nothing resolved the problem.

I spent some time on this during the week and found a workable solution for my customers. Almost all of our customers servers utilise an internal drive as a destination for the TI archives, then sync the archives to the external drive for off-site storage. So, quite simple I've written a script that disables the external USB drive(s) prior to TI running it's backup task.

The script consists of two calls using devcon.exe (a x64 version that works with server 2008 is available in the Windows XP x64 support tools, this isn't available from the Microsoft site for some reason) to disable both the USBSTOR drive device and the USB mass storage device. I schedule the script to run a few minutes before TI, then add a post-backup script to the task which enables them again... problem solved. The basis of the script can be found here.

Of course, if the external drive is the destination for your archive this doesn't work. However, you may be able to call the enable script during the pre-backup script. I haven't tested this idea, just thinking out loud.

Apologies if this has come up before, I hope it helps someone.

0 Users found this helpful

Hello Omnivision,

Thank you for choosing Acronis Enterprise Software.

We would like to thank you for sharing this script and solution with us, I will forward it to our Experts Team for review.

Thank you for your cooperation!

Wow. 2008 Server came out in let me see ... 2008. I reported the problem in ... 2008. Everyone is up in arms about it and here it is ... end of 2009. Instead of finding a work around why don't you address the issue and fix the problem? I know why.... your too busy addressing the issues with the worst product know to man.... ABR10! Your support is a joke!

Oh ... and BTW the problem also exists with Winows 2003 Server 32-bit. Not that you care or will do anything about it...

Well ... I have had the same problem on and off for years. I have started a new thread on it if anyone is interested. Upgrading the the lastest build of Echo Server did not do the trick. Here is the link if anyone is interested.

http://forum.acronis.com/forum/7026