pap

Hi Today I tried to build my Drivepool new from Scratch. I attached 2 pcs. 8TB (expand in future every time by 2 pcs) and 2 pcs 1TB SSD for cache. In the Image1 you can see the 8T Drives as "ARCHIV A 1" "ARCHIVE B 1" and the 2 Cache on the left side in the Diskmanager, on the right side, stable pool is not created. I add "ARCHIVE A 1" to Pool as the first drive. If you look at the Diskmanager in the Image 2 on the left side only a 2 TB Drife is created. If I attach all the other Drives, and try to copy a lot of files to the Pool Drive, the pool breaks if the limit of 2TB is reached. Can you help me please. Thanks a lot Best Regards from Austria Drivepool.pdf

Hi Thanks for answer, seems to be solved, at the Moment more than 75% of the big file is balanced. Problem was not primary the disk but the old SAS SATA Controller which displays 8TB Drives but was only able to write/read 2TB. And the big file was going to fill beyont 2TB. For the Moment i delete old files from the pool, so more space is available and after balancing all will be smaller then 2TB. I ordered a new Controller, hope that the Change of the controler will not destroy my pool. Best Regards from Austria Peter

Hi I was using Drivepool (V.2.1.1.561) for aprx. 3 Month without any Problems. Last Week I copied a big File (800GB in one File) to my Drivepool, and Drivepool is not able to balance the Pool. My Drivepool use 2 Disks (1T each named CACHE A and CACHE as cache, and 2 Disks (8T each named “ARCHIV A 1” and “ARCHIVE B 1”). I use only the “SSD Optmizer” as Balancer. I am able to copy the big file to the pool without any problem. I can see the file on the 2 CACHE Disks. After finishing the copy, the pool start to balance. (I can see the activity Led’s on the 2 Disks (one ARCHIV & one CACHE)) The Progress continues to something about 2% then restarts without any error again with 0.2% and so on. If the Process starts again the Target Drive is changing (I can see this on the Activity Led of the Drive.) In the Log File I can find a Warning like: DrivePool.Service.exe Warning 0 [FileMover] Error moving '\\?\Volume{9bd3e1c2-cfee-4611-8d32-3d37ba293688}\PoolPart.aaa84030-e4de-4a84-ac23-09c7c2711284\Archiv\Backup Veeam\PAP Alle Produktiven VM2016-04-10T143651.vbk' to '\\?\Volume{514e8456-d9c0-4fe7-870d-b082b2fc97b5}\PoolPart.838af591-1ccb-410d-9658-06ec3463365d\Archiv\Backup Veeam\PAP Alle Produktiven VM2016-04-10T143651.vbk'. Falscher Parameter 2016-04-10 17:37:17Z 45157247662 If I delete the big file, select “Neu erfassen…” in the Pool Options, my cache drives are empty, and the pool seems to be ok. The Service Folder as zip file is attached. Thanks for Help Best Regards from Austria Peter ​​ ​ Service.zip

Hi Thanks for Answer. No Antivirus or such Software is running an my 2012R2 Server. fltmc: Reports Dedup(8), luafv(1), npsvctrig (1). (x is nrb. of Instances) Balancing Status: ok I tried <setting name="DrivePool_RunningFile" serializeAs="String"> <value>C:\Program Files\StableBit\DrivePool\</value> </setting> lets see tomorrow, at the moment there is a balancing running (for the last 24h for 820GB one file at the moment ready for 77%) and I assume that the file will only be built at the beginning of balancing. The log (zi) is in the attachment. Thanks again for help Best Regards from Austria Peter ​ Service.zip

Hi again I am using Drivepool now for aprx. one Month, works fine. Now I found 2 Topics I want to ask: I am using some 8TB Seagate Archive V2 as Archivepool with redundancy. As Cache, I first use 2 SSD´s each 480GB. All works fine but write speed is not as fast as writing to a single SSD. After a while, i had to copy files larger than the SSD Size do the pool and write speed drops to aprx. 35MB/s as expected. Larger SSD´s are expensive, so I tried to use 2 fast spinning Disks as Cache, marked them as "SSD" in the Balancer "SSD Optimizer" (all other Balancers are disabled). It works as expected, but again not as fast as writing to a single Disk. The Files are Backup file, so I want to ask if there is a possibility to use only one Disk as "SSD Cache" and after finishing writing to this Disk the Balancer copies the file(s) to my duplicated Archive Disks. I know that for the first time of the copy all files are only on one Disk, if this Disk dies, all files are gone. However, as these files are backup files, no problem, I start Backup again. The second question is about automation the Backup Process. Is it possible to get information about the Balancing (% Ready, .. ) with an external scripting language? Thanks for Help Best Regards from Austria Peter

Hi again Thanks for quick answer, tried this in the follwing way. Put a 480GB SSD to my Pool, installed "DrivePool.SSDOptimizerPlugin.Setup_1.0.3.5_x64", under Pool Options, Ausgleichen, Balancer only SSD Optimizer is checked, my 2 test spinning Drives (WD Green 1TB) are marked as Archive, my SSD is marked as SSD. "Fill SSD drives up to" = 75% Under Ausgleichen, Einstellungen, "Sofort ausgleichen" is checked. If I copy a file aprox. 150GB to my Share (Drivepool) I got stable 100 MB/s writing, also show in my Task Manager, NIC. I think that's the the max Speed of my datasource, may old WDGreen 1TB drive, and my 1GB LAN. After the copy was finished, th new file is on the SSD and on one of the 2 Archive Drives (1TB WD Green). So it is dupplicate as it should be because the Pool is configured for Duplication. What I dont understand at the moment is, why the file is not moved to the second Spinning Disk, and the SSD is going to be empty for the next copy. Thanks for Help Peter

Hi I am new to drivepool, looks great. I am testing in the 30 Day´s Evaluation Period. Is it possible to build a System (regarding on a specific balancing System) for Archive files. All new files are stored in a drivepool (2*n Disks) with duplication so all files are "safe". If the files get older then a specific amount of days (e.g.365) and are untouched (no update or rewrite) i want to move the files to other disks (maybe a new pool??) like "Seag... Archive HDD v2 8TB" without duplicating. This Drives are based on "Shingled Magnetic Recording (SMR) Technology" which means that the writing Speed is slow especially for larger files or if disk usage is > 75%. I know I could do th move manually or by script. A scale out Option is a "first level Cache" build of SSD, fast but asynchronous move to a diskpool (with sync. duplication) and after xx Days moving to SMR Archive. Thanks for any Help Best Regards from Austria Peter