Laptop logs off--now what?

[cedarcreek]

Basic question here, folks. I backup four computers, two are laptops. Occasionally one or both of the laptops are removed from the network during the backup, either before it's their turn, or in the midst of their backup. This causes Retrospect to stop the script's execution entirely, even if there's another client waiting in the wings to backup next.

 

Is there a way to script Retrospect such that when it doesn't find the next client (or that client is suddenly removed), it moves on to the next one and continues the backup operation? As it is, I've put these two removable clients at the end of the line, but it doesn't help if Client 3 heads off before its turn even though Client 4 is available and waiting on the network.

 

Or is the only option to manually re-run the day's script?

 

Thanks for any input.

[natew]

Hi

 

How about using a "backup server" script to backup your computers. It is much more flexible when it comes to computers leaving the network.

 

Nate

[cedarcreek]

I'm sorry, but I'm not quite sure what a "backup server" script would be.

 

We do not have a server in the network, simply a hub. Does that mean I cannot do a "backup server" script?

 

If I can do the script without a server, is it possible to do using the Retrospect Desktop software (with clients) that I now have or do I have to purchase a different, server-based Retrospect software package?

[AmyJ]

A Backup Server script is just a different type of script you can create - it is one of your options when you go to Automate > Scripts > New. See the User's Guide for detailed information on Backup Server scripts.

[cedarcreek]

Thank you for the explanation. I've read the manual now about "backup server" scripts--I'd avoided that section before because I didn't think it pertained to our setup. My bad.