How does ATI 2016 select the default destination drive?
In short, I have Windows 10 with 3 disks attached:
- C: - the system drive
- E: - 250 GB external drive on USB (Lacie)
- F: 2 TB external drive on e-SATA (Seagate)
When I create a new backup scheme (entire PC) and go to select the destination, I am presented with 3 choices:
- Acronis Cloud
- LACIE (E:)
- Browse...
I really wish that ATI would show the 2 TB drive as option 2 instead of having to choose it via the browse function.
I tried changing the drive letter on the Lacie-disk to L (to put in behind F in the drive-letter list) in the hope that ATI simply chose the first non-system disk as option 2, but that did not change anything.
Would it not make sense for ATI to either choose the first non-system disk, or better yet, the non-system disk with the most free space. e.g. my 2 TB drive?
A drive connected to eSATA is considered as an internal drive. So if you select backup entire PC also that eSATA drive will be backed up - and of course you cannot store a backup there.
Try to manually select all source partitons which you want to backup, C: and all other partions on this harddisk. Then you should be able to store the backup on eSATA drive.
MiniMax,
As user Berti has indicated, you are one of those users that must not select "Entire PC" as your backup selection, in order avoid the esata disk being included. As he has indicated, choose the Disk & Partitions and manually choose what is to be included. Be sure to include all partions (except for esata disk) including any without drive letters.
I would recommend that your destination choice always be using the "browse" option. By doing so, you can choose to put your tib files into a folder of your choosing, If you don't choose the browse option, then the tib files will be placed scattered onto the root drive of the target disk perhaps mixed with other tib files from other tasks.
Deleted (double post)
As I said, I was going to check what this "Entire PC" actually meant, but then I got a Blue Screen crash (DRIVER_POWER_STATE_FAILURE)! Now, with Berti's explanation, it seems like I do not have to do that.
Incidentially, when I checked the mini-dump after the crash, I got this:
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe0009e7fe600, Physical Device Object of the stack
Arg3: fffff803390ada90, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe000a7026010, The blocked IRP
0: kd> !irp ffffe000a7026010
Irp is active with 5 stacks 2 is current (= 0xffffe000a7026128)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
cmd flg cl Device File Completion-Context
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
0 e1 ffffe0009e7fe600 00000000 fffff8015c3160d0-ffffe0009ea0a5a0 Success Error Cancel pending
\Driver\atapi CLASSPNP!ClasspPowerUpCompletion
Args: 00000000 00000001 00000001 00000000
[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
0 e1 ffffe0009ea0a060 00000000 fffff8015b6a3850-00000000 Success Error Cancel pending
\Driver\disk partmgr!PmPowerCompletion
Args: 00000000 00000001 00000001 00000000
[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
0 e1 ffffe0009ea0ab10 00000000 fffff80337317d74-ffffe0009e7db7d0 Success Error Cancel pending
*** ERROR: Module load completed but symbols could not be loaded for fltsrv.sys
\Driver\partmgr nt!PopRequestCompletion
Args: 00000000 00000001 00000001 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-ffffe0009e7db7d0
Args: 00000000 00000000 00000000 00000000
A Google-search tells me that fltsrv.sys is an Acronis component!
I found the "Enter PC" confusing too. In Windows "This PC" includes all attached devices; SD cards, USB drives, cameras, etc. At least Acronis could list the devices that will be backed up.