Has anyone notice a speed difference between a client with 2.01 installed and 1.4.10? In a virtualized environment with all machine assigned the same amount of hardware resources I get 45Kbps for clients using 2.0.1 and 560Mbps for machines running the 1.4.10 client. Or was there a setting I missed?
Yeah, EOL does not simply mean that it is not receiving updates and that your only worries are from the internet. It also means that there will not be any bug fixes and that you are several years behind on features.
I know precisely what End Of Life means. I work in IT. I was running 1.4.12 on the server quite well. I decided to test the Beta as the new features are quite enticing. I found it is not working and posted to this forum as that is what this thread is for. If what you are saying is that the new version is specifically designed not to run on Server 2003, then I will either reinstall 1.4.12 or search for a different software for my purposes.
To be quite frank, we are approaching a year that XP has been EOL, why would anyone target it? At this point, any project will continue building for it as long as it does not block anything else. As soon as it causes any difficultly in development, you drop all support. There is no sense in supporting a market that has completely faded.
Yeah, I haven’t done anything on purpose to remove the Windows XP support, but I haven’t tested it either (so it probably won’t work). This area is entirely complaint-driven.
If it does not load please use DependencyWalker to tell me which function it cannot load.
I haven’t done any major testing I just noticed that the lone xp client I was running the test on (rest are windows vista/7/8/10 and server 2008/2012) automatically updated to the 2.0.x beta from the server and then stopped connecting to the server (internet based) so no longer backing up
tried to upgrade 1.4.13 with 2.0.x on a windows 2008 server and the windows service does not start anymore.
Faulting application urbackup_srv.exe, version 0.0.0.0, time stamp 0x56b9cccb, faulting module api-ms-win-crt-runtime-l1-1-0.d, version 6.0.6002.18881, time stamp 0x51da3d16, exception code 0xc0000135, fault offset 0x00000000000b6fc8, process id 0x490, application start time 0x01d16f4ee232727f.
Once version 2 has become stable, will you be applying the commits to the ‘next’ branch in github? This way we can see what are the modifications we need to make to version 1 of the source code in order to ‘upgrade’ to version 2.
Or do we have to recompile the new version 2 source code from scratch?
So, I have a bunch of specialty XP clients which run specialized software (such as CNC control software) which cannot be upgraded without replacing the specialized equipment ($$$). I know XP is long out of support, but if there is a way we get get these backed up, it would be super awesome. I’ve tried using the 1.4.11 client with a 2.0.8 server, but have been having issues with getting image backups working (I will post details in a separate post).
I ran DependancyWalker for UrBackupClient.exe and UrBackupBackend.exe on a fully updated XP VM and it said the following DLLs were missing: