Jump to content

Intermitten connection problems


Recommended Posts

I have Retrospect 6.1.126 running on a G5, backing up it and a G4, IMac, EMac (All OSX) and PC (XP). I have the client software running on all 4. I have it scheduled to backup every night beginning at 7:00 pm. I have it set to back up 1 folder every 15 minutes until all are done. It will back up the first, then can't connect for the next (same computer), then it will connect, then it won't. I came in this morning and tried to run some mannually and one wouldn't work 4 times, then on the 5th it did. I pinged the computer fine. I went under Config>Clients and every computer is listed as responding. Here is the log from last night:

 

+ Normal backup using G5 Customer Backup at 6/14/2007 7:00 PM

To backup set G5 Customer Backup…

 

- 6/14/2007 7:00:10 PM: Copying 0 - Customer Files on John's HD…

6/14/2007 7:00:15 PM: Comparing 0 - Customer Files on John's HD…

6/14/2007 7:00:17 PM: Execution completed successfully.

Completed: 15 files, 17.4 MB

Performance: 346.1 MB/minute (259.5 copy, 519.1 compare)

Duration: 00:00:07 (00:00:01 idle/loading/preparing)

 

+ Normal backup using G4 Customer Backup at 6/14/2007 7:15 PM

To backup set G4 Customer Backup…

Can't access volume 0 - Customer Files on Jimmy Riddle’s Computer, error -1028 (client is not visible on network).

6/14/2007 7:15:18 PM: Execution incomplete.

 

+ Normal backup using G4 Logos at 6/14/2007 7:30 PM

To backup set G4 Logos…

Can't access volume 02 - Logos, art, signatures on Jimmy Riddle’s Computer, error -1028 (client is not visible on network).

6/14/2007 7:30:17 PM: Execution incomplete.

 

+ Normal backup using G4 To Burn File at 6/14/2007 7:45 PM

To backup set G4 To Burn File…

 

- 6/14/2007 7:45:12 PM: Copying CD files on Jimmy Riddle’s Computer…

6/14/2007 7:45:12 PM: Connected to Jimmy Riddle’s Computer

6/14/2007 7:45:12 PM: No files need to be copied.

6/14/2007 7:45:15 PM: Execution completed successfully.

Duration: 00:00:03 (00:00:03 idle/loading/preparing)

 

+ Normal backup using G4 MyDocs at 6/14/2007 8:00 PM

To backup set G4 MyDocs…

Can't access volume 00 - Web Sites on Jimmy Riddle’s Computer, error -1028 (client is not visible on network).

6/14/2007 8:00:16 PM: Execution incomplete.

 

+ Normal backup using G4 Inhouse at 6/14/2007 8:15 PM

To backup set G4 Inhouse…

Can't access volume 02 - In House (New) on Jimmy Riddle’s Computer, error -1028 (client is not visible on network).

 

- 6/14/2007 8:15:16 PM: Copying 02 - In House (Old) on Jimmy Riddle’s Computer…

6/14/2007 8:15:16 PM: Connected to Jimmy Riddle’s Computer

6/14/2007 8:15:16 PM: No files need to be copied.

6/14/2007 8:15:25 PM: Execution completed successfully.

Duration: 00:00:09 (00:00:02 idle/loading/preparing)

 

- 6/14/2007 8:15:27 PM: Copying 03 - Inhouse folder on Jimmy Riddle’s Computer…

6/14/2007 8:15:27 PM: No files need to be copied.

6/14/2007 8:15:29 PM: Execution completed successfully.

Duration: 00:00:02 (00:00:02 idle/loading/preparing)

 

6/14/2007 8:15:31 PM: Execution incomplete.

Total duration: 00:00:13 (00:00:04 idle/loading/preparing)

 

+ Normal backup using Pricing PrintSmith at 6/14/2007 8:30 PM

To backup set Pricing PrintSmith…

 

- 6/14/2007 8:30:16 PM: Copying PrintSmith Folder on Eddie Morelock’s Computer…

6/14/2007 8:30:16 PM: Connected to Eddie Morelock’s Computer

6/14/2007 8:30:48 PM: Comparing PrintSmith Folder on Eddie Morelock’s Computer…

6/14/2007 8:31:09 PM: Execution completed successfully.

Completed: 21 files, 130.2 MB

Performance: 318.7 MB/minute (278.9 copy, 371.9 compare)

Duration: 00:00:53 (00:00:04 idle/loading/preparing)

 

+ Normal backup using Sarah Customer Backup at 6/14/2007 8:45 PM

To backup set Sarah Customer Backup…

 

- 6/14/2007 8:45:14 PM: Copying 00 - Customer Files on Sarah Travis's Computer…

6/14/2007 8:45:14 PM: Connected to Sarah Travis's Computer

6/14/2007 8:45:17 PM: Comparing 00 - Customer Files on Sarah Travis's Computer…

6/14/2007 8:45:19 PM: Execution completed successfully.

Completed: 2 files, 76 KB

Performance: 2.2 MB/minute (2.2 copy, 2.2 compare)

Duration: 00:00:05 (00:00:01 idle/loading/preparing)

 

+ Normal backup using GraphicsPC-Websites at 6/14/2007 9:00 PM

To backup set GraphicsPC-Websites…

 

- 6/14/2007 9:00:15 PM: Copying Websites on GraphicsPC…

6/14/2007 9:00:15 PM: Connected to GraphicsPC

6/14/2007 9:00:15 PM: No files need to be copied.

6/14/2007 9:00:21 PM: Execution completed successfully.

Duration: 00:00:06 (00:00:05 idle/loading/preparing)

 

+ Normal backup using GraphicsPC-00 at 6/14/2007 9:15 PM

To backup set GraphicsPC-00…

 

- 6/14/2007 9:15:16 PM: Copying 00-Misc on GraphicsPC…

6/14/2007 9:15:16 PM: Connected to GraphicsPC

6/14/2007 9:15:16 PM: No files need to be copied.

6/14/2007 9:15:18 PM: Execution completed successfully.

Duration: 00:00:02 (00:00:01 idle/loading/preparing)

 

+ Normal backup using GraphicsPC-A at 6/14/2007 9:30 PM

To backup set GraphicsPC-A…

 

- 6/14/2007 9:30:17 PM: Copying A on GraphicsPC…

6/14/2007 9:30:17 PM: Connected to GraphicsPC

6/14/2007 9:30:17 PM: No files need to be copied.

6/14/2007 9:30:21 PM: Execution completed successfully.

Duration: 00:00:04 (00:00:03 idle/loading/preparing)

 

+ Normal backup using GraphicsPC-B at 6/14/2007 9:45 PM

To backup set GraphicsPC-B…

 

- 6/14/2007 9:45:16 PM: Copying B on GraphicsPC…

6/14/2007 9:45:16 PM: Connected to GraphicsPC

6/14/2007 9:45:16 PM: No files need to be copied.

6/14/2007 9:45:18 PM: Execution completed successfully.

Duration: 00:00:02 (00:00:02 idle/loading/preparing)

 

+ Normal backup using GraphicsPC-C at 6/14/2007 10:00 PM

To backup set GraphicsPC-C…

 

- 6/14/2007 10:00:13 PM: Copying C on GraphicsPC…

6/14/2007 10:00:13 PM: Connected to GraphicsPC

6/14/2007 10:00:13 PM: No files need to be copied.

6/14/2007 10:00:15 PM: Execution completed successfully.

Duration: 00:00:02 (00:00:01 idle/loading/preparing)

 

+ Normal backup using GraphicsPC-D at 6/14/2007 10:15 PM

To backup set GraphicsPC-D…

 

- 6/14/2007 10:15:10 PM: Copying D on GraphicsPC…

6/14/2007 10:15:10 PM: Connected to GraphicsPC

6/14/2007 10:15:10 PM: No files need to be copied.

6/14/2007 10:15:12 PM: Execution completed successfully.

Duration: 00:00:02 (00:00:01 idle/loading/preparing)

 

+ Normal backup using GraphicsPC-E at 6/14/2007 10:30 PM

To backup set GraphicsPC-E…

Can't access volume E on GraphicsPC, error 519 (network communication failed).

6/14/2007 10:30:18 PM: Execution incomplete.

 

+ Normal backup using GraphicsPC-F at 6/14/2007 10:45 PM

To backup set GraphicsPC-F…

Can't access volume F on GraphicsPC, error 519 (network communication failed).

6/14/2007 10:45:13 PM: Execution incomplete.

 

+ Normal backup using GraphicsPC-G at 6/14/2007 11:00 PM

To backup set GraphicsPC-G…

Can't access volume G on GraphicsPC, error 519 (network communication failed).

6/14/2007 11:00:18 PM: Execution incomplete.

 

+ Normal backup using GraphicsPC-H at 6/14/2007 11:15 PM

To backup set GraphicsPC-H…

 

