Spider99

I think it must be a drive pool or possible LSI thing as i am getting the same thing i.e. 129 and 153 events for me the 153 are on the pool drive same as you i think - and Chris indicated when i raised it a while back as not something to worry about - some days i get lots of warnings some none - i updated the drivers, bios and firmware on my LSI card yesterday and only have one so far today but 40 in last 7 days. as for 129 - none so far today - so possibly thats cured(?) only difference from you was iaStorA rather than storachi - possible SAS vs SATA difference - i have only had 5 in the last 7 days used to get a lot of 153 when i had Rocket Raid cards which i have replaced - but they had loads of other issues so never bothered with these warnings

an added thought - raid5 having only one level of redundancy - when you change a failed drive the others can fail during the rebuild process - then you loose all your data on that array - this is one of the reasons i have gone away from raid that i have used for years to DP - also depending how you create the arrays they are not usually easy to move to another machine and work out of the box as DP will. Sounds like you only have 3 disk raid5's or plan to - in that case you have 33% redundancy and its not that far off 50% with DP

Problem I have my nightly backups (Veeam) for each machine copied to my DP server each night but as these files created by Veeam just grow in size over time (no shrink option other than restart the backup history?) they become very large. Recently a single file was getting into the 200GB range before i reset the history (i.e. start again) When the files are updated they are stored on my NAS and then copied to my DP Server via SyncBackPro The copying is fine and not any issue. Question When the backups are copied to my DP server they tend to fill up the cache (4x 256GB drives with real time duplication) then a rebalance occurs sometime later and the data is moved to the archive drives - this works fine. So is there anyway for large files to bypass the ssd cache and get written to the archive disks directly (accepting the copy might be slower) without disabling the ssd cache for "other" files I guess i am asking for an exception list for the ssd cache by size/type of file? I dont think this is possible but would like to be proved wrong

if you have a ups then the "lie" is irrelevant as the system will be protected and shut down before the battery is exhausted and flush the disks (assuming you set it up correctly) - if it did not then you would run the risk of loosing data every time you shut down so not sure i understand the point you are making? Happy New year by the way

That makes a reasonable difference in speed - also upped the priority from -2 to 0 - will experiment further but much better

hmmm the files were on two ssd's that dp had just emptied rather than an archive drive .... A forced remeasure sorted it will ignore in future as long as it does not happen too often

Well it is the same physical drive as the system but another partition - only added it as a replacement for a ssd that went walkies after a reboot - as that one came back i have since removed the D: drive from the pool Strange thing is the server is on a ups but i suppose MS dont think thats enough - hmmmm what does that command line do exactly ??

Yes its essentials - had it happen a few times yesterday when creating directories on a shared drive via windows explorer that shared drive is under server folders not shared folders

well with time the disks have a much better spread of data - none of them are consistent in amount - but broadly they are "even" ish the ssd came back to life on a reboot and has stayed up since - odd

Thanks will give the options in the config file a try Thing is though you do get some file activity listed when the pool is moving files from one disk to another when things are out of balance - so some balancing is shown

For me its a bit hit and miss Copying to the pool - files appear During a balance - if files are being moved within the archive disks - to balance up disk space etc i see files being moved But if files are being moved out of the ssd cache then i have no disk activity apparently this is with 2.2.0.734

Nope a reboot does not clear the issue - think it did when i had this on one disk

What does the above indicate as have had this a couple of times recently and when you check the disks they are empty? A reboot appears to clear the misleading info - the ghost data is indicated as duplicated - across two ssd's used for cache both showing the same ghost size So is the data duplicated or not? Is this a symptom of something else? Is it an interface bug? etc

