MatBailie

When I enabled the logging I couldn't log in at all (everything froze just after desktop appeared). Managed to get in to safe-mode and remove the anti-virus (Avast) and rebooting now seems fine (without the original issues). Will be trying Avira or something next, unless you have a better recommendation? Thanks for your help. I'm happy to reproduce the issue and supply the logs if you want them, otherwise I'm happy that I now have options to remedy this fully myself Thanks again, Mat.

I recently had to migrate my drivepool from my server to my desktop (MB died). Since then my desktop has been Very slow to login. - Turn on, fans start at full speed - ~12s later, Login Screen appears - Fans still full, Login dialogue won't show - ~45s later, fans go to normal (MB software loaded?) and can log in now - ~10s later screen goes black - ~40s later desktop appears When I uninstal DP, I can log in straight away, and desktop appears with a couple of seconds. Is this normal / expected behaviour? Or anything I can do to speed this up? I won't be replacing the server motherboard any time soon

But what would the behaviour of DrivePool be if we tried this? For example... Initial Setup > I have 3 drives (1.5TB, 1TB, 1TB) > I create a pool with the 1.5TB drive and 1TB drive > I move my Photos folder to that pool and set it to duplicate > After duplication has finished I remove the 1TB drive from the server and take it to work > I add the other 1TB to that pool At this point I should have three copies of my family photos, one copy being at work for disaster recovery. Use for off-site-backup: > I add new photos to the pool, and they are copied to both drives > I remove some photos, and/or move them around in sub-folders > At the end of the month I pull the 1TB drive from the server and take it to work > I bring back the old 1TB drive and plug it in to the server What happens now? > I suppose that all of the new files will copy to the 1TB drive > But will the deletions and file moves be replicated as well? > Or would files from the 1TB drive become part of the pool and replicate to the 1.5TB drive? > Or would it simply not work at all? I suppose I could make this work by monthly wiping the 1TB drive before I plug it in, then add it to DrivePool. But I'd rather not Cheers, Mat.