Generic Errormessage when starting migration due to wrong calculation of free space

Hi,

I just got an error message trying to do a migration on a rather big solution of ours.
When starting the deployment in ottodeploy I just got a generic error message while the serverlogs show nothing (not even debug).
Splitting the deployment into two subdeployments works so I checked the free space.

The solution is 62 GB in total spread over multiple files.

C:
Has the FileMaker Database Folder and has 116GB free space

E:
Has the backups and has 132 GB free space

Otto seems to check for 3x the free space even if the solution is deployed to multiple disks.

as I see it it would only need 2x the size of the solution on C AND E at most.
Or am I thinking it wrong?

Thanks
Tobias

EDIT:
Seems I cant calculate myself, as C does not have 2 times the free space of the solution. But would it need it really? Should there not only be enough additional space for 1 copy of the solution on C?

I am also sometimes getting issues with the free space requirement, especially when using third-party hosting where disk space is often not very generous. I wonder if there could be some kind of override to, e.g., lower the requirement from 3x to 2x - assuming, of course, that this can be assumed to be safe.