I am trying to configure two physical RHEL servers that are not domain-joined. I need to back these servers up and need to install the agent first.
Considering all firewall rules are in place, which would be the best way to install the file system agent and then configure for backups.
Would a decoupled install work just fine? Installing the agent locally on the client server, then adding the client fetching “the configuration information from the client that is already installed in decoupled mode.”
I am having a hard time finding documentation with a case like this.
All I am trying to figure out is how to get the Commserve to reach the servers once the agents are installed. Once the Commserve can talk to the clients I am able to configure the rest.
I was wondering if this is even possible. Usually, I deal with servers that are domain-joined.
Thanks in advance!
Best answer by Rajiv
Hello @SMDQ I don't think we would need the client to be connected to domain for installation purpose. Just make sure the communication is working via IP address to CS and vice versa. If the machine is up without the domain, you can still install the agent using the IP address and the hostname.
Otherwise, a decoupled installation is also a suitable approach.
1. Perform a Decoupled Installation: Install the File System Agent on the RHEL servers using the decoupled installation method. This allows the agent to be installed without immediate connectivity to the CommServe. 2. Configure the Client Manually: After the installation, manually configure the client on the CommServe. This involves adding the client to the CommServe with its IP address or hostname, ensuring that it matches the configuration on the RHEL server. 3. Check Connectivity and Firewall Rules: Ensure that all necessary firewall rules are in place to allow communication between the CommServe and the RHEL servers. This includes opening the required ports for Commvault operations. 4. Fetch Configuration: Once the CommServe can reach the RHEL servers, fetch the configuration from the CommServe to the client. This syncs the client with the CommServe, allowing for proper management and backup configuration.
Hello @SMDQ I don't think we would need the client to be connected to domain for installation purpose. Just make sure the communication is working via IP address to CS and vice versa. If the machine is up without the domain, you can still install the agent using the IP address and the hostname.
Otherwise, a decoupled installation is also a suitable approach.
1. Perform a Decoupled Installation: Install the File System Agent on the RHEL servers using the decoupled installation method. This allows the agent to be installed without immediate connectivity to the CommServe. 2. Configure the Client Manually: After the installation, manually configure the client on the CommServe. This involves adding the client to the CommServe with its IP address or hostname, ensuring that it matches the configuration on the RHEL server. 3. Check Connectivity and Firewall Rules: Ensure that all necessary firewall rules are in place to allow communication between the CommServe and the RHEL servers. This includes opening the required ports for Commvault operations. 4. Fetch Configuration: Once the CommServe can reach the RHEL servers, fetch the configuration from the CommServe to the client. This syncs the client with the CommServe, allowing for proper management and backup configuration.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.