Aller au contenu principal

True Image 2010 & RAID

Thread needs solution

True Image 2010 corrupted my RAID 1 volume while creating an image backup. AMAZING!!!

Just downloaded latest release 2010.7046 and installed the PlusPak which was not installed before.

Will this new build non-destructivly image backup a RAID 1 volume?

What's up here Aconis? Where are you? This should be a very hot topic with a very visable solution.

Tnx,
Richard

0 Users found this helpful

Hello, Richard.
Could you send the Acronis System Report that are required for further investigation. Do we have a softaware RAID configuration or HW one?

This is a Dell T3400 with hardware raid using the Intel Matrix Manager for W7.

Each time I have tried to create an image of the raid volume, the system hangs within a few seconds of running and I must force a shutdown.

Upon reboot, Intel Matrix Manager reports my raid volume is damaged and spends 2-4 hours reverifying the volume.

Fichier attaché Taille
26454-88336.zip 1.5 Mo

Hello, Richard.
According to the info you provided you are still using the old build of ATI Home 2010 (build 6053). Am I right?

When I had the proplem, yes. I loaded the 7046 build yesterday and backup of the raid volume went ok.

You guys need to publicly announce there is an issue with the 6053 build and raid. It would have wiped me out if I had a less robust raid system.

Richard I use 25 Precision workstations at work; 380, 490, T3400, T3500 and T5500's and many of them have raid one or zero setups. On the ones with Raid 0 if I force a reboot for any reason not just an Acronis issue the machine takes about 5-7 minutes to boot and reports it is rebuilding the array due to corruption once it finally boots up.
That said I'm fairly sure its the non battery backed up raid controllers that the Precisions use for raid that is causing your curruption issues. Interestingly if said Precisions are in Raid 0 they do not exibit this behavior and do not currupt. You would expect the Raid 0 configuration to be less reliable in the case of a hard reboot but they work fine.