- 6/14/2007 11:15:13 PM: Copying H on GraphicsPC…

6/14/2007 11:15:13 PM: Connected to GraphicsPC

6/14/2007 11:15:13 PM: No files need to be copied.

6/14/2007 11:15:15 PM: Execution completed successfully.

Duration: 00:00:02 (00:00:01 idle/loading/preparing)

 

+ Normal backup using GraphicsPC-I at 6/14/2007 11:30 PM

To backup set GraphicsPC-I…

 

- 6/14/2007 11:30:20 PM: Copying I on GraphicsPC…

6/14/2007 11:30:20 PM: Connected to GraphicsPC

6/14/2007 11:30:20 PM: No files need to be copied.

6/14/2007 11:30:21 PM: Execution completed successfully.

Duration: 00:00:01

 

+ Normal backup using GraphicsPC-J at 6/14/2007 11:45 PM

To backup set GraphicsPC-J…

 

- 6/14/2007 11:45:16 PM: Copying J on GraphicsPC…

6/14/2007 11:45:16 PM: Connected to GraphicsPC

6/14/2007 11:45:19 PM: Comparing J on GraphicsPC…

6/14/2007 11:45:21 PM: Execution completed successfully.

Completed: 3 files, 1073 KB

Performance: 25.1 MB/minute (20.9 copy, 31.4 compare)

Duration: 00:00:05

 

+ Normal backup using GraphicsPC-K at 6/15/2007 12:00 AM

To backup set GraphicsPC-K…

 

- 6/15/2007 12:00:17 AM: Copying K on GraphicsPC…

6/15/2007 12:00:17 AM: Connected to GraphicsPC

6/15/2007 12:00:17 AM: No files need to be copied.

6/15/2007 12:00:19 AM: Execution completed successfully.

Duration: 00:00:02 (00:00:01 idle/loading/preparing)

 

+ Normal backup using GraphicsPC-L at 6/15/2007 12:15 AM

To backup set GraphicsPC-L…

 

- 6/15/2007 12:15:17 AM: Copying L on GraphicsPC…

6/15/2007 12:15:17 AM: Connected to GraphicsPC

6/15/2007 12:15:17 AM: No files need to be copied.

6/15/2007 12:15:19 AM: Execution completed successfully.

Duration: 00:00:02 (00:00:01 idle/loading/preparing)

 

+ Normal backup using GraphicsPC-M at 6/15/2007 12:30 AM

To backup set GraphicsPC-M…

 

- 6/15/2007 12:30:15 AM: Copying M on GraphicsPC…

6/15/2007 12:30:15 AM: Connected to GraphicsPC

6/15/2007 12:30:25 AM: Comparing M on GraphicsPC…

6/15/2007 12:30:27 AM: Execution completed successfully.

Completed: 11 files, 2172 KB

Performance: 28.2 MB/minute (18.1 copy, 63.6 compare)

Duration: 00:00:12 (00:00:03 idle/loading/preparing)

 

+ Normal backup using GraphicsPC-N at 6/15/2007 12:45 AM

To backup set GraphicsPC-N…

 

- 6/15/2007 12:45:18 AM: Copying N on GraphicsPC…

6/15/2007 12:45:18 AM: Connected to GraphicsPC

6/15/2007 12:46:08 AM: Comparing N on GraphicsPC…

6/15/2007 12:46:46 AM: Execution completed successfully.

Completed: 15 files, 163.6 MB

Performance: 228.2 MB/minute (204.4 copy, 258.3 compare)

Duration: 00:01:28 (00:00:02 idle/loading/preparing)

 

+ Normal backup using GraphicsPC-O at 6/15/2007 1:00 AM

To backup set GraphicsPC-O…

 

- 6/15/2007 1:00:12 AM: Copying O on GraphicsPC…

6/15/2007 1:00:12 AM: Connected to GraphicsPC

6/15/2007 1:00:26 AM: Comparing O on GraphicsPC…

6/15/2007 1:00:32 AM: Execution completed successfully.

Completed: 4 files, 8730 KB

Performance: 68.2 MB/minute (56.8 copy, 85.2 compare)

Duration: 00:00:20 (00:00:05 idle/loading/preparing)

 

+ Normal backup using GraphicsPC-P at 6/15/2007 1:15 AM

To backup set GraphicsPC-P…

 

- 6/15/2007 1:15:17 AM: Copying P on GraphicsPC…

6/15/2007 1:15:17 AM: Connected to GraphicsPC

6/15/2007 1:15:17 AM: No files need to be copied.

