Group: Forum Members
As others have said, you can't capture an image of your D drive to a file on your D drive. To unpack the error message, the path (your destination, where you're storing the image file) is contained within the image (the scope of data you're trying to back up). Theoretically this configuration might actually be possible thanks to VSS, but you still wouldn't want to do it because you would quickly fill up your disk. For example:
- Your D drive starts out with 100GB of data on it.
- You capture an image of it, which for the simplicity we'll assume does not use compression. Now your D drive has 200GB of total data, namely its original 100GB and a backup file that's also 100GB.
- Even if nothing else on D changes, if your next backup is an Inc, it will have to back up that newly generated 100GB file. Now you've got another 100GB backup file and a total of 300GB consumed. This repeats indefinitely, with each Inc backup consuming another 100GB on your destination just to back up the previously generated backup file, even when none of your original source data is changing.
- It looks even worse if you capture Full backups each time. Starting with the original 100GB of source data again, the first Full would be 100GB, for a total of 200GB on D consumed. The next Full would create a 200GB file (for the original data plus the original backup), taking your total disk consumption to 400GB. The Full after that would therefore generate a 400GB file, and so on with each Full backup doubling your disk consumption, again even when none of your original data is changing.
And that doesn't even consider that it's not especially wise to store backups on the same disk as the source data, since that still leaves you at risk of losing all of your data in case of a disk failure.