Chris Sykes

I have seen this more than one now with the data on my drive pool. My pool contains 4x drives with the majority of the data duplicated with one specific folder not due to it being a DB. I'm looking to move my data into a raided hardware and I've gone through the auto removal where I remove a drive and allow it to complete. Once the drive is completed being removed I check the pool folder on the drive and there is 100's of GB of data left on the drive. I proceed to check the pooled data and copy this over, the majority is there already but I've had instances where some of this data is missing. This makes me inclined to belive that the duplication Is either not working, or the drive removal is not fully moving the data off the drive being removed or both.

Hello, I have the Cloud Drive on Trial to see if this solution is going to suit me else I will be removing Drive pool and going to RAID drives to allow DFSR. My situation is 1x Windows Essentials Server 2016 running Drive pool with 3x 4TB & 1x 3TB drives as a pool, this pool has majority of shares/folders duplicated to aleviate a drive failure. One folder however is not duplicated (Client Backups) as duplicating this causes issues with the database. I have a 2x server with 4x 12TB drives running a Windows Hyper-V 2019 server with a guest running Windows Server Standard 2019, this is a 2nd Domain Controller and as such I would like to duplicate the data across from the Essentials server to the standard server. As DFSR doesnt work with Drive Pool I am looking at alturnatives before biffing off some of the Drives from Drivepool and RAIDing them and therefor allowing DFSR to work with those drives. So far I have created the Cloud Drive to look at a Shared folder on the DC server, creating the drive in Cloud Drive and then I struggle with the Drive Pool side, I can obviously add it to the current pool but this wont suit as I would have to set all folders to have multiple duplications so using my storage. I have also tried adding the Cloud Drive to a seperate pool and then with the current pool (so Pool A & B ) and also as a seperate pool, then pooling both the seperate pools together (Pool A, Pool B, Pool A & B ). The issue I have is both scenarios the pool is greyed out as if the Data in the current pool is not "readable" and as such doesnt allow that data to be duplicated accross to the Cloud Drive pool. Is there a guide on such a situation as I have searched on this a few times and found something where manual intervention is required, this is something I would prefer to avoid if possible.

Hello, Sorry for delayed response, I dont have any duplication errors at the time when this occurs. Currently I don't run server backup as the data is too large as a consumer to backup.

Hello, I have been running drive pool for a good few years and im running this on a Server 2016 Essentials server to pool 4x drives together. As my client Backups are over 2TB in size I ideally want to duplicate the Client Backup folder to reduce the risk of loosing data if I have a drive failure. As such the majority of time I run duplication on the Client Backup folder, however when the client backups get into a hissy fit its near impossible to run the repair backup tool. To get round this I saw a fix a few years back that involved the process of un-duplicating the client backup folder, then running the tool again. Once the database was repaired re-duplicating the folder. This seems to always work perfectly OK, however each time this is done I'm putting my backup data at risk. Has anyone else seen this and fixed this issue?