TimTheSettler

Here's a historical benchmark for you. You'll notice that I replaced the two 18TB drives with two 14TB drives (hence the reason for the parity sync of the two 14TB drives on Sat and Sun in the middle). Note that one of the parity checks took four days. If the server is in use during a parity check then the check will take a lot longer. These are all Exos drives.

Add the following to your SMB settings. https://forums.unraid.net/topic/84988-smb-settings-to-force-nobodyusers/

That's how I understand it. The daemon is restarted so that a new log can be started.

When drives appear, disappear, and then reappear it could mean the drive is dying but could also mean that the cable is broken or not connected properly. I've had this happen to me in some older systems I've had. It could be that I played with the cable a few too many times and I ruined the wires or it was a crappy cable to begin with. Once I replaced the cable the drive came back and ran beautifully for a few more years. I've also had cases where the drive appears to be getting errors and then I move it around to another drive bay or put it into another computer and then everything is ok. The errors (usually bad sectors) are re-evaluated and are not bad sectors after all. There seems to be no rhyme or reason sometimes. Thermal shock and excessive heat are what usually kills components. My oldest working hard drive (shown below) has been running continuously for over 12 years.

@BobNik @adminmat @ConnerVT @nraygun Hi guys. I was curious about this myself and here are some things that I found. As you can guess the apcupsd daemon controls the UPS communication. The number in brackets is the process ID of that daemon process. It seems that, on a weekly basis, the old process [524] is destroyed (exited) and a new process [13221] is created. Obviously your process numbers would be different from mine. This weekly restart process is controlled by "logrotate". You can find logrotate.conf in the "/etc" folder. Basically the logrotate config file is run and then all scripts within the logrotate.d folder are run. In the /etc/logrotate.d folder you'll see apcupsd which contains the following commands. The rc.d is a folder that contains "run commands" for daemons. More info here --> https://linux.die.net/man/8/logrotate and https://forums.unraid.net/topic/119894-resolved-problems-with-apcupsd-starting-at-regular-times-when-disabled/ The UPS Self Test is a test that the UPS performs on a regular basis and the apcupsd daemon simply posts the results to the log. It's interesting my settings show SELFTEST = NO and yet my UPS still does a regular Self Test. Maybe just a bug with apcupsd. See this for more info about the Self Test --> https://www.apc.com/ca/en/faqs/FA405317/ Note below in the screenshots that everything in my settings jives with the logs especially the power failure at 6:50:34 lasting for 2 seconds.

"Belongs to them" has a few meanings. Any data that's "out there" is "out there" which means that it's sitting outside of your network so Mr. Grey is partially correct simply because someone else has it. What they do with it is another thing. If Google or some other site says that it's your data then that's all well and good but they still have your data and you need to trust that their network doesn't get hacked and then your data is no longer yours alone. This is why I like the idea of using a cloud service but having the data encrypted which is what apandey is doing. Even if the backup site is hacked your encrypted data has no meaning to the hackers.

I wouldn't bother if you're just a typical home user which many people here are. However, there are some nice benefits that @itimpi has mentioned. Bit rot detection is nice but a rare occurrence and hard drives are designed to catch this so is it worth it just for that? Maybe. ZFS also has snapshot but would you use that? No. The one thing that I like is that ZFS supports inline compression such that when you save a file it's compressed and then saved to the disk in the compressed state. This can save some space for you. However, you need to keep in mind that reading and writing files requires the extra step of compressing and decompressing it. Will unRAID support that feature? I'm not sure. Another cool thing is deduplication but this requires massive amounts of memory and some planning of file block sizes since the file block determines how much memory is used to keep track of all the blocks. There are also ways to improve performance like ARC/L2ARC and SLOG/ZIL. Are you confused yet? Join the club. It's not an easy file system to just plug in and use. So when you take all these "configurable" parts away you're left with "just another file system". So for now I don't see a benefit but as people use the file system and other smart people make it easier to use and/or set up then it will become "the next best thing". This is what I'm hoping for. I see the array or caches as being synonymous with a ZFS vdev. The drawback is that you need to think about your setup before you build your server whereas right now it's all pretty simple with unRAID which is what I love about unRAID. Forgive me but I think the following is a great explanation of ZFS. The link is to TrueNAS. Someone here needs to write up something similar but with reference to unRAID once ZFS officially shows up for unRAID. https://www.truenas.com/docs/references/zfsprimer/

