-
Posts
408 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Leifgg
-
-
Hi...
Well, I just went to take over the backup for the other machine and all seemed to be working. Even if I look on-line at my account I can see the server name is now the name of that backup set.
However, it also seemed to have done an upgrade or something. I did not notice the version it was...but now it is ver 4.4.1 and it reads "Unable to connect to the backup engine" when it is trying to start. I have restarted both dockers and have the same issues.
Suggest you stop both containers. Then start the CrashPlan container and wait a few minutes and then start the CrashPlan Desktop container.
If you check the latest history.log you will probably find that it actually has updated the CrashPlan container to 4.5.0
The CrashPlan Desktop container doesn’t update itself but should work with this version.
-
Hi...
Ok, I am wondering as I could not seem to find the answer. Is this only to allow another machine to use crashplan to backup to my UnRAID server or does this allow for me to select directories etc to send to a CrashPlan cloud backup server?
Right now I use a separate Windows machine that is mapped to the unRAID server that sends files to the CrashPlan cloud. I am looking to remove that machine and I am looking to be able to send files to the CrashPlan cloud. (IE, our PHOTOS share.)
Thanks
The CrashPlan Docker container is primarily intended to backup files on your unRAID server to the CrashPlan cloud. It can also backup between folders and to/from external drives and other servers using the plugin Unasigned Devices.
The CrashPlan Desktop Docker container is used to configure the backups and to monitoring them.
Docker containers requires unRAID 6.
If you are backing up your unRAID server today using CrashPlan on Windows, you can adopt CrashPlan to use your new configuration meaning that you keep your current backup so you don’t need to start all over again.
If you have used Docker containers before its relatively easy to setup, in not it will take some effort to understand the concept.
There is a guide in my signature that might be useful to have a look at.
-
Plex has been updated and should work. Latest PlexPass version is 0.9.14.4. Regarding transcoding to RAM I haven’t enough experience to give any advice since I mostly can use Direct play.
-
The easiest way to use CrashPlan is by using the CrashPlan Docker container and the CrashPlan Desktop Docker container. When I tested this two days ago it was still working after the update to version 4.5.0 but after checking this one more time today it doesn’t. Basically it worked as long as I didn’t restart the CrashPlan Desktop Docker container but after I did that that, the CrashPlan Desktop Docker doesn’t start.
I believe that the update did brake the CrashPlan Desktop Docker container and that the maintainer of these containers need to look into this and hopefully make an update to the latest release.
Edit: Some more testing done, after restarting the CrashPlan Desktop Docker container a few times its up and running again and everything looks ok.
-
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.
-
-
-
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.
-
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.
New release 0.9.14.3 for Plexpass users is available.
-
There are two folders inside the Handbrake Container, Output and Movies.
- The Output folder is directed to /mnt/cache/videos/AVI/ (on your cache drive)
- The Movies folder is directed to /mnt/user/videos/AVI/ (on your array)
If you want both the Output and Movies folder directed to same location you need to change the mappings.
Edit: I looked a bit more into this and your mappings are actually correct (but a bit confusing). For clarity I would use /mnt/cache/videos/AVI/ for both Output and Movies.
Also make sure that the share videos is set to Use cache disk: Only in Share Settings. Otherwise the Mover could move your files to the array.
The default settings for the Destination is set to nobody as default so you need to change that to the Output folder. Click the down arrow and select Other and browse for the Output folder.
Tested your config and input and output files are in same folder.
- The Output folder is directed to /mnt/cache/videos/AVI/ (on your cache drive)
-
Haven’t used this Docker for a while but check if you selected the Output folder in the Handbrake GUI as well.
-
Plex is not playing anything anymore and unsure where to start my troubleshooting. Here on the site of plex support forums. This all happened when i tried to upgrade to the newest unraid version. My reboot got hung up and it last a few hours, the drives wouldn't unmount. I did a hard reboot and plex doesn't work anymore but i have the upgrade to the newest unraid version and even put a new plex docker build.
Have a look a couple of posts back pls.
-
-
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.
-
I am a little confused, what is the best way to install perl and which version should I install?
I think the old way. http://mirrors.slackware.com/slackware/slackware64-14.1/slackware64/d/perl-5.18.1-x86_64-1.txz Into /boot/extra .
This means just putting "perl-5.18.1-x86_64-1.txz" in /boot/extra?
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.
-
hey, i'm new to plex on unRAID, so first up, thx. alot for peoples time to bring it to unRAID and supporting it. i appreciate that alot, 'cause i know how much work (time) is involved.
just installed it and got it running, albeit not tested every feature. basically it has my library (before on Mac), all paths corrected to new unRAID location and a first test (using PHT on Mac) to check that it streams (locally). that works.
now, i'm curious, how the update feature (Plex Pass member) should work, or better said, how i should expect it to work. alle settings are correct, it searches for PP-releases) and says it's up-to-date - currently 0.9.14.1. on plex.tv's website the latest is one increment higher (as of today 0.9.14.2.1547-60c867f; released 17th of nov.).
my understanding was/is, that linuxserver.io implementation of the plex-server allows for direct updating, without any work on the maintainers site. is this correct? or does the maintainer-team need to update urls (or anything behind the scenes) to allow it to see it a new release?
and (solely my personal interest) on which platform is this plex-server container based on (in comparison to plex.tv offered downloads)? is it one of the linux distros like ubuntu, or uses it the special unRAID built?
greets,
Blacky
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?
-
I've just installed a new SSD and the 'Format' button is disabled. I opened a terminal, formatted as btrfs and mounted all manually, but the plugin then doesn't show the drive as mounted. Would prefer to format and mount via the plugin - any ideas?
Go to Settings, Unassigned Devices and change Destructive Mode: to Enabled
-
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.
[CONTAINER] CrashPlan & CrashPlan-Desktop
in Docker Containers
Posted
I have done this procedure and it’s a bit scary…
First go to CrashPlan support pages and look for adopting another computer:
https://support.code42.com/CrashPlan/4/Configuring/Replacing_Your_Device
Read this very carefully!
CrashPlan will notice that your data now is at a new location and will need to scan all your files and compare them with what they have on their server. This will take time, for me a several days with 6 TB of data.
Make sure to map your backup so that all previous shares/folders are included in the backup.