Veritas InfoScale™ for Kubernetes Environments 8.0.200 - Linux
- Overview
- System requirements
- Preparing to install InfoScale on Containers
- Installing Veritas InfoScale on OpenShift
- Introduction
- Prerequisites
- Additional Prerequisites for Azure RedHat OpenShift (ARO)
- Considerations for configuring cluster or adding nodes to an existing cluster
- Installing InfoScale on a system with Internet connectivity
- Installing InfoScale in an air gapped system
- Installing Veritas InfoScale on Kubernetes
- Introduction
- Prerequisites
- Installing the Special Resource Operator
- Tagging the InfoScale images on Kubernetes
- Applying licenses
- Tech Preview: Installing InfoScale on an Azure Kubernetes Service(AKS) cluster
- Considerations for configuring cluster or adding nodes to an existing cluster
- Installing InfoScale on Kubernetes
- Installing InfoScale by using the plugin
- Undeploying and uninstalling InfoScale
- Configuring KMS-based Encryption on an OpenShift cluster
- Configuring KMS-based Encryption on a Kubernetes cluster
- InfoScale CSI deployment in Container environment
- CSI plugin deployment
- Raw block volume support
- Static provisioning
- Dynamic provisioning
- Resizing Persistent Volumes (CSI volume expansion)
- Snapshot provisioning (Creating volume snapshots)
- Managing InfoScale volume snapshots with Velero
- Volume cloning
- Using InfoScale with non-root containers
- Using InfoScale in SELinux environments
- CSI Drivers
- Creating CSI Objects for OpenShift
- Installing and configuring InfoScale DR Manager on OpenShift
- Installing and configuring InfoScale DR Manager on Kubernetes
- Disaster Recovery scenarios
- Configuring InfoScale
- Administering InfoScale on Containers
- Upgrading InfoScale
- Troubleshooting
Collecting logs by using SORT Data Collector
For troubleshooting purposes, logs are most necessary, By using SORT Data Collector(sortdc), you can collect node-level and cluster-level logs and InfoScale-specific logs at the node and cluster level as well.
Collecting logs on OpenShift
- Run
sortdcon the bastion node. With a single instance running on a bastion node, all node-level and cluster-level logs are collected. - Run the following command on the bastion node to export cluster's
admin.conftoKUBECONFIG.export KUBECONFIG=/etc/kubernetes/admin.conf
- Run the
sortdctool. OpenShift node-level and cluster-level logs are saved at the location you specify while running the tool.
Collecting logs on Kubernetes
- Run
sortdcon the master node. With a single instance running on a master node, all node-level and cluster-level logs are collected. - Run the following command on the master node to export cluster's
admin.conftoKUBECONFIG.export KUBECONFIG=/etc/kubernetes/admin.conf
- Run the
sortdctool. Kubernetes node-level and cluster-level logs are saved at the location you specify while running the tool.
Run the following commands on every InfoScale Driver Container in the InfoScale cluster for InfoScale-specific node-level and cluster-level logs.
- Login to the InfoScale Driver Container.
On an OpenShift cluster, run the following command on the bastion node.
oc exec -it <InfoScaleDriverContainerPodName> -n infoscale-vtas -- /bin/bash
On a Kubernetes cluster, run the following command on the master node.
kubectl exec -it <InfoScaleDriverContainerPodName> -n infoscale-vtas -- /bin/bash
- Run the following commands to create and enable the swap file.
dd if=/dev/zero of=/var/log/swapfile bs=1024 count=1000000; mkswap /var/log/swapfile; swapon /var/log/swapfile;
- Run /opt/VRTSspt/VRTSexplorer/VRTSexplorer.
Specify log location as
/var/log/to collect explorer files at the host-mounted path. - Run the following commands to disable and remove the swapfile.
swapoff /var/log/swapfile; rm -f /var/log/swapfile;
Note:
Ensure that you run these commands on all InfoScale Driver Containers.