Basically everyone's suggestion here is correct in one way or another. As Aran points out, syncthing is a synchronization tool. It's sort of like a backup in the sense that you have another copy somewhere else and it's even possible to snapshot the data but it's not a true backup. The reason why all the suggestions are right is because you need to get the data off the phone and syncthing is the easiest way to do that. Set it up so that your phone is a device and your unRAID server is a device and then link the pictures on your phone to a folder on your unRAID server. That will mirror the pictures from the phone to the unRAID server. Next, you should set up duplicacy or Vorta and then back up the pictures folder that's on the unRAID server. That's the true backup and those products will create efficient snapshots for you (using deduplication). So, whenever you take a picture on the phone it's get synchronized to the unRAID server and then backed up. If you accidentally delete a picture on the phone then that deletion is synchronized to the unRAID server and the file is deleted but Duplicacy/Vorta will have a snapshot of that picture from a previous backup (assuming the backups are frequent enough). You can then restore the picture from the backup.

I'm not a command-line guy so I would go with #1.

Parity is redundancy which implies duplication. So parity is a form of backup. Parity also helps in the ease of recovery. But other things can happen to that server or the data so a separate backup server serves a few more purposes: Separate hardware (complete server backup) Offsite location A snapshot in time (history) Many people say, "I want to back up my data", and then there are lots of ideas about backup software, parity, multiple machines, etc. Backing up your data is about protecting your data and backup is only part of that protection (encryption and access to the data are others). A good backup strategy involves multiple parts and parity is a nice, easy, and effective way to get started. But I digress because we've already established that people here are using parity in their main servers. Do you need it in a backup server? Only if your backup data contains important info not held elsewhere (like the snapshot history for me).

I'm glad it works for you guys. As you can guess, I'm paranoid. Burned too many times and don't have time to deal with massive restores. On one hand I love to putter around and try new things but that's my hobby time. When something fails and I rely on it then it cuts into my real life and that's too valuable. In the end I feel that a few hundred bucks is cheaper than me tearing my hair out at 3am after six hours of trying to fix/recover from a problem that came up.

Point noted, good to know. I was mainly comparing unRAID to TrueNAS.

No parity? On a backup system? Interesting...

His 5 Pros are: Resource consumption - Agree ZFS Support - Who cares? I wouldn't list this as a plus (or minus). It's just a feature. Hardware requirements - Agree Parity - Agree GUI - Agree His 5 Cons are: Transfer speed - Maybe Learning curve - Disagree (Thanks to the GUI) although a wizard to get you started would be a nice addition. ARM support - Really? Single Admin - Seems like a good point but I'm on the fence. Not free - Free is nice but it also means that it might not be supported very well (or at all) down the road.

