![]() ![]() I'm trying to utilize my FreeNAS box (running a ZFS Raid1 array) as my means of being able to access my data. That said, I find myself living off of my CR-48 laptop now, which has a 16gb hard drive. I'm trying to be more green since, well, I'm too poor to afford these energy bills, so I set up a spare box that, according to my wattage meter, is CONSIDERABLY more energy efficient than my desktop. My desktop is a gaming rig, dual monitors, blah blah blah. I have a lot of raided setups so losing data isn't the concern. But the idea here isn't necessarily to have backups. So you thereby own the files you are writing to the local disk of your system. As the data gets written to your newly installed hard drive on your computer, you are writing the data as the owner logged in. So you log in as Bob and copy the files over. On the flip side, let's say your hard drive dies. So the files on the file server are thereby owned by. When you transfer files to it, those files take on the ownership of Bob since that's the user you're logged in as. Let's say your name is Bob, and you log into my FreeNAS file server as Bob. If the owner/group doesn't transfer, I really don't see how it matters. Again, I just want a reliable way to back up files. I have used it many years ago, but I'll try it now. Nonetheless, I will continue to use CIFS as I find it to be better suited for me. I can only hope something like BTRFS in the future has better support for this. That said, it is a little bit of a bummer that Linux file systems don't play too nice with CIFS and vice versa. I've taken even the largest of files and pushed/pulled them through both protocols to/from my file server, and in each instance they end the transfer within seconds of each other, which over a 20 minute transfer is remarkable that they can be so close. There is literally no difference in speed. I've also done a ton of speed comparisons with CIFS and NFS. I would only consider using NFS in a production environment if they bumped up security to at least require user authentication. CIFS at least has the security barrier there. I mean, I just can't imagine using NFS in a production environment. NFS, while simpler in design, has literally no security. I've done a lot of homework recently on NFS and CIFS. The man page offers full details, but I found a lot of good info on rsync examples by Googling around the web.Yeah, I hear ya there. Rsync is very powerful, but also very complex, and I am far from an expert on using it. ![]() But for me, it means that my backup is always perfectly synchronized with the source, which is what I want. Not everyone wants to do this, so you should consider the consequences of that option. The -delete option means that if I delete a file in the source between backups, then it will be deleted in the destination also on my next backup. I simply copy the commands from a text file (a BASH script would work nicely too) and paste into a terminal after making sure that I have the correct flash drive inserted (the destination: /media/stan/DBB0-4F8C/). Rsync -delete -avhs "/home/stan/Documents/ALL_eStatements" "/media/stan/DBB0-4F8C/" Rsync -delete -avhs "/home/stan/Documents/HomeBank" "/media/stan/DBB0-4F8C/" & Rsync -delete -avhs "/home/stan/Documents/MyKeePass" "/media/stan/DBB0-4F8C/" & so it would likely be slower on an external hard drive, or even worse over a network connection.įor my own personal rsync backup solution, I join several rsync commands together (concatenate) with & similar to this: I did this backup on the same hard drive and it took about 7-8 minutes. I ran it again with sudo and then it copied every file, but that makes root the owner of the backed up directory. Also, the command as given above neglected to copy 8 files (yes, only 8 out of over 330,000) due to permission problems. it was over 330,000 files and about 6 GB. I ran a test of the above command on my own /usr directory. I'm not quite sure that /usr is a useful backup for you, but that is your decision. ![]() If you put the trailing / it will only copy the loose files inside (and create quite a mess in your destination). That will copy the directory itself and all the contents. Especially note that there is no trailing / on the source.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |