Salta al contenuto principale

2017 boot disk backup

Thread needs solution

I have been using ATI through many versions.  I have usually created a rescue CD or USB thumb drive and booted that into the Linux system.  That has always had the boot drive I am backing create a full image that allowed my to replace a failed boot drive with a blank drive and restore and be running without endless updates or activations.  A couple of programs I use link the activation to the HD or SSD id information and to get them operating again usually all you have to do is contact the vendor and explain you had a disk failure.

I have found that creating a disk, not drive letter, backup from the Windows GUI ATI application in 2017 is very convenient.  However, my concern is that in recovering from a total drive failure I won't be able to just boot from an external rescue media and recover the .tib to a blank drive and have everything boot as before as there might be some file locks on files and they don't make it into the .tib.  Has anyone done a full recovery from a .tib created by ATI 2017 from windows while it is running?  Does the recovery work as flawlessly as one made by a rescue disk boot?

0 Users found this helpful

Leo, there should be very little difference between a backup created by ATIH 2017 running with Windows, and a backup created by booting from an Acronis Rescue Media disc or USB stick.  The key differences are in terms of some items that are excluded by default by the Windows application, you can see these on the Exclusions page of the Option for your backup task where such as the Windows page file, swap file, hibernation file and System Volume Information files / folders are excluded by default, along with .tib files, temporary files etc.

Acronis running with Windows uses snapshot technology via Windows Volume Shadow Copy Service (VSS) to capture locked / system files so that the whole OS and its files can be included in the backup when doing a full disk & partitions backup.

Where you do still need the Acronis Rescue Media is in performing any bare-metal type recovery, i.e. a total disk failure, plus the MVP's would highly recommend using this for any OS type recovery even if you are restoring an earlier backup of your Windows partition.  This is recommended rather than attempting this type of recovery from within the Windows ATIH application, as this would then need to modify your Windows boot configuration files to create a temporary Linux OS environment from which to launch the Acronis restore operation.

In risposta a di truwrikodrorow…

Thanks.  I expected to have to use the rescue media to recover to a bare metal drive.  Perfect.

You asked: 'Has anyone done a full recovery from a .tib created by ATI 2017 from windows while it is running?  Does the recovery work as flawlessly as one made by a rescue disk boot?"

Yes, I have done full disk recoveries from backup images created by ATI Windows version. Yes, they worked fine. As Steve says, the differences should be subtle.

And, to emphasize what Steve said, I recommend that any disk or partition recoveries be performed after booting from the ATI Rescue Media. It doesn't matter whether the backup was created from ATI Windows or the Rescue Media. If you're recovering a disk or partition, do it after booting from the ATI Rescue Media, not from Windows.