![]() If it's taking about 15 minutes to duplicate a 250 MB file and I have 1.31 TB to duplicate I'm wondering if it'll finish in time for me to see it (I'm in my mid 60's! :-) ). The problem isn't any particular folder, it seems to be that as it's catching up with duplication it really is duplicating, just frustratingly slow. Go back to the first folder and sure enough the copytemp file is gone. After about 15 minutes it finishes with that folder and moves on to another, and I see a new file in that folder with random guid etc. I can see, by comparing reported file sizes, that it's a copy of a particular file in the same folder. ![]() When I switch to that folder there's a file named (random guid).copytemp where random guid really is just a random guid. ![]() If I hover over the bouncing bar at the bottom of the GUI I can see it's working on a particular folder in the Video area. And then it sits there for what feels like forever. However, after the measure, it goes into checking and at about the 25% point it starts trying to duplicate. It now reports (for a total pool size of 25.5 TB) the following when measure runs. So, even though the drive wasn't bad, I did the same. And then I think I shot myself in the foot! I've replaced bad drives a number of times over the years, and I've always done the immediate removal followed by automatic duplication and it's always worked. The entire array is set to duplication.Īt which point I decided to add a 4TB drive to DP and withdraw, one at a time, a pair of 2TB drives so I could assign them as a separate pool for use as a backup target folder. So I did the install, added appropriate drivers for my eSata cards etc, installed DP and up it comes. My motherboard recently died and it became time to move from DP on WHS2011 to DP on Server 2016 Essentials.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |