Loading...

Adding Application-Consistent Protection for Kubernetes

For Kubernetes, to achieve application-consistent protection, use pre-process script files and post-process script files. You can use pre-scripts and post-scripts for application-consistent protection on both Windows and Linux access nodes.

Pre-scripts and post-scripts are batch files or shell scripts that you can run before or after certain job phases. Both pre-script and post-script must be provided for application-consistent protection.

Use the following steps to create and execute pre-process script files and post-process script files:

  1. In the software_installation_directory, create a folder named kscripts.
    • On a Windows access node, create a folder named kscripts in the software_installation_directory\ContentStore\Base folder.
    • On a Linux access node, create a directory named kscripts in the software_installation_directory/Base directory.
  2. Add the pre-process script file or the post-process script file with the following naming convention:
    • namespace.application_name.prescript
    • namespace.application_name.postscript

      where application_name is the name of the discovered application.

    To execute th scripts for all namespaces that have the specific application, add the script files with the following naming convention:

    • $.application_name.prescript
    • $.application_name.postscript

      where application_name is the name of the discovered application.

Examples

Pre-process script for MySQL:

# cat /opt/commvault/Base/kscripts/mydatabase.myapplication.prescript
mysql -h host_name -p password -P port_number -u user_name
flush tables with read lock;

Post-process script for MySQL:

# cat /opt/commvault/Base/kscripts/mydatabase.myapplication.postscript
mysql -h host_name -p password -P port_number -u user_name
unlock tables;
exit;

Last modified: 3/10/2021 5:50:05 PM