Normand_Nadon

I will admit that I did not understand it all at first... My brain is not collaborating this week, I am sick! Re-reading it a couple times helped and it made a lot of sense! Do I understand it right that Unraid shows me: But in reality, this is all smoke and mirrors created by the sorcery of symlinks and in fact it is structured as such behind the scene Am I right to see it that way?

To save time, I activated the "root" option and it works fine I created a subvolume called ".snapshot" For some reason, it works... The full volume gets it's snapshot inside the .snapshot subvolume, and the .snapshot folder exists inside the snapshot, but is empty... maybe there is something in Unraid or BTRFS that keeps it from making snapshots of snapshots... can't tell!

I think I just answered myself

Ooooooooh! Thanks! Will the snapshot exclude the snapshot folder? (I don't want to snapshot the snapshot!)

Oooooooh! Thank you @primeval_god and @JorgeB !!! That is what I was telling you... Snapshots have been around for millennias, so all the documentation I could find was assuming I knew what a snapshot was from the beginning, from other types of filesystems! You can clearly see that I don't Would you mind pointing me to a clear procedure on how to that? My guts tell me this: rename all the shares as [SHARE'S NAME]_OLD, create subvolumes named as [SHARE'S NAME], move the data inside those subvolumes (should be near instantaneous as it is just re-mapping the location) delete the old share... Does it make sense ? EDIT: Oh... and how will Fuser manage that? I have shares that are splitted between the cache and on the array

I can't help you get less confused! I have no idea what I am doing! Here is what I want to do: I want to take hourly snapshots of the entire drive, and be able to recover if ever I make a stupid mistake... I know snapshots don't replace backups, but I don't want to make as many backups as I take snapshots, if it makes sense

@primeval_god, I don't know what I am missing, but when I navigate to the individual snapshot folders (either from the plugin, or from the terminal) all I see is all the preceding snapshots, but no file... I really don't get how it works!

First of all, thank you @primeval_god, in 12 or so lines, you made this a million times simpler to understand for me! I have been trying to understand the concept for days! (I will admit I need to google COW and what it means... but 95% of you explanation was clear to me!) But what is the meaning of this then? Does it apply only to remote sends ? Amazing! I will experiment on this and report if I still need help!

First of all, thanks for the amazing work on this plugin! Here is my question now (with context): I have been using Unraid for several years now, but I just got interested in BTRFS snapshots (after destroying a lot of data due to an error I made... A noob error that should never have happened!) All the documentation I could find is aimed at people who already know what filesystem snapshots are and how they work... I don't! My use-case is: To be able to roll back a few hours in case I screw-up... the rest is managed by daily replication of data with rsync on another server and some other backup strategies. There is a lot of movement in the week on this server as it syncs with work related stuff, so hundreds of files might change/be created per week. When I create snapshot on a schedule, the default value is to base it on the previous snap. What am I supposed to do if I want to only keep a week worth of hourly snapshots, with auto-deletion of older snaps? Won't deleting a previous snap destroy data? How does one roll back a file, folder, or a state of the file system on unraid? We don't have Timeshift or other cool GUI stuff like that of which I am aware. Can it be done while the server is running? Do I need to mount the disk on a live boot and use Timeshift? Feel free to send me obvious guides that I might have missed (Esspecially in the form of videos if available) Have a nice day EDIT: All my snapshots are directly on the filesystem from which they originated for the moment. I don't send them to a remote. The goal is to roll-back files if I screw-up something, not back-up the entire drive on a server on the moon for preservation.

if the mongo container is on the same network as the rocketchat container, you can also do: mongodb:27017 (you have to write it exactly the same way you named the mongodb container... avoid capitalisation and special characters... it sometimes causes issues)

why do you add mongodb:// before the ip? Normally you would just set the ip and port...

I found a way... can't tell if it is the right way, but it works! I tried comparing the way network worked on my personal workstation with virt-manager to check why it worked here but not on Unraid. I ended-up manually typing the network interface settings in the xml and it worked! So, basically, doing a direct connexion to the br0 bridge... The UI does not have this option.

This is he config in the VM if it can be of any help

So, I wanted a little bit more network bandwidth from my Unraid Server to the LAN. I added a reclaimed 4 NIC card to the server and configured 2 links in bond mode 0 (balanced-rr) The speed on NFS is almost 2Gbps, same for docker, works amazingly. The only thing that refuses to work, is that once I activate bonding, nothing that I do will make my VM function with br0 as it used to... All other services happily use br0, even docker. The VM is set with br0 and virtio-net, as per recommended in the manual. This is not working... the VM refuses to talk to the network. If I set it to virbr0 it will work, but I lose access to the local network What can be done to have my VM work on br0 or any combination that would give me access to the LAN as weel as the Internet?

hello @guy.davis and thank you for your work. I was wondering, why is Machinaris taking so much ressources on my Unraid Server? I am farming only, and the hard drives are in the same machine, mounted directly inside the container. Fuse is not used for those drives, they are directly mounted as /mnt/disks/farmer## (4 x 6GB HDD) Machinaris takes anywhere from 6 to 8 GB of RAM and makes regular 100% spikes on cpu cores... What explains this behavior?