sota

The native backup tool that comes with Windows 7 and up, including the server versions, is solid as a rock, especially when you want to do disaster recovery. My production servers use it exclusively. Also works flawlessly, and Any-Monkey-Can-Do-It, even with native encrypted drives. I have recovery down to a single USB stick, plus the backup drive obviously, and some ridiculously simple instructions, which predominantly consist of "click <NEXT>" about 6 times.

backup and restore is my main method with windows 10. GHOST was my go-to for the longest time, but the version I have doesn't work with win10 properly.

https://kalenetwork.org/ also, getting ready to migrate the install to an SSD. what a pain in the ****.

just loaded kale crypto.

ok. also silicoin is synced, and passing a massive # of PPF, but no wins yet for me.

how's your chaingreen behaving? the logs are way too damn busy in INFO mode, compared to other 'coin.

getting a lot of... [The semaphore timeout period has expired] [The remote computer refused the network connection] errors, along with a lot of connect attempts on port 9444 instead of 10444. silicoin is a disaster.

grassy ass.

my silicoin still won't connect. mind posting up some of the IPs?

PS C:\Plots> .\getStats.ps1 Start Time: 07/11/2021 10:08:17 BLOCKCHAIN: .chia Eligible for Farming Count : 82598 Average : 1.25960677013971 Sum : 104041 Maximum : 9 Minimum : 0 Property : Found 0 proofs 0 .chia ------------------ BLOCKCHAIN: .flax Eligible for Farming Count : 56098 Average : 1.30614282149096 Sum : 73272 Maximum : 10 Minimum : 0 Property : Found 1 proofs 2 .flax ------------------ BLOCKCHAIN: .spare-blockchain Eligible for Farming Count : 60985 Average : 1.29961465934246 Sum : 79257 Maximum : 8 Minimum : 0 Property : Found 3 proofs 48 .spare-blockchain ------------------ BLOCKCHAIN: .chaingreen Eligible for Farming Count : 6373 Average : 1.44217793817668 Sum : 9191 Maximum : 10 Minimum : 0 Property : Found 0 proofs 0 .chaingreen ------------------ BLOCKCHAIN: .goji-blockchain Eligible for Farming Count : 76075 Average : 1.25460400920145 Sum : 95444 Maximum : 8 Minimum : 0 Property : Found 12 proofs 24 .goji-blockchain ------------------ BLOCKCHAIN: .seno2 Eligible for Farming Count : 66070 Average : 1.28883002875738 Sum : 85153 Maximum : 11 Minimum : 0 Property : Found 9 proofs 20 .seno2 ------------------ BLOCKCHAIN: .hddcoin Eligible for Farming Count : 22356 Average : 1.41058328860261 Sum : 31535 Maximum : 8 Minimum : 0 Property : Found 88 proofs 42 .hddcoin ------------------ End Time: 07/11/2021 10:38:18 Elapsed Time: 1801.1945474 seconds PS C:\Plots> HDDcoin had some problems early on, as you can see.

looking at the silicoin github, looks like v0.0.6 might show up soon.

tonight's education: NR12000 can only use PC3-xxxxxE memory. U or R is no bueno. I happen to have 4 1GB sticks of the correct memory floating around, so the machine now has 11GB of ram. It's happier (namely, more responsive.) I'd figured out, but running resource monitor, that the pagefile was getting hit pretty good with only 8GB of ram and 7 sh!tcoins going. I'll need to order up 6 sticks of 8GB PC3-12800E memory to boost both boxes to 32GB ram (might as well.) No idea if that's the max the board will take, but since I can't find any docs for the damn thing I'll go with that. Maybe when box #2 comes in I'll try searching on whatever numbers I can find on the mainboard itself. Starting all 7 sh!tcoins is a pain in the *bleep*. Hoping to have the SSDs off the server in the next day or 2. Then I'll have the fun of backing up, restoring, and waiting for all of the sh!tcoins to re-sync after being down for what will probably be 30-45 minutes.

man all the fleabay people are still wanting too much $$ for drives.

can you tell it to not make portable plots?

and i'm seeing over on the HDD coin page, there's a dude who's won WAY more than should be possible... and he's running 16 nodes. now i'm starting to wonder, if I shouldn't retask all these old machines, not as plotters, but as farmers.

so apparently the newest version of chia plots faster? if I upgrade to that, will it bork my plots for the other shitcoins? I don't want to plot "portable" plots right now, and I want to keep farming on all the other coins.

I might get bigger disks at some point, if the $/TB is right. I'd want to have 2 backup copies anyways so I was clearly focused on $/TB vs. absolute convenience. Plus, with them being smaller like that, if a disk does die it takes less with it. That coupled with having duplicates, and them being cold storage, I figure i'm on the better side of being safe. with regards to running all these forks (7 currently) on the same box... looking at a couple metrics I'm seeing... CPU < 20% memory is 6.8GB/8GB boot/DB storage HDD is getting crushed at near 100% average. now that the replacement drives have come in for another project, I'll get the SSDs pulled out of that, and re-task one of them to this and the other NR12000 box. we'll see what effect that has. otherwise, i'm starting to think that I'll need to split the forks between these 2 boxes, and cross-link them to gain access to their plots. both have dual NICs, so i'm considering doing a dedicated/sandboxed network, just for plot sharing. that'll keep management/proof traffic from causing contention.

my silicoin is still borked. installed 0.0.5 and no joy.

hence my love affair with <$10/TB 4TB disks

I run either a full or incremental backup (the joys of the archive flag. ), then clone the backup disks to another set, so I have 2 complete backups of my data.

got my 10pack of 900GB 10k SAS DP disks in just now. seller didn't disclose, they're 520byte format. got sg_format taking care of it now, hopefully, but i'm gonna bitch the dude out a bit for NOT mentioning that. also need to order another stick of memory for these chenbro machines. 8GB is getting tight with 7 sh*tcoins all running at the same time.

when I did my unraid array backup a couple times, I noted the file copy speeds, and determined that they were within a couple % (at worst) of what the raw pre-clear data rates were for that size/style drive, so given that using a windows VM gave me the functionality I need (archive flag on the files, allows me to spread the backup across dissimilar sized drives) I'm going with it for now. the other nice bit is, it stores the backup in NTFS format, which means if unraid took a total poop I could just connect the backup disks to any windows machine and get access to the files, if I needed them before I got unraid back up and running.

does it do something similar to the archive attribute in windows? that was my biggest stumbling block with any other choices. I need to be able to split up the 50TB protected array, on to many smaller disks. and frankly, running a windows VM under unraid and using robocopy, with the source array as a UNC, and the target device(s) as locally attached disks (passed through from UD), I'm still seeing full data rate to the target disks (100MB/s+), so I don't think i'm hurting in terms of speed.

see my sig.

at this point i'm gambling on one of these forks having some value at some point. it's about the best I can do.