SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
150-minute backup tendency
Author Message
Post 150-minute backup tendency 
Gang,

Virtually all of the WinXP boxes I'm backing up will fail (for various
reasons) after 2.5 hours. Local boxes (on my net) will go longer, to
roughly 3.5 hours, but the boxes I'm backing up over the net tend to stop at
at between 2 hours and 2.5 hours.

Here's the log file from one of the more successful backups (over the net).
Two backup runs went much longer, proving that this is not a "barrier" per
se, but more of a tendency. Average backup run from this file below is 163
minutes, but as you can see, lots of 150-minute runs.

Any suggestions of things to tweak to try to get these full backup runs
(initial backup runs) to go longer? What is the deal with these signal=ALRM
errors?

Thanks,

Todd

2004-07-16 14:00:03 full backup started for directory docs
2004-07-16 14:00:06 Got fatal error during xfer (auth failed on module docs)
2004-07-16 14:00:11 Backup aborted (auth failed on module docs)
2004-07-16 14:02:45 full backup started for directory docs
2004-07-16 15:31:58 Got fatal error during xfer (Child exited prematurely)
2004-07-16 15:32:03 Backup aborted (Child exited prematurely)
2004-07-16 15:32:03 Saved partial dump 0
[92 Minutes]
2004-07-16 16:00:02 full backup started for directory docs
2004-07-16 18:13:20 Aborting backup up after signal ALRM
2004-07-16 18:13:21 Got fatal error during xfer (aborted by signal=ALRM)
2004-07-16 18:13:21 Saved partial dump 0
[133 minutes]
2004-07-16 19:00:01 full backup started for directory docs
2004-07-16 21:18:37 Aborting backup up after signal ALRM
2004-07-16 21:18:38 Got fatal error during xfer (aborted by signal=ALRM)
2004-07-16 21:18:38 Saved partial dump 0
[139 minutes]
2004-07-16 22:00:02 full backup started for directory docs
2004-07-17 00:59:46 Aborting backup up after signal ALRM
2004-07-17 00:59:48 Got fatal error during xfer (aborted by signal=ALRM)
2004-07-17 00:59:48 Saved partial dump 0
[180 minutes]
2004-07-17 01:02:04 full backup started for directory docs
2004-07-17 04:53:32 Aborting backup up after signal ALRM
2004-07-17 04:53:34 Got fatal error during xfer (aborted by signal=ALRM)
2004-07-17 04:53:35 Saved partial dump 0
[231 minutes -- great run!]
2004-07-17 05:00:03 full backup started for directory docs
2004-07-17 10:33:00 Aborting backup up after signal ALRM
2004-07-17 10:33:01 Got fatal error during xfer (aborted by signal=ALRM)
2004-07-17 10:33:02 Saved partial dump 0
[333 minutes -- if only they could all be like this! read on...]
2004-07-17 11:00:03 full backup started for directory docs
2004-07-17 13:29:43 Aborting backup up after signal ALRM
2004-07-17 13:29:44 Got fatal error during xfer (aborted by signal=ALRM)
2004-07-17 13:29:44 Saved partial dump 0
[150 minutes]
2004-07-17 14:00:02 full backup started for directory docs
2004-07-17 16:28:45 Aborting backup up after signal ALRM
2004-07-17 16:28:47 Got fatal error during xfer (aborted by signal=ALRM)
2004-07-17 16:28:47 Saved partial dump 0
[148 minutes]
2004-07-17 17:00:02 full backup started for directory docs
2004-07-17 19:30:17 Aborting backup up after signal ALRM
2004-07-17 19:30:19 Got fatal error during xfer (aborted by signal=ALRM)
2004-07-17 19:30:19 Saved partial dump 0
[150 minutes]
2004-07-17 20:00:03 full backup started for directory docs
2004-07-17 22:28:39 Aborting backup up after signal ALRM
2004-07-17 22:28:46 Got fatal error during xfer (aborted by signal=ALRM)
2004-07-17 22:28:47 Saved partial dump 0
[148 minutes]
2004-07-17 23:00:15 full backup started for directory docs
2004-07-18 01:28:44 Aborting backup up after signal ALRM
2004-07-18 01:28:46 Got fatal error during xfer (aborted by signal=ALRM)
2004-07-18 01:28:46 Saved partial dump 0
[148 minutes]
2004-07-18 05:00:03 full backup started for directory docs
2004-07-18 07:29:06 Aborting backup up after signal ALRM
2004-07-18 07:29:10 Got fatal error during xfer (aborted by signal=ALRM)
2004-07-18 07:29:10 Saved partial dump 0
[149 minutes]
2004-07-18 08:00:02 full backup started for directory docs
2004-07-18 10:32:43 Aborting backup up after signal ALRM
2004-07-18 10:32:45 Got fatal error during xfer (aborted by signal=ALRM)
2004-07-18 10:32:46 Saved partial dump 0
[152 minutes]
2004-07-18 11:00:02 full backup started for directory docs
2004-07-18 13:32:12 Aborting backup up after signal ALRM
2004-07-18 13:32:13 Got fatal error during xfer (aborted by signal=ALRM)
2004-07-18 13:32:13 Saved partial dump 0
[152 minutes]
2004-07-18 14:00:01 full backup started for directory docs
2004-07-18 15:28:08 full backup 0 complete, 45503 files, 3032020927 bytes,
101 xferErrs (0 bad files, 0 bad shares, 101 other)
2004-07-19 14:00:01 incr backup started back to 2004-07-18 13:00:01 for
directory docs
2004-07-19 16:14:50 Aborting backup up after signal ALRM
2004-07-19 16:14:54 Got fatal error during xfer (aborted by signal=ALRM)
2004-07-19 17:00:02 incr backup started back to 2004-07-18 13:00:01 for
directory docs
2004-07-19 17:23:14 incr backup 1 complete, 873 files, 249110058 bytes, 12
xferErrs (0 bad files, 0 bad shares, 12 other)
2004-07-20 17:00:02 incr backup started back to 2004-07-18 13:00:01 for
directory docs
2004-07-20 17:27:34 incr backup 2 complete, 1234 files, 256266190 bytes, 12
xferErrs (0 bad files, 0 bad shares, 12 other)



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Post 150-minute backup tendency 
On 07/21 10:36 , Todd Curry wrote:

