The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software
Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)
robnicholson wrote:Hi Anton,
I used the default block size of 256k. No, didn't enable the delete checkbox as it said "experiemental". It was a pure copy using the robocopy /mir option.
This is a pure test so I can delete and re-recreate the disk device and target if needed.
Cheers, Rob.
Have you re-created or created new one?I've recreated the deduplication disk with a 4k block size and deletion turned on. When I went through this time, block size defaulted to "auto" (so I changed it to 4k) so I'm not sure why I ended up 256k. I'm pretty sure I would not have changed it myself from "auto" to 256k so that's a bit perplexing.
Agree. I think we will add this when deletion support will stop being experimental.One other change request for you to raise. You cannot tell from the device properties window whether deletion is on or off. See attached screenshot. Needs "Deletion On/Off" adding under deduplication settings.
Maybe, but we couldn`t recreate this in our tests lab. If you will catch this once again it would be great if we could saw the screenshots and dtailed description of waht was done to get this. But I hope that we will never hear about this againWhilst I'm on the subject of little quirks, the first time I went through creating this deduplication disk and got to the bit where I specified the virtual disk location, the metadata location & name was blank. I'm afraid I didn't screenshot it at the time so all I can supply it when it worked the second time. I remember been very confused the first time as I wasn't sure what metadata was (I can guess), where to put it or what to call it.
Maybe this only happens on a new server build?
It is using 256K by defaultBTW - what does StarWind do if you set the block size to auto? Does it vary the block size depending upon the data being sent to the dedupe disk?
Deleted old disk and created a new one with 4k block size, not auto. So far it's looking better. 232GB of disk space used by Windows but the spdata file is 199GB. So a deduplication ration of 1.16. Will let it finished the entire copy of 886GB source data now.Have you re-created or created new one?
robnicholson wrote:Deleted old disk and created a new one with 4k block size, not auto. So far it's looking better. 232GB of disk space used by Windows but the spdata file is 199GB. So a deduplication ration of 1.16. Will let it finished the entire copy of 886GB source data now.Have you re-created or created new one?
Rob.
robnicholson wrote:Hiya - have been on holiday for two weeks so will follow-up later this week.
Regards, Rob.