restic-windows-backup

Powershell scripts to run Restic backups on Windows. Simplifies the process of installation and running daily backups.

Features

• VSS (Volume Snapshot Service) support - backup everything, don't worry about what files are open/in-use
• Removable, External Drives - drives can be identified by their volume labels or serial numbers, making it easy to backup drives that occasionally aren't there or change drive letter.
• Easy Installation - install.ps1 script downloads Restic, initializes the restic repository, and setups up a Windows Task Scheduler task to run the backup daily
• Easy to update - update.ps1 script can be used to keep your scripts up to date with the latest release on GitHub
• Backup, Maintenance and Monitoring are Automated - backup.ps1 script handles
  • Emailing the results of each execution, including log files when there are problems
  • Runs routine maintenence (pruning and checking the repo for errors on a regular basis)
  • And, of course backing up your files.

Installation Instructions

1. Create your restic repository
   1. This is up to you to sort out where you want the data to go to. Minio, B2, S3, etc.. Refer to the restic documents about how to create your repository.
2. Install the scripts
   1. Create script directory: C:\restic
   2. Download scripts using the update.ps1 script.
      1. Open PowerShell
      2. Change your working directory to the installation directory

         cd c:\restic
         

      3. Run the update.ps1 script:

         Invoke-Expression (Invoke-WebRequest -Uri "https://raw.githubusercontent.com/kmwoley/restic-windows-backup/main/update.ps1" -UseBasicParsing).Content
         

      Alternatively, you can download the scripts from this repository and and unzip them into C:\restic
   3. Launch PowerShell as Administrator
   4. Change your working directory to C:\restic
   5. If you haven't done so in the past, set your Powershell script execution policy to allow for scripts to run. For example, this is a good default:

      Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
      

   6. Depending on the policy you choose, may need to 'unblock' the execution of the scripts you download by running Unblock-File *.ps1
3. Create secrets.ps1 file. The secrets file contains location and passwords for your restic repository.
   1. secrets_sample.ps1 is an example of the secrets.ps1 file. Copy or rename this file to secrets.ps1 and edit.
   2. Restic will pick up the repo destination from the environment variables you set in this file - see this doc for more information about configuring restic repos https://restic.readthedocs.io/en/latest/030_preparing_a_new_repo.html
   3. Email sending configuration is also contained with this file. The scripts are able to send email about the success/failure of each backup attempt.
4. Create config.ps1 file. The config file contains the settings that control how the script runs backups, forgets snapshots, and prunes the restic repository. It's important that you configure this file to meet your needs since it will be backing up and maintaining your repository.
   1. config_sample.ps1 contins an example configuration file. Copy or rename this file to config.ps1 and edit to suit your needs.
   2. Add your $BackupSources to config.ps1
      1. By default, all of C:\ will be backed up. You can add multiple root drives to be backed up. And you can define only specific folders you would like backed up.
      2. External, removable disk drives (i.e. USB hard drives) can be identified by their Volume Label, Serial Number, or Device Name. For example, if you have an external device with the Volume Label "MY BOOK", you can define a backup source as $BackupSources["MY BOOK"]=@(). It is recommended to use the device serial number to identify external drives to backup, which you can find using the Powershell get-disk command. You may also want to set $IgnoreMissingBackupSources=$true to avoid seeing errors when the removable drive is not present.
   3. Review all of the default settings in config.ps1.
      1. Most of the defaults are safe, but you should be sure restic is configured to meet your specifics needs.
      2. Warning - if you're using a shared restic repository across multiple machines, pay close attention to the $SnapshotRetentionPolicy settings to be sure this script does not intentionally destroy backup data in your repository.
5. Run install.ps1 file
   1. From the elevated (Run as Administrator) Powershell window, run .\install.ps1
   2. This will initialize the repo, create your logfile directory, create a scheduled task in Windows Task Scheduler to run the task daily, and install Send-MailKitMessage module.
6. Add files/paths not to backup to local.exclude
   1. If you don't want to modify the included exclude file, you can add any files/paths you want to exclude from the backup to local.exclude
