I've tried to read all I can find described about Drive Pool, but I haven't seen a real explanation of how Drive Pool handles a drive in the pool being disconnected for long periods of time. Let's say I wanted to have a drive which is periodically connected and then removed to act as an offsite backup. Or let's say I had an external drive connected to my laptop which houses primarily games and I don't generally need those when I'm disconnected, but would still like it to be part of the pool for other content. I'm just not clear how drive pool knows how to re-sync things.
Related to this, am I correct in assuming that you cannot pool the same drives twice with the same content; for example, have laptop A pool it's D: drive and a shared E: from laptop B, and then have laptop B pool it's E: drive and the shared D: from laptop A. If that is possible, how does it sync and not become inconsistent with concurrent accesses/disconnects?
Thanks, still wrapping my head around what Drive Pool can and can't do, I think I'm still imagining it to be slightly different than it is.