Search the Community

Hey all! I'm still on my trial of DrivePool but am overall liking it quite a bit. However, I've run into one major problem I don't know how to solve and I'm hoping someone here knows a solution. I use the paid version of Macrium Reflect to backup my entire gaming PC. It writes a main image that's a full backup (it usually comes out to about 1-1.3TB after compression) and then writes up for 4 incremental backups after that, then rotates those out, always keeping no more than 5 backups. My DrivePool lives on my home server under my desk and I run the Macrium Reflect backup set to a share I have on that server. When I tried to start my backup, my pool looked like the attached screenshot. About 4TB of space left between a few drives. When I execute my Macrium Reflect script, it also reports the same amount of space remaining. However, multiple times today I've tried to run the full backup and it's failed between 20% and 40%. According to the Reflect logs, it's because it...ran out of space. Even without compression, the total backup from my gaming PC is less than 2TB, it most certainly is not running out of space. As you can see from the screenshot, I do have duplication turned on but even with that taken into account, there's still more than enough space available. I'm not sure why this would be happening or what to do about it. I can engage Macrium support as well but I figured someone here might have a better idea. I can set Reflect to split the backup into multiple smaller files and may try that but I'm not sure why that would be necessary. I'm not sure why writing one large file over the network would keep failing this way. Anyone have an idea why this might be happening and if there's some kind of solution? Thanks all!