dsp

I am a powershell beginner and hoping someone else had this exact same issue/question. Does anyone have a script or know how to set a script to see if all my clouddrives are up before starting a VM? I would like my VMs to start up in a specific order but I cant seem to think of a good way to check if the cloud drives are healthy first before turning on the next VM.

Direct movement between the poolparts using a powershell script. The balancer seems to just balance the files randomly and I only want to slowly move files out of my LocalPool into my CloudPool.

I think I may have come up with a config that will work. Anyone have thoughts on below? LocalPool -> Local drives CloudPool -> Cloud drives LargePool -> LocalPool + CloudPool I set LargePool to fill to LocalPool only. I don't think there is any way to balance just a certain subset of files. So I setup a scheduled task/job to just move "old" files from LocalPool to CloudPool. On LargePool, I will still be able to see all files but the recent files will be stored on my local drives only. I think this works?

I was wondering if there was a way to archive old files into a 3rd drive pool (cloud drive)? I am sure there is some way to do this but I am tired and cant think it through. Here is the setup I would like below. Files go into SSD Cache. From Cache, it goes into my local HDD Pool. (I have this part already setup) But then I want any old/stale files to then move into my cloud drive pool? I am not sure if the disk balancer goes from first in first out? I would like to have a local pool of files where only some of the files are pushed into the cloudpool and then stops. This way it keeps a large local cache that can be quickly accessed and just slowly pushes old files into the cloudpool. Sorry if this does not make sense. I can try to explain better if this doesnt.

Not sure where I am supposed to be posting this but I figured I would try here first. I was hoping for a feature that would allow us to empty the SSD optimizer at a specific rate. (For example, move X gbs from SSD to archive when the SSD drive is this full or this much data needs to be moved.) Currently, when the criteria is met, the entire SSD is emptied into the archives all at once. My goal is to keep the more current data on the SSD and slowly push older data into the archives. I am hoping to just move the first X GBs written be moved to the archive whenever the trigger criteria is met but leaves the remainder of the data on the SSD. An example would be if I had a 1 TB SSD. Once it reaches 800 GBs used, it would then push the first 200 GBs into the archives now making the SSD 600 GBs used. Rinse and repeat forever. Not sure if this is possible or this can be added in as a feature down the road?

Ah darn. After I posted this, I started to research alternatives and came across primocache. If you heard of it or used it before? I am wondering if primocache might be a useful alternative.

Just wondering if anyone is using primocache with CloudDrive? I am trying to get the benefits of a read/write cache. I am currently using drivepool with 3 cloud drives and 1 SSD cache disk. For the most part, this is working well with the SSD cache disk being the write cache. However, I am noticing that the clouddrive cache does not appear to be as fast as the cache disk. Also, when I set the clouddrive cache to a really large size, 50 gbs+, it takes awhile for the system to shutdown at times. I was hoping for a solution where I could speed everything up. I have 1 gigabit up/down connection and a 2tb ssd I can use as a cache. Each clouddrive have their own individual 250 gb ssd disk for a cache as well.

Is there a way to make Drivepool store the most recent x GBs of files on a certain disk, and then move old files off of it and balance into my archive disks? I would like it so my most recently added files are stored on my SSD drive but slowly push out all data to my archive disks. Currently the SSD Cache plugin will let my SSD fill up, but then immediately empty it out once it starts to balance it.