- Backblaze linux personal install#
- Backblaze linux personal password#
- Backblaze linux personal download#
- Backblaze linux personal windows#
I get a monthly email that the machines I'm backing up are, infact, backing up. It is pretty smart about not consuming all the network bandwidth on a machine (good for places where 1Mbit upload is considered pretty good).
Backblaze linux personal install#
I install it, I configure it, I never touch it again unless something goes wrong.
Backblaze linux personal windows#
The things I love about Backblaze on Windows is that it's very much no-nonsense. I'd like to make a case for making Backblaze on Linux with B2 as the backend (or at least charge like B2). There's a post here that perfectly explains it, and I'm fully in agreement with the rationale of not just offering flat-rate options. If you have to stop the container during the initial backup the backup will continue where it left once the container is started again.īackblaze is now configured to automatically backup your linux files, to check the progress or change settings use the VNC Server.There's been a ton of posts asking about Backblaze on linux OSs.Ī lot of the responses from Backblaze can be summed up as "Offering Backblaze on Linux would make it unprofitable". When the analysis is complete make shoure the client performs the initial backup (this should happen automatically).ĭepending on the number and size of the files you want to back up and your upload speed, this will take quite some time. You can dis- and reconnect from and to the VNC server at any time, this will not affect the Backblaze client. Once you hit "Ok" or "Apply" the client will start scanning your drives again, this might take a very long time depending on the number of files you mounted under the /data/ dir, just be patient and leave the container running. I'd also reccommend to remove the blacklisted file extensions from the "Exclusions" tab.
You can also set a better name for your backup here, by default the rather obscure container id is used. To change that click the Settings button and check the box for the "D:" drive, this drive corresponds to the /data/ directory of your container. You will notice that currently only around 10 files are backed up. Once the Installer is finished the backblaze client should open automatically.
Backblaze linux personal password#
Just enter your backblaze account email into the white box and hit enter, then the you should see the rest of the ui.Įnter your password and hit "Install", the installer will start scanning your drive. The installer might look a bit weird (all white) at the very beginning. When you only see a black screen once you are connected press alt-tab to activate the installer window.
Backblaze linux personal download#
When starting the container for the first time, it will automatically initialize a new Wine prefix and download & run the backblaze installer. To go through the setup process you must connect to the integrated vnc server via a client like RealVNC Client. The noVNC only serves a HTTP connection by default, please make sure to configure your firewall to only allow local connections in that case.įirewall-cmd -permanent -add-rich-rule "rule family="ipv4" source address="192.168.178.0/24" port port="25900" protocol="tcp" accept" # This part is important, don't forget it! You may use any port here (e.g.: if you have a reverse proxy)
80:8081 # Exposes the client to http port 80. REMOTE_HOST=backblaze-personal-wine # This must be the container_name of the backblaze-personal-wine container my/important/spreadsheets:/data/spreadsheets my/important/photos:/data/photos # All directories that should be backed up should be mounted under the "/data/" directory opt/docker/backblaze-personal-wine:/wine/ # The location to store the backblaze Wine prefix in
0 kommentar(er)
