Custom selection of a directory for script execution on a remote Linux server

Context:

• To execute scripts on a custom remote directory on a remote server, you can configure CDM externally with the remote directory where the script is expected to be pushed and then executed.
• If the directory is not present, CDM creates it as far as the user and the filesystem have necessary permissions.

Note: This is applicable for custom script execution only from the Advance Options in the backup job window. CDM agent code is mandated to run under the /tmp directory only and you cannot customize the directory location for the agent code and its execution. Hence it is mandatory to have execution rights to the user and filesystem.

Pre-requisites:

1. The directory and the user both must have the necessary permissions to execute the script.
2. Verify that the filesystem where the directory is present is not restricted with the 'noexec' option.

Steps to update the default remote script directory location from /tmp to a custom directory:

1. SSH to CDM appliance using root user credentials.
2. Navigate to directory /opt/virgo/repository/ecx-usr.
3. Look for a file named com.catalogic.ecx.remoteexecutor.properties.
4. Open the file and you can see a property named 'remote.config.script.destinationLocation' whose default value is set to '/tmp' (For example, remote.config.script.destinationLocation=/tmp).
5. Update the property value to the custom directory as per the requirement and save the file. For example, remote.config.script.destinationLocation=/data. In this case, script is pushed to the /data directory and executed from there.
6. In order to have CDM reflect this change and consider the updated directory path, CDM services need to be restarted/rebooted.
7. Also note that this is a global property and will be reflected for all script executions on Linux servers across all jobs.

Precautionary measures before restarting CDM appliance:

1. Make a maintenance window available for about 15 to 20 mins.
2. Verify that there are no active running jobs and restore jobs in the RESOURCE ACTIVE state. 
3. If any job is in the Active or Resource Active state, make sure to bring them to the IDLE state before restarting CDM services.
4. Only when above prerequisites are satisfied, CDM services can be restarted using the admin console GUI.
5. After reboot, wait about 10 minutes for all service to come up. Now CDM can leverage the updated remote directory value to run the scripts on a remote server.