the only rule for the primary NIC allows all traffic. I do have ipchains active on these Linux machines, but all the restrictive rules are for the secondary "exposed" NIC. This would indicate that the problem is the client or at least how it deals with responding to the discover process when the machine has two NICs. Without doing anything special, FileMaker Server is only available on the primary NIC. I have FileMaker Server running on these machines and FileMaker Pro can "discover" the server and list the served files. So whats the deal with the Linux client and 2 NICs? I dare say that if I instructed Retrospect for Windows to forget these Linux clients it wouldn't discover them either. When I set up my Windows Backup Server my Linux machines were just on the LAN and used only one of their NICs. the machines I can't "discover" have both NICs active and are acting as network gateways. What I've found is that the working machine had one active NIC. I've had a think about what is different between my environments and I've reconfigured one of my Linux machines to replicate the working configuration I encountered. The first site produced the same experience as I have in my LAN. This afternoon I installed Retrospect 5.1 at two client sites. I installed Retrospect 5.1 on the MacOS X iBook and it could "discover" everything except the Linux machines, but it could see them once they were added to the client database by entering their IP addresses. It backs up 2 Linux machines, a MacOS X Server, a MacOS 9.2 iBook, a MacOS X iBook and 3 older MacOS desktops. Perhaps I should outline the environment I was testing in.Ĭurrently I'm running a W2K box as a "Backup Server". Chemin de la GVuiteboeuf, Switzerland +41. I was using Retrospect 5.0, but I've been able to reproduce the same situation on a clean machine. Are you looking for a free backup software for Linux, Windows, VMware or Mac Take a look at Bacula - advanced free enterprise-ready open source backup software. Having added them my Linux clients by IP I've upgraded by Qube3s to client version 6.5.108 but they still don't "appear" when I attempt to add clients. At least now I can add them by IP.Īny suggestions as to what the problem is? Server evaluation key but it still can't "see" my Linux machines on the Machines are running client 6.0.143 and 6.5.105. Installation of 5.1 went well, but it will not see my Linux machinesĪlthough my Windows (Backup Server) can see them. Supports the Linux client I've downloaded an evaluation version to give it a Qube3s to be precise) and its been working great. I've been using the Windows version to backup my Linux machines (Cobalt > Disaster Recovery CD and support for Red Hat "Linux" versions 6.2, 7.1, This exciting new version adds many new features including a bootable
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |