ok, so we're starting to look at moving to Agents on the Fly configuration, and on the system I've tested this with I'm very much liking the results. Had a brief conversation with our Unix guy however, and this raised a question about how we have our NAS mounts configured and if this will work with AotF.
We have /usr/sap mounted locally to our hosts, and then we have /<sid>/ whatever on a NAS mount that is shared between hosts. We have up to 4 hosts (primary/secondary and then second failover set) that all share the NAS. Since the AotF is installed on the shared mount, how does it pick up the new host name if the primary fails and the host moves to the secondary or failover servers? These are active/passive, so only one server at a time is actively using the connection.
When the Agent is initially installed, it identifies the host name where it is installed, but when the NAS flips to another server, that host name no longer matches the agent. Do we simply need to create profiles for all possible hosts in the profile directory? But then how does runtime.properties fit into the picture, since it only contains 1 host name??
I know we've had problems with the host_profile being corrupted because of being installed on a shared drive - does AotF suffer from similar issues? Or do we need to install them to a truly local drive?
So many questions... lol
Thanks.
Bernie Krause