From 80e9929b117e8dadc5269fe4fbf837e6e04ea74b Mon Sep 17 00:00:00 2001 From: DoTheEvo Date: Wed, 1 Jan 2025 11:12:14 +0100 Subject: [PATCH] update --- .../kopia_server_start.cmd | 37 ++++++++++++++----- kopia_backup/readme.md | 7 +++- 2 files changed, 34 insertions(+), 10 deletions(-) diff --git a/kopia_backup/kopia_server_deploy_service_win/kopia_server_start.cmd b/kopia_backup/kopia_server_deploy_service_win/kopia_server_start.cmd index d96cf60..919de8a 100644 --- a/kopia_backup/kopia_server_deploy_service_win/kopia_server_start.cmd +++ b/kopia_backup/kopia_server_deploy_service_win/kopia_server_start.cmd @@ -1,15 +1,34 @@ kopia server start --insecure --config-file=C:\Kopia\repository.config --log-dir=C:\Kopia\Kopia_Logs --address=127.0.0.1:51515 --server-username=admin --server-password=aaa --enable-actions -:: to have full functinality of kopia server -:: replace the above command with the new one below +:: to have full functinality of a kopia server +:: replace the above command with the one below :: in it the address was changed to 0.0.0.0 to allow connection over network -:: and tls cert stuff was added to allow server functinality +:: and tls cert stuff was added without which server does not functions -rem kopia server start --tls-generate-cert --tls-cert-file C:\Kopia\tls_kopia.cert --tls-key-file C:\Kopia\tls_kopia.key --config-file=C:\Kopia\repository.config --log-dir=C:\Kopia\Kopia_Logs --address=0.0.0.0:51515 --server-username=admin --server-password=aaa +:: kopia server start --tls-generate-cert --tls-cert-file C:\Kopia\tls_kopia.cert --tls-key-file C:\Kopia\tls_kopia.key --config-file=C:\Kopia\repository.config --log-dir=C:\Kopia\Kopia_Logs --address=0.0.0.0:51515 --server-username=admin --server-password=aaa -:: restart the kopia service and check C:\Kopia if the tls_kopia files are there -:: now again edit this file - remove "--tls-generate-cert" part from it +:: restart the kopia service and check C:\Kopia if the tls_kopia files are now there +:: now again edit this file to remove "--tls-generate-cert" part from the command +:: restart the service again -:: to add user that will be able to backup -:: execute when connected to the repo -rem kopia server user add myuser@mylaptop +:: log in to the webGUI and create a repo + +:: now theres need to add users that will be able to backup to that repo +:: no GUI for that for whatever reason +:: open windows cmd / powershell as admin +:: connect to the repo manually +:: could help going to the webgui > repository > small shell-icon at the bottom +:: click on it and it will show command to execute to get repo status +:: adjust the command to be about adding a user + +:: C:\Kopia\kopia.exe --config-file=C:\Kopia\repository.config server user add myuser@mylaptop + +:: once again restart the kopia service + +:: now finally can go to the client machine +:: Kopia Repository Server +:: give the ip address and port, use https, something like https://10.0.19.95:51515 +:: write random stuff in to "Trusted server certificate fingerprint (SHA256)" +:: kopia on connect attempt will tell what the the real fingerprint is +:: kopy it in to the field and try connect agan +:: can override username/machine name in the advanced section diff --git a/kopia_backup/readme.md b/kopia_backup/readme.md index c24fc0c..5c891c0 100644 --- a/kopia_backup/readme.md +++ b/kopia_backup/readme.md @@ -87,6 +87,11 @@ if planning serious use. how it works under the hood.
[Here](https://kopia.discourse.group/t/kopia-snapshot-retention-policies-demystified/2941) is more in-depth, it is quite important to read and understand. +* **Ignore** - simplest way is creating a file `.kopiaignore` in the root + of the backup target and in it list paths to ignore, one path per line, + relative to the root. An example: if you backup `/home/user`, + you create the ignore file at `/home/user/.kopiaignore` + and in it have `temp/` to ignore the directory temp in that users home. * **Maintenance** is automatic. * **Restore** from backups is most easily done by mounting a snapshot.
Web GUI versions have button for it, cli version can do `sudo kopia mount all /mnt/temp &` @@ -352,7 +357,7 @@ the reliability of always running in the background as a service. This deployment does not make use of the main Kopia Server feature, to be a repository for other machines running Kopia, just local deployment. -Few edits of `kopia_server_start.cmd` can make it happen though. +Steps to get that working outlined in the `kopia_server_start.cmd`. * [Download this repo](https://github.com/DoTheEvo/selfhosted-apps-docker/archive/refs/heads/master.zip), delete everything except `kopia_backup/kopia_server_deploy_service_win` folder.