I am trying to understand the logic and practical implications of using the TI9 Acronis Secure Zone functionality. 1. Reason for using the Acronis Secure Zone (ASZ) The only practical reasons that I can see to use the ASZ is to enable the Acronis Startup Recover Manager and the Acronis Snap Restore. Is there any other reason to implement the ASZ? 2. Benefits of using the Acronis Startup Recovery Manager (ASRM) What are the benefits of using the ASRM? Why not just boot from the TI9 CD? What functionality does the ASRM provide that is not provided when booting from the TI9 CD? 3. Location of the ASZ Common sense dictates that the ASZ should always be located on a different disk to the system. Understandably this disk should be part of the local system and not a network drive. But must the ASZ be located on an Internal Disk or can it be located on an External USB drive? (The documentation isn't very clear about this, it just refers to a "local disk"). 4. The ASRM and the Master Boot Record (MBR) The ASRM must be activated before it can be used. When a user activates the ASRM it overwrites the MBR with Acronis proprietary code. Which MBR does it overwrite? The MBR on the System Disk or the MBR on the disk where the ASZ is located? 5. Risks in using the ASRM Overwriting the MBR is a risky business. If this process goes wrong the disk may become unusable and might need to be reformatted. How does Acronis deal with such an eventuality? 6. 3rd-party Boot Manager If the user has a 3rd-party Boot Manager installed on the System Disk (by default the Windows BootLoader will always be installed) then that Boot Manager (or the Windows BootLoader) will become inoperative because it will no longer recognise the MBR. Must the user now reinstall the Boot Manager? If the user installs or reinstalls a Boot Manager AFTER activating the ASRM the MBR will once again be overwritten with the proprietary code of the Boot Manager application. What happens now if the user boots using the ASRM? The MBR will now contain the code of the Boot Manager and not the Acronis code. Will the ASRM boot? If "yes" how is this possible and why does the ASRM overwrite the MBR in the first place. If "no" then what happens? 7. ASZ on Disk_2 Assume that on Disk_2 the user has several partitions containing data. The disk also has an additional partition containing the Acronis Secure Zone. Assume also that Disk_1 (the System Disk) fails. The user now boots using the ASRM. Where does the ASRM look for the MBR? It won't find it on Disk_1 because that disk has failed. Therefore logic dictates that the Acronis proprietary MBR must be located on the same disk as the ASZ - in this case Disk_2. Disk_2 would have initially not had an MBR because it was simply a data disk. When the user activated the ASRM the Acronis proprietary MBR was written to this disk. What are the implications for doing this? How high are the risks? What are the risks? 8. System Disk Failure Assume that the System Disk fails. The user has a ASZ setup on Disk_2. The user removes the failed disk and replaces it with a new disk. The user now boots the system using the ASRM. How will the user reconstruct the failed System Disk to the new disk while ensureing that the new disk geometry matches the Partition Table that is contained within the system image?