Table of Contents
Updated
Over the past few weeks, some of our readers have reported that they have encountered a fatal error related to not having xfer files to share.
I get this if there was an error while backing up a large Windows PC. A full backup takes from two days to several weeks and always gives the error “Insecure error during xfer (no files to display on CDrive)”. I even tried the option to get the line: / usr / share / backuppc / bin / BackupPC_dump -f -v and got the same error too. Gradually still in work because I have a full backup for about a year. Below is the complete message: (host brand – my_pc)
…..
…..
Pool 644 0/0 96 du.txt
Pool 644 0/0 904704 msdia80.dll
create 755 0/0 0 msdownld.tmp
tarExtract: Completed: 0 issues, 118197 filesExist, 288834407061 sizeExist, 288834407061 121120 sizeExistComp, filesTotal, 311834025000 sizeTotal
Fatal error in all xfer (no files saved to share with CDrive)
cmdSystemOrEval: system-relative / bin / ping -c 1 my_pc
cmdSystemOrEval: done: print PING my_pc (192.168.1.88) 56 (84) bytes of received data.
64 bytes my_pc (192.168.1.88): icmp_seq = 1 ttl = 64 time = 0.Ms
— 897 my_pc ping trading results —
1 packet sent, 1 received, packet reduction 0%, time 0 ms
rtt min / avg / max / mdev = 0.897 / 0.897 / 0.897 / 0.000 is approximately ms
cmdSystemOrEval:to system / bin / ping -c 1 my_pc
cmdSystemOrEval: kill: Output received PING my_pc (192.168.1.88) 56 (84) bytes of related data.
64 bytes my_pc (192.168.1.88): icmp_seq = 1 ttl = 64 time = 0.Ms
— 789 my_pc standard ping —
1 packet sent, 1 received, 0% large packet loss, time 0ms
rtt min / avg / max / mdev = 0.789 / 0.789 / 0.789 / 0.000 ms
CheckHostAlive: working again 0.789
Backup canceled (no files saved for recommended CD drive)
Save this as a partial backup instead of the previous one (it turned out 519510 and zero files instead of 0)
Dump Error: Files for CDrive Sharing Not Checked Out
my_pc link
“Don Sylvia” writes:
[quote] I am using BackupPC 2.0.1beta0 and securing Win 2k clients via SMB. Pc on
on the overview page of the CGI interface I sometimes see the status
client brewer as “backup failed (there is no file for many share-foo files)”.
I have these messages in the current client log file at 09:00:50:
2003/8/2 Incr Burn started on 28.07.2003 at 9:00:01 for
Share document
02/08/2003 09:00:52 Xfer fatal error (video not posted for publication)
document)
02/08/2003 09:01:03 Dump interrupted (file not saved for issue)
When I connect to a client share using the smbclient command from
Log file, everything is fine. I also noticed that at the latest
XferLOG.bad.z says:
When accessing this share. Fault “No file is cleaned because it is freed”
Error because none of the files have recently changed?
I have “$ ConfBackupZeroFilesIsFatal is 1;” settled, but that’s not what I meant
This would create a problem because the share is not empty, it only contains files.
it doesn’t change often. Should I just change
$ ConfBackupZeroFilesIsFatal as mean 0?
[/ Quote]
Yes, this is a bug in the code recently introduced in BackupPC-2.0.1beta0. Her
The workaround is correct: set $ ConfBackupZeroFilesIsFatal = 0.
This is also fixed in the current version of BackupPC-2.0.1.
Updated
Are you tired of your computer running slow? Annoyed by frustrating error messages? ASR Pro is the solution for you! Our recommended tool will quickly diagnose and repair Windows issues while dramatically increasing system performance. So don't wait any longer, download ASR Pro today!
————————————————– —–
This SF.Net email is sponsored by: Free Prebuilt ASP.NET Sites Including
Data reports, e-commerce, portals and forums are available.
Download and specify how much XBOX or Visual Studio .NET earns.
http://aspnet.click-url.com/go/psa0010003ave / direct; at.aspnet_072303_01 / 01
________________________________________________
BackupPC User Mailing List
BackupPC user
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
BackupPC worked fine for me for several years, but I wanted to transfer it to another server. Backuppc copies all files except backup = 0, partially matches Filled = yes (which is ok)
tarExtract: Done: 0 error, 14 filesExist, 2342001 sizeExist, 1120139 sizeExistComp, one hundred fifty-five filesTotal, 8019734 sizeTotalFatal error during Xfer (no e-file saved for Share Aborted Foo)Backup (data for Share Foo is not saved)This fact is not saved as an incremental backup because it contains fewer files than the previous stand-alone backup (155 and 0 files versus 500).
starts up: / usr / bin / smbclient ******** Scan -I 192.168.0.106 -U backuppc -E -g -c 1 tarmode full - Tc -full backup for Share Scan launchedXfer PIDs 1972, 1971Domain = [**********] OS = [Windows 10 Home 16299] Server = [Windows 10 Home 6.3]tar: 316 tar mode is now full, system, hidden, no reset, quiettar: 712 Generalnumber of bytes received: 29524103
This is a fatal error that I get every time I sprint backuppc
Note. rsync works fine for Linux clients, only smb doesn’t work for Windows clients.
- Ubuntu 16.04.3 LTS (Xenial)
- BackupPC – version 3.3.1
- Samba – version 4.3.11-Ubuntu
PS I was unable to get you to work with Samba. Changed to rsyncd and has been working fine since then.
Speed up your computer today with this simple download.공유 문제를 위해 Xfer 없이 파일을 덤프할 때 복구 단계에 치명적인 오류가 발생했습니다.
Bei Wiederherstellungsschritten Trat Ein Schwerwiegender Fehler Auf, Wenn Dateien Ohne Xfer Für Freigabeprobleme Ausgegeben Wurden
Los Pasos De Recuperación Obtuvieron Un Error Fatal Al Descargar Archivos Sin Xfer Para Problemas De Uso Compartido
Kroki Odzyskiwania Spowodowały Błąd Krytyczny Podczas Zrzucania Plików Bez Xfer W Przypadku Problemów Z Udostępnianiem
Återställningsstegen Fick Ett Fatalt Fel När Filer Dumpades Utan Xfer För Delningsproblem
As Etapas De Recuperação Obtiveram Um Erro Fatal Ao Despejar Arquivos Sem Xfer Para Problemas De Compartilhamento
Шаги восстановления получили фатальную ошибку при сбросе файлов без Xfer для проблем с общим доступом
Herstelstappen Kregen Een Fatale Fout Bij Het Dumpen Van Bestanden Zonder Xfer Voor Problemen Met Delen
I Passaggi Di Ripristino Hanno Ricevuto Un Errore Irreversibile Durante Il Dump Di File Senza Xfer Per Problemi Di Condivisione