Drive Imager has two ways to handle an acquisition that will not fit on one destination.
For a single destination in a supported Native Go segmented E01 or AFF4 workflow, imaging pauses when the destination fills. The user can then swap the full drive with a new drive and resume the same still-active job.
If you want to connect multiple drives via a USB hub, sequential spillover can use multiple connected destination drives in a supported Native Go segmented E01 or AFF4 workflow. It fills one destination, then writes the next segment to the next destination, and so on. The output manifest records where each segment was written, so the results can be hashed and verified. When Verify After Creation is enabled, a dependent Image Verify job checks the complete image after acquisition; it does not verify one destination in isolation.