7. Add C:\restic\restic.exe to the Windows Defender / Virus & Threat Detection Exclude list
   1. Backups on Windows are really slow if you don't set the Antivirus to ignore restic.
   2. Navigate from the Start menu to: Virus & threat protection > Manage Settings > Exclusions (Add or remove exclusions) > Add an exclusion (Process) > Process Name: "C:\restic\restic.exe"
8. (Recommended) To a test backup triggered from Task Scheduler
   1. It's recommended to open Windows Task Scheduler and trigger the task to run manually to test your first backup.
      1. Open Task Scheduler > Find "Restic Backup" > Right Click > Run
   2. The backup script will be executed as the SYSTEM user. Some of your files might not be accessible by this user. If you run into this, add the SYSTEM user to the files where you get "Access Denied" errors.
      1. Folder > Properties > Security > Advanced > Add ("SYSTEM" Principal/User) > Check "Replace all child object permission entries with inheritable permission entries from this object" > Apply > OK
9. (Recommended) Do a test restore
   1. These scripts make it easy to work with Restic from the Powershell command line. If you run . .\config.ps1; . .\secrets.ps1 you can then easily invoke restic commands like
      1. & $ResticExe find -i "*filename*"
      2. & $ResticExe restore ...

Updating restic-windows-backup

Use update.ps1 to update the installed restic-windows-backup scripts to the latest release.

1. Open PowerShell (no need to be Administrator)
2. Change directory to your installation directory (e.g. c:\restic)
3. Run update.ps1

update.ps1 Details

Running update.ps1 without any parameters will check for a new release from kmwoley/restic-windows-backup. If there is a newer release, the script will overwrite the local files in the script directory with the updated scripts.

• The script will not overwrite your local configuration files (i.e. config.ps1 or secrets.ps1).
• Any custom files created in the installation directory will not be deleted or modified (e.g. any custom action scripts, log files, etc.)
• The script will warn before overwriting any files that have been changed since the last installation.
• When update.ps1 is run the first time, it will prompt before overwriting (since it may not know the current version of the fiels installed).

update.ps1 Options

• -Mode <release | branch> (Default: release) - change if the script updates from the latest release or a branch of kmwoley/restic-windows-backup
• -Branch <branch> (Default: 'main') - When in branch mode, this parameter controls which branch to install from. Defaults to the main branch.
• -InstallPath <directory> - choose which directory to install the files into. Defaults to the directory that update.ps1 is in.

Backup over SFTP

You can use any restic repository type you like pretty easily. SFTP on Windows, however, can be particularly tricky given that these scripts execute as the SYSTEM user and need to have access to the .ssh keys. Here are some steps and tips to getting it working.

1. Install as above. Your repository should be created properly. Tasked backups will fail for now though. This is because the install.ps1 file is executed with your user, whereas the tasked backup will run as SYSTEM, which does not have any ssh config yet.
2. Open Task Scheduler and make sure the restic task is not running anymore by checking the active tasks
3. Edit config.ps1 and turn off the internet connection test: $InternetTestAttempts = 0 as the test does not recognize sftp addresses correctly
4. Copy the .ssh directory content from %USERPROFILE%\.ssh to %WINDIR%\System32\config\systemprofile\.ssh (This is the ssh config the SYSTEM account uses)
5. If you use a private key to access the sftp services it also needs to be in this directory. ssh checks the permissions though, so they need to be changed as well:
   1. Right click your key > Properties > Security > Advanced
      1. Change the owner to SYSTEM
      2. Disable inheritance and keep the permissions
      3. Remove all principals except SYSTEM and the Administrators group

This should get you up and running. If not, download PsExec, start a powershell as admin user and run .\PsExec.exe -s -i powershell.exe. In this shell you will be the system user and you can try things out. See what ssh user@server says or try cd C:\restic\; . .\config.ps1; . .\secrets.ps1; & $ResticExe check (If you get lock errors, remember to check the Task Scheduler for any running restic instances in the background)

Feedback?

Feel free to open issues or create PRs!