Two things to consider with pictures on phones: You'll want them backed up. At some point the phone will run out of space. The easiest way to solve the "running out of space" problem is to buy a microSD card and add more space. This might not be possible or it might be too expensive. The other thing that solves both problems but requires a bit of work is to install syncthing on the phone and your unRAID server. Link the folder on the phone to a folder on unRAID (full bidirectional sync). When the phones are on the same network as the unRAID server (in your house - easiest/safest solution) then the photos are synchronized between the phone and unRAID. Once in a while you or mom or the wife will need to move photos from that folder on to another folder on the unRAID server. This way the photos are still archived and sitting on the server but moving them out of the synchronized folder means that they are also removed from the phone thereby freeing up space. So, just to clarify a bit here. Each phone has a corresponding folder on the unRAID server. Then, once in a while you move the photos from each of those folders to an archive folder somewhere else. The easiest way to clean up the photos is to find a family event like a past birthday and move all those into a folder just for that event (like an album). The drawback is that they are off the phone but if you're running out of space then so what. Your "photo album" (folder) is still on unRAID and can be accessed. Personally I have ALL photos synchronized to ALL my devices (phones, tablets). We're talking about 77,000 photos (250GB). I just make sure that any new phone I buy has a microSD slot and then I buy a 256GB (or 512GB) card. Now I'll never run out, I have all photos available to me, and everything is backed up. (Make sure to encrypt the card when you first put it in.) Actually my setup is more sophisticated so read on if you're interested. There's the camera folder on the phone and a separate pictures folder. The camera folder is bidirectional sync which means that changes on either side are reflected back to the other device/server. The pictures folder is one-way sync from unRAID to the phone. All common pictures are put into the pictures folder and these are pushed to the phone. This means that the phone has all family photos. When you take a picture on the phone it's saved to the camera folder. The camera folder is specific to the device but is synchronized to unRAID as a backup. At some point you manage the camera folder (on unRAID) by moving photos from the camera folder to the pictures folder (like all photos for a birthday). This moves the photos out of the camera folder on the phone but pushes them back up to the phone and into the pictures folder. The benefit here is that each person takes their own photos but by moving the photos from the camera to the pictures you are sharing those photos because the pictures can be replicated to all devices. If you're not sure if this makes sense but you're curious about how it works then I can explain it better with a diagram but if no one cares then I won't bother with diagrams. In the pictures above note that camera folder is two-way sync between the camera folder on the phone to unRAID (left pic). The right pic shows a one-way sync from unRAID back up to the phone into the pictures folder on the phone. Your photos app (Google Photos or Samsung Gallery) will show all pics in both folders.

Appdata once a month (automated). Flash drive every three months or so (manually). All data (documents, pictures, media, etc.) (~28TB) synchronized real-time (syncthing) between four servers in three different locations with daily backup (Vorta/Borg).

That's cool. This is probably a stupid question but how do you do that? Not to take anything away from @Hoopster and rsync because I like that solution, especially the logging/email part, but I really like the backup software I see out there. Since Vorta/Borg (and others) use dedupe it's pretty efficient and there's a history of file locations if files are moved around. I used to have files in six different places and couldn't remember why I had them there and they were taking up lots of space because of that. My backup runs each night and I have a detailed prune cycle so I keep daily info for a couple weeks then weekly info for a few months then monthly info for a couple years, etc. My largest archive is 25TB so it runs pretty good at that size (although if you add a TB of data it can take a day to process all that). Here's an example of a couple movie folders that I renamed. In the end they don't take up any extra space and I know what happened if I wonder about it later. Also, thanks to @Aran and @Hoopster. As @ConnerVT points out, your suggestions are gold. I love the remote management.

Do people actually say "WD"? It sounds weird.

Most backup software uses deduplication which is really nice.

