- #CRASHPLAN INSTALL INSTALL#
- #CRASHPLAN INSTALL UPDATE#
- #CRASHPLAN INSTALL DRIVER#
- #CRASHPLAN INSTALL PRO#
- #CRASHPLAN INSTALL WINDOWS#
To do this, click on “Sharing” in TrueNAS, then on “Unix Shares (NFS)”. The solution I arrived at was to share my NAS files via NFS and mount that in the VM. As far as I can tell, there is no way, at least from the TrueNAS interface to expose them directly like you can in a TrueNAS jail. We need to expose our NAS shares to the VM so that they can be backed up by CrashPlan. On Debian and Ubuntu, all the default options should be fine.
#CRASHPLAN INSTALL INSTALL#
Just go grab the install tar.gz, untar it, run the installer as root.
#CRASHPLAN INSTALL WINDOWS#
If you connect via VNC and see console output stating that X Windows is about to launch, either log in via SSH and restart X or restart the VM, then immediately attach via VNC until it gets to the login screen.įirst you should install CrashPlan. However, this will not matter as far as backing stuff up goes as the Crashplan service is already launched at that point. Then reconnect via VNC and eventually be greeted with a graphical login screen.įor reasons that are unknown to me, sometimes X Windows will fail to launch if you are not connected via VNC when it gets to the X Windows launch point in the bootup process, at least in Debian. This last step is not documented anywhere that I could find, but I was able to derive this based on instructions for setting up a BSD based VM.Īt this point, you should be able to reboot the VM.
#CRASHPLAN INSTALL DRIVER#
Put the following content inside: Section "Device" Identifier "Card0" Driver "fbdev" EndSection To do this we need to create “/usr/share/X11//nf”. The last step is to tell XWindows to use a fbdev device for the graphical interface. Save the file, then run the following: # update-grub Now add the following two lines to /etc/default/grub, replacing any existing similar lines, and changing the resolution to match the one you previously set for Bhyve’s VNC device: GRUB_GFXMODE=1600x1200 GRUB_GFXPAYLOAD_LINUX=keep #Not sure this is needed
#CRASHPLAN INSTALL UPDATE#
Now get to a root shell.įirst thing we need to do fix our environment, and get vim installed before updating grub to set our resolution correctly: # apt update # apt install vim # export PATH=$PATH:/sbin:/usr/sbin # vim /etc/default/grub From the VNC access, you may be able to switch to a new console via Ctrl +Alt + F1, but if that doesn’t work, you may need to SSH into your VM. You now need to get to the command line prompt of your VM. Whatever you pick, make sure it is a standard resolution and remember it as we will need it later. Finally edit the resolution to something you would like to use normally. Now click edit on the VNC device and uncheck the “Delay VM Boot Until VNC Connects”. As far as I can tell the only way to do this, is to navigate to the “Devices” tab under your VM in TrueNAS and delete the CDROM device. Once the install completes, it will tell you to remove the install disk and restart. I would deselect the “Print Server” as well. It is critical that you also check “OpenSSH Server” in the installer. I recommend using a light GUI like either XFCE or LXDE. When prompted quickly select the “Limited Graphical” installer.
Then connect using the built in VNC display. This is critical or you will see a scrambled mess when you boot into the VM. Makes sure to leave the network settings to allow the VM to have it’s own IP address, and select and upload the Install CD for your distro (assuming Debian from now on).īefore you start the VM, click on it, go to “Devices”, and then click “Edit” on the VNC device. The rest of the setup should be pretty straight forward. What follows is how I got it working in my environment.
#CRASHPLAN INSTALL PRO#
Another issue is that CrashPlan Pro basically made GUI a requirement (again probably to prevent people from doing what I am trying to do). First Crashplan long ago dropped any semblance of support and compatibility with FreeBSD this is likely at least partially to make it harder to do exactly what I want to do and also a consequence of the CrashPlan Pro service moving away from Java to Electron. Unfortunately, CrashPlan has not been supported for a long time, and I could not find a good guide to setting this up, so I made my own…Ĭrashplan is not supported for a variety of reasons. Most of this stuff was easy to transition to TrueNAS. However, my current NAS solution was a custom Debian server, with OpenZFS on Linux, CrashPlan Pro, Plex, Syncthing, and various monitoring scripts to scrub the ZFS tank, monitor my UPS, and send me phone alerts. I recently wanted to update my NAS to use TrueNAS as it has come a long way from the old days of FreeNAS. Setting up TrueNAS with Crashplan Pro Backup
0 kommentar(er)
