Thanks, all - I will give Urbackup a try.
What's the consensus best practice for backing up a Windows box to OMV?
I've used Crashplan in the past, but for a lot of reasons I'd like to find a lower-friction alternative.
And we all should be grateful for this since there is a million of SMB shares publicly available on the Internet without any restrictions
I get the problem (really). I suppose one could quibble whether the client is really the best place to address the issue, but that's neither here nor there.
That said, I do have a specific use case (small number of public, static files, well-protected LAN, highly transient user base, SMB1 banished from the premises) that would make this ability desirable. I'm just looking for a definitive answer on whether it's still possible.
I am now using a virtualbox Ubuntu on the server to download and to copy the data to the server (same machine) via smb mount.
after some gb it cancel with an error. why?
So your VM and your SMB server are running on the same physical machine? If so, you may be thinking that it's bypassing your physical networking equipment entirely, and thus ruling out a network hardware problem. This may not be the case, depending on how you've configured your virtualbox networking. If you're using bridged networking (virtual and physical servers all have IPs on the same subnet) the IP packets are still going out over your network, hitting your router, and coming back to the exact same NIC (but addressed to a different IP). So if you're thinking you've taken network hardware out of the equation - not necessarily.
I agree that you have a network problem. Replacing cables is the easiest place to start. If you can't easily swap out routers and switches, at least try powering everything down at the same time, and bringing it back up. Routers and even switches can sometimes lose their minds if they run for months and months without a reboot. If you start getting >930 mbps in iperf after restarting the network gear, keep an eye on it - you may find that you need to restart a specific router/switch every month or two (which you might be able to live with). Or you might find you have to do it every day or so (or every hour or so), which might drive you to replacement sooner.
Simple requirement: I'd like to be able to access a Samba share from any stock, unmodified Windows 10 machine with NO login and NO password. Years ago this was easy, but Microsoft has made it progressively harder with seemingly every update. Is this even possible these days?
I have read dozens and dozens of forum posts (here and elsewhere) to no avail. Most are outdated because Microsoft keeps changing things.
My sense is that this is no longer possible without making local group policy changes to the Windows box (which defeats my purpose; I want anyone with wifi access to be able to easily read (only) these files). But I've never gotten a definitive answer on whether this is the case. Does anyone know?
If it is possible, can someone point me to a definitive, up-to-date tutorial on it?
Just some opinions/thoughts
My personal take on the SBC NAS topic is:
- 1 SBC combined with 1 HDD. With this setup I even consider using USB storage with USB-to-SATA bridges known to work well
- When it's about to attach 2-4 HDD to a host and comparing overall costs some x86 solutions look more appealing than a RK3399 + PCIe SATA HBA + custom enclosure + custom PSU -- though a lot higher idle and active consumption
- NanoPi M4 + SATA HAT are a perfect upcylce attempt for an already existing NAS or PC case with 2-4 SATA slots (due to avoiding waste I would always try to use an old PC or NAS case with such a tiny 'NAS core' like M4 + SATA HAT)
- Performance difference between a 9215 and a 9235 with spinning rust in your setup will be negligible (with SSDs or arrays the 9235 clearly outperforms the single lane 9215)
Thanks! I'm leaning towards the M4, and your take on the 9215 makes me a lot more comfortable with that choice.
Great points about x86 - I'm going SBC for this project for not-terribly-practical reasons: (1) I'm going to build a custom oak case just because I like doing that sort of thing; (2) I've got a ton of castoff PSU components I can repurpose; and (3) I just like playing with SBCs.
Looking forward to getting started! I'm sure I'll have a ton of configuration-related questions later, but for now I'm going to the lumber store.
Thanks for the advice!
I've been researching SBC NAS options; I've spent a lot of time on this forum and have learned a lot - it's a great resource.
I'm looking for an ARM board configuration that will support multiple spinning-rust drives (not RAIDed) and possibly run a light-duty web server or Nextcloud in the background. I'd like to be able to saturate GbE and have decent local HDD-to-HDD transfer speeds.
The Helios 4 looks nice but it's a bit pricey and perhaps still experiencing a few growing pains. The RockPro64 and NanoPi M4 both look pretty good, and I assume will perform similarly given they have the same SOC. The NanoPi gets rave reviews for reliability and support, and the size is nice, but I'm not thrilled with powering it via USB-C. OTOH the RockPro64 supports faster SATA chipsets through its PCIe slot, and is a little cheaper if you compare 4GB versions.
Q1: Any thoughts between these two boards? Other boards I should look at? (There's not too many multi-SATA options that I've seen.)
Q2: Will the NanoPi M4's SATA hat (Marvell 9215-based) bog down on multiple drives?
Q3: If I go with the RockPro64, is a Marvell 9235 like https://www.amazon.com/CREST-D…ell-Chipset/dp/B00AZ9T41M the best choice, or is there another chipset worth looking at?