New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Native Windows port #936
Comments
Thanks to @Anakonda for doing the native windows port! The basics work, but it will for sure need more testing, fixes and enhancements - please file tickets for anything that shows up (make sure you mention "windows branch" for problems only happening in that branch). |
Hello, I would like to try borg under Windows. Is there any documentation on the native port? E.g. what python packages are needed. Regards, |
Hello, I just saw that an executable is already created here: That's good. Before deploying borg as native executable, an installer would be even better, but for testing, it is not needed I think. If you would like people to test the native windows, I think that a compiled version of this branch would be needed. Is that available from somewhere? Regards, |
@henfri latest version is available here https://ci.appveyor.com/project/borgbackup/borg/build/artifacts |
@Anakonda is this a native windows port, or does it install sigwin? |
Cygwin, you mean? Greetings, |
@henfri thanks. Will try it, curious to see how it stacks up against rclone and duplicati |
Hello, no, it does not run. It is missing ctypes.wintypes:
Greetings, |
Here is working one: https://www.dropbox.com/s/tolumpufc179j77/borg.zip?dl=0 |
Thanks. But I get an error message doing
So, I suppose that I need "ssh" installed somewhere? Greetings, |
You are trying to backup to a server? Where did you get that address? |
Hello, yes. The adress is the one that I use for backing up my linux machine. I will try plink. Greetings, |
Hello, I tried plink now.
Platform: Windows LaptopHendrik 10 10.0.14393 AMD64 Intel64 Family 6 Model 69 Stepping 1, GenuineIntel I can also try openssl. Can you point me at a download link? There seem to be several ports. Greetings, |
There is bug in windows version, You need to authenticate via ssh key. See some guides how to set that up. |
Hello, I did my first backup from Windows now. In putty go to settings->connection->SSH->auth --> private key for authorization and select the private key that was created by puttygen. Test the connection from putty. No password should be needed. If this runs, you are set. |
Hello, would you be willing also to provide an 32bit executable? Regards, |
... and with the latest Version, please as I am also suffering from this: |
Hello, I have used this version of Borg for a while now. I had in the past not seen errors (but I was running it in Background). But now I continiously get:
How can I further debug this issue? Greetings, |
@henfri often it is a very fundamental problem with ssh not working. |
Hello Thomas, wouldn't it be good to make the output a bit more clear and even isolate the problem further in the output? What's surprising: The error happens after a long time. I am able to backup successfully if I select smaller folders. It's a bit of a locked situation.. I cannot do anything, I fear. Any Ideas? |
Check if you ssh works if you invoke it with similar params manually. Not sure how we can do better as the failure is in ssh. |
so what's the status of the Windows port? the install docs refer to the Linux subsystem or Cygwin but do not seem to refer to this i may need to work on windows for a client and I'm wondering what the best way to go would be - should i try that windows branch? or cygwin? |
Hello, |
Hi guys! Could you please give me some points on how to use this port on Windows 10? I extracted
What am I doing wrong? |
Do not extract 'library.zip' |
Thanks for your reply, @Anakonda
|
If you're looking for a Windows backup software for productive use, it's probably a better idea to stick to something better tested on Windows. |
You are probably right @enkore. I'm usually using another backup solutions on Windows. And I'm also using Borg backup on about 30 Linux and FreeBSD servers. Thanks for your reply anyway. There are some mixed solutions of Borg backup on Linux + Windows I'm going to consider. |
Hello, sorry, but where under https://ci.appveyor.com/project/borgbackup/borg/build/artifacts do I find the download? Appart from that: What's the future of the windows-builds. Regards, |
Hello -again, apart from my previous question:
--> I can login without password. Regards, |
@henfri can't tell much about the windows stuff except that it needs more developers, reviewers, testers and a more continued effort. I can only review very simple windows related changed, to review more advanced stuff it needs developers with experience of windows fs and apis. |
Hello, Greetings, |
There is more recent windows related work in master branch that was done independently of the windows branch. It was smaller, limited scope stuff that I could review and so it got merged. Maybe doing the smaller, simpler steps first makes sense. |
yes. Do you know, whether the current master branch works in windows? I think, that also we can distinguish between: In order not to loose the existing work though, it would be good if someone familiar with it could review the old commits in the windows branch, adopt them into the current master and create (small) pull requests. |
I don't know. I only rarely test borg on cygwin, but i don't have a wsl nor a native win32 development system. Yeah, someone(tm) could do that. Start with the simple stuff. I think the initial goal should be something like "backup and restore my documents folder" rather than something with ntfs permissions / ACLs, special features, etc. |
@henfri as the link says appveyour keeps artifacts only for 6 months. New ones are generated automatically as soon as something is pushed to the windows branch. I have not tested the cygwin port, running with wsl should work as is. Most of the code in windows branch can be used again when it is time to do Windows spesific stuff. I could maybe do something if it were to master branch and not to windows branch. |
Hi Thomas, I understand. Regards, |
git show, git cherry-pick. not sure if there is something better / more comfortable. |
@Anakonda thanks for your reply
What do you mean by that? |
I meant that its discouraging to see lot of commits pushed to master thinking I should merge them to windows branch. The merges I ended up doing were not easy. I don't want that mess again. |
Hello, I fully understand that. That is also my concern. I suppose you suggest that first your work should be merged into master, right? @ThomasWaldmann What's your view on this? I think @Anakonda has a point here. I assume, you would merge, if the changes come in smaller pull requests? Regards, |
I won't merge the windows branch "as is". It is beyond my capability to review or maintain it. Also (IIRC) at least some of the changesets aren't very "clean" / "focussed". Smaller, focussed, clean, "simple enough" PRs are welcome. More difficult ones are welcome, too, if there is somebody reviewing them and there are windows developers being able to maintain the code. |
Hello Thomas, I fear, this way there is no way forward. I can understand Anakondas frustration/unwillingness to maintain the current approach of having to merge everything that is done in master into windows. I have the impression that anakonda is willing to maintain the code. And I would use and test it. So, what would be needed:
What do you think? Greetings, |
the code should be reviewed by somebody with a clue of win32 api. if it is unclear to @Anakonda what's unclean/unfocussed, i can point at it, but it might be rather obvious. |
Hello, I reviewed this one:
Apart from that, I do not see anything that could break functionality on non win32 platforms and nothing that would be 'dirty'. Greetings, |
I suggest that we forget the windows branch for now, it is no way mergeable with master, instead start making (very) small changes to master. |
Can AppVeyor be restarted to regenerate the Windows builds? Presumably it's better than nothing? |
Would also like to see a windows version |
+1 for win build |
+1 |
If borg could run directly on a normal Windows installation (via cmd, not requiring cygwin or other major runtime support), it could be useful for windows machines that do not have cygwin installed.
Notes:
Doing a native windows port is likely quite some work over a longer time, due to all the differences between windows and UNIX-like operating systems. Whether it can be done in a pretty (regarding to source code changes) and good working (regarding to practical use) way has to be seen.
Because of that, it will have to live in a separate branch of the repository at first (which should be regularly updated from master branch, so it is kept up-to-date and without potential merge conflicts).
At some time in the future, that branch might or might not get merged into master.
💰 there is a bounty for this
I opened a (first) bounty for this - if you would like to see this happen, feel free to support this or a future, related bounty.
The goal and scope of this bounty is:
The text was updated successfully, but these errors were encountered: