Crashplan exclude folder12/29/2023 ![]() (FIP is currently processing disks 11 & 12, so there were some files open that probably slowed them down a bit.)ĭisk 5: HGST HDN724040ALE640 PK1338P4GT2D9B 4 TB 133 MB/sec avgĭisk 11: HGST HMS5C4040ALE640 PL2331LAG6W5WJ 4 TB 100 MB/sec avgĭisk 12: HGST HMS5C4040ALE640 PL1331LAHE2R0H 4 TB 102 MB/sec avg Using jbartlett's excellent drive performance test all 3 of those disks are performing at right about the same speeds. ![]() Of the 4TB drives (md4, 11 & 12) 5 & 12 run to completion in 6-10 hours (don't recall off the top of my head), but disk 11 regularly takes the 30+ hours. By extreme, I mean 30+ hours.įilesystem Size Used Avail Use% Mounted on I've noticed that one disk takes an extreme amount of time to be checked by FIP. I recall that when I first excluded the folders, there was some sort of drop-down picker and that the format above was created by that, but now I'm not so certain of my recollection and I may have just made it up.ġ) why am I still getting notifications of file mismatches in these folders?Ģ) if the answer to 1) is "because the exclude folder format is wrong", what is the correct format for this box? Do I need the full path, and if so from root (/)? The numbered directories are the ones CrashPlan creates when an incoming backup is created. I want to include my /mnt/user/Backups share because all my machines at home are backing up to here, but I want to exclude a subset of directories under that share because my server is a backup location for several family member's machines. I am getting notifications of hash key mismatches from directories that are in my exclude custom folder list.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |