![]() And I’m sure the other apps work well for some folks. ![]() Likewise with the sftp backup.īorg is good at what it does. I can mount the GPS restic backup with a single restic command, no problem. The first backup to GCS using Restic took a few days (~150GB), then I simply deleted the Borg buckets. Some background info - backup size for the entire platfrom is currently about 850 GB, with most of the data being contributed to by user Nextcloud data. I especially like having the SFTP backend, which I use to run a daily cronjob backup of a 100 or so important files to my VPS. I have Cloudron installed on a Netcup VPS, and am having trouble setting up a reliable backup strategy that works on a consistently while being cost effective. I re-wrote my backup scripts to use Restic and they were 60% smaller. I was amazed that it had all the features I wanted and was easy to use. So then I tried Restic, which I didn’t know much about. One of the apps dropped dot-directories everywhere it went. Many of the command-line specs were overly complicated, with too many advanced setttings that I didn’t care about. Some required you to provide a new version name every time you did backup (instead generating one automatically). More than one had no -exclude-if-present feature, which I needed (note: old-fashioned tar has had that feature for years, as does Borg). Some required a password file and and you had to keep track of where you stored that (instead of just a password). One of them forced you to run local and remote backups (even if you only wanted to run a local backup that day) I found I could get around this with a cryptic environment variable. For example, some didn’t have a mount feature, or the mount only worked on the local side. So I tried Duplicati, Hashbackup, and then Duplicacy. So that got me thinking about switching to another backup solution, one that had backends (GCS, S3, sftp, etc.). So I had no way to check the backup except to download them all and check them locally. Then tried to borg-mount that (which I had done before) and it failed with a cryptic message. One day I wanted to spot-check the cloud backup, see if my files were really there. I wrote a long shell script to run Borg to the USB HDD, then ran rclone-sync of the Borg repo files to GCS. I used Borg for a few years, for backup of my home PC to local USB disk and to Google Cloud Storage. The Scoop wiki has a nice write-up comparing Scoop and Chocolatey.Hi, just a quick note here to say thanks for Restic ![]() While some of these tools may be available through Chocolatey, the Scoop ecosystem is designed with such tools in mind. Scoop also seems natural for installing command-line tools that you might miss from Unix-like systems, such as Linux or Mac. If you do not have Admin access to your system (for instance, this is a shared server with Remote Desktop access), then Scoop is the right choice. Apps will not by default show in the start menu, and if plugins or addons expect to find the installation in a certain directory (looking at you, OBS Studio!), there will be some inconvenience and tedious setup. By default, it installs packages to ~/scoop/ and this is both a strength and a confusion point. Scoop is designed for developers who have an affinity for Unix. In an Admin-level PowerShell window, the following should work, provided you have set the ExecutionPolicy as above:Įnter fullscreen mode Exit fullscreen mode Scoop: non-Admin by default, installs in user directory The applications will have shortcuts in your start menu, and possibly on your desktop. In general, installing one of these packages, such as Google Chrome, will require elevated Admin privileges, and will install it where you would expect (likely C:\Program Files\ or C:\Program Files (x86)\). Chocolatey: conventional install locations, as AdminĬhocolatey can install from a community repository with thousands of packages. This policy will "win" when you are logged in. The second line means that all scripts and configuration files downloaded from the Internet must be signed by a trusted publisher, but scripts you write yourself will work, for the current user. The first line means that all scripts and configuration files on this computer must be signed by a trusted publisher, even if you write them yourself. Enter fullscreen mode Exit fullscreen mode
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |