Hi Albert -- BESR doesn't resize the partitions automatically when restoring to a larger drive configuration. After selecting the restoration points, the edit function has to be used to adjust the partition sizes for the desired partition(s) that need resizing. I too have made this mistake when restoring my own workstation from a BESR image. The result was 60GB of unused space in my scenario. Restoring the image again and having BESR resize the partitions made it right again. There is an option to
Restore Drive to fill unallocated space" but I think that is more geared toward drives with a single partition being restored to a larger drive.
The lack of an index file (SV2I) during a cold backup is still an issue. For the moment, we all have to live with restoring the cold backup v2i files individually.
It appears that the Dell utility partition was restored three times, thus the QTY(3) EISA partitions. Frankly, they are not really needed given the availability of NTFS disk utilities on bootable optical media. The last PowerEdge 2950 server I built with the the aid of the Dell Installation Utilities DVD specifically offered the option to skip installing a Dell Utility partition. The partition is obviously not required by Dell to make the server work. When restoring this server again, I would just skip restoring the Dell Utility partition. I remember that you had worked out the solution before in this post:
http://www.symantec.com/connect/forums/cold-backup-using-besro-852-srd-error
The only thing I would change is not restoring the Dell Utility partition, which would require restoring the MBR to the C: partition instead. Having BESR resize the partitions won't break your Domain Controller or Exchange configurations. Unlike Linux, Windows can handle restoring data to resized partitions without much intervention. The most that is required is an extra reboot because the OS will see the resized volumes as new drives.