Network Error With Fd During Backup Err=connection Timed Out
FAQForumsJoin Our Forums!General TopicsBakBone NetVaultCA Brighstor ARCserveCommVault GalaxyEMC NetWorkerHP Data ProtectorIBM TSMSymantec Backup ExecSyncSort Backup ExpressSymantec NetBackupOpen-Source AmandaOpen-Source BackupPCOpen-Source BaculaOpen-Source Rdiff-BackupOpen-Source RsnapshotWikiRecent ChangesSpecial PagesPopular PagesCategoriesContact CurtisYour AccountYour DetailsMaintain SiteLogoutYours Search • FAQ • Memberlist • Log in Backup Central Forums Forum Index » Bacula » Network error with FD during Backup: ERR=Connection reset by The time now is Thu Oct 20, 2016 11:21 pm View previous topic | View next topic Page 1 of 2 Goto page 1, 2Next Network error with FD during Backup: ERR=Connection reset by Author Message Michael Neuendorf Guest Network error with FD during Backup: ERR=Connection reset by Hello there, I have a problem while backing up two windows servers in two different installations. The scenarios are almost equal: - Bacula-dir (v5.0.1) on Ubuntu 10.04.3 virtualized with VMware vSphere 5 Hypervisor - Bacula-sd (v5.0.1) on same server with file storage on a NAS, mounted via iSCSI. - Windows Server with problem in installation 1: Windows 2003 32bit SP1 virtulized on different VMware vSphere 5 Hypervisor, Bacula-fd 5.2.3 - Windows Server with problem in installation 2: Windows 2008R2 SP1 64bit virtulized on same hypervisor, Bacula-fd 5.2.6 - Many other Servers (virtualized and physical), Windos or Linux, without any problems. In both installations occur the errors shown below two to three times a week (not in all backups). I have three jobs per server and it is not always the same job, but always the same server. What I have done: - Use a newer FD version - Just one concurrent job per server ("Maximum Concurrent Jobs = 1" on all FDs) - Set "Heartbeat Interval = 60" on FD, SD and Dir I hope, someone has a clue for me or a hint, where to troubleshoot further. Best regards Michael Neuendorf The logs of the two server: 2012-09-19 22:58:45 bacula-dir JobId 13962: Start Backup JobId 13962, Job=nina_systemstate.2012-09-19_21.50.01_31 2012-09-19 22:58:46 bacula-dir JobId 13962: Usi
instructions: Windows Mac Red Hat Linux Ubuntu Click URL instructions: Right-click on ad, choose "Copy Link", then paste here → (This may not be possible with some types of ads) More information about our ad policies X You seem to have CSS turned off. Please don't fill out this field. You seem to have CSS turned off. Please don't fill out this field. Briefly describe the problem (required): Upload screenshot of ad (required): Select a file, or drag & drop file here. ✔ ✘ Please provide the ad click URL, if possible: Home Browse Bacula Mailing Lists Bacula Brought to you by: kerns, ricozz Summary Files Reviews Support Wiki Mailing Lists Discussion bacula-announce bacula-beta bacula-bugs bacula-commits bacula-devel bacula-devel-fr bacula-docs bacula-ryol bacula-users bacula-users-es bacula-users-fr Re: [Bacula-users] http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/bacula-25/network-error-with-fd-during-backup-err-connection-reset-by-119622/ Fatal error: Network error with FD during Backup: ERR=Connection timed out Re: [Bacula-users] Fatal error: Network error with FD during Backup: ERR=Connection timed out From: Carlo Filippetto
> I have added the heartbeat interval on all daemons, but no change. The _all_ deamons involved is important.
FD-сервером (клиентом) находится маршрутизатор (используется NAT) - выполняемая задача (job) может вдруг ни с того, ни с сего остановиться с ошибкой "Fatal error: Network error with FD during Backup: ERR=Connection reset by peer".Дело всё в том, что Director, инициируя задачу на клиенте, в процессе выполнения просто ждёт - весь трафик идёт между FD-сервером (клиентом) и SD-сервером (storage). Маршрутизатор спустя установленное время (timeout, у cisco - 7200 секунд) решив, что соединение между Director-сервером и FD-сервером (клиентом) умерло, просто удаляет информацию о соединении из своей таблицы соединений, обрывая таким образом выполняемую задачу.Решается проблема тривиально - на FD-сервере (клиенте) в конфигурационном файле в секцию FileDaemon добавить: Heartbeat Interval = 60При действующем Heartbeat-интервале FD-сервер в процессе выполнения работы пересылает heartbeat-пакеты Director-серверу, создавая таким образом активность в соединении и маршрутизатор, видя, что соединение "живо", не вмешивается.Ссылки:Client/File daemon ConfigurationTimeout (?) problems with some Full backups Posted by Roman Sozinov at 8:14 AM Labels: backup, bacula, tips 7 comments: StasikOS said... Это в случае если на маршрутизаторе настрен NAT или всегда? September 1, 2009 at 9:08 AM Roman Sozinov said... to StasikOS:Хороший вопрос :) У меня проблема вылезла в случае использования NAT, а вот без использования NAT по идее таких проблем быть не должно. September 1, 2009 at 9:25 AM StasikOS said... Вот-вот. В случае обычно