Virtually all of the WinXP boxes I'm backing up will fail (for various
reasons) after 2.5 hours. Local boxes (on my net) will go longer, to
roughly 3.5 hours, but the boxes I'm backing up over the net tend to stop at
at between 2 hours and 2.5 hours.

what is your timeout set to?

try setting this:

# timeout in seconds.
# this sometimes incorrectly means the duration of the backup.
# set to 12 hours, and see if backups no longer fail with 'ALRM'
$Conf{ClientTimeout} = 43200

in the per-machine configuration file; and see if it makes a difference.

--
Carl Soderstrom
Systems Administrator
Real-Time Enterprises
www.real-time.com


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Post 150-minute backup tendency 
Carl, this helped immensely; I assumed that 7200 would be fine, but upping
that by a factor of 6 has kept my internet backups running smoothly and
continuously. Thanks!

-----Original Message-----
From: Carl Wilhelm Soderstrom [mailto:chrome < at > real-time.com]
Sent: Wednesday, July 21, 2004 11:48 AM
To: Todd Curry
Cc: backuppc-users < at > lists.sourceforge.net
Subject: Re: [BackupPC-users] 150-minute backup tendency


On 07/21 10:36 , Todd Curry wrote:

Virtually all of the WinXP boxes I'm backing up will fail (for various
reasons) after 2.5 hours. Local boxes (on my net) will go longer, to
roughly 3.5 hours, but the boxes I'm backing up over the net tend to stop
at
at between 2 hours and 2.5 hours.

what is your timeout set to?

try setting this:

# timeout in seconds.
# this sometimes incorrectly means the duration of the backup.
# set to 12 hours, and see if backups no longer fail with 'ALRM'
$Conf{ClientTimeout} = 43200

in the per-machine configuration file; and see if it makes a difference.

--
Carl Soderstrom
Systems Administrator
Real-Time Enterprises
www.real-time.com





-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Post 150-minute backup tendency 
I've only been on the list for a few weeks, and I've read Carl telling
people to increase that timeout at least three times (Once to me.) I think
it's probably about time to make it into the documentation, isn't it? Smile

I still love this product. We were using tapeware, and waiting up to 4-5
hours for a restore of one file. Now, of course, it only takes minutes.

Kudos!

-----Original Message-----
From: backuppc-users-admin < at > lists.sourceforge.net
[mailto:backuppc-users-admin < at > lists.sourceforge.net]On Behalf Of Todd
Curry
Sent: Thursday, July 22, 2004 9:57 PM
To: Carl Wilhelm Soderstrom
Cc: backuppc-users < at > lists.sourceforge.net
Subject: RE: [BackupPC-users] 150-minute backup tendency


Carl, this helped immensely; I assumed that 7200 would be fine, but upping
that by a factor of 6 has kept my internet backups running smoothly and
continuously. Thanks!

-----Original Message-----
From: Carl Wilhelm Soderstrom [mailto:chrome < at > real-time.com]
Sent: Wednesday, July 21, 2004 11:48 AM
To: Todd Curry
Cc: backuppc-users < at > lists.sourceforge.net
Subject: Re: [BackupPC-users] 150-minute backup tendency


On 07/21 10:36 , Todd Curry wrote:

Virtually all of the WinXP boxes I'm backing up will fail (for various
reasons) after 2.5 hours. Local boxes (on my net) will go longer, to
roughly 3.5 hours, but the boxes I'm backing up over the net tend to stop
at
at between 2 hours and 2.5 hours.

what is your timeout set to?

try setting this:

# timeout in seconds.
# this sometimes incorrectly means the duration of the backup.
# set to 12 hours, and see if backups no longer fail with 'ALRM'
$Conf{ClientTimeout} = 43200

in the per-machine configuration file; and see if it makes a difference.

--
Carl Soderstrom
Systems Administrator
Real-Time Enterprises
www.real-time.com





-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.725 / Virus Database: 480 - Release Date: 7/19/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.725 / Virus Database: 480 - Release Date: 7/19/2004



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB