w3wilkes

Yes, the licenses are not Windows OS specific. They should work on Win7 and up.

I don't know if the drive idle change is with the 3.7.0.0 version since the release info in the Announcements section of the forums doesn't mention it. You could open a ticket and ask the developer. Submit a request – Division-M - Support (division-m.com)

Have you opened a support request? The developer can tell you exactly what logging he'll need for your issue. Submit a request – Division-M - Support (division-m.com)

Almost sound like the target drive has gone to sleep. You should open a ticket and see if the developer has any hints for you. Submit a request – Division-M - Support (division-m.com)

Sorry I'm so late to your party. Have you checked the manual, it's in the DB program Files directory? In my own case the only thing I have on my DB drives is well known so knowing what's where is no big deal for me. It would really be nice if DB kept a "catalog" of files in the pool so that questions like this could be easily answered. I've submitted this as a request before. Maybe if we get more people to suggest it...

So what's the load/unload cycle min? Will the drive crash at 300,001 cycles? If the drive did a load/unload every minute the drive would die in 208 days at 300,000 cycles.

As you know, most any drive of any size can be added to the pool as long as it's NTFS formatted. The unknown is drive longevity/reliability and speed. My guess is if it's slower than your existing drives and dup'd data is being written to it, I would guess it would slow down the operation. Can't speak to the Synology question.

Thanks for letting us know what the issue and solution was.

Sorry this is so late! Sounds like you need to open a support ticket with the dev. Here's the link; Submit a request – Division-M - Support (division-m.com)

I presume you opened a ticket as @CBers suggested in reply to your prior post. What was the reply?

Thanks for the update Anthony! The OP doesn't say what version of DB they're running. Hopefully they are trying with 3.7.0.0. I've always thought it's a good idea to put DB version and OS version in your signature.

Interesting, I just did a Check for updates and don't see that 20H2 has been dropped. Where is the official release 20H2 for Win10 pro?

You should be able to use drive bender manager to remove the "D:" mount point.

You will need a target drive to receive the data from the pool. The easiest way would be to have DB active so you can access your big "K" drive and then just copy from the big "K" drive to your target location.

Glad you got it working.