Re: [BackupPC-users] Failing incremental backups on Windows 10 (backuppc 3.x)
On 06/04 01:34 , Alan Ballard wrote: > Running a packet trace with WireShark was more informative. It showed the > Windows client getting transmission timeouts and retransmitting; then after > 5 retransmits terminating the connection. An interesting thing I noticed > was that the timeout interval was quite short... about 300msec. It turns > out that Windows tunes the timeout based on the observed response on the > connection. In this case, at the start of the rsync operation there are > many short fast interactions, then the server bogs down as it does the delta > copies of a large file. Huh, that's really interesing. Thanks for the troubleshooting! -- Carl Soderstrom Systems Administrator Real-Time Enterprises www.real-time.com ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
[BackupPC-users] Failing incremental backups on Windows 10 (backuppc 3.x)
I've been running a backuppc server (currently version 3.x) for several years, backing up a small collection of Linux and Windows machines. I recently added a new Windows 10 machine (using rsyncd), and found that, while full backups worked well, incrementals almost always failed. Some research here found a number of other reports of this over the years, but I couldn't find a solution. So, here is what I found out about the situation and the workaround that I'm currently using. Logfiles on client and server weren't very helpful (even at high log levels). They indicated that the Windows system thought the connection had dropped and so the rsync.exe task terminated. Then some 20 minutes later the server detected that the client had gone so it terminated. Running a packet trace with WireShark was more informative. It showed the Windows client getting transmission timeouts and retransmitting; then after 5 retransmits terminating the connection. An interesting thing I noticed was that the timeout interval was quite short... about 300msec. It turns out that Windows tunes the timeout based on the observed response on the connection. In this case, at the start of the rsync operation there are many short fast interactions, then the server bogs down as it does the delta copies of a large file. The client sending the changed blocks seems to get too far ahead and eventually the timeouts occur. (It is probably significant that this new machine with the problem is much faster than any I was previously backing up; in fact faster than the server.) There doesn't seem to be any way in Windows to set a minimum transmit timeout (you can just set the initial value, which isn't helpful here). But I found that by setting(*) the maximum retries to 15 instead of the default 5, the incremental backups succeed. This isn't an ideal fix. It's a global change so means the Windows system is slow detecting "real" connection failures. And of course there is a lot of unnecessary retransmission using up network bandwidth, though this is not a big concern in my case. I thought it might be possible to add an extra layer of buffering in the server to keep it responsive on the connection, though this might not be practical for really large files. Or maybe some higher level flow control to throttle the sender. Or perhaps the network adapter parameters on either client or server could be tweaked to address the issue. I would appreciate any thoughts on better solutions. I don't know if BackupPC 4.x has the same issue. Installing and testing that is one of my next projects . * setting the max retries via regedit: add or change the DWORD parameter \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\TcpMa xDataRetransmissions. ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] restore issue on backuppc 4.1.5
On 2019-06-04 07:33, Philip Parsons (Velindre - Medical Physics) wrote: > Thanks for the reply Michael. > > I've tried to restore to another share on another server and am getting > NT_STATUS_BAD_NETWORK_NAME > > I don't want to overwrite the existing data, I just want to be able to > download data to another share so that I can QA our backups. > > Running: /usr/bin/smbclient destinationserver\\share -U domainaccount -E > -d 1 -c tarmode\ full -mSMB3 -Tx - > > Running: /usr/local/BackupPC/bin/BackupPC_tarCreate -h sourceserver -n 510 -s > sourceshare -t /sourcefolder > > Xfer PIDs are now 104823,104824 > > WARNING: The "syslog" option is deprecated > > [ skipped 1 lines ] > > This backup will fail because: tree connect failed: > NT_STATUS_BAD_NETWORK_NAME > > tree connect failed: NT_STATUS_BAD_NETWORK_NAME > > [ skipped 1 lines ] > > tree connect failed: NT_STATUS_BAD_NETWORK_NAME > > readOutput: sysread returns 0 and got EOF (exit ok = , ) > > XferErr Non-zero exit status from smbclient > > restore failed: tree connect failed: NT_STATUS_BAD_NETWORK_NAME > > thanks again for any advice! > > Phil Samba errors are maddeningly unspecific. In this case, the error translates to "something about that share ain't working for me." It could be anything from the share name being misspelled, or the wrong part of the tree, or permission errors. At any rate, the simplest way to diagnose this is to start with what the share names are: smbclient -L //destinationserver This should give you a list of valid shares -- if the sharename you tried doesn't exactly match one of the shares in that list, viola, that is the trouble. (N.B. I do mean *exactly.* There's no support for joining the tree at a different point in the hierarchy.)___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] restore issue on backuppc 4.1.5
Thanks for the reply Michael. I've tried to restore to another share on another server and am getting NT_STATUS_BAD_NETWORK_NAME I don't want to overwrite the existing data, I just want to be able to download data to another share so that I can QA our backups. Running: /usr/bin/smbclient destinationserver\\share -U domainaccount -E -d 1 -c tarmode\ full -mSMB3 -Tx - Running: /usr/local/BackupPC/bin/BackupPC_tarCreate -h sourceserver -n 510 -s sourceshare -t /sourcefolder Xfer PIDs are now 104823,104824 WARNING: The "syslog" option is deprecated [ skipped 1 lines ] This backup will fail because: tree connect failed: NT_STATUS_BAD_NETWORK_NAME tree connect failed: NT_STATUS_BAD_NETWORK_NAME [ skipped 1 lines ] tree connect failed: NT_STATUS_BAD_NETWORK_NAME readOutput: sysread returns 0 and got EOF (exit ok = , ) XferErr Non-zero exit status from smbclient restore failed: tree connect failed: NT_STATUS_BAD_NETWORK_NAME thanks again for any advice! Phil From: Michael Stowe [mailto:michael.st...@member.mensa.org] Sent: 22 May 2019 15:45 To: General list for user discussion, questions and support Cc: Philip Parsons (Velindre - Medical Physics) Subject: Re: [BackupPC-users] restore issue on backuppc 4.1.5 On 2019-05-22 05:32, Philip Parsons (Velindre - Medical Physics) wrote: Hi, I'm having an issue with restoring to a share and am trying to deal with this before it becomes a need to restore situation! We're using BackupPC v4.1.5. I've had the following error when trying to restore: Running: /usr/bin/smbclient servername\\sharename -U accountname -E -d 1 -c tarmode\ full -mSMB3 -Tx - Running: /usr/local/BackupPC/bin/BackupPC_tarCreate -h servername -n 211 -s sharename -t -r / -p /temp/ /restorefolder Xfer PIDs are now 48288,48289 WARNING: The "syslog" option is deprecated [ skipped 1 lines ] tar:316 tarmode is now full, system, hidden, noreset, quiet tar:1597 Can't mkdir temp: NT_STATUS_OBJECT_NAME_COLLISION readOutput: sysread returns 0 and got EOF (exit ok = , ) XferErr Non-zero exit status from smbclient restore failed: BackupPC_tarCreate failed Does anyone know what could be causing this? Thanks in advance, Phil It looks like you're trying to restore to a directory called temp, which already exists, but is hidden. You probably just want to choose a different directory to restore to. ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