Mainly for information as not a Drivepool problem but it initially looks like it is when first experienced. I was getting slow copy performance to the pool via my 10G network - basically it would run fine at close to 500mb/s (sata ssd to sata ssd) about as fast as it can go with the disks involved. This would continue for a minute or so then the copy would slow down to 20-30mb/s or in some cases virtually zero - it was during a copy of a +200gb backup file so not a small file problem which i initially thought it might be. With further testing i found it would happen on virtually any file with a reasonable size so the file size is not the contributing factor although it does show the problem more fully the larger the file being copied is. One thought was that something was overheating and being throttled - checked Scanner no disk was above 35c. Sending pc also had low temps as well. Also checked the 10G network cards and they were showing no errors and normal temps according to the driver info. The server with DP installed was very sluggish to respond when the slow copy occurred but memory load was at most 50% on a 32GB system - hmmmm odd When monitoring a copy more closely on the server i could see the "modified" memory in Task manager climb as a large copy started and would peak out at about 12GB at which point the copy would slow down to an effective crawl. Over time (few minutes) this would decrease back to a lower value and then the copy would speed up again but would drop to a crawl when the "modified" memory peaked again. So i checked the write cache settings on all drives and found all but one had write cache enabled - odd why would one not have it checked - well it turns out that write cache is disabled on the system drive of a domain controller by default. So after enabling it the copy speed went back to normal. However this does not survive a reboot as windows 20212 r2 Essentials must check this value and turn it off. - Grrr So to prevent slow copies on your network (occurs on 1g and 10g Lan) dont include your OS drive or any partition (my mistake) of the drive in your pool especially if its an ssd with SSD Optimizer as when files get written to that drive the performance slows to a crawl and will speed up again when copying to other ssd's - so you get very variable copy performance and a very sluggish pc until the memory is cleared out. I am experimenting with an option to modify the memory cache size in 2012 r2 to see if it makes any difference to the performance. As i can see that on a 10g network the performance does still decrease (with write cache enabled) when the memory cache is filled to approx 50% of normal copy speed - this might be related to DP doing real time duplication but not sure yet. Will report back when i understand more Hope this helps somebody with similar issues

I currently use a NAS to backup my data separate from the duplication i have with DP have looked at cloud backups but they take way too long and might not be there when you need them and most solution have issues with the provider limiting speed or your isp getting picky with you using too much bandwidth etc to do the backup - i tried essentials 2012 but i found it to be a typical MS botch job so am using SyncBackPro and am going through all the options finding the right balance - used to use it years ago and got a nice discount to the latest version it has cloud functionality these days so might give that a go again when i get the chance Veeam End Point is what i use on my Pc's for backup and restore - you can use it on the DP box as well although install can be a challenge and have found if you turn off the DP service first it installs a lot easier - just turn the dp service back on after and it runs fine

it got rid of the lot including in my case including unwanted backup files

what i found today was setting the drive space equaliser to % rather than free space remaining has it appears solved the imbalance the predicted space used on most drives is now close to 50% - the three which were not being filled or only to a small amount are now due to be filled to 50 % have a couple of odd ones but much better balance it still has to actually do it - approx 28% done at present thing i still dont like is the balance is prioritising the archive drives over the ssd cache - which is the wrong way around - as this should be emptied first! Especially as have had an ssd go futt on me - no warning - nothing from scanner - just not there after a reboot - it did have some files on it but not sure what yet as was experimenting with immediate duplication off - typical - nothing lost as it was stuff i had downloaded off the net so i can get it again will pull that drive and test it tomorrow when balance done.

it could be the siig card as an external box should not bring the host down - usually is the box still running when the pc dies? do you have another pc you can plug the box into to test?

i was able to get ownership but it would appear to delete the files in svi but they would just come back - the vssadmin does the trick though just do it from an elevated ps prompt

Should i see activity on the pool when its balancing as files are being moved around? I do see new files being copied to the pool just nothing when balancing. Also why is the balancer so slow to move files off the ssd cache - can take more than a day to clear them out - have loads of free space ?????

yes should have said 2012 r2 - as yes you do have access in window 7 10 etc - but its missing from 2012 r2 - hence why i went looking the fsmgmt.msc is a new one on me - actually it works in win 10 as well

If you have a large amount of "other" files taking up space on your pool drive and would like to reduce the amount of "wasted" space then... Warning doing this could stuff up you pc so go carefully and if it goes to pot its not my fault Your friend here is the powershell cmdlet "vssadmin" if you run the command via an elevated powershell window vssadmin list shadowstorage it will list your vss stores etc and then run vssadmin resize shadowstorage /on=[drive letter]: /For=[drive letter]: /MaxSize=[maximum size] See http://woshub.com/how-to-clean-up-system-volume-information-folder/ for more details got rid of 70GB+ of unneeded vss data for me Enjoy

Yes it 2012 R2 and it not my ticket so good to know its not just me I thought it was just when you create a new dir in a root directory but it appears to be any directory creation that can set it off

i have had something similar with a lag on say creating a new directory explorer will hang for a minute or so - then all will be ok after that - i thought it was a windows glitch - hmmmm strange thing is if i run a backup which will create new directories it will zip through with no issues???? this is on windows 10 Pro

Hi One way is not to assign a drive letter to the new drive - i.e. mount it to a directory Or once added do a swap of the drive letters - then it should stay permanent