Strange Copy Problem
I have Version 2011 and create a partition backup on my notebook. Then I copy this file to my desktop computer. There I can click on it and it opens. But when I make a validation on the desktop it says backup is corrupted. Then I copy this corrupted backup back to my notebook and make there a validation again and there is no problem.
So I am not able to create a backup of the backup-file (Explorer is used for this)?
The major difference of both systems is that the desktop computer runs with RAID 0. The OS and the Acronis versions are on both systems exactly the same - Win 7 32.
- Accedi per poter commentare
Thank you for your response. The problem is more complex - even the CRC of the files is the same but they still are different for Acronis. This copy problem happens sometimes. But the following happens always:
I have a backup on the notebook and access it using the network with my desktop PC. I can click on this backup file on the notebook and open it with the desktop PC. I can even mount it on the desktop PC. But I cannot validate it on the desktop PC. I would say this is an Acronis bug.
- Accedi per poter commentare
You may find these of interest. The validation of a backup can be very hardware intensive.
You may also wish to use a free program such as "Replicator" to copy the file from one location to another and to make sure the copy is not trashed.
http://kb.acronis.com/content/1517
- Accedi per poter commentare
Thank you all very much for your support. It helps my to understand that I was too self confident when I used Acronis. From my point of view Acronis does not like networks or USB connections - for whatever reason. The CRC of the files are the same on both computers and both computers are top of the line and checked with the hardest stress tests.
I have very many TB of data that I move around over USB and networks. And I have learned before from bad experience to check every new device for CRC errors when moving around data - there is really bad HW possible. Only problem left is with the validation of Acronis. I have been using Acronis for very many years now and with very slow computers (but still state of the art then) and with USB and networks. I never ever had a problem like this before. Something must be very special when Acronis tries to access media on external units. I guess only a debug would find out what creates the problems. But I am warned now.
Because of this my new procedure is to create a backup with validation. Copy it to the external drive - no need to validate there since it might not work anyway. Then copy it back to the source computer and validate again. A little bit time consuming in the long run and still no guarantee that the backup might work on a new computer if the original source computer dies. Recently the 750 GB harddisk of my notebook died within minutes and only some of the backups on my deskop PC for it worked in the end. A very bad experience. And the very strange thing - one backup was copied from the notebook to the desktop PC. From there it was copied to the backup disks of the desktop PC and to two external USB drives in addition. Now guess which of the many backup files worked - again it was the same file. Only the one that went from the notebook to the desktop PC and then to the backup disks of the desktop PC. Honestly this does not make sense to me anymore. And all had the same CRC. I know this is hard to believe and sounds crazy. And I am not talking about validation problems. I could not even open the backups when I clicked on them. I know it is hard to believe.
But again - thank you. We cannot debug the software to find the exact reason for the problem and Acronis does not have my computer setup. Only special thing on my desktop is a 3x1TB disk INTEL-RAID 0. But this is the most stable disk setup I had in more than 40 years IT experience. A chkdsk for instance there is simply a waste of time. There was never ever a problem even if you switch off the power when it runs. Only Acronis created bad sectors at every restore for a while - but this got fixed then and works in version 2011.
- Accedi per poter commentare