[BackupPC-users] Remote backups of a win2003 server keeps failing after a certain amount of time.
Remote backups of a win2003 server keeps failing after a certain amount of time (almost every time about 20h later / data 11 GB already done). Backup method: Rsyncd Server client: Rsync via Deltacopy (great piece of easy to configure software thanks to someone on this list, works perfectly for win2K, winXP, vista, win2003) Slow upload +- 512 KB/s 25 GB of data on a separate partition (not the windows one) Another win2003 with similar data (but less 9g) hasn't got a problem. The first full needed 24h, +- 100 KB/s average. = Could it be a specific file is too big? Too long name? = Anyone could point me to what to search for? Greetings, Koen Linders Contents of file /var/lib/backuppc/pc/80.201.242.118/LOG.012009, modified 2009-01-07 09:44:29 2009-01-01 20:00:00 full backup started for directory dDRIVE 2009-01-02 16:23:54 Aborting backup up after signal ALRM 2009-01-02 16:23:55 Got fatal error during xfer (aborted by signal=ALRM) 2009-01-02 16:23:55 Saved partial dump 0 2009-01-02 20:00:00 full backup started for directory dDRIVE 2009-01-03 16:24:01 Aborting backup up after signal ALRM 2009-01-03 16:24:02 Got fatal error during xfer (aborted by signal=ALRM) 2009-01-03 16:24:04 Saved partial dump 0 2009-01-03 17:00:00 full backup started for directory dDRIVE 2009-01-04 13:23:27 Aborting backup up after signal ALRM 2009-01-04 13:23:28 Got fatal error during xfer (aborted by signal=ALRM) 2009-01-04 13:23:28 Saved partial dump 0 2009-01-04 14:00:01 full backup started for directory dDRIVE 2009-01-05 10:26:18 Aborting backup up after signal ALRM 2009-01-05 10:26:20 Got fatal error during xfer (aborted by signal=ALRM) 2009-01-05 10:26:23 Saved partial dump 0 2009-01-05 15:19:04 full backup started for directory dDRIVE 2009-01-06 11:51:22 Aborting backup up after signal ALRM 2009-01-06 11:51:26 Got fatal error during xfer (aborted by signal=ALRM) 2009-01-06 11:51:29 Saved partial dump 0 2009-01-06 11:58:05 full backup started for directory dDRIVE 2009-01-07 09:44:26 Aborting backup up after signal ALRM 2009-01-07 09:44:28 Got fatal error during xfer (aborted by signal=ALRM) 2009-01-07 09:44:29 Saved partial dump 0 Contents of file /var/lib/backuppc/pc/80.201.242.118/XferLOG.0.z, modified 2009-01-07 09:44:28 (Extracting only Errors) full backup started for directory dDRIVE Connected to 80.201.242.118:873, remote version 30 Negotiated protocol version 28 Connected to module dDRIVE Sending args: --server --sender --numeric-ids --perms --owner --group -D --links --hard-links --times --block-size=2048 --recursive --ignore-times . . Sent exclude: Thumbs.db Sent exclude: IconCache.db Sent exclude: Cache Sent exclude: cache Sent exclude: /Documents and Settings/*/Local Settings/Temporary Internet Files Sent exclude: /Documents and Settings/*/Local Settings/Temp Sent exclude: /Documents and Settings/*/NTUSER.DAT Sent exclude: /Documents and Settings/*/ntuser.dat.LOG Sent exclude: /Documents and Settings/*/Local Settings/Application Data/Microsoft/Windows/UsrClass.dat Sent exclude: /Documents and Settings/*/Local Settings/Application Data/Microsoft/Windows/UsrClass.dat.LOG Sent exclude: /Documents and Settings/*/Local Settings/Application Data/Mozilla/Firefox/Profiles/*/Cache Sent exclude: /Documents and Settings/*/Local Settings/Application Data/Mozilla/Firefox/Profiles/*/OfflineCache Sent exclude: /Documents and Settings/*/Recent Sent exclude: *.lock Sent exclude: /WINDOWS Sent exclude: /RECYCLER Sent exclude: /MSOCache Sent exclude: /System Volume Information Sent exclude: /AUTOEXEC.BAT Sent exclude: /BOOTSECT.BAK Sent exclude: /CONFIG.SYS Sent exclude: /hiberfil.sys Sent exclude: /pagefile.sys Sent exclude: /Program Files/F-Secure/common/policy.ipf Sent exclude: NTUSER.DAT.LOG Sent exclude: NTUSER.dat Sent exclude: *.tmp Sent exclude: /Profiles/VTB/*/NTUSER.DAT Sent exclude: /Profiles/VTB/*/ntuser.dat.LOG Sent exclude: /Profiles/VTB/*/Local Settings/Application Data/Microsoft/Windows/UsrClass.dat Sent exclude: /Profiles/VTB/*/Local Settings/Application Data/Microsoft/Windows/UsrClass.dat.LOG Sent exclude: /Profiles/VTB/*/Local Settings/Application Data/Mozilla/Firefox/Profiles/*/Cache Sent exclude: /Profiles/VTB/*/Local Settings/Application Data/Mozilla/Firefox/Profiles/*/Cache Sent exclude: /Profiles/VTB/*/Local Settings/Application Data/Mozilla/Firefox/Profiles/*/OfflineCache Sent exclude: /Profiles/VTB/*/Recent Sent exclude: /Profiles/VTB/*/NetHood Sent exclude: /Profiles/VTB/*/Onlangs geopend Sent exclude: /Profiles/VTB/*/UserData Sent exclude: /Public/Backup Xfer PIDs are now 30058 [ skipped 25915 lines ] Remote[2]: file has vanished: Shares/Audiologie/administratie HOTO en FM/Facturatie/faktuuraanvraag FM en H.A/FM + hulpmiddelen/~$orbeeld Veranneman facturatie FM en hulpmiddelen.doc (in dDRIVE) [ skipped 83 lines ] finish: removing in-process file Shares/Audiologie/backup/PC MPI047/Backup.bkf Child is aborting Done: 22734 files, 11921915308 bytes Got fatal error during xfer (aborted by signal=ALRM)
Re: [BackupPC-users] Remote backups of a win2003 server keeps failing after a certain amount of time.
I forgot to add the windows logbook errors: 1) The description for Event ID ( 0 ) in Source ( rsyncd ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: rsyncd: PID 644: rsync: writefd_unbuffered failed to write 4092 bytes [sender]: Connection reset by peer (104). 2) The description for Event ID ( 0 ) in Source ( rsyncd ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: rsyncd: PID 644: rsync error: error in rsync protocol data stream (code 12) at /home/lapo/packaging/rsync-3.0.4-1/src/rsync-3.0.4/io.c(1541) [sender=3.0.4]. -Oorspronkelijk bericht- Van: Koen Linders [mailto:koen.lind...@koca.be] Verzonden: 07 January 2009 10:17 Aan: BackupPC-users@lists.sourceforge.net Onderwerp: [BackupPC-users] Remote backups of a win2003 server keeps failing after a certain amount of time. Remote backups of a win2003 server keeps failing after a certain amount of time (almost every time about 20h later / data 11 GB already done). Backup method: Rsyncd Server client: Rsync via Deltacopy (great piece of easy to configure software thanks to someone on this list, works perfectly for win2K, winXP, vista, win2003) Slow upload +- 512 KB/s 25 GB of data on a separate partition (not the windows one) Another win2003 with similar data (but less 9g) hasn't got a problem. The first full needed 24h, +- 100 KB/s average. = Could it be a specific file is too big? Too long name? = Anyone could point me to what to search for? Greetings, Koen Linders Contents of file /var/lib/backuppc/pc/80.201.242.118/LOG.012009, modified 2009-01-07 09:44:29 2009-01-01 20:00:00 full backup started for directory dDRIVE 2009-01-02 16:23:54 Aborting backup up after signal ALRM 2009-01-02 16:23:55 Got fatal error during xfer (aborted by signal=ALRM) 2009-01-02 16:23:55 Saved partial dump 0 2009-01-02 20:00:00 full backup started for directory dDRIVE 2009-01-03 16:24:01 Aborting backup up after signal ALRM 2009-01-03 16:24:02 Got fatal error during xfer (aborted by signal=ALRM) 2009-01-03 16:24:04 Saved partial dump 0 2009-01-03 17:00:00 full backup started for directory dDRIVE 2009-01-04 13:23:27 Aborting backup up after signal ALRM 2009-01-04 13:23:28 Got fatal error during xfer (aborted by signal=ALRM) 2009-01-04 13:23:28 Saved partial dump 0 2009-01-04 14:00:01 full backup started for directory dDRIVE 2009-01-05 10:26:18 Aborting backup up after signal ALRM 2009-01-05 10:26:20 Got fatal error during xfer (aborted by signal=ALRM) 2009-01-05 10:26:23 Saved partial dump 0 2009-01-05 15:19:04 full backup started for directory dDRIVE 2009-01-06 11:51:22 Aborting backup up after signal ALRM 2009-01-06 11:51:26 Got fatal error during xfer (aborted by signal=ALRM) 2009-01-06 11:51:29 Saved partial dump 0 2009-01-06 11:58:05 full backup started for directory dDRIVE 2009-01-07 09:44:26 Aborting backup up after signal ALRM 2009-01-07 09:44:28 Got fatal error during xfer (aborted by signal=ALRM) 2009-01-07 09:44:29 Saved partial dump 0 Contents of file /var/lib/backuppc/pc/80.201.242.118/XferLOG.0.z, modified 2009-01-07 09:44:28 (Extracting only Errors) full backup started for directory dDRIVE Connected to 80.201.242.118:873, remote version 30 Negotiated protocol version 28 Connected to module dDRIVE Sending args: --server --sender --numeric-ids --perms --owner --group -D --links --hard-links --times --block-size=2048 --recursive --ignore-times . . Sent exclude: Thumbs.db Sent exclude: IconCache.db Sent exclude: Cache Sent exclude: cache Sent exclude: /Documents and Settings/*/Local Settings/Temporary Internet Files Sent exclude: /Documents and Settings/*/Local Settings/Temp Sent exclude: /Documents and Settings/*/NTUSER.DAT Sent exclude: /Documents and Settings/*/ntuser.dat.LOG Sent exclude: /Documents and Settings/*/Local Settings/Application Data/Microsoft/Windows/UsrClass.dat Sent exclude: /Documents and Settings/*/Local Settings/Application Data/Microsoft/Windows/UsrClass.dat.LOG Sent exclude: /Documents and Settings/*/Local Settings/Application Data/Mozilla/Firefox/Profiles/*/Cache Sent exclude: /Documents and Settings/*/Local Settings/Application Data/Mozilla/Firefox/Profiles/*/OfflineCache Sent exclude: /Documents and Settings/*/Recent Sent exclude: *.lock Sent exclude: /WINDOWS Sent exclude: /RECYCLER Sent exclude: /MSOCache Sent exclude: /System Volume Information Sent exclude: /AUTOEXEC.BAT Sent exclude: /BOOTSECT.BAK Sent exclude: /CONFIG.SYS Sent exclude: /hiberfil.sys Sent exclude: /pagefile.sys Sent exclude: /Program
Re: [BackupPC-users] Remote backups of a win2003 server keeps failing after a certain amount of time.
Hi,
Koen Linders wrote on 2009-01-07 10:17:20 - [[BackupPC-users] Remote
backups of a win2003 server keeps failing after a certain amount of time.]:
Remote backups of a win2003 server keeps failing after a certain amount of
time (almost every time about 20h later / data 11 GB already done).
Backup method: Rsyncd
[...]
Contents of file /var/lib/backuppc/pc/80.201.242.118/LOG.012009, modified
2009-01-07 09:44:29
2009-01-01 20:00:00 full backup started for directory dDRIVE
2009-01-02 16:23:54 Aborting backup up after signal ALRM
2009-01-02 16:23:55 Got fatal error during xfer (aborted by signal=ALRM)
2009-01-02 16:23:55 Saved partial dump 0
signal ALRM is always caused by BackupPC aborting the backup after
$Conf{ClientTimeout} has passed without BackupPC detecting any progress. In
the case of rsync(d), this needs to account for the complete backup due to the
way it is implemented (for tar type backups, I believe it is only the duration
of the longest file transfer). The default value is 72000 seconds == 20 hours.
Raise $Conf{ClientTimeout} to a value that will allow your backup to complete.
A too high value has the drawback of not detecting stuck backups for that
amount of time. This is nothing to worry about for your first backup. Perhaps
just add a '0' and change the value back after the first backup has
successfully completed. Future rsync(d) backups should hopefully complete
significantly faster.
2009-01-02 20:00:00 full backup started for directory dDRIVE
2009-01-03 16:24:01 Aborting backup up after signal ALRM
2009-01-03 16:24:02 Got fatal error during xfer (aborted by signal=ALRM)
2009-01-03 16:24:04 Saved partial dump 0
I'm not sure why you repeatedly get a partial dump 0 though instead of the
transfer restarting from the point it was originally interrupted (using the
previous partial as reference). That would allow the backup to eventually
complete even without increasing ClientTimeout, but it does not seem to be
happening in your case.
Regards,
Holger
--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
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] Remote backups of a win2003 server keeps failing after a certain amount of time.
Thanks for the reply.
I changed the value to 144000 for this client and will wait another day (or
two).
Maybe it hangs on a specific file? I hope changing the value worked.
Anyway, thx :)
Koen Linders
-Oorspronkelijk bericht-
Van: Holger Parplies [mailto:wb...@parplies.de]
Verzonden: 07 January 2009 12:35
Aan: Koen Linders
CC: BackupPC-users@lists.sourceforge.net
Onderwerp: Re: [BackupPC-users] Remote backups of a win2003 server keeps
failing after a certain amount of time.
Hi,
Koen Linders wrote on 2009-01-07 10:17:20 - [[BackupPC-users] Remote
backups of a win2003 server keeps failing after a certain amount of time.]:
Remote backups of a win2003 server keeps failing after a certain amount of
time (almost every time about 20h later / data 11 GB already done).
Backup method: Rsyncd
[...]
Contents of file /var/lib/backuppc/pc/80.201.242.118/LOG.012009, modified
2009-01-07 09:44:29
2009-01-01 20:00:00 full backup started for directory dDRIVE
2009-01-02 16:23:54 Aborting backup up after signal ALRM
2009-01-02 16:23:55 Got fatal error during xfer (aborted by signal=ALRM)
2009-01-02 16:23:55 Saved partial dump 0
signal ALRM is always caused by BackupPC aborting the backup after
$Conf{ClientTimeout} has passed without BackupPC detecting any progress. In
the case of rsync(d), this needs to account for the complete backup due to
the
way it is implemented (for tar type backups, I believe it is only the
duration
of the longest file transfer). The default value is 72000 seconds == 20
hours.
Raise $Conf{ClientTimeout} to a value that will allow your backup to
complete.
A too high value has the drawback of not detecting stuck backups for that
amount of time. This is nothing to worry about for your first backup.
Perhaps
just add a '0' and change the value back after the first backup has
successfully completed. Future rsync(d) backups should hopefully complete
significantly faster.
2009-01-02 20:00:00 full backup started for directory dDRIVE
2009-01-03 16:24:01 Aborting backup up after signal ALRM
2009-01-03 16:24:02 Got fatal error during xfer (aborted by signal=ALRM)
2009-01-03 16:24:04 Saved partial dump 0
I'm not sure why you repeatedly get a partial dump 0 though instead of the
transfer restarting from the point it was originally interrupted (using the
previous partial as reference). That would allow the backup to eventually
complete even without increasing ClientTimeout, but it does not seem to be
happening in your case.
Regards,
Holger
--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
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] Remote backups of a win2003 server keeps failing after a certain amount of time.
Koen Linders wrote at about 14:05:56 + on Wednesday, January 7, 2009: Thanks for the reply. I changed the value to 144000 for this client and will wait another day (or two). Maybe it hangs on a specific file? I hope changing the value worked. That is very likely with Windoze. Rsync with protocol 28 can get stuck on files with long or weird filenames. If so you will see that rsync stops partway through by looking at the XferLOG file. Note this problem doesn't occur with protocol 30 (used by rsync 3.0) BUT this is not yet supported by perl-File-RsyncP. You can get around this by using rsyncd (with or without a separate ssh tunnel) instead of straight rsync. This question seems to come up once a week or more. If not already in the FAQ it should probably be added. Maybe it should also be added to the comments in the config.pl file too. -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ 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/
