tayadating.blogg.se

1. #SONARR BACKUP UPDATE#
2. #SONARR BACKUP UPGRADE#
3. #SONARR BACKUP CODE#
4. #SONARR BACKUP SERIES#
5. #SONARR BACKUP WINDOWS#

#SONARR BACKUP SERIES#

Subtitles synchronization score threshold for series

#SONARR BACKUP UPGRADE#

I'm also happy to answer any related questions if I know the answer.Number of days to go back in history to upgrade subtitles (up to 30) I always welcome feedback on my posts, please contact me if you have any. If you have any problems with the script, please open an issue on the GitHub project.

#SONARR BACKUP UPDATE#

This release adds the job's processing speed to the report, adds an update checker, and brings an option (disabled by default) to mention the specified Discord user when a job fails. Īdapted my other project ( VeeamSlackNotifications) for Discord with various improvements and Discord-specific changes. įixed bugs introduced in the last release and updated instructions. įixed transferred data and total data stats.Ĭhanged name of configuration file and cleaned up the alert sender. Minor changes, mostly to config template. I've made a number of improvements to the way backups are reported, resulting in reports that look better and are much easier to understand. Powershell.exe -File C:\VeeamScripts\VeeamDiscordNotifications\DiscordNotificationBootstrap.ps1

Unblock-File C:\VeeamScripts\VeeamDiscordNotifications\DiscordNotificationBootstrap.ps1

#SONARR BACKUP WINDOWS#

The reason you may need to do this is Windows often blocks execution of downloaded scripts. If you don't want to do that, replace the script path in section 5 below with the following Powershell.exe -ExecutionPolicy Bypass -File C:\VeeamScripts\VeeamDiscordNotifications\DiscordNotificationBootstrap.ps1 You may also need to set your PowerShell execution policy to Unrestricted. Just make sure you replace only the Discord URL and nothing else. All you have to do here is replace the webhook URL with your own from step 3. Older versions of Notepad don't support LF line endings, so this file may look pretty fucked up, but it doesn't really matter in this case. Open the configuration file: notepad.exe C:\VeeamScripts\VeeamDiscordNotifications\config\conf.json If you'd like to use the avatar that I used, here it is. You'll see something similar to the following:Īs you can see mine has already been configured, but all you need to do is set the name, upload an image for the avatar if you'd like, then copy the webhook URL. I created a channel called "backups" for this service.Ĭlick "Edit Channel", then navigate to the "Webhooks" section and click "Create Webhook". Open Discord and go to the settings of the channel that you want Veeam to report to. You've now extracted the release and cleaned up the download. Remove-Item C:\VeeamScripts\VeeamDiscordNotifications-v1.5.zip Rename-Item C:\VeeamScripts\VeeamDiscordNotifications-v1.5 C:\VeeamScripts\VeeamDiscordNotifications Extract and clean up Expand-Archive C:\VeeamScripts\VeeamDiscordNotifications-v1.5.zip -DestinationPath C:\VeeamScripts If you receive this error, run the following command and then re-issue the above command. You may recieve an SSL error as in some cases winhttp uses TLS1 by default (depends on a few things), and GitHub appears to no longer accept TLS1. Invoke-WebRequest -Uri -OutFile C:\VeeamScripts\VeeamDiscordNotifications-v1.5.zip There may be later releases so take a look and replace the version number in the commands below with the latest if applicable. To make the directory run the following command in PowerShell: New-Item C:\VeeamScripts -Type directory 2. I will keep these instructions updated and in-line with current release as much as possible, but if something is out of date then please contact me. If I were Tim Cook, I would tell you that the project has been reinvented. I've now found a set of scripts that do what I did better and have forked the project to make a number of my own improvements to the Slack project.Īs of, I've adapted it for Discord and re-released it under it's own repository. A couple of months down the line I had a look in the logs, reviewed my scripts and realised it was actually an absolute mess and frankly quite shit. I thought this was running well as it looked good from the reports I was seeing.

#SONARR BACKUP CODE#

Version 2 was using some of my own code and some code from scripts I found on the internet. I started off by attempting to make my own scripts for this, but that didn't go so well, so I tried again. In a similar fashion to part 1, this setup has been running for a while and I'm very pleased with it's flawless functionality. Part 1 details notifications for Sonarr, Radarr and Lidarr. Part 2 of a Discord notifications series.