6/15/2007 1:15:22 AM: Execution completed successfully.

Duration: 00:00:05 (00:00:03 idle/loading/preparing)

 

+ Normal backup using GraphicsPC-Q at 6/15/2007 1:30 AM

To backup set GraphicsPC-Q…

 

- 6/15/2007 1:30:17 AM: Copying Q on GraphicsPC…

6/15/2007 1:30:17 AM: Connected to GraphicsPC

6/15/2007 1:30:17 AM: No files need to be copied.

6/15/2007 1:30:20 AM: Execution completed successfully.

Duration: 00:00:03

 

+ Normal backup using GraphicsPC-R at 6/15/2007 1:45 AM

To backup set GraphicsPC-R…

 

- 6/15/2007 1:45:15 AM: Copying R on GraphicsPC…

6/15/2007 1:45:15 AM: Connected to GraphicsPC

6/15/2007 1:45:15 AM: No files need to be copied.

6/15/2007 1:45:19 AM: Execution completed successfully.

Duration: 00:00:04 (00:00:02 idle/loading/preparing)

 

+ Normal backup using GraphicsPC-S at 6/15/2007 2:00 AM

To backup set GraphicsPC-S…

 

- 6/15/2007 2:00:14 AM: Copying S on GraphicsPC…

6/15/2007 2:00:14 AM: Connected to GraphicsPC

6/15/2007 2:00:22 AM: Comparing S on GraphicsPC…

6/15/2007 2:00:23 AM: Execution completed successfully.

Completed: 3 files, 488 KB

Performance: 8.1 MB/minute (4.7 copy, 28.5 compare)

Duration: 00:00:09 (00:00:02 idle/loading/preparing)

 

+ Normal backup using GraphicsPC-T at 6/15/2007 2:15 AM

To backup set GraphicsPC-T…

 

- 6/15/2007 2:15:16 AM: Copying T on GraphicsPC…

6/15/2007 2:15:16 AM: Connected to GraphicsPC

6/15/2007 2:20:46 AM: Comparing T on GraphicsPC…

6/15/2007 2:27:01 AM: Execution completed successfully.

Completed: 141 files, 579.8 MB

Performance: 98.9 MB/minute (106.0 copy, 92.7 compare)

Duration: 00:11:45 (00:00:02 idle/loading/preparing)

 

+ Normal backup using GraphicsPC-U at 6/15/2007 2:30 AM

To backup set GraphicsPC-U…

 

- 6/15/2007 2:30:15 AM: Copying U on GraphicsPC…

6/15/2007 2:30:15 AM: Connected to GraphicsPC

6/15/2007 2:30:31 AM: Comparing U on GraphicsPC…

6/15/2007 2:30:33 AM: Execution completed successfully.

Completed: 16 files, 10.1 MB

Performance: 70.6 MB/minute (40.0 copy, 300.2 compare)

Duration: 00:00:18 (00:00:01 idle/loading/preparing)

 

+ Normal backup using GraphicsPC-V at 6/15/2007 2:45 AM

To backup set GraphicsPC-V…

 

- 6/15/2007 2:45:19 AM: Copying V on GraphicsPC…

6/15/2007 2:45:19 AM: Connected to GraphicsPC

6/15/2007 2:45:52 AM: Comparing V on GraphicsPC…

6/15/2007 2:46:11 AM: Execution completed successfully.

Completed: 9 files, 42.1 MB

Performance: 98.9 MB/minute (78.8 copy, 132.7 compare)

Duration: 00:00:52 (00:00:01 idle/loading/preparing)

 

+ Normal backup using GraphicsPC-W at 6/15/2007 3:00 AM

To backup set GraphicsPC-W…

 

- 6/15/2007 3:00:17 AM: Copying W on GraphicsPC…

6/15/2007 3:00:17 AM: Connected to GraphicsPC

6/15/2007 3:00:32 AM: Comparing W on GraphicsPC…

6/15/2007 3:00:38 AM: Execution completed successfully.

Completed: 63 files, 52.7 MB

Performance: 316.0 MB/minute (225.7 copy, 526.6 compare)

Duration: 00:00:21 (00:00:01 idle/loading/preparing)

 

+ Normal backup using GraphicsPC-X at 6/15/2007 3:15 AM

To backup set GraphicsPC-X…

 

- 6/15/2007 3:15:14 AM: Copying X on GraphicsPC…

6/15/2007 3:15:14 AM: Connected to GraphicsPC

