The software is indeed promising, but the limitations of the unpaid version may be enough to tide you over to pay or uninstall it altogether, due to the constraints. Integration with popular cloud services such as Google Drive, Dropbox, and more, is also available, the process being very much the same. Thereafter, interacting with the Sync button will get the app to transfer the files that are not present in both folders. For instance, that can happen in the event that there were new additions to the source folder, while the backed-up version hadn't been updated. This is so you don't miss any of a file's contents when you back it up to a drive. After you first boot it up, you will be prompted to enter two folders via the intuitively designed menu at the top.Ĭlicking to analyze them will have the software proceed to parse through the contents you fed into it, looking for any file differences. The layout of the app is simple, making it easy to get the hang of navigating through it. But what if you wanted to back your data up to a physical drive, wanted to check if anything is missing, and even get the option to sync between multiple cloud services? GoodSync looks to deliver on those aspects, and the Free version provides a peek into its capabilities. As cloud solutions have seen a sharp increase in popularity and demand, a good amount of services happen to primarily focus on that part. The backup software available on the market is not of a small number. The process can get very busy because when you tend to work with multiple files and folders, you tend to inadvertently skip some. Still interested in getting one done by the way.Backing up can get tricky at times, especially when there are lots of files and folders involved. It might be a good solution, but my perspective is that a daemon based/docker based solution would be much cleaner. Interested, but don't have the time to invest. I've not done anything with Windows VM on unraid yet. I've been told by GoodSync support that the TCP based version of GoodSync is significantly faster - ergo a second reason to get a docker created for it. Recreating the share fixed the problem and now Goodsync works great. The general feeling being that the word 'documents' seems to have been a problem somehow between SMB 2.0 and 3.0. The fix turned out to be creating the share again. When 6.2.4 came out, I started to have errors as described in this post. I had used "documents" (note case) as the share name which worked fine in the past. I think, it turned out to be a problem with a sharename. I've had problems with SMB 3.0 support with unRaid in the past. Its the difference between running SMB and a direct TCP/IP app. Which makes sense, ergo my quest for a shining docker knight. Someone mentioned I should just install it in a docker. Goodsync support states that /etc/init.d must be present - and sure enough when I configure GsServer service as a daemon, I got a 'can't install service error'. rc.S loads the single user mode one-shot services and core system daemons, then it loads rc.M to start multi-user mode and load all other system services and post-boot scripts to configure the rest of the system. It uses two staging scripts, rc.S and rc.M, to load all necessary services as well as rc.local to load any extra daemons and services that may or may not use init scripts. I tried to install it command-line from the console, but the slackware base for unraid is missing /etc/init.d that Goodsync wants in order to install.Īs I've been told, Slackware uses sysvinit with BSD style scripting.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |