Leifgg

ChrashPlan has released version 4.5.0 and it looks like a minor update. From what I can tell, the CrashPlan Container and the CrashPlan Desktop container is still working. You should be able to see the update in the history.log when it has been done.

Happy to hear you got it working! Don’t know if you are aware if the PlexPass settings already…

Like the enclosed pic except for the server tab?

Not sure I understand… The WebUI is your server. Don’t you see your media and the same name for Plex as you hade before? Edit: Wait, I am probably mistaken, sorry! You probably need to go to settings in the WebUI and select Server and make the settings there same as you hade before.

I did the same some time ago. I believe I kept exactly the same settings for the container as I had previously and everything was where I left it when I started again. Have you stopped the Needo container? Do you get the Plex WEB gui?

Yes that’s possible but your files will be in a backup archive in a compressed format that only can be restored by CrashPlan.

New release 0.9.14.3 for Plexpass users is available.

Have a look a couple of posts back pls.

This is a "Plex" problem: http://lime-technology.com/forum/index.php?topic=42148.msg421493#msg421493

They have acknowledged the problem and promised to jump into it straight away. I got the feeling that when they looked at some logs from a user they understood what was going on. Has something to do with the implementation of the new transcoder.

If you are using latest version (0.9.14.2) there is a (known) problem with transcoding. I did revert to 0.9.12.19 to get it working.

That one should work, place it in /boot/extra It will be loaded when you boot your system.

Good question! The container itself will be reloaded from scratch again so there are no worries about that since it is basically static, nothing should get stored inside it. Regarding any data stored outside the container (the appdata share) I honestly don’t know but at least I have never had any corruption there either.

The Plex container from Linuxserver.io will be updated automatically if you restart the container. You will be notified in the Plex WEB Gui when an update is available. However, 0.9.14.x is a pre-release that isn’t notified since it is considered too early for everybody to use.

Basically there are two different scenarios. The basic concept with CrashPlan is like you do it now (?), like backing up single computer to the CrashPlan cloud or if you have the family subscription several computers (I assume you have CrashPlan installed on your Laptop). The implementation for unRAID is unsupported by CrashPlan but is basically a port of the CrashPlan app so that it can be used/installed in Docker containers on a unRAID server. The purpose of this is to be able to backup all files on your server to the CrashPlan cloud. I don’t know how the family subscription works but I guess that, since it allows several computers (max 10), connected to your account you could use two licenses for your PCs and one for a unRAID server. A common solution used is to have a single license subscription and install CrashPlan on the unRAID server. Then you setup a backup software on your PCs and let them backup to the unRAID server. With this setup you backup your PCs as well as the server to the CrashPlan cloud. There are different alternatives for backing up your PC to the unRAID server but SyncBackSE for Windows is known as a relatively easy to use. You can also use CrashPlan to backup to other computers and USB disks as well but what it does best is backing up to the cloud. Local backups are compressed backup archives with a property format that would need the CrashPlan app to be able to restore. Does this make sense or did I just make you more confused?

The CrashPlan Desktop container is only for configuring the backup and to monitoring the status. You can turn it off when not needing it, the CrashPlan container will continue to run and take care of your backup. The Windows client is actually a full client/server app (= both CrashPlan Containers combined) but when it is used together with the CrashPlan container the server part is not used and it works in the same way as the CrashPlan Desktop container. I am not sure I understand your setup; do you use CrashPlan on Windows to backup a Windows PC or do you use the CrashPlan container to back up your server?

The guide in my signature might be able to help you. If you are having trouble to get the Windows client to connect you can always install the CrashPlan Desktop container to get you started. Make sure that both the CrashPlan container as well as the CrashPlan Desktop container are updated and start the CrashPlan container first then the CrashPlan Desktop container.

Probably will make an update on the guide thanks to ljm42, just need to get my things up and running to do some testing

I am using rsync to make a backup once a week of the appdata folder on my cache drive to a folder on my array and let CrashPlan backup that folder. Here is a script that I run manually but it can be automated using a cron job. You could do the same with the flash drive but I believe that the array should be stopped before running the backup. I think I have read somewhere that unless you haven’t done that and do a restore unRIAD will run a parity check when you start the server. #!/bin/bash # # --- Syntax - rsync --- # -a archive # -v verbose # -r recursive (copies directories) # -t preserve modification times # -O omit directories from -t # -J omit symlinks from -t # -H preserve hard links # --delete delete at destination if missing at source # > Output to log file # >> Append output to log file # # --- Syntax - tar --- # -cf archive.tar file1 dir1 Create File (archive) with list of files or directories to include (path if needed) # -cvf Verbose # -cjvf archive.tar.bz2 Compress with bzip2 # -czvf archive.tar.gz Compress with gzip # # --- Syntax - docker --- # docker stop CouchPotato Stop a specific container # docker stop $(docker ps -a -q) Stop all containers # etc/rc.d/rc.docker stop Stop all containers and Docker service # docker start CouchPotato Start a specific container # /etc/rc.d/rc.docker start Start all containers set to autostart # clear # Set start time START=$(date +"%Y-%m-%d %T") echo --- Stop Dockers /etc/rc.d/rc.docker stop echo --- Start job: AppdataLocalBackup.sh echo -------------------------------------------------------------------------- echo --- Begin backup: appdata folder on cache drive to Backup share rsync -avrtOJH --delete --exclude-from 'exclude.txt' //mnt/user/appdata/ //mnt/user/Backup/appdata/ >/boot/logs/Appdata_local_backup.log tar -czf /mnt/user/Backup/appdata/Plex.tar.gz /mnt/user/appdata/Plex echo --- End backup: appdata folder on cache drive echo -------------------------------------------------------------------------- echo --- End job: AppdataLocalBackup.sh echo --- Start Dockers /etc/rc.d/rc.docker start # Set finish time END=$(date +"%Y-%m-%d %T") echo --- Start: "$START" echo --- Finish: "$END"

I thought crashplan clients auto updated? Just installed crashplan desktop and I'm getting the "disconnected from backup engine" error. Damn. Really wanted this to work. Only the CrashPlan engine container, not the CrashPlan Desktop container. Still possible to get the Windows client to connect to the CrashPlan engine container.

I believe that the Desktop Container isn’t updated yet to the latest version of CrashPlan.

CrashPlan is primarily intended for backing up files from a computer or a server to the CrashPlan Cloud (their servers) so that you have an offsite backup. You can do local backups as well from your PC to unRAID if you do some tricks http://lime-technology.com/forum/index.php?topic=17672.0 For doing the above you install CrashPlan on your Windows PC. However, you should be aware that your backup is in a compressed backup archive in a property format so you will not be able to do anything with your files except for restoring them with CrashPlan. CrashPlan does incremental backups as well as keep different version of your files depending on the settings you make. When you install CrashPlan on unRAID the primary reason usually to back up your server. There is a guide in my signature that explains this a bit more.

The recommended default mapping suggested (not mandatory) from unRAID 6.2 is said to be /mnt/user/appdata/crashplan for as system using User Shares. When you change mappings the Container gets downloaded again with version 4.3.0, that’s why it will go through the auto update again.

Never happened to me (heard that one before… ) Suggest checking the log located at your server in log folder at the location where your config is stored. Look for history.log and service.log to start with a see if you can get some hints there. If you see that the version is 4.4.1 that is a good sign. Basically poke around and look for logs with latest time stamps.

Was the server running when you made the changes to my.service.xml? If it was you probably need to restart the CrashPlan container. Then you also need to copy the new files to your PC as well. Have you Disable CrashPlan Backup Service on your PC?