6/15/2007 3:15:14 AM: No files need to be copied.

6/15/2007 3:15:15 AM: Execution completed successfully.

Duration: 00:00:01

 

+ Normal backup using GraphicsPC-Y at 6/15/2007 3:30 AM

To backup set GraphicsPC-Y…

 

- 6/15/2007 3:30:10 AM: Copying Y on GraphicsPC…

6/15/2007 3:30:10 AM: Connected to GraphicsPC

6/15/2007 3:30:26 AM: Comparing Y on GraphicsPC…

6/15/2007 3:30:31 AM: Execution completed successfully.

Completed: 57 files, 87.3 MB

Performance: 498.5 MB/minute (327.1 copy, 1046.8 compare)

Duration: 00:00:21

 

+ Normal backup using GraphicsPC-Z at 6/15/2007 3:45 AM

To backup set GraphicsPC-Z…

Can't access volume Z on GraphicsPC, error 519 (network communication failed).

6/15/2007 3:45:17 AM: Execution incomplete.

Quit at 6/15/2007 3:45 AM

 

None of the computers are set to go to sleep. We have screen savers running on each one, but that's it. This is driving me crazy! What's the use of having a backup program, if it's not going to backup? Any ideas?

Link to comment
Share on other sites

Quote:

and a G4, IMac, EMac (All OSX) and PC (XP). I have the client software running on all 4.

 


What version of Retrospect client on each?

 

Also,

 

(1) Do you happen to have the Retrospect cshutdown.py script installed on the clients to shut them down when the backup is finished?

 

(2) What happens if you turn the screen saver off, or if you set its kick-in time out to, say, 30 minutes?

 

(3) Are you SURE that the clients are not going to sleep? Have you checked the Energy Saver preferences?

 

(4) Is there a reason that you don't back up all of the sources on each computer in a single per-computer script? Is there some special reason why you are running multiple scripts for each computer?

 

And, while I'm asking, is there a reason (other than having a separate backup set for each computer) why you aren't backing up all computers in a single script?

 

Just some things to consider.

 

Russ

Link to comment
Share on other sites

Quote:

What version of Retrospect client on each?

 


Mac- 6.1.107 PC-7.0.107

 

Quote:

Also,

 

(1) Do you happen to have the Retrospect cshutdown.py script installed on the clients to shut them down when the backup is finished?

 


No.

 

Quote:

(2) What happens if you turn the screen saver off, or if you set its kick-in time out to, say, 30 minutes?

 


The screen saver wasn't on this morning when I tried to manually back up and still got the error message.

 

Quote:

(3) Are you SURE that the clients are not going to sleep? Have you checked the Energy Saver preferences?

 


Yep. The hard drives are not set to go to sleep.

 

Quote:

(4) Is there a reason that you don't back up all of the sources on each computer in a single per-computer script? Is there some special reason why you are running multiple scripts for each computer?

 


We're a print shop. Our files are huge as they are, if I tried to back up each computer with one script, the files would be larger than a DVD could hold.

Link to comment
Share on other sites

Ok. Only oddity that I spot is that the Retrospect client is VERY old. Current Mac Retrospect client is 6.1.130. Current PC client for use with Retrospect 6.1 Mac is 7.0.112, so you might want to update them. Updates are here:

Retrospect updates

 

It's not as if (compared to what I'm doing each day) that you are backing up a lot of files or a lot of data, so the updating catalog phase should happen quite quickly on close of each backup set.

 

It wasn't until your last post that I realized that you are doing DVD backups, and you haven't said which version of RDU you have installed, or what DVD drive you have, or whether you did a manual configuration of the drive.

 

If your RDU (Retrospect Driver Update) is old, or if it is the most very recent one (RDU 6.1.10.100), that could be causing other problems, perhaps not these problems. You might want to update (or regress) your RDU if necessary to RDU 6.1.9.102. RDU updates are here:

RDU version history

 

If you've done a manual configuration of the DVD drive (rather than use the configuration supplied by the RDU), that could cause it to go slowly, but probably wouldn't cause these problems. You could test that, after getting RDU 6.1.9.102, by dragging the .rdi file in /Library/Preferences/Retrospect to the desktop (with Retrospect not running) to preserve it in case you want to go back to that manual configuration of the drive, then test using the default (and usually better) configuration parameters in the RDU.

 

Other than these suggestions, I'm stumped.

 

Russ

Link to comment
Share on other sites

