u/benuntu

I have a couple extra nodes and want to set one up as a room server at home. What I'd like is to be able to see public and private channel messages once I get back home. At work, reception is spotty and I get some, but not all messages. At home I have a roof repeater which is working well and I receive a lot more messages there than at work.

So, say at work I receive 2 out 10 messages sent on the public channel during the day. When I get home, will the room server automatically send me the remaining 8 messages? Or will I get duplicates? Or do I have to actually log into the room server to see messages stored there?

EDIT: My take on the room server was totally wrong, thanks for the clarification. I think the only logical solution to missed messages is to get permission for a roof node at work!

I just added a single 10TB drive to my existing 6 drive raidz2 vdev. I know that when adding a new vdev you need to rebalance since no existing data is copied over to a new vdev. But with just adding a disk to an existing pool, is that necessary?

Here's the situation: My house is in a valley with two good repeaters up on a ridge 13 miles away. My current roof node has an Alfa 915 and running a Rak 4631. The signal is pretty good but there are other nodes further up on the ridge that I can't reach. If there are good atmospheric conditions I can sometimes get a flood notification.

I have another roof node running Meshtastic (same setup) and thinking about flashing that one to mesh core but adding a Yagi antenna pointed directly at the repeaters on the ridge. My two roof nodes are about 10 feet apart currently.

My question is whether it is going to cause any problems to have two repeaters. I'd like to keep an omni-directional antenna on the current MC node so I have good local coverage but extend my range to get further up in the hills. So, good idea, bad idea, or waste of time?

I think my current backup strategy is a good one, but I have read that it may not be the best approach if the primary repository is corrupted in some way. Would it be better to create a separate backup for each repository, and not do a backup copy job? Below is my current process/environment, and I'm looking for suggestions on how to improve it or if this looks correct.

• 11 VMs on Hyper-V (across 4 hosts in cluster)
• VMs stored on flash SAN
• Off-domain, bare metal backup server
• On-site repository: Synology RS2423+
• Off-site repository: Synology RS2423+
• Off-site Veeam Proxy
• Site-to-Site VPN connection on symmetrical 1Gbps
• Backblaze B2 bucket (immutable)

Backup process:

1. Backup VMs to on-site repository
2. Backup Copy to B2
3. Backup Copy to off-site repository
4. Test restore backups quarterly (instant recovery)