I'm using Vorta (Borg). You can use it on your regular server and point the Vorta container to your backup server as a target. However, I do something a bit weird. I syncthing my data from my regular server to the backup server and then back up that data using Vorta. So the backup server has two copies of everything, one that is synchronized and the other is the backup. The drawback is that you need double the space. The good thing is that it's easy to restore (because syncthing repropogates everything back to all the other servers and all the work (Vorta backup process) happens on my most powerful server (the backup server). In your case I would just use the backup server as a target. Bring it up, run Vorta on your main file server so that the backup server gets a new copy, and then shut down the backup server until next time.

The answer might be somewhere in the forum topic quoted above but I find that some of these topics have lots of info and suggestions and in the end it's hard to know what needs to done. People just post a link and say "It's in there." but where in there is it? Maybe @Squid can help to point out what exactly needs to be done for you in 6.9.2.

I'm assuming that the xbox is using DHCP to get an IP address from your internal network. In this case the DHCP server is going to send back a gateway IP address which is usually the IP address of your router. The xbox then sends all external traffic (outside of the local network) to the gateway. In this case you need to set up the VPN connection on your gateway device (the router). If the router supports the VPN service then you're laughing and you just need to set it up. If the router does not support this then you can go through the unRAID server but now you need to tell the xbox that unRAID is your gateway and you need to set up the unRAID server to talk to the VPN service. No one can really tell you the exact steps because no one is privy to the exact setup that someone might have at home. The best you can do is to understand the basics here and then use the many, many guides that exist out on the internet to figure out how to make it all work for you.

I'm definitely not an expert in this but a VPN is an encrypted tunnel that you set up between two machines. Usually it's from one network to another network (LAN over WAN, like the internet, connecting to another LAN). Typical uses back in the day were to connect your home computer to your work's network or for a work site to connect to another work site. The benefit, if the routing is set up properly, is that each device appears to be connected directly to each other even though there might be a vast distance between the devices. The secondary benefit (although it's become the primary now) is the encrypted communication between the devices. Nowadays people use a VPN like IPVanish to hide their IP or to encrypt all traffic across the internet. I personally don't bother with this for the following reasons: Encrypted connections are slower than normal connections and require extra processing on either end to encrypt and decrypt the the data. A long time ago the processing needed to encrypt/decrypt was a problem but nowadays it's a moot point because processors are more powerful or encryption logic is added to the processor (https://en.wikipedia.org/wiki/AES_instruction_set). But the connection is still technically slower because encrypted data is usually larger than the data you're intending to send and encrypted data does not compress well or at all (https://docs.actian.com/vectorhadoop/5.1/index.html#page/Security/How_to_Compute_the_Width_of_Encrypted_Data.htm) although this also tends to be a moot point nowadays. If I truly need an encrypted connection then I ensure that I'm using an SSL connection (HTTPS). If you're connected to a web site using SSL and you're using VPN then you're double-encrypting your data (which is ok but unnecessary). The end-point of your VPN tunnel (IPVanish) decrypts your data and therefore knows what you're doing. You need to ensure that they respect your privacy. Some VPN companies will log your activity while others won't on purpose. Note here too that your data is still going to the destination website as cleartext (unless using SSL) but it now appears that you're a member of the VPN's local network. In other words your IP has changed. There's an extra hop to the VPN for all connections. Instead of being connected directly to your destination you first go through the VPN provider's servers. So what's the point of the Wireguard VPN that's integrated into unRAID? The idea here is twofold, you can access your home network but also your home server becomes like the IPVanish server. In other words, you connect to your home machine and all data sent there is encrypted and you appear to be a member of that local network. Usually it ends here and the goal is to simply access your home LAN from a remote location (like the coffee shop) but with the added benefit that the connection is encrypted and secure. The other benefit is that you can access your home devices, media, and data remotely so it appears that you're at home even though you're somewhere else (in another country perhaps). Now your home VPN connection appears like the IPVanish connection. The biggest drawback to using it this way is that all data traffic is going to your home network first and then out into the world. This means that your home bandwidth is used a lot (lots of data being routed into and out of your home internet connection). If you're trying to set up a VPN connection from the unRAID server to IPVanish (which is what you're trying to do) then you need to search for "IPVanish Linux client" (https://www.ipvanish.com/vpn-setup/linux/) and install the client on the server and then you need to set up the routing so that all connections go through there. If it's done right then all data sent out from the unRAID server goes through IPVanish. In this case the end server that you're connecting to will see you as a device on the IPVanish network. So if the IPVanish server is in the US then it appears that you are also in the US. Keep in mind that all connections will now go through this IPVanish server which means that you have an added hop to this server.

I might be missing something here but I have Plex running as a docker on my unRAID server and I do NOT have a Plex account at all. I'm able to view all my local content using the Plex app on my Roku device. Once in a blue moon (very rare) I get a window showing up that tries to get me to sign up for an account but I just bypass it. One note is that I can only access the server locally. I have VPN access between all my servers and I'm unable to get to the GUI remotely but that all makes sense since I don't have an account.

Interesting that the new NT version is very similar to the existing Exos drives. Seagate Datasheet comparing the NE and NT versions (20TB and 18TB): https://www.seagate.com/content/dam/seagate/migrated-assets/www-content/datasheets/pdfs/ironwolf-pro-20tb-DS1914-21-2206US-en_US.pdf Seagate Datasheet for Exos drives (20TB and 18TB): https://www.seagate.com/content/dam/seagate/migrated-assets/www-content/datasheets/pdfs/exos-x20-channel-DS2080-2111US-en_CA.pdf Product Manual for Seagate NT drives (22TB and 20TB): https://www.seagate.com/content/dam/seagate/migrated-assets/www-content/product-content/ironwolf/en-us/docs/204482900b.pdf