The fact that you're getting two different kinds of communication errors, -519 and -1028, suggests to me that you're having a network communication issue. You don't provide any information regarding your physical wiring, but if needs to be clean, well terminated, unpinched, CAT5 or better. Was the network wiring professional done?

 

> We're a print shop. Our files are huge as they are, if I tried to back up each computer

> with one script, the files would be larger than a DVD could hold.

 

This doesn't make any sense to me. If your Media isn't large enough to hold all the data you need to back up, it doesn't matter if you're running a single script or a dozen. When your scripts are running overnight, there's no one there to swap Media Members. You'll have to better explain what your backup stragegy that overcomes the size limitation of the type of backup device you're using.

 

There's no reason to connect and then reconnect to a client computer. I'd suggest making a Source Group for each physical client machine, and putting the necessary folders into each group, for use in your script(s).

 

Dave

Link to comment
Share on other sites

Quote:

Ok. Only oddity that I spot is that the Retrospect client is VERY old. Current Mac Retrospect client is 6.1.130. Current PC client for use with Retrospect 6.1 Mac is 7.0.112, so you might want to update them. Updates are here:

 

It's not as if (compared to what I'm doing each day) that you are backing up a lot of files or a lot of data, so the updating catalog phase should happen quite quickly on close of each backup set.

 

It wasn't until your last post that I realized that you are doing DVD backups, and you haven't said which version of RDU you have installed, or what DVD drive you have, or whether you did a manual configuration of the drive.

 

If your RDU (Retrospect Driver Update) is old, or if it is the most very recent one (RDU 6.1.10.100), that could be causing other problems, perhaps not these problems. You might want to update (or regress) your RDU if necessary to RDU 6.1.9.102. RDU updates are here:

 

If you've done a manual configuration of the DVD drive (rather than use the configuration supplied by the RDU), that could cause it to go slowly, but probably wouldn't cause these problems. You could test that, after getting RDU 6.1.9.102, by dragging the .rdi file in /Library/Preferences/Retrospect to the desktop (with Retrospect not running) to preserve it in case you want to go back to that manual configuration of the drive, then test using the default (and usually better) configuration parameters in the RDU.

 

Other than these suggestions, I'm stumped.

 

Russ

 


I'll try updating all the clients and see if that helps. I thought that I had already done that, but I guess I didn't.

 

I backup each night to files. Then, once a month, I move those files to DVD's and store them off-site. If I were to backup each computer to one file, over the course of a month, they'd be so big, they wouldn't fit on a disc. That's why I back them up to multiple files.

Link to comment
Share on other sites

Quote:

The fact that you're getting two different kinds of communication errors, -519 and -1028, suggests to me that you're having a network communication issue. You don't provide any information regarding your physical wiring, but if needs to be clean, well terminated, unpinched, CAT5 or better. Was the network wiring professional done?

 


 

The computers are all connected to a switch by CAT5 cables. I have the backups scheduled every 15 minutes. I don't understand why it can connect to a computer 2 times successfully and then can't connect the next time and then can the next, etc.

Link to comment
Share on other sites

Quote:

but when I downloaded the Windows client, it creates a file with a .rcu extension. What am I supposed to do with that?

 


Those are files that can be "pushed" from Retrospect. Put them somewhere then use "update client" (configure > clients).

 

Quote:

I have the backups scheduled every 15 minutes.

 


Be aware that the Retrospect script scheduler is bizarre and non-standard. Here's the algorithm that it uses:

At any time when the scheduling list is checked, if there are scripts whose scheduled time is past, then run the first of those scripts IN ALPHABETIC ORDER - the scripts are NOT run in the order in which they were scheduled. I am not aware that this is documented anywhere, but that's the way it works. Learned it the hard way.

 

A side effect of this is that, if a script runs past the scheduling window to the next scripts such that two scripts become runnable when the current script finishes, then the scripts may not run in the order you expect. To work around this bug (um, feature) that has existed at least since Retrospect 2.0, I name my scripts alphabetically for their run order in addition to appropriately scheduling them.

 

Quote:

I don't understand why it can connect to a computer 2 times successfully and then can't connect the next time and then can the next, etc.

 


You are perhaps trying to understand that which cannot be understood by us mere mortals. It may be a race condition such that the client is cleaning up from a previous script and is not answering.

 

Russ

Link to comment
Share on other sites

'fraid I can't solve it but I recognise the problem sometimes it helps to know someone else has the same crap! Was told by my techie that it's a known problem and when I migrate to osx completely the problem will go away. Which it hasn't. although it ain't half as bad as it was. Will watch this one...

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...