You know what would be really cool to do, is to tie AppleTalk and TCP/IP into the Retrospect Clients.
This seems like it would work real well for DHCP clients to have both AppleTalk and TCP/IP talking to the server. Why? AppleTalk could be used to tell the server the current IP address of the machine. It could also be used as a fall back in case IP fails.
This won't solve any problems for folks that don't pass AppleTalk at all, but it will for the others.
I am having problems keeping my windows clients backed up.
Our setup is as follows:
Mac G4 running Retrospect 4.3
We have 4 subnets in our building. Our G4 lives on one , while the clients live on the other 3 subnets.
The problem appears to be related to DHCP.
We have a seven day lease period for IP addresses.
It appears that whenever the client's IP address changes, the backup server loses track of the client and therefore the client does not get backed up.
I have to manually add them back into the client database and re-add them to the script.
Does anyone have any experience or suggestions with running a backup server and using DHCP as the method for assigning IP addresses?