Need specific directions....
I currently have ATI Home 2012 running on Win 7 64-bit, but am willing to upgrade Acronis if necessary.
I have three computers each with the boot drive (C) on an SSD hooked to the mobo and the data drives on a separate RAID card. As a emergency backup for the three C drives, I keep one spare SSD in the closet.
Using Acronis, I keep an incremental back-up of each C drive on my NAS.
What I intend to do if any of the C drives fail is to take the spare SSD out of the closet, plug it in to one of the other computers and use Acronis to "restore" the backup image of the drive that failed to the new SSD, then swap that SSD for bad one.
Is it as simple as this? ...back-up C to a .tib file on the NAS and then use a working computer to restore from the NAS to a fresh SSD?
Do I need to backup both the reserved and the C volumes? Or, when Acronis backs up the C drive, does it include the reserved partition automatically?
In the restore process, will the drive letter of the restored back up change because the computer it is being restored on already has a C drive?
When Acronis restores the back up of the C drive to a fresh SSD, does it overwrite the new drive's DiskID or the Volume Serial Number ... whichever is used by software manufacturers to control piracy ... or will the apps (including Windows) have to be re-activated when the computer boots from the restored back up?
Do I need ATI 2014 Premium to do this?
Thanks.
- Anmelden, um Kommentare verfassen zu können
Thanks, but do you realize how complicated it is to do this? Essentially, I want to make a copy of the boot disk and then from a good computer restore the copy to a new SSD.
Why would I have to use a TI boot disk to do so? I am very good at this type of thing, but have no idea what this means: "First boot following the restore should be only the new restored disk attached. Drive letters will be restored ok when only the restored disk is attached during first boot following restore."
I will read your link...
- Anmelden, um Kommentare verfassen zu können
Yes, this backup or restore process is "not a piece of cake" so to speak. The more familiar you are with the process, the less chance for user error.
Here is a link to information provided by Acronis.
http://forum.acronis.com/system/files/delete-tib-file.jpg
Restoring from the Recovery CD ( or other) is the recommended procedure. When restoreing from another computer, this has been posted to cause either one or both computers not to boot so restore from the CD has a better chance of working.
My suggested way is not the only way but my guides have helped lot of users to have a successful restore. Note, if your systems are not of the BIOS type but are the new UEFI or Win8, you could have additionall issues.
My comment which you do not understand is one way of stating
After the restore, shutdown and disconnect the backup disk and disconnect the original source disk if those are attached. The first bootup after the restore should NOT contain two identical disks--only the new replacment disk.
If both old and new SD attached at same time during first boot after restore, either one or both could be damaged and neither bootable. This can be prevented by having only the new disk attached on the first boot following a restore.
- Anmelden, um Kommentare verfassen zu können
Yes ... thanks. But, why can't someone from Acronis respond here to why there should be any risk of a computer used to restore an image to an SSD to not be bootable afterwards? What is going on in the restore process other than unzipping the .tib file and copying it to the fresh SSD? If it isn't this simple, what else is going on?
- Anmelden, um Kommentare verfassen zu können
In answer to your last post, it all depends on how you've made your image and for some PCs (mainly brand name models) how they have laid out the disk.
If you have installed Windows yourself and made a complete disk image non booting on a recovery is more likely to be down to a user mistake, with brand name systems there are added areas that can cause problems, such as on UEFI systems the partitions not being in the same order as recommended by Microsoft, special disk sector sizes, most problems though are due to the active flag not being marked correctly, which is easy to solve and the first thing to check.
- Anmelden, um Kommentare verfassen zu können