Well I recently spent a weekend on the phone with Symantec Support working through the same error message that Astoundry said was having. I was migrating a server from old hardware to new hardware and every option that Symantec had me attempt continued to give the error @ 99%: "cluster beyond end" EA3905F3. We tried every different option of restore, attempted to convert my BESR image to VMDK which worked and meant the BESR image was good, and I even took a whole new image from the source. The one issue that seemed to stick out that Symantec was insistent on, was some issue with partitions on the original server. One difference b/t the servers was a larger sized drive on the old hardware compared to a slightly smaller drive on the new hardware. (although BESR is supposed to be able to shrink partitions when laying down an image.)
After spending 2 12 hour days trying to get this resolved, I took Astoundry's option as well as Symantec's, and finally got it to work. I did both options at the same time simply because I was not going to spend any more time than i had already, so i technically don't know which worked. Astoundry says to use BESR 7 to create image and lay down on new server; Symantec suggested that I shrink the partition on the original old server. (Good thing this was a migration only and not a DR restore to different hardware so I still could boot my original server!). So I uninstalled BESR 8.02 on the old server and installed version 7.04 (FYI: the SRD disk included with BESR 7.04 is actually v7.02 as Astoundry suggests). Also, i was lucky enough to already have my old BESR 7.0 license key so I could still download v7 from their fileconnect site. I also shrank the partition of my old source server well below the drive size of my destination hardware. (using BootIT partition utility)
Unfortunately, Symantec has only a handful of previous cases with error "EA3905F3", and they were not helping support out at all with my case. Also, when I emailed tech support stating that I had finally resolved my issue by doing both options at the same time, they said they could not post this in their knowledgebase without actually knowing which was the real resolution - whether 8.x would not have choked if I had just re-partitioned the server or if 7.x would have worked either way. So hopefully this will reach anyone with this problem.
Message Edited by SCollins on 08-23-2